| 词条 | Lion Air Flight 610 | ||||||||||||||||||||
| 释义 |
| occurrence_type = Accident | name = Lion Air Flight 610 | image = File:B737M8-PK-LQP.jpg | alt = | caption =PK-LQP, the aircraft involved in the accident, photographed in September 2018 | date = {{start-date|29 October 2018|29 October 2018}} | summary = Crashed shortly after take-off; under investigation | site = Java Sea, off the north coast of Karawang Regency, Indonesia | coordinates = {{coord|5|46|15|S|107|07|16|E|type:event|display=inline,title}} | fatalities = 189 | injuries = | aircraft_type = Boeing 737 MAX 8 | tail_number = PK-LQP | aircraft_name = | operator = Lion Air | passengers = 181 | crew = 8 | missing = | survivors = 0 | origin = Soekarno–Hatta International Airport Jakarta, Indonesia | stopover = | stopover0 = | last_stopover = | destination = Depati Amir Airport Pangkal Pinang, Indonesia | IATA = JT610 | ICAO = LNI610 | callsign = LION INTER 610 | occupants = 189 }}{{OSM Location map | coord = {{coord|-4.3|105.7}} | zoom = 6 | float = right | width = 235 | height = 230 | caption = Crash site of Lion Air Flight 610 relative to its origin and destination | title = | scalemark = 120 | shape1 = image | mark1 = MUTCD I-5.svg | mark-size1 = 16 | label1 = Soekarno–Hatta Intl AP | mark-coord1 = {{coord|-6.127400|106.652140}} | label-pos1 = left | label-size1 = 14 |label-color1 = green | label-offset-x1= | label-offset-y1= |mark-title1=Soekarno–Hatta Intl AP |mark-image1= |mark-description1= | mark-coord2={{coord|-2.157669|106.137726}} | label2 = Depati Amir Airport | label-pos2=left | label-offset-x2= | label-offset-y2= |mark-title2=Depati Amir Airport |mark-image2= |mark-description2= |mark3 = Red pog.svg |mark-size3 = 10 |mark-coord3={{coord|-5.813333|107.126944}} |label3 = Crash site |label-color3 = red |label-pos3=top |label-offset-x3= |label-offset-y3= |mark-title3=Crash site |mark-image3= |mark-description3= }} Lion Air Flight 610 was a scheduled domestic flight operated by the Indonesian airline Lion Air from Soekarno–Hatta International Airport in Jakarta to Depati Amir Airport in Pangkal Pinang. On 29 October 2018, the Boeing 737 MAX 8 operating the route crashed into the Java Sea 12 minutes after takeoff, killing all 189 passengers and crew. It was the first major accident involving the new Boeing 737 MAX series aircraft, introduced in 2017, and the deadliest involving a 737, surpassing Air India Express Flight 812 in 2010. It is the deadliest accident in Lion Air's 18-year history, surpassing the 2004 crash in Surakarta that killed 25, and the second deadliest aircraft accident in Indonesia behind Garuda Indonesia Flight 152. The Indonesian government deployed a search and rescue operation which found debris early in the morning and recovered human remains from a {{convert|150|nmi|km|adj=mid}} wide area. The first victim was identified two days after the crash. The flight data recorder was located on 1 November and recovered for analysis. One member of the volunteer rescue team died during recovery operations. The cockpit voice recorder was found on 14 January 2019.[1] Preliminary investigations revealed serious flight control problems that traumatized passengers and crew on the aircraft's previous flight, as well as signs of Angle of attack (AoA) sensor and other instrument failures on that and previous flights, tied to a potential design flaw involving the Maneuvering Characteristics Augmentation System (MCAS) of the 737 MAX series. As a result, the United States Federal Aviation Administration and Boeing issued warnings and training advisories to all operators of the 737 MAX series to avoid letting the MCAS cause an abrupt dive similar to the Lion Air flight. These advisories were not fully implemented, however, and the design issues are suspected to be involved in the Ethiopian Airlines Flight 302 crash on 10 March 2019, leading to the worldwide grounding of all 371 operating 737 MAX aircraft. AircraftThe aircraft involved was a Boeing 737 MAX 8, registration PK-LQP, line number 7058, powered by two CFM International LEAP engines.[2] The aircraft was leased from China Minsheng Investment Group (CMIG) Aviation Capital and delivered new to Lion Air on 13 August 2018.[3][4] At the time of the accident, the aircraft had flown about 800 hours in service.[5] This was the first accident involving a 737 MAX since the type's entry into service on 22 May 2017,[6] and the deadliest accident involving a Boeing 737.[7] Passengers and crewThere were 189 people on board the aircraft: 181 passengers (178 adults, 1 child and 2 infants), as well as six cabin crew and two pilots.[8] Officials confirmed that all 189 passengers and crew on board had been killed.[9][10] CrewThe flight's captain was an Indian national, who had flown with the airline for more than seven years and had about 6,000 hours of flight experience; and the co-pilot was an Indonesian who had about 5,000 hours of flight experience. The six flight attendants were also Indonesian.[11] Passengers
Twenty Ministry of Finance employees,[12] 10 Audit Board of Indonesia employees,[12] two auditors from the {{ill|Finance and Development Inspection Agency|id|Badan Pengawasan Keuangan dan Pembangunan}},[13] three Ministry of Energy and Mineral Resources employees,[14] three public attorneys,[15] three Indonesian National Police officers,[16] six Bangka Belitung Regional People's Representative Council members,[17] and three judges of Indonesia's High Court and National Court,[18] for a total of 38 civil servants, three police officers and 10 state officials, were among the passengers. There were two confirmed foreigners among those on board: the pilot from India and an Italian citizen, former professional cyclist Andrea Manfredi.[19][20] Flight details and accidentThe aircraft took off from Jakarta on 29 October 2018 at 6:20 a.m. local time (28 October 2018, 11:20 p.m. UTC) and was scheduled to arrive at Depati Amir Airport in Pangkal Pinang at 7:20 a.m.[21] It took off in a westward direction before circling around to a northeast heading, which it held until crashing offshore northeast of Jakarta in waters estimated to be up to {{convert|35|m|ft}} deep.[23][22] The flight crew had requested clearance to return to the Jakarta airport {{convert|19|nmi|mi km}} into the flight.[23][24] The accident site was located {{convert|34|km|mi nmi}} off the coast of the island of Java.[25] Communication between air traffic control (ATC) and Flight 610 was suddenly lost at 6:33 a.m.[26] ATC immediately informed authorities about the incident and the Indonesian National Search and Rescue Agency deployed three ships and a helicopter to the area.[27] At 7:30 a.m., the agency received reports that Flight 610 had crashed a few kilometres from an offshore oil platform.[28] Workers on the platform reportedly saw the aircraft crash with a steep nose-down angle.[29] Boats from the platform were immediately deployed and debris from the crashed aircraft was found shortly after.[30] ResponseOn 29 October, Indonesia's Transportation Ministry ordered all of the country's airlines to conduct emergency inspections on their 737 MAX 8 aircraft. The ministry would also launch a special audit on Lion Air to see if there were any problems with its management system.[31] The Transportation Ministry announced that all Indonesian Boeing 737 MAX 8 aircraft were airworthy and were allowed to resume normal operations on 31 October.[32] A Basarnas spokesperson confirmed to reporters that the aircraft had crashed;[33] Muhammad Syaugi, head of Basarnas, later confirmed that there had been casualties, without specifying a number.[23] In response to the crash, the Indonesian Transportation Ministry set up crisis centres in Jakarta[34] and Pangkal Pinang.[35][36] Lion Air also offered free flights for the families of the victims to Jakarta. On 30 October, more than 90 relatives were flown to Jakarta for the identification of the victims.[37] CEO of Lion Air Edward Sirait stated that accommodation had been provided for the relatives, and later added that relatives should go to Halim Perdanakusuma International Airport for further information.[38] The Indonesian National Police announced that a trauma healing team would be provided for the relatives of the victims.[39] Indonesia's People's Representative Council announced on 29 October that they would examine the Standard Operating Procedure of Lion Air and the airworthiness of the aircraft. They would also examine the health history of the crew of Flight 610.[40] The Speaker of the People's Representative Council, Bambang Soesatyo, later asked the government to enforce stricter rules for the aviation industry and to audit every airliner in the country.[41] On 1 November, Indonesian Minister of Transportation Budi Karya Sumadi announced that the government would evaluate every low-cost carrier in Indonesia.[42] As 20 of the passengers were employees of the Indonesian Ministry of Finance, Sri Mulyani, the Indonesian Finance Minister, immediately visited the Indonesian Search and Rescue Agency's office in Jakarta, seeking coordination and further information.[43] She later announced that every employee of her ministry should wear a black ribbon for a week to commemorate the victims.[44] Posthumous awards would be given to the 20 victims and scholarships would be given to the victims' children.[45] Minister of Health Nila F Moeloek[46] and Minister of Transportation Budi Karya Sumadi visited the relatives of the victims. Indonesian President Joko Widodo, who was attending a conference in Bali during the crash,[47] visited the recovery efforts at the Port of Tanjung Priok the next day.[48] The Australian Department of Foreign Affairs and Trade announced that its staff would be banned from flying on Lion Air, as well as its subsidiary airlines Batik Air and Wings Air, until the cause of the accident was known.[49] The Indonesian Minister of Transportation, Budi Karya Sumadi, later stated that his ministry would hold talks with the Australian government about the warning.[50][51] The government-owned social insurance company Jasa Raharja announced that the victims' families would each receive 50 million rupiah (US${{To USD|50000000|IDN|round=yes}}) in compensation.[52] In the immediate aftermath of the crash, the Indonesian media were warned by Indonesian Broadcasting Commission for their unethical coverage of the crash. Some media were accused of pushing the family members to answer unethical questions.[53] Chairman of Indonesia's Alliance of Independent Journalists (AJI), Abdul Manan, stated that images of debris were broadcast repeatedly and inappropriately. This, in turn, traumatized relatives of the victims. In response, some Indonesians voiced their anger and disappointment on social media.[54] On 31 October, Transportation Minister Budi Karya Sumadi temporarily suspended Lion Air's technical director Muhammad Arif from his duties based on the crash investigation. Budi said the ministry had also suspended an unspecified number of Lion Air technicians who had cleared the aircraft for its final flight.[55] Recovery operationsIndonesia's National Search and Rescue Agency (Basarnas) launched a search and rescue operation, with assistance from the Indonesian Air Force,[56] the Indonesian Navy,[57] and the Republic of Singapore Navy. Basarnas dispatched about 150 people in boats and helicopters to the site of the accident.[58] Civilian vessels also responded to the reports of a downed aircraft, and the crew of a tugboat reported to authorities in Tanjung Priok that they had witnessed an aircraft crash at 6:45 a.m. and located debris in the water at 7:15 a.m.[21][33] The Indonesian Agency for Assessment and Application for Technology deployed the research ship Baruna Jaya, which had been previously used in the search for Adam Air Flight 574 and Indonesia AirAsia Flight 8501.[59] Officials from the Indonesian National Search and Rescue Agency announced that the search and rescue operation would be conducted for seven days and be extended by three days if needed. A command centre was set up in Tanjung Priok.[60] On 29 October, authorities said that all on board were presumed dead and that the first human remains had been recovered.[61] Divers had located fragments of the aircraft's fuselage and assorted debris, but had yet to find the onboard flight recorders.[61] An official from the Indonesian National Armed Forces suggested that most of the victims were still inside the fuselage, as in the days following the crash rescue personnel only managed to recover a small number of body parts.[62] Officials stated that bad visibility and strong sea current hampered the search and rescue effort.[63] On the same day, the Indonesian National Search and Rescue Agency published the area of the search and rescue operation. It was divided into two main areas. The first was a {{convert|62|nmi}}{{clarify|reason=How large, is it 62 nautical miles wide, 62 miles long, 62 miles square or 62 square miles?|date=November 2018}} underwater search area while the second was a "visual search" area, {{convert|124|nmi}} wide.[64] On 30 October, the search area was divided into 13 sectors. The search area was widened to {{convert|150|nmi}},{{clarify|reason=Is this an area 150 miles wide or an area of 150 square miles?|date=November 2018}}[65] reaching as far as Indramayu to the east. Approximately 850 personnel from the Indonesian National Search and Rescue Agency, Indonesian National Armed Forces and volunteers participated in the operation.[66] At least 13 bodies were retrieved from the crash site.[67] Indonesian officials confirmed that faint pings had been heard in the search area.[68] On 31 October, it was reported that acoustic "pings" had been detected, no further than {{convert|3|km}} from the group of eight current search points, which were possibly from one or both of the underwater locator beacons (ULBs) attached to the aircraft's flight recorders.[69] The first victim was identified on 31 October.[70] At the time, more than a dozen body parts had been found by authorities. Some of the parts had drifted more than {{Convert|5|km|}} in the sea current. Police also reported that 152 DNA samples had been collected from the victims' relatives.[70] Hundreds of pieces of the aircraft had also been recovered; all of them were transported to Tanjung Priok, Jakarta.[71] Authorities stated that the search area for dead bodies and debris would be focused in the sea off Karawang Regency, a coastal area of Java close to the crash site, as analysis showed that the sea currents in the area would bring debris to the south. A command centre was set up in Tanjung Pakis, Karawang to oversee the salvage effort.[71] On the same day, authorities widened the search area from {{convert|10|nmi}} to {{convert|15|nmi}}. In all, 39 ships (including 4 equipped with sonar) and 50 divers were deployed to the search area.[72] The Indonesian National Police announced that 651 personnel had joined and assisted in the search and rescue operation.[73] Officials stated that the operation, starting from 31 October, would focus on finding the fuselage of the aircraft and the flight recorders.[74] The joint search and rescue team announced on 31 October that at least three objects, one of which was suspected to be one of the aircraft's wings, were found in the search area.[75] Officials confirmed that "pings" from the aircraft's ULBs were also heard near the area.[76] On 1 November, searchers announced that they had found Flight 610's flight data recorder (FDR), which was located at a depth of {{convert|32|m}}. The cockpit voice recorder (CVR), however, was reported as not yet found.[77] According to a transport safety official, quoted by Reuters news agency, authorities did not initially know for certain whether the "crash survivable memory unit" was from the flight data recorder or cockpit voice recorder, as portions of it were missing.[78] Haryo Satmiko, deputy chief of Indonesia's National Transportation Safety Committee (NTSC), the body investigating the crash, told journalists that the device's poor condition was evidence of the "extraordinary impact" of the crash, which had separated the memory unit from its housing.[79][80] Despite the damage, investigators were able to recover data from the aircraft's most recent 19 flights spanning 69 hours, and planned to begin analysis on 5 November.[80] On 2 November, the joint search and rescue team deployed more than 850 personnel and 45 vessels to the crash site. The aerial search area was widened to {{convert|190|nmi}} and the "underwater search area" was widened to {{convert|270|nmi}}.[81] Joint search and rescue team announced that some engine parts were found in the search area.[82] One of the aircraft's landing gears was recovered in the afternoon.[83] Meanwhile, the Disaster Victim Identification team stated that at least 250 body parts had been recovered from the crash site.[84] On 3 November, it was reported that a volunteer Indonesian rescue diver had died during the search, on the afternoon of 2 November.[85] It is believed he died from decompression sickness.[86] A second landing gear and both of the aircraft's engines were recovered by search and rescue personnel, and the main body of the aircraft had been located. The main wreckage of the aircraft was located {{convert|7.5|mile}}{{clarify|reason=Are these miles or nautical miles?|date=November 2018}} from the coast of Tanjung Pakis and was about {{convert|200|metre|yd}} from the location where the FDR was discovered. Divers were immediately dispatched to the area. Faint "pings" from the ULB attached to the aircraft's CVR were also heard.[87][88][89][87] On 4 November, nearly 1,400 personnel, including 175 divers, were dispatched to the crash site. 69 ships, 5 helicopters and 30 ambulances were also dispatched.[90] The Head of the Indonesian National Search and Rescue Agency Muhammad Syaugi announced that the search and rescue operation would be extended for another three days.[91] On 10 November the NSRA ended its search for victims,[92] but on 22 November were continuing to search intensively for the CVR.[93] On 23 November, investigators concluded the victim identification process. Out of 189 people on board, 125 (89 men and 36 women) were identified, including the two foreigners. Another 64 bodies are still unaccounted for.[94] On 14 December, it was reported that Lion Air had paid US$2.8 million for a second attempt to search for the CVR, with a specialized boat being brought in to assist in the search, expected to last 10 days.[95] The attempt began on 20 December,[96] but ended on 3 January 2019 without success. The NTSC announced plans to launch their own search, and were negotiating with the Indonesian Navy to borrow one of their ships.[97] On 8 January 2019, they announced they would be resuming the search for the CVR (using their own funding).[98] The CVR was found by the Indonesian Navy near the crash site, at a depth of 30 m but covered by 8-meter thick mud,[99] on 14 January 2019, more than two months after the accident.[1][100] InvestigationInternational assistanceA Boeing technician and engineering team, and a team from the US National Transportation Safety Board arrived on 31 October to help with the investigation being conducted by the NTSC. Personnel from the US Federal Aviation Administration (FAA) and engine manufacturer GE Aviation were also sent to Indonesia. A team from Singapore, that had already arrived on the night of 29 October, was to provide assistance in recovering the aircraft's flight recorders. The Australian Transport Safety Bureau sent two of its personnel to assist with the downloading process of the FDR.[101] Previous flight problemsThe aircraft was used on a flight from Ngurah Rai International Airport, Bali to Soekarno-Hatta International Airport, Jakarta the night before the crash. Detailed reports from that flight revealed that the aircraft had suffered a serious incident, which left many passengers traumatized. Passengers in the cabin reported heavy shaking and a smell of burnt rubber inside the cabin. At one point, the aircraft had dropped more than {{convert|200|ft}} in a few seconds.[102] The seat belt sign was never turned off from takeoff to landing. A recording of air traffic control communications indicated that the pilot had called a "pan-pan",[103] the second highest alert level, below only a Mayday call. However, the crew later decided to cancel the pan-pan and continue the flight to Jakarta.[104] The aircraft's maintenance logbook revealed that the aircraft suffered an unspecified navigation failure on the captain's side, while the First Officer's side was reported to be in good condition.[105] Passengers recounted that the aircraft had suffered an engine problem and were told not to board it as engineers tried to fix the problem. While the aircraft was en route to Jakarta, it had problems maintaining a constant altitude, with passengers stating that it was like "a roller-coaster ride".[106] The chief executive officer of Lion Air, Edward Sirait, said the aircraft had a "technical issue" on Sunday night, but this had been addressed in accordance with maintenance manuals issued by the manufacturer. Engineers had declared that the aircraft was ready for takeoff on the morning of the accident.[107][108] A later report claimed that a third pilot was on the flight to Jakarta and told the crew to cut power to the stabilizer trim motors which fixed the problem. This method is a standard memory item in the 737 checklist.[109] Subsequently, the National Transportation Safety Committee confirmed the presence of an off-duty Boeing 737 MAX 8 qualified pilot in the cockpit but did not confirm the role of the pilot in fixing the problem, and denied that there was any recording of the previous flight in the CVR of Lion Air Flight 610.[110] Early assessment of potential factorsIndonesian aviation expert Gerry Soejatman speculated that the pitot tubes, used in the airspeed indication system, may have played a role in the crash. They have contributed to previous similar crashes.[111][112] The Indonesian Meteorology, Climatology, and Geophysical Agency (BMKG) reported that the weather was clear around the time of the crash, with winds at {{Convert|5|knots|}} from the northwest. Visibility was good with no cumulonimbus cloud Flight abnormalitiesAviation experts noted that there were some abnormalities in the altitude and the airspeed of Flight 610. Just three minutes into the flight, the captain asked the controller for permission to return to the airport as there were flight control problems. [115] About eight minutes into the flight, data transmitted automatically by the aircraft showed it had descended to about {{Convert|5000|ft|}} but its altitude continued to fluctuate. The mean value of the airspeed data transmitted by Flight 610 was around {{Convert|300|knots|km/h mph}}, which was considered by experts to be unusual, as typically aircraft at altitudes lower than {{Convert|10000|ft|}} are restricted to an airspeed of {{Convert|250|knots|km/h mph}}. Ten minutes into the flight, the data recorded the aircraft dropping by more than {{Convert|3000|ft|}}. The last recorded altitude of the aircraft was {{Convert|2500|ft|}}.[116][117] November findingsOn 5 November, the NTSC announced that Flight 610 was still intact when it crashed into the sea at high speed, citing the relatively small size of the pieces of debris. The impact was so powerful that the strongest part of the aircraft was obliterated.[118] The NTSC also stated that the engines of Flight 610 were still running when it crashed into the sea,[119] indicated by the high RPM. Further examination of the aircraft's instruments revealed that one of the aircraft's airspeed indicators had malfunctioned for its last four flights, including the flight to Denpasar.[120] On 7 November, the NTSC confirmed that there had been problems with Flight 610's angle of attack (AoA) sensors. Thinking that it would fix the problem, the engineers in Bali then replaced one of the aircraft's AoA sensors, but the problem persisted on the penultimate flight, from Denpasar to Jakarta. Just minutes after takeoff, the aircraft abruptly dived. The crew of that flight, however, had managed to control the aircraft and decided to fly at a lower than normal altitude. They then managed to land the aircraft safely and recorded a twenty-degree difference between the readings of the left AoA sensor and the right sensor.[121] NTSC chief Soerjanto Tjahjono told the press that future reporting or actions, enacted to prevent similar problems on similar aircraft, would be decided by Boeing and US aviation authorities.[122] On 28 November, Indonesia investigators said the Lion Air jet was not airworthy on the flight before the crash. Several relatives of the crash victims have already filed lawsuits against Boeing.[123] Preliminary reportOn 28 November, the Indonesian National Transportation Safety Committee (NTSC) released its preliminary accident investigation report.[124] After airspeed and altitude problems, an AoA sensor was replaced and tested two days earlier on the accident aircraft.[136] Erroneous airspeed indications were still present on the subsequent flight on 28 October, which experienced automatic nose down trim.[136] The runaway stabilizer non-normal checklist was run, the electric stabilizer trim was turned off, and the flight continued with manual trim; the issues were reported after landing.[136] Shortly after takeoff on 29 October, issues involving altitude and airspeed continued due to erroneous AoA data and commanded automatic nose-down trim via the Maneuvering Characteristics Augmentation System (MCAS).[136] The flight crew repeatedly commanded nose-up trim over the final ten minutes of the flight.[136] The report does not state whether the runaway stabilizer trim procedure was run or whether the electric stabilizer trim switches were cut out on the accident flight.[125] Leeham News, which principally covers Airbus, Boeing, Bombardier and Embraer issues,[126] reported that the crew did not have a clear knowledge that trim runaway checklist will disengage MCAS.[127]Boeing pointed to the successful troubleshooting conducted on 28 October as evidence that the MCAS did not change runaway stabilizer procedures,[128] and emphasised the longstanding existence of procedures to cancel MCAS nose-down commands.[145] CVROn 21 January 2019, the NTSC announced that it would not release transcript from the CVR found a week earlier until the final report was released, expected to be between August and September 2019.[129] However, following the Ethiopian Airlines Flight 302 crash on 10 March 2019 which meant the data from the CVR of the Lion Air Flight 610 were shared among the investigators, media citing anonymous sources reported that CVR recorded the pilots mentioning several problems, trying to climb, and checking the quick reference handbook for a solution.[130] NTSC denied these claims but stated the pilots began to panic at the end of the flight.[131] AftermathReactionPotential cause |
||||||||||||||||||||
| 随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识，基本涵盖了大多数领域的百科知识，是一部内容自由、开放的电子版国际百科全书。