The Indonesian government's search and rescue found debris and human remains soon after from a 280 km (150 nmi) wide area. The first victim was identified two days after the crash. The flight data recorder (FDR) was found on 1 November and recovered for analysis. One member of the volunteer rescue team died during recovery operations.
Preliminary investigations revealed serious flight-control problems that traumatized passengers and crew on the aircraft's previous flight, as well as signs of failures of an angle-of-attack (AoA) sensor and other instruments on that and previous flights, tied to a design flaw involving the maneuvering characteristics augmentation system (MCAS) of the MAX series. As a result, the United States Federal Aviation Administration and Boeing issued warnings and training advisories to all operators of the MAX series to avoid letting the MCAS cause similar problems. These advisories were not fully implemented, however, and the design issues were suspected to have also been involved in the Ethiopian Airlines Flight 302 crash on 10 March 2019, prompting a worldwide grounding of all 737 MAX aircraft.
The accident was investigated by the Indonesian National Transportation Safety Committee (NTSC), which published its final report in October 2019. The NTSC found nine factors that contributed to the accident, without assigning precedence amongst them.[1]: 215
Aircraft and crew
The 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. It made its first flight on 30 July 2018[3] and was delivered new to Lion Air on 13 August 2018.[4][5] At the time of the accident, the aircraft had flown about 800 hours in service.[6] This was the first accident involving a 737 MAX since the type's entry into service on 22 May 2017,[7] and the deadliest accident involving a Boeing 737.[8]
The flight's cockpit crew included Captain Bhavye Suneja (31), an Indian national,[9] who had flown with the airline for more than seven years and had about 6,028 hours of flight experience (including 5,176 hours on the Boeing 737) and received his training in California;[10][11][1] and Indonesian Co-pilot Harvino (41),[12][b] who had 5,174 hours of flight experience, 4,286 of them on the Boeing 737. The six flight attendants were also Indonesians.[13]
Flight details and accident
Map showing flightpath of Lion Air Flight 610
The aircraft took off from Jakarta on 29 October 2018 at 6:20 am local time (28 October 2018, 11:20 pm UTC) and was scheduled to arrive at Depati Amir Airport in Pangkal Pinang at 7:20 am.[14] 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
as much as 35 m (115 ft) deep.[15][16] The flight crew had requested clearance to return to the Jakarta airport 35 km (19 nmi) into the flight.[17][18] The accident site was located 34 km (18 nmi) off the coast of the island of Java.[19]
Communication between air traffic control (ATC) and Flight 610 was suddenly lost at 6:33 am.[20] ATC informed the National Search and Rescue Agency, which deployed three ships and a helicopter to the area.[21] At 7:30 am, the agency received reports that Flight 610 had crashed a few kilometres from an offshore oil platform.[22] Workers on the platform reportedly saw the aircraft crash with a steep nose-down angle.[23] Boats from the platform were immediately deployed and debris from the crashed aircraft was found shortly after.[24]
Victims
On board the aircraft were 189 people: 181 passengers (178 adults, one child, and two infants), as well as six cabin crew and two pilots.[25] All 189 passengers and crew on board were killed.[26][27]
Of the 189 occupants, 187 were from Indonesia, one passenger was from Italy, and the captain was from India.[citation needed]
On 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 also launched a special audit on Lion Air to see if any problems existed with its management system.[37] The Transportation Ministry announced that all Indonesian Boeing 737 MAX 8 aircraft were airworthy and were allowed to resume normal operations on 31 October.[38]
A Basarnas spokesperson confirmed to reporters that the aircraft had crashed;[39] Muhammad Syaugi, head of Basarnas, later confirmed that casualties had occurred, without specifying a number.[15]
The Transportation Ministry set up crisis centres in Jakarta[40] and Pangkal Pinang.[41][42] Lion Air 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.[43] 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.[44] The Indonesian National Police announced that a trauma-healing team would be provided for the relatives of the victims.[45]
Indonesia's People's Representative Council announced on 29 October that they would examine the standard operating procedures of Lion Air and the airworthiness of the aircraft. They would also examine the health history of the crew of Flight 610.[46][needs update] 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.[47] On 1 November, Indonesian Minister of Transportation Budi Karya Sumadi announced that the government would evaluate every low-cost carrier in Indonesia.[48]
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.[49] She later announced that Finance Ministry employees should wear a black ribbon for a week to commemorate the victims.[50] Posthumous awards were issued to the 20 victims and scholarships to their children.[51]
Minister of Health Nila F Moeloek[52] 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,[53] visited the recovery efforts at the Port of Tanjung Priok the next day.[54]
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.[55] The Indonesian Minister of Transportation, Budi Karya Sumadi, later stated that his ministry would hold talks with the Australian government about the warning.[56][57][needs update]
The government-owned social insurance company Jasa Raharja announced that the victims' families would each receive 50 million rupiah (US$3495) in compensation.[58]
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.[59] 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.[60]
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.[61]
Recovery operations
Aerial view of Lion Air Flight 610 crash site
Indonesia's National Search and Rescue Agency (Basarnas) launched a search-and-rescue operation, with assistance from the Indonesian Air Force,[62] the Indonesian Navy,[63] and the Republic of Singapore Navy. Basarnas dispatched about 150 people in boats and helicopters to the site of the accident.[15] 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 am and located debris in the water at 7:15 am.[14][39] 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.[64]
Officials from Basarnas 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.[65]
On 29 October, the director of operations for Basarnas said that all on board were presumed dead and that the first human remains had been recovered.[66] Divers had located fragments of the aircraft's fuselage and assorted debris, but had yet to find the onboard flight recorders.[66] Air Marshal Muhammad Syaugi, head of Basarnas, 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.[67] Poor underwater visibility and strong sea current hampered the search and rescue effort.[68]
On the same day, Basarnas published the area of the search-and-rescue operation, divided into two main areas. The first was a 115 km (62 nmi) long underwater search area, while the second was a "visual search" area, 230 km (124 nmi) wide.[69]
On 30 October, the search area was divided into 13 sectors. The search area was widened to 280 km (150 nmi),[70] reaching as far as Indramayu to the east. Approximately 850 personnel from the National Search and Rescue Agency, National Armed Forces and volunteers participated in the operation.[71] At least 13 bodies were retrieved from the crash site.[72] Indonesian officials confirmed that faint pings had been heard in the search area.[73]
On 31 October, acoustic "pings" were reported to have been detected, no further than 3 km (1.6 nmi) 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.[74]
The first victim was identified on 31 October.[75] At the time, more than a dozen body parts had been found by authorities. Some of the parts had drifted more than 5 km (2.7 nmi) in the sea current. Police also reported that 152 DNA samples had been collected from the victims' relatives.[75] Hundreds of pieces of the aircraft had also been recovered; all of them were transported to Tanjung Priok, Jakarta.[76] 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.[76]
On the same day, authorities widened the search area from 19 to 28 km (10 to 15 nmi). In all, 39 ships (including four equipped with sonar) and 50 divers were deployed to the search area.[77] The National Police announced that 651 personnel had joined and assisted in the search-and-rescue operation.[78] Officials stated that the operation, starting from 31 October, would focus on finding the fuselage of the aircraft and the flight recorders.[79]
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.[80] Officials confirmed that "pings" from the aircraft's ULBs were also heard near the area.[81]
On 1 November, searchers recovered Flight 610's flight data recorder (FDR), which was located at a depth of 32 m (105 ft).[1]: 240 The cockpit voice recorder (CVR) was reported as not yet found.[82][83] Haryo Satmiko, deputy chief of National Transportation Safety Committee (NTSC) (Indonesian: Komite Nasional Keselamatan Transportasi), 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.[84][85] 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.[85]
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 350 km (190 nmi) and the "underwater search area" was widened to 500 km (270 nmi).[86] Joint search-and-rescue team announced that some engine parts were found in the search area.[87] One of the aircraft's landing gear was recovered in the afternoon.[88] Meanwhile, the Disaster Victim Identification team stated that at least 250 body parts had been recovered from the crash site.[89]
A volunteer rescue diver died during the search on the afternoon of 2 November, likely from decompression sickness.[90][91]
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 was located, 13.9 km (7.5 nmi) from the coast of Tanjung Pakis and about 200 m (220 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 cockpit voice recorder were also heard.[92][93][94]
On 4 November, nearly 1,400 personnel, including 175 divers, were dispatched to the crash site; 69 ships, five helicopters and thirty ambulances were also dispatched.[95] The Head of the National Search and Rescue Agency Muhammad Syaugi announced that the search-and-rescue operation would be extended for another three days.[96]
On 10 November, Basarnas ended its search for victims,[97] but on 22 November, were continuing to search intensively for the CVR.[98]
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 were unaccounted for.[99]
Lion Air paid US$2.8 million for a second attempt to search for the CVR between 19 and 29 December, using the offshore supply vessel MPV Everest.[1]: 243 [100][101] Divers detected a signal from an underwater locator beacon coming from underneath the aircraft wreckage and were able to fix the approximate position of the CVR, but did not succeed in recovering it.[1]: 243
The NTSC funded a further underwater search using Indonesian Navy vessel KRI Spica, which started on 8 January 2019 and continued until the CVR was recovered on 14 January.[1]: 244 [102][103] The cockpit voice recorder was found at a depth of 30 m (98 ft) covered by mud that was 8 m (26 ft) thick.[104][105][106]
Investigation
International assistance
The Lion Air aircraft flight recorders were retrieved with assistance from Singapore's Transport Safety Investigation Bureau, which sent on 29 October 2018, three specialists and an underwater locator beacon detector to help recover the devices.[107] The Australian Transport Safety Bureau sent two of its personnel to assist the Indonesian NTSC with the downloading process of the FDR.
In August 2019, an early draft of the NTSC report was leaked.[108] The report in circulation blamed design and oversight lapses playing a key role in the Lion Air Flight 610 crash and also identified pilot and maintenance errors as causal factors among a hundred elements of the crash chronology, without ranking them.[109][110] Lion Air expressed objections because NTSC's draft, according to a source who requested anonymity, attributed 25 lapses to Lion Air out of 41 lapses found.[111] Also, doubts arose about the acceptability of some photographs used in the investigation, as they could be fabricated evidence of repair to the doomed Lion Air MAX. The company opposed raising an issue about the photographs in the final accident report.[112]
A 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.[113] 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.[114]
Previous flight problems
The 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 61 m (200 ft) in a few seconds.[115] The seat-belt sign was never turned off from takeoff to landing. A recording of ATC communications indicated that the pilot had called a "pan-pan."[116] The crew later decided to cancel the pan-pan and continue the flight to Jakarta.[115]
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.[117]
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."[118] 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.[119][120] Information later emerged that a third pilot was on the flight to Jakarta and told the crew to cut electrical power to the stabilizer trim motors. This method is a standard memory item in the 737 checklist and, on this flight, it fixed the problem.[121] 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 this person in fixing the problem, and denied that any recording existed of the previous flight in the CVR of Lion Air Flight 610.[122]
Early assessment of potential factors
The erratic nature of the flight path led Indonesian aviation expert Gerry Soejatman to speculate that the pitot tubes, used in the airspeed indication system, may have played a role in the crash; they had contributed to previous crashes.[123][124]
The Indonesian Meteorology, Climatology, and Geophysical Agency reported that the weather was clear around the time of the crash, with winds at 9.3 km/h (5 kn) from the northwest. Visibility was good with no cumulonimbus clouds.[125] Police Hospital Chief Musyafak said that an examination of the body parts indicated that explosion or fire on board the aircraft was unlikely.[126]
Flight abnormalities
Flight JT610 altitude and speed
Aviation experts noted some abnormalities were seen 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 the aircraft had flight-control problems.[127] About eight minutes into the flight, data transmitted automatically by the aircraft showed it had descended to about 1,500 m (5,000 ft), but its altitude continued to fluctuate. The mean value of the airspeed data transmitted by Flight 610 was around 300 kn (560 km/h; 350 mph), which was considered by experts to be unusual, as typically aircraft at altitudes lower than 3,000 m (10,000 ft) are restricted to an airspeed of 250 kn (460 km/h; 290 mph). Ten minutes into the flight, the data recorded the aircraft dropping by more than 910 m (3,000 ft). The last recorded altitude of the aircraft was 760 m (2,500 ft).[128][129]
November 2018 findings
On 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.[130] The NTSC also stated that the engines of Flight 610 were still running when it crashed into the sea,[131] indicated by high engine speed. 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.[132]
On 7 November, the NTSC confirmed that been problems has occurred with Flight 610's 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 20° difference between the readings of the left and the right AoA sensors.[133] 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 U.S. aviation authorities.[134]
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 filed lawsuits against Boeing.[135]
Preliminary report
On 28 November, the Indonesian NTSC released its preliminary accident investigation report.[136] After airspeed and altitude problems, an AoA sensor was replaced and tested two days earlier on the accident aircraft.[137] Erroneous airspeed indications were still present on the subsequent flight on 28 October, which experienced automatic nose-down trim.[137] 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.[137] 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 MCAS.[137] The flight crew repeatedly commanded nose-up trim over the final ten minutes of the flight.[137] The preliminary report did not state whether the runaway stabilizer trim procedure was run or whether the electric stabilizer trim switches were cut out on the accident flight.[137]
Leeham News, which principally covers Airbus, Boeing, Bombardier, and Embraer issues,[138] reported that the crew did not have a clear knowledge that trim runaway checklist will disengage MCAS.[139]
Boeing pointed to the successful troubleshooting conducted on 28 October as evidence that the MCAS did not change runaway stabilizer procedures,[140] and emphasised the longstanding existence of procedures to cancel MCAS nose-down commands.[141]
Cockpit voice recorder
The CVR was found on 14 January 2019.[105] On 21 January 2019, the NTSC announced that it would not release transcript from the CVR until the final report was released.[142] Following the Ethiopian Airlines Flight 302 crash on 10 March 2019, however, the data from the CVR of the Lion Air Flight 610 were shared among the investigators; media citing anonymous sources reported that the CVR recorded the pilots mentioning several problems, trying to climb, and checking the quick-reference handbook for a solution.[143] NTSC denied these claims, but stated the pilots began to panic at the end of the flight.[144]
Final report
The NTSC released its final report into the accident on 25 October 2019.[145] The report listed nine "Contributing Factors":
Contributing factors [are] define[d] as actions, omissions, events, conditions, or a combination thereof, which, if eliminated, avoided or absent, would have reduced the probability of the accident or incident occurring, or mitigated the severity of the consequences of the accident or incident. The presentation is based on chronological order and not to show the degree of contribution.
1. During the design and certification of the Boeing 737-8 (MAX), assumptions were made about flight-crew response to malfunctions that, even though consistent with current industry guidelines, turned out to be incorrect.
2. Based on the incorrect assumptions about flight-crew response and an incomplete review of associated multiple flight deck effects, MCAS's reliance on a single sensor was deemed appropriate and met all certification requirements.
3. MCAS was designed to rely on a single AoA sensor, making it vulnerable to erroneous input from that sensor.
4. The absence of guidance on MCAS or more detailed use of trim in the flight manuals and in-flight crew training, made it more difficult for flight crews to properly respond to uncommanded MCAS.
5. The AoA DISAGREE alert was not correctly enabled during Boeing 737-8 (MAX) development. As a result, it did not appear during flight with the miscalibrated AoA sensor, could not be documented by the flight crew, and was therefore not available to help maintenance identify the miscalibrated AoA sensor.
6. The replacement AoA sensor that was installed on the accident aircraft had been miscalibrated during an earlier repair. This miscalibration was not detected during the repair.
7. The investigation could not determine that the installation test of the AoA sensor was performed properly. The miscalibration was not detected.
8. Lack of documentation in the aircraft flight and maintenance log about the continuous stick shaker and use of the runaway stabilizer NNC meant that information was not available to the maintenance crew in Jakarta, nor was it available to the accident crew, making it more difficult for each to take the appropriate actions.
9. The multiple alerts, repetitive MCAS activations, and distractions related to numerous ATC communications were not able to be effectively managed. This was caused by the difficulty of the situation and performance in manual handling, NNC execution, and flight-crew communication, leading to ineffective CRM application and workload management. These performances had previously been identified during training and reappeared during the accident flight.
The report stated that 31 pages were missing from the airplane's logbook. The NTSC recommended that Lion Air improve the duration and content of its safety management system training, including the identification of equipment hazards, such as the continuous stick shaker and trim runaway, which the pilot on the previous flight did not report. The Indonesian Directorate General of Civil Aviation was urged to improve its oversight of airlines and maintenance organisations.[146][147]
Aftermath
Reaction
Potential cause
The CFM LEAP engines used on the 737 MAX have a higher bypass ratio and have a larger nacelle than the engines of previous Boeing 737 models, requiring them to be placed further forward and upwards on the wing compared to previous models. This destabilises the aircraft pitch at high AoAs due to a change in aerodynamics.
The MCAS was designed to mitigate this aerodynamics issue in the 737 MAX series, automatically commanding the aircraft to pitch downwards if its AoA was too high, but out of two AoA sensors on the aircraft, MCAS would only read data from a single sensor.[148] Former Boeing engineers expressed the opinion that a nose-down command triggered by a sensor single point of failure is a design flaw if the crew is not prepared, and the FAA was evaluating a fix of the possible flaw and investigating whether the pilots' transition training is adequate.[149] A malfunction in the captain-side AoA sensor, as occurred on the flight, caused the MCAS system to continuously trim the aircraft nose-down, causing the plane to crash.[150]
FAA warnings
On 7 November, on the basis of preliminary information gathered in the investigation of the Lion Air accident, the US FAA issued an emergency airworthiness directive requiring that amended operating limitations and procedures relating to erroneous data from an AoA sensor be inserted into the aircraft flight manual of each 737 MAX aircraft,[151][152] and urged all airlines operating Boeing 737 MAX 8s to heed the warnings.[153]
On 25 October 2019, after the release of the Final Report by NTSC, the FAA revoked the repair certification of Florida-based Xtra Aerospace LLC, which fixed an AoA sensor suspected of contributing to the crash.[154]
On 15 November, the Air Line Pilots Association in the United States, representing 61,000 pilots, urged the FAA and NTSB to ensure pilots receive all relevant information addressing a "potential, significant aviation system safety deficiency."[159] The association's United Airlines branch, in line with its management, disagrees as the 737 pilot manual includes a standard procedure to shut down the flight-control behavior, and dismissed the MCAS implication in the accident as "speculation" based on the Boeing safety-warning bulletin and the follow-on FAA airworthiness directive.[160]
Boeing's defense
In an internal message on 19 November 2018, Boeing CEO Dennis Muilenburg defended the flight-crew operations manual as describing the relevant function of MCAS.[161] On 20 November, Boeing was to hold a conference call with 737 MAX operators to detail the new MCAS not present in the Next Generation models.[162]
The conference call was cancelled later, to be replaced by a series of regional calls to allow more questions.[163]
On 25 October 2019, after the release of the final investigation report by NTSC, Boeing President and CEO Dennis Muilenburg responded:
"We are addressing the KNKT's [NTSC's] safety recommendations, and taking actions to enhance the safety of the 737 MAX to prevent the flight control conditions that occurred in this accident from ever happening again. Safety is an enduring value for everyone at Boeing and the safety of the flying public, our customers, and the crews aboard our airplanes is always our top priority. We value our long-standing partnership with Lion Air and we look forward to continuing to work together in the future."[164]
In January 2020, newly released unredacted internal messages within Boeing employees reveal that they have mocked Lion Air with profanity, belittling the airline for requesting additional simulator training for their Boeing 737 MAX pilots in 2017 citing that Lion's sister airline (Malindo Air) have already operated the type.[165][166] Lion Air co-founder and former CEO Rusdi Kirana, currently the Indonesian ambassador to Malaysia, considered cancelling Lion Air's outstanding 190 Boeing aircraft orders – worth some $22 billion at list prices – over what he viewed as an attempt by Boeing to blame Lion Air for the crash.[141]
Legal action
On 31 December 2018, the family of the first officer filed a lawsuit against Boeing, claiming negligence. The lawsuit also claimed that the aircraft's sensors provided inaccurate flight data, causing its antistall system to improperly engage, as well as Boeing not providing proper instructions to pilots about how to handle the situation.[167]
In March 2019, victims' families reported irregularities, saying that Lion Air pressured them into signing away their rights to seek legal recourse for undercompensation.[168][169]
In December 2020, a federal judge in Chicago froze the assets of attorney Thomas Girardi, as "finding that he misappropriated at least US$2 million in client funds that were due to the families of those killed in the crash".[170][171] He was disbarred from legal practice and ordered return US$2.3 million in funds.[172]
On 10 March 2019, another 737 MAX 8, operated by Ethiopian Airlines (registration ET-AVJ), crashed shortly after takeoff from Addis Ababa; all 157 people on board perished. This raised further concerns about the safety of the 737 MAX and culminated in all 737 MAX aircraft being grounded worldwide for 21 months.[173]
^Pheroze L. Vincent (18 October 2019). "Java plane crash shatters Delhi family". telegraphindia.com. Retrieved 12 April 2022. Bhavye passed out of Ahlcon Public School in 2005 before learning to fly at Bel-Air International in San Carlos, California.
