Maneuvering Characteristics Augmentation System

The Maneuvering Characteristics Augmentation System (MCAS) is a flight control law (software mode) developed by Boeing which became notorious for its role in two fatal accidents of the 737 MAX before the aircraft was grounded worldwide. First deployed on the Boeing KC-46 Air Force tanker, MCAS adjusts the horizontal stabilizer trim to push the nose down when the aircraft is operating in manual flight, with flaps up, at an elevated angle of attack (AoA), so the pilot will not inadvertently pull the airplane up too steeply, potentially causing a stall. However, in both cases, MCAS activated by erroneous indications from its sensors.

Movable horizontal stabilizer on an Embraer ERJ-170

During aircraft certification, Boeing removed a description of MCAS in the MAX flight manuals, leaving pilots unaware of the system when the airplane entered service.[1] On November 10, 2018, twelve days after Lion Air Flight 610 crashed, Boeing publicly revealed MCAS in a discussion with airline operators and other aviation interests. [2] Yet, a recovery procedure highlighted by Boeing and the FAA failed to prevent the crash of Ethiopian Airlines Flight 302, which led to the global grounding of all 737 MAX aircraft pending investigations and software fixes.

In April 2019, Boeing admitted that MCAS played a role in both accidents and asserted that MCAS is not an anti-stall system. On the Boeing 737 MAX, MCAS was intended to mimic pitching behavior similar to aircraft in the previous generation of the series, the Boeing 737 NG. The investigations identified numerous defects with associated systems, including an AoA disagree message that should have prevented MCAS activation. The Wall Street Journal reported that Boeing failed to share information about that issue for "about a year" before the Lion Air crash in Indonesia.[3]


MCAS on the 737 MAXEdit

 
The MAX uses an adjustable stabilizer, moved by a jackscrew, to provide the required pitch trim forces. Generic stabilizer illustrated.

The Maneuvering Characteristics Augmentation System (MCAS) flight control law was implemented on the 737 MAX to mitigate the aircraft's tendency to pitch up because of the aerodynamic effect of its larger, heavier, and more powerful CFM LEAP-1B engines and nacelles.[4] The stated goal of MCAS, according to Boeing, was to provide consistent aircraft handling characteristics at elevated angles of attack in certain unusual flight conditions only and hence make the 737 MAX perform similarly to its immediate predecessor, the 737NG.[5]

737-200 JT8D engine with original cowling design
737-800 (Next Generation) CFM56 engine with ovoid inlet
737 MAX 9 CFM LEAP-1B engine with 787-derived engine chevrons

MCAS's role in the accidentsEdit

 
The tracking data of Lion Air Flight 610 from Flightradar24
 
The vertical airspeeds of the Boeing 737 MAX 8s involved in the JT 610 and ET 302 crashes

Investigators determined that MCAS was triggered by falsely high angle of attack (AoA) inputs, as if the plane had pitched up excessively. On both flights, shortly after takeoff, MCAS repeatedly actuated the horizontal stabilizer trim motor to push down the airplane nose.[6][7][8][9] Satellite data for the flights, ET 302 and JT 610, showed that the planes struggled to gain altitude.[10] Pilots reported difficulty controlling the airplane and asked to return to the airport.[11][12]

On March 11, 2019, after China had grounded the aircraft,[13] Boeing published some details of new system requirements for the MCAS software and for the cockpit displays, which it began implementing in the wake of the prior accident five months earlier:[6]

  • If the two AoA sensors disagree with the flaps retracted, MCAS will not activate and an indicator will alert the pilots.
  • If MCAS is activated in non-normal conditions, it will only "provide one input for each elevated AoA event."
  • Flight crew will be able to counteract MCAS by pulling back on the column.

On March 27, Daniel Elwell, the acting administrator of the FAA, testified before the Senate Committee on Commerce, Science, and Transportation, saying that on January 21, "Boeing submitted a proposed MCAS software enhancement to the FAA for certification. ... the FAA has tested this enhancement to the 737 MAX flight control system in both the simulator and the aircraft. The testing, which was conducted by FAA flight test engineers and flight test pilots, included aerodynamic stall situations and recovery procedures."[14] After a series of delays, the updated MCAS software was released to the FAA in May 2019.[15][16] On May 16, Boeing announced that the completed software update was awaiting approval from the FAA.[17][18] The flight software underwent 360 hours of testing on 207 flights.[19] Boeing also updated existing crew procedures.[6] The implementation of MCAS has been found to disrupt autopilot operations.[20]

On April 4, 2019 Boeing publicly acknowledged that MCAS played a role in both accidents.[21]

Purpose of MCAS and the stabilizer trim systemEdit

The FAA and Boeing both refuted media reports describing MCAS as an anti-stall system, which Boeing asserted it is distinctly not.[22][23][24] The aircraft had to perform well in a low-speed stall test.[25] The Joint Authorities Technical Review "considers that the STS/MCAS and elevator feel shift (EFS) functions could be considered as stall identification systems or stall protection systems, depending on the natural (unaugmented) stall characteristics of the aircraft".

The JATR said, "MCAS used the stabilizer to change the column force feel, not trim the aircraft. This is a case of using the control surface in a new way that the regulations never accounted for and should have required an issue paper for further analysis by the FAA. If the FAA technical staff had been fully aware of the details of the MCAS function, the JATR team believes the agency likely would have required an issue paper for using the stabilizer in a way that it had not previously been used; this [might have] identified the potential for the stabilizer to overpower the elevator."[26]

DescriptionEdit

 
an angle of attack (AOA) sensor

BackgroundEdit

The Maneuvering Characteristics Augmentation System (MCAS) is a flight control law[27] built into the Boeing 737 MAX's flight control computer, designed to help the aircraft emulate the handling characteristics of the earlier Boeing 737 Next Generation. According to an international Civil Aviation Authorities team review (JATR) commissioned by the FAA, MCAS may be a stall identification or protection system, depending on the natural (unaugmented) stall characteristics of the aircraft.[26][28][29] Boeing considered MCAS part of the flight control system, and elected to not describe it in the flight manual or in training materials, based on the fundamental design philosophy of retaining commonality with the 737NG. Minimizing the functional differences between the Boeing 737 MAX and Next Generation aircraft variants allowed both variants to share the same type rating. Thus, airlines can save money by employing and training one pool of pilots to fly both variants of the Boeing 737 interchangeably.[30]

When activated, MCAS directly engages the horizontal stabilizer, thus is distinct from an anti-stall device, such as stick pusher, which physically moves the pilot's control column forward and engages the airplane's elevators when the airplane is approaching a stall.

Boeing's former CEO Dennis Muilenburg said "[MCAS] has been reported or described as an anti-stall system, which it is not. It's a system that's designed to provide handling qualities for the pilot that meet pilot preferences."[31]

The 737 MAX's larger CFM LEAP-1B engines are fitted further forward and higher up than in previous models. The aerodynamic effect of its nacelles contributes to the aircraft's tendency to pitch up at high angles of attack (AOA). The MCAS is intended to compensate in such cases, modeling the pitching behavior of previous models, and meet a certain certification requirement,[32] in order to enhance handling characteristics and thus minimizing the need for significant pilot retraining.[33][34][31]

The software code for the MCAS function and the computer for executing the software are built to Boeing's specifications by Collins Aerospace, formerly Rockwell Collins.[35]

 
The trim wheel and cutoff switches in a previous generation cockpit

As an automated corrective measure, the MCAS was given full authority to bring the aircraft nose down, and could not be overridden by pilot resistance against the control wheel as on previous versions of the 737.[36] Following the Lion Air accident, Boeing issued an Operations Manual Bulletin (OMB)[37] on November 6, 2019 to outline the many indications and effects resulting from erroneous AOA data and provided instructions to turn off the motorized trim system for the remainder of the flight, and trim manually instead. Until Boeing supplemented the manuals[38] and training, pilots were unaware of the existence of MCAS due to its omission from the crew manual and no coverage in training.[36] Boeing first publicly named and revealed the existence of MCAS on the 737 MAX in a message to airline operators and other aviation interests on November 10, 2018, twelve days after the Lion Air crash.[2]

Safety engineering and human factorsEdit

As with any other equipment on board an aircraft, the FAA approves a functional "design assurance level" corresponding to the consequences of a failure, using the SAE International standards ARP4754 and ARP4761. MCAS was designated a "hazardous failure" system. This classification corresponds to failures causing "a large reduction in safety margins" or "serious or fatal injury to a relatively small number of the occupants", but nothing "catastrophic".[39]

The MCAS was designed with the assumption, approved by FAA, that pilots would react to an unexpected activation within three seconds.[40]

MCAS technology readinessEdit

The MCAS design parameters originally envisioned automated corrective actions to be taken in cases of high AoA and G-forces beyond normal flight conditions. Test pilots routinely push aircraft to such extremes, as the FAA requires airplanes to perform as expected. Before the MCAS, test pilot Ray Craig determined the plane did not fly smoothly, in part due to the larger engines. Craig would have preferred an aerodynamic solution, but Boeing decided to implement a control law in software.

According to a news report from the Wall Street Journal, engineers who had worked on the KC-46A Pegasus tanker, which includes an MCAS function, suggested MCAS to the design team.[41]

With the MCAS implemented, new test pilot Ed Wilson said the "MAX wasn’t handling well when nearing stalls at low speeds” and recommended MCAS to apply across a broader range of flight conditions. This required the MCAS to function under normal G-forces and, at stalling speeds, deflect the vertical trim more rapidly and to a greater extent—but now it reads a single AoA sensor, creating a single point of failure that allowed false data to trigger MCAS to pitch the nose downward and force the aircraft into a dive.[42][33] "Inadvertently, the door was now opened to serious system misbehavior during the busy and stressful moments right after takeoff", said Jenkins of The Wall Street Journal.[43]

The FAA did not conduct a safety analysis on the changes. It had already approved the previous version of MCAS, and the agency's rules did not require it to take a second look because the changes did not affect how the plane operated in extreme situations. [44]

The Joint Authorities Technical Review found the technology unprecedented: "If the FAA technical staff had been fully aware of the details of the MCAS function, the JATR team believes the agency likely would have required an issue paper for using the stabilizer in a way that it had not previously been used. MCAS used the stabilizer to change the column force feel, not trim the aircraft. This is a case of using the control surface in a new way that the regulations never accounted for and should have required an issue paper for further analysis by the FAA. If an issue paper had been required, the JATR team believes it likely would have identified the potential for the stabilizer to overpower the elevator."[26]

In November 2019, Jim Marko, a manager of aircraft integration and safety assessment at Transport Canada aviation regulator's National Aircraft Certification Branch questioned the readiness of MCAS. Because new problems kept emerging, he suggested to his peers at FAA, ANAC and EASA to consider the safety benefits of removing MCAS from the MAX.[45]

ScrutinyEdit

 
Altitude and speed of Lion Air Flight 610

The MCAS has been under scrutiny following the fatal crashes of Lion Air Flight 610 and Ethiopian Airlines Flight 302 soon after takeoff. The Boeing 737 MAX global fleet has been grounded by all airlines and operators, and a number of functional issues have been raised.[46][47][48]

The MCAS deflects the horizontal stabilizer four times farther than was stated in the initial safety analysis document.[46] Due to the amount of trim the system applies to the horizontal stabilizer, aerodynamic forces resist pilot control effort to raise the nose. As long as the faulty AOA readings persist, a human pilot "can quickly become exhausted trying to pull the column back".[49] In addition, switches for the horizontal stabilizer trim assist now serve a shared purpose of turning off the MCAS. In simulator sessions, pilots were stunned by the substantial effort needed to manually crank the trim wheel out of its nose down setting.[50][51][52]

Boeing CEO Dennis Muilenburg has stated that there was "no surprise, or gap, or unknown here or something that somehow slipped through a certification process."[53] On April 29, 2019 he stated the design of the aircraft was not flawed and reiterated that it was designed per Boeing's standards.[54] In a May 29 interview with CBS, Boeing admitted that it had botched the software implementation and lamented the poor communications.[55]

On September 26, the National Transportation Safety Board criticized Boeing’s inadequate testing of the 737 MAX, and pointed out that Boeing made erroneous assumptions on pilots’ response to alerts in 737 MAX, triggered by activation of MCAS due to a faulty signal from an angle-of-attack sensor.[56][57]

The Joint Authorities Technical Review (JATR), a team commissioned by the FAA for 737 MAX investigation, concluded that FAA failed to properly review MCAS. Boeing failed to provide adequate and updated technical information regarding the MCAS system to FAA during Boeing 737 Max certification process, and had not carried out a thorough verification by stress-testing of the MCAS system.[29][58]

On October 18, Boeing turned over a discussion from 2016 between two employees which revealed prior issues with the MCAS system.[59]

Boeing's own internal design guidelines related to the 737 MAX's development stated that the system should "not have any objectionable interaction with the piloting of the airplane" and "not interfere with dive recovery".[60] The operation of MCAS violated those.[61]

NTSBEdit

On September 26, 2019, the NTSB released the results of its review of potential lapses in the design and approval of the 737 MAX.[62][63](p1)[64] The NTSB report concludes that assumptions "that Boeing used in its functional hazard assessment of uncommanded MCAS function for the 737 MAX did not adequately consider and account for the impact that multiple flight deck alerts and indications could have on pilots' responses to the hazard". When Boeing induced a stabilizer trim input that simulated the stabilizer moving consistent with the MCAS function, "... the specific failure modes that could lead to unintended MCAS activation (such as an erroneous high AOA input to the MCAS) were not simulated as part of these functional hazard assessment validation tests. As a result, additional flight deck effects (such as IAS DISAGREE and ALT DISAGREE alerts and stick shaker activation) resulting from the same underlying failure (for example, erroneous AOA) were not simulated and were not in the stabilizer trim safety assessment report reviewed by the NTSB."[63][63][65]

The NTSB questioned the long-held industry and FAA practice of assuming the nearly instantaneous responses of highly trained test pilots as opposed to pilots of all levels of experience to verify human factors in aircraft safety.[66] The NTSB expressed concerns that the process used to evaluate the original design needs improvement because that process is still in use to certify current and future aircraft and system designs. The FAA could for example randomly sample pools from the worldwide pilot community to get a more representative assessment of cockpit situations.[67]

Supporting systemsEdit

The updates proposed by Boeing focus mostly on MCAS software.[27] In particular, there have been no public statements regarding reverting the functionality of the stabilizer trim cutout switches to pre-MAX configuration. A veteran software engineer and experienced pilot suggested that software changes may not be enough to counter the 737 MAX's engine placement.[68] Seattle Times notes that while the new software fix Boeing has proposed "will likely prevent this situation recurring, if the preliminary investigation confirms that the Ethiopian pilots did cut off the automatic flight-control system, this is still a nightmarish outcome for Boeing and the FAA. It would suggest the emergency procedure laid out by Boeing and passed along by the FAA after the Lion Air crash is wholly inadequate and failed the Ethiopian flight crew."[69]

Boeing and the FAA decided that the AoA display and an AoA disagree light, which signals if the sensors give different readings, were not critical features for safe operation.[70] Boeing charged extra for the addition of the AoA indicator to the primary display.[71][72] In November 2017, Boeing engineers discovered that the standard AoA disagree light cannot independently function without the optional AoA indicator software, a problem affecting 80% of the global fleet which had not ordered the option.[73][74] The software remedy was scheduled to coincide with the roll out of the elongated 737 MAX 10 in 2020, only to be accelerated by the Lion Air accident. Furthermore, the problem had not been disclosed to the FAA until 13 months after the fact. Although it is unclear whether the indicator could have changed the outcome for the ill-fated flights, American Airlines said the disagree indicator provided the assurance in continued operations of the airplane. "As it turned out, that wasn't true." [75]

Runaway stabilizer and manual trimEdit

In February 2016, the EASA certified the MAX with the expectation that pilot procedures and training would clearly explain unusual situations in which the seldom used manual trim wheel would be required to trim the plane, i.e. adjust the angle of the nose; however, the original flight manual did not mention those situations.[76] The EASA certification document referred to simulations whereby the electric thumb switches were ineffective to properly trim the MAX under certain conditions. The EASA document said that after flight testing, because the thumb switches could not always control trim on their own, the FAA was concerned by whether the 737 MAX system complied with regulations.[77] The American Airlines flight manual contains a similar notice regarding the thumb switches but does not specify conditions where the manual wheel may be needed.[77]

Boeing's CEO Muilenburg, when asked about the non-disclosure of MCAS, cited the "runaway stabilizer trim" procedure as part of the training manual. He added that Boeing's bulletin pointed to that existing flight procedure. Boeing views the "runaway stabilizer trim" checklist as a memory item for pilots. Mike Sinnett, vice president and general manager for the Boeing New Mid-Market Airplane (NMA) since July 2019, repeatedly described the procedure as a "memory item".[78] However, some airlines view it as an item for the quick reference card.[79] The FAA issued a recommendation about memory items in an Advisory Circular, Standard Operating Procedures and Pilot Monitoring Duties for Flight Deck Crewmembers: "Memory items should be avoided whenever possible. If the procedure must include memory items, they should be clearly identified, emphasized in training, less than three items, and should not contain conditional decision steps."[80]

In November 2018, Boeing told airlines that MCAS could not be overcome by pulling back on the control column to stop a runaway trim as on previous generation 737s.[81] Nevertheless, confusion continued: the safety committee of a major U.S. airline misled its pilots by telling that the MCAS could be overcome by "applying opposite control-column input to activate the column cutout switches".[82] Former pilot and CBS aviation & safety expert Chesley Sullenberger testified, "The logic was that when MCAS was activated, it had to be, and must not be prevented."[83] In October, Sullenberger wrote, "These emergencies did not present as a classic runaway stabilizer problem, but initially as ambiguous unreliable airspeed and altitude situations, masking MCAS."[84]

In a legal complaint against Boeing, the Southwest Airlines Pilot Association states:[85]

An MCAS failure is not like a runaway stabilizer. A runaway stabilizer has continuous un-commanded movement of the tail, whereas MCAS is not continuous and pilots (theoretically) can counter the nose-down movement, after which MCAS would move the aircraft tail down again. Moreover, unlike runaway stabilizer, MCAS disables the control column response that 737 pilots have grown accustomed to and relied upon in earlier generations of 737 aircraft.

In May 2019, The Seattle Times reported that the two stabilizer cutoff switches on the MAX operate differently than on the earlier 737 NG. On previous aircraft, one cutoff switch deactivates the thumb buttons on the control yoke that pilots use to move the horizontal stabilizer; the other cutoff switch disables automatic control (as from autopilot) to move the stabilizer in the tail. On the MAX, both switches do the same thing: they cut off all electric power to the stabilizer, both from the yoke buttons and from an automatic system, like MCAS. With all power to the stabilizer cut, pilots have no choice but to use the mechanical trim wheel in the center console.[86] However, as pilots pull on the 737 controls to raise the nose of the aircraft, aerodynamic forces on the elevator create an opposing force, effectively paralyzing the jackscrew mechanism.[87]> It becomes very difficult for pilots to hand crank the trim wheel.[87] The problem was encountered on earlier 737 versions, and a "roller coaster" emergency technique for handling the flight condition was documented in 1982 for the 737-200 but did not appear in training documentation for later versions (including the MAX).[87]

MCAS circumvention for ferry flightsEdit

During the groundings, special flights to reposition MAX aircraft to storage locations, as per 14 CFR § 21.197, flew at lower altitude and with flaps extended to circumvent MCAS activation, rather than using the recovery procedure after the fact. Such flights required a certain pilot qualification as well as permission from corresponding regulators, and with no other cabin crew or passengers.[88][89]

Horizontal stabilizer actuatorEdit

The horizontal stabilizer is fitted with a conventional elevator for flight control. However it is itself all-moving about a single pivot and can be trimmed to adjust its angle. The trim is actuated via a jackscrew mechanism.

Slippage concernEdit

Sylvain Alarie and Gilles Primeau, experts on the horizontal stabilizers, observed anomalies in the data from the aircraft data recorders: a progressive shift of 0.2 degrees of the horizontal stabilizer, before the crash. "It may not seem like much, but it is an order of magnitude higher than what is normally allowed when designing systems like these", says Gilles Primeau. They say that the movements are easily observable, and disallowed according to Regulation 395A. These anomalies raise fundamental questions about this jack screw, which controls the horizontal stabilizer since the beginning of the 737 models, first certified in 1967.[90]

These slips are particularly visible on flight ET302: "While there is no MCAS command, and no control of the pilots, we see a movement of the jack screw which controls the horizontal stabilizer, we see a slip. And at the very end of the flight, the jack screw starts to slide again with an increase in the speed of the plane and its dive," says Alarie.[90]

Since its original design, the 737 has become 61% heavier, 24% longer, and 40% wider, and its engines twice as powerful. These experts are concerned that the loads on the jack screw have potentially increased since the creation of the 737. By regulations, the controls must be designed for 125% of the foreseeable loads.[90][91] These experts have raised concerns about the motors possibly overheating in April 2019.[92]

Manual trim stiffnessEdit

In the early 1980s a problem was found with the 737-200 model. When the elevator operated to raise or lower the nose, it set up a strong force on the trim jackscrew which opposed any corrective force from the control systems. When attempting to correct an unwanted deflection using the manual trim wheel, exerting enough hand force to overcome the force exerted by the elevator became increasingly difficult as speed and deflection increased and the jack screw effectively jammed in place.[93]

A workaround was developed called the "roller coaster" technique. Counter-intuitively, to correct an excessive deflection causing a dive the pilot first pushes the nose down further, before easing back to gently raise the nose again. During this easing back period, the elevator deflection reduces or even reverses, its force on the jackscrew does likewise and the manual trim eases up. The workaround was included in the pilot's emergency procedures and in the training schedule.[93]

However while the 737 MAX has a similar jackscrew mechanism the "roller coaster" technique has been dropped from the pilot information. During the events leading to the two MAX crashes, the stiffness of the manual trim wheel repeatedly prevented manual trim adjustment to correct the MCAS-induced nose-down pitching. The issue has been brought to the notice of the DoJ criminal inquiry into the 737 MAX crashes.[93]

In simulator tests of Ethiopian Airlines Flight 302 flight scenario, the trim wheel was "impossible" to move when one of the pilots would instinctively pull up from the nosedives. It takes 15 turns to manually trim the aircraft one degree, and up to 40 turns to bring the trim back to neutral from the nose down position caused by MCAS.[94]

Angle of Attack (AoA)Edit

As per Boeing technical description: "the Angle of Attack (AoA) is an aerodynamic parameter that is key to understanding the limits of airplane performance. Recent accidents and incidents have resulted in new flight crew training programs, which in turn have raised interest in AoA in commercial aviation. Awareness of AOA is vitally important as the airplane nears stall."[95] Chesley Sullenberger said AoA indicators might have helped in these two crashes. "It is ironic that most modern aircraft measure (angle of attack) and that information is often used in many aircraft systems, but it is not displayed to pilots. Instead, pilots must infer (angle of attack) from other parameters, deducing it indirectly."[96]

AoA sensorsEdit

Though there are two sensors on the MAX only one of them is used at a time to trigger MCAS activation on the 737 MAX. Any fault in this sensor, perhaps due to physical damage,[83] creates a single point failure: the flight control system lacks any basis for rejecting its input as faulty information.

Reports of a single point of failure were not always acknowledged by Boeing. Addressing American Airlines pilots, Boeing vice-president Mike Sinnett contradicted reports that the MCAS had a single-point failure, because the pilots themselves are the backup. Reporter Useem said in The Atlantic it was "showing both a misunderstanding of the term and a sharp break from Boeing's long-standing practice of having multiple backups for every flight system".[97]

Problems with the AoA sensor had been reported in over 200 incident reports submitted to the FAA; however, Boeing did not flight test a scenario in which it malfunctioned.[98]

The sensors themselves are under scrutiny. Sensors on the Lion air aircraft were supplied by United Technologies' Rosemount Aerospace.[99]

In September 2019, the EASA said it prefers triple-redundant AoA sensors rather than the dual redundancy in Boeing's proposed upgrade to the MAX.[100] Installation of a third sensor could be expensive and take a long time. The change, if mandated, could be extended to thousands of older model 737s in service around the world.[100]

A former professor at Embry-Riddle Aeronautical University, Andrew Kornecki, who is an expert in redundancy systems, said operating with one or two sensors "would be fine if all the pilots were sufficiently trained in how to assess and handle the plane in the event of a problem". But, he would much prefer building the plane with three sensors, as Airbus does.[101]

AoA Disagree alertEdit

In November 2017, after several months of MAX deliveries, Boeing discovered that the AoA Disagree message, which is indicative of potential sensor mismatch on the primary flight display,[102] was unintentionally disabled.[6]

Clint Balog, a professor at Embry-Riddle Aeronautical University, said after the Lion Air crash: "In retrospect, clearly it would have been wise to include the warning as standard equipment and fully inform and train operators on MCAS".[103] According to Bjorn Fehrm, Aeronautical and Economic Analyst at Leeham News and Analysis, "A major contributor to the ultimate loss of JT610 is the missing AoA DISAGREE display on the pilots' displays."[104]

The software depended on the presence of the visual indicator software, a paid option that was not selected by most airlines. [105] For example, Air Canada, American Airlines and Westjet had purchased the disagree alert, while Air Canada and American Airlines also purchased, in addition, the AoA value indicator, and Lion Air had neither.[106][107] Boeing had determined that the defect was not critical to aircraft safety or operation, and an internal safety review board (SRB) corroborated Boeing's prior assessment and its initial plan to update the aircraft in 2020. Boeing did not disclose the defect to the FAA until November 2018, in the wake of the Lion Air crash.[108][109][110][111] Consequently, Southwest had announced to pilots that its entire fleet of MAX 8 aircraft will receive the optional upgrades.[112][113] In March 2019, after the second accident of Ethiopian Airlines Flight 302, a Boeing representative told Inc. magazine, "Customers have been informed that AoA Disagree alert will become a standard feature on the 737 MAX. It can be retrofitted on previously delivered airplanes."[114]

On May 5, 2019, The Wall Street Journal reported that Boeing had known of existing problems with the flight control system a year before the Lion Air accident.[115] Boeing defended that "Neither the angle of attack indicator nor the AoA Disagree alert are necessary for the safe operation of the airplane." Boeing recognized that the defective software was not implemented to their specifications as a "standard, standalone feature." Boeing stated, "...MAX production aircraft will have an activated and operable AoA Disagree alert and an optional angle of attack indicator. All customers with previously delivered MAX airplanes will have the ability to activate the AoA Disagree alert."[109] Boeing CEO Muilenburg said the company's communication about the alert "was not consistent. And that's unacceptable."[116][109]

Visual AoA indicatorEdit

 
The primary flight display of a Boeing 737-800 aircraft with a functional angle of attack display on the upper right; the AoA Disagree alert would appear as a text message.

Boeing published an article in Aero magazine about AoA systems, "Operational use of Angle of Attack on modern commercial jet planes":

The AoA indicator can be used to assist with unreliable airspeed indications as a result of blocked pitot or static ports and may provide additional situation and configuration awareness to the flight crew.[95]

Boeing announced a change in policy in the Frequently Asked Questions in a (FAQ) about the MAX corrective work, "With the software update, customers are not charged for the AoA Disagree feature or their selection of the AoA indicator option."[117]

In 1996, the NTSB issued Safety Recommendation A-96-094.

TO THE FEDERAL AVIATION ADMINISTRATION (FAA): Require that all transport-category aircraft present pilots with angle-of-attack info in a visual format, and that all air carriers train their pilots to use the info to obtain maximum possible airplane climb performance.

The NTSB also stated about another accident in 1997, that "a display of angle of attack on the flight deck would have maintained the flightcrew's awareness of the stall condition and it would have provided direct indication of the pitch attitudes required for recovery throughout the attempted stall recovery sequence." The NTSB also believed that the accident may have been prevented if a direct indication of AoA was presented to the flightcrew (NTSB, 1997)."[118](p29)

Flight computer architectureEdit

In early April 2019, Boeing reported a problem with software affecting flaps and other flight-control hardware, unrelated to MCAS; classified as critical to flight safety, the FAA has ordered Boeing to fix the problem correspondingly.[119] In October 2019, the EASA has suggested to conduct more testing on proposed revisions to flight-control computers due to its concerns about portions of proposed fixes to MCAS.[120] The necessary changes to improve redundancy between the two flight control computers have proved more complex and time-consuming than the fixes for the original MCAS issue, delaying any re-introduction to service beyond the date originally envisaged.[121]

In January 2020, new software issues were discovered, affecting monitoring of the flight computer start-up process and verifying readiness for flight.[122] In April 2020, Boeing identified new risks where the trim system might unintentionally command nose down during flight or prematurely disconnect the autopilot. [123]

Microprocessor stress testingEdit

The MAX systems are integrated in the "e-cab" test flight deck, a simulator built for developing the MAX.[124][125] In June 2019, "in a special Boeing simulator that is designed for engineering reviews,"[126] FAA pilots performed a stress testing scenario – an abnormal condition identified through FMEA after the MCAS update was implemented[127] – for evaluating the effect of a fault in a microprocessor: as expected from the scenario, the horizontal stabilizer pointed the nose downward. Although the test pilot ultimately recovered control, the system was slow to respond to the proper runaway stabilizer checklist steps. Boeing initially classified this as a "major" hazard, and the FAA upgraded it to a much more severe "catastrophic" rating. Boeing stated that the issue can be fixed in software.[128] The software change will not be ready for evaluation until at least September 2019.[129] EASA director Patrick Ky said that retrofitting additional hardware is an option to be considered.[20]

The test scenario simulated an event toggling five bits in the flight control computer. The bits represent status flags such as whether MCAS is active, or whether the tail trim motor is energized. Engineers were able to simulate single event upsets and artificially induce MCAS activation by manipulating these signals. Such a fault occurs when memory bits change from 0 to 1 or vice versa, which is something that can be caused by cosmic rays striking the microprocessor.[130]

The failure scenario was known before the MAX entered service in 2017: it had been assessed in a safety analysis when the plane was certified. Boeing had concluded that pilots could perform a procedure to shut off the motor driving the stabilizer to overcome the nose-down movement.[131] The scenario also affects 737NG aircraft, though it presents less risk than on the MAX. On the NG, moving the yoke counters any uncommanded stabilizer input, but this function is bypassed on the MAX to avoid negating the purpose of MCAS.[132] Boeing also said that it agreed with additional requirements that the FAA required it to fulfill, and added that it was working toward resolving the safety risk. It will not offer the MAX for certification until all requirements have been satisfied.[128]

Early news reports were inaccurate in attributing the problem to an 80286[133] microprocessor overwhelmed with data, though as of April 2020 the concern remains that the MCAS software is overloading the 737 MAX's computers.[134]

Computer redundancyEdit

As of 2019, the two flight control computers of Boeing 737 never cross-checked each other's operations; i.e., each was a single non-redundant channel. This lack of robustness existed since the early implementation and persisted for decades.[130] The updated flight control system will use both flight control computers and compare their outputs. This switch to a fail-safe two-channel redundant system, with each computer using an independent set of sensors, is a radical change from the architecture used on 737s since the introduction on the older model 737–300 in the 1980s. Up to the MAX in its prior-to-grounding-version, the system alternates between computers after each flight.[130] The two computers' architecture allowed switching in-flight if the operating computer failed, thus increasing availability. In the revised architecture, Boeing required the two computers to monitor each other so that each one can vet the other.[121]

Trim system malfunction indicatorEdit

In January 2020, during flight testing, Boeing discovered a problem with an indicator light; the defect was traced to the "redesign of the two flight computers that control the 737 MAX to make them more resilient to failure". The indicator, which signals a problem with the trim system, can remain on longer than intended by design.[135][136]

ReferencesEdit

  1. ^ Laris, Michael (June 19, 2019). "Changes to flawed Boeing 737 Max were kept from pilots, DeFazio says". The Washington Post. Retrieved 29 February 2020.
  2. ^ a b Hradecky, Simon (January 14, 2019). "Crash: Lion B38M near Jakarta on Oct 29th 2018, aircraft lost height and crashed into Java Sea, wrong AoA data". The Aviation Herald. Retrieved 2 March 2020.
  3. ^ Andy Pasztor; Andrew Tangel; Alison Sider (May 6, 2019). "Boeing Knew of Problem for a Year". Wall Street Journal. p. A1.
  4. ^ "Boeing's automatic trim for the 737 MAX was not disclosed to the Pilots". Leeham News and Analysis. 2018-11-14.
  5. ^ "Your 737 MAX Questions. Answered: 5. What is MCAS?". Boeing.
  6. ^ a b c d "737 MAX software update". Boeing.
  7. ^ "Boeing flies first 737 MAX 7 with MCAS software update". saemobilus.sae.org. Retrieved 2019-06-06.
  8. ^ "The Boeing 737 MAX: Is the problem with the plane or the pilots?". Intelligent Aerospace. 2019-03-12. Retrieved 2019-07-03.
  9. ^ "Change to 737 MAX controls may have imperiled planes". Reuters. Retrieved 2019-07-03.
  10. ^ Levin, Alan. "Clue Linking Mysterious Boeing 737 Max Disasters Came From Space". Bloomberg News. Retrieved June 6, 2019.
  11. ^ Lazo, Luz; Laris, Michael; Aratani, Lori; Paletta, Damian (March 13, 2019). "FAA's emergency order grounding Boeing jets came after the agency identified similarities between crashes in Ethiopia, Indonesia". The Washington Post. Retrieved March 13, 2019.
  12. ^ Beech, Hannah; Suhartono, Muktita (March 20, 2019). "Confusion, Then Prayer, in Cockpit of Doomed Lion Air Jet". The New York Times. Retrieved March 21, 2019.
  13. ^ Gates, Dominic (March 18, 2019). "Flawed analysis, failed oversight: How Boeing, FAA certified the suspect 737 MAX flight control system". The Seattle Times. Retrieved March 19, 2019.
  14. ^ "The State of Airline Safety: Federal Oversight of Commercial Aviation". U.S. Department of Transportation (DOT). March 27, 2019. Retrieved July 27, 2019. On January 21, 2019, Boeing submitted a proposed MCAS software enhancement to the FAA for certification. To date, the FAA has tested this enhancement to the 737 MAX flight control system in both the simulator and the aircraft. The testing, which was conducted by FAA flight test engineers and flight test pilots, included aerodynamic stall situations and recovery procedures. The FAA's ongoing review of this software installation and training is an agency priority, as will be the roll-out of any software, training, or other measures to operators of the 737 MAX.
  15. ^ Gates, Dominic (2019-04-01). "Boeing's software fix for 737 MAX still weeks away from delivery to FAA". The Seattle Times. Retrieved 2019-04-02.
  16. ^ Corfield, Gareth (March 19, 2019). "Boeing big cheese repeats pledge of 737 Max software updates following fatal crashes". The Register. Retrieved 2019-04-02.
  17. ^ Rappard, Anna-Maja; Wallace, Gregory. "Boeing says it has completed 737 Max software fix". CNN. Retrieved 2019-05-17.
  18. ^ MacMillan, Douglas (May 16, 2019). "Boeing says 737 Max update is being held up by FAA questions". The Washington Post. Retrieved May 19, 2019.
  19. ^ Josephs, Leslie (2019-05-16). "Boeing says it has completed a software update for 737 Max anti-stall system linked to fatal crashes". CNBC. Retrieved 2019-05-27.
  20. ^ a b "Boeing 737 Max's Autopilot Has Problem, European Regulators Find". Bloomberg News. 2019-07-05. Retrieved 2019-07-06.
  21. ^ Gregg, Aaron (April 4, 2019). "Boeing CEO apologizes for lives lost and acknowledges role of company's flight-control system in two crashes". The Washington Post.
  22. ^ "Congress holds fiery hearings on Boeing 737 Max 8 approval". CBS News. Retrieved 2019-06-04.
  23. ^ Broderick, Sean; Norris, Guy; Warwick, Graham (March 20, 2019). "The Boeing 737 MAX MCAS Explained". Aviation Week & Space Technology.
  24. ^ Ostrower, Jon (November 13, 2018). "What is the Boeing 737 Max Maneuvering Characteristics Augmentation System". The Air Current. Retrieved March 14, 2019.
  25. ^ "14 CFR § 25.203 - Stall characteristics". LII / Legal Information Institute. Retrieved 2019-07-02.
  26. ^ a b c Hart (2019). Boeing 737 MAX Flight Control System : Observations, Findings, and Recommendations (PDF). FAA.
  27. ^ a b "737 MAX SOFTWARE UPDATE". Boeing.
  28. ^ "FAA Updates on Boeing 737 MAX". www.faa.gov. Retrieved 2019-10-19.
  29. ^ a b "FAA failed to properly review 737 MAX jet anti-stall system: JATR findings". Reuters. 2019-10-11. Retrieved 2019-10-11.
  30. ^ Warwick, Graham (Mar 20, 2019). "The Boeing 737 MAX MCAS Explained". Aviation Week. Retrieved 2019-06-04.
  31. ^ a b Zhang, Benjamin (29 April 2019). "Boeing's CEO explains why the company didn't tell 737 Max pilots about the software system that contributed to 2 fatal crashes". Business Insider.
  32. ^ "14 CFR § 25.203 - Stall characteristics". LII / Legal Information Institute. Retrieved 2019-07-02.
  33. ^ a b Ostrower, Jon (November 13, 2018). "What is the Boeing 737 Max Maneuvering Characteristics Augmentation System". The Air Current. Retrieved March 14, 2019.
  34. ^ Bazley, Tarek (March 11, 2019). "Control system under scrutiny after Ethiopian Airlines crash". Al Jazeera.
  35. ^ "Boeing's 737 Max design contains fingerprints of hundreds of suppliers". Washington Post. Retrieved 2019-06-04.
  36. ^ a b "My Testimony Today Before the House Subcommittee on Aviation". Sully Sullenberger. 2019-06-19. Retrieved 2019-06-20.
  37. ^ "Boeing Statement on Operations Manual Bulletin". Boeing. November 6, 2018. Retrieved 2 July 2019.
  38. ^ "FAA Issues Emergency AD Against Boeing 737 Max 8". Flying. Retrieved 2019-07-02.
  39. ^ Campbell, Darryl (2019-05-02). "The many human errors that brought down the Boeing 737 Max". The Verge. Retrieved 2019-06-13.
  40. ^ "The inside story of MCAS: How Boeing's 737 MAX system gained power and lost safeguards". The Seattle Times. 2019-06-22. Retrieved 2019-06-24.
  41. ^ Tangel, Alison Sider and Andrew. "WSJ News Exclusive | Before 737 MAX, Boeing's Flight-Control System Included Key Safeguards". WSJ. Retrieved 2019-09-30.
  42. ^ Baker, Mike; Gates, Dominic (March 26, 2019). "Lack of redundancies on Boeing 737 MAX system baffles some involved in developing the jet". The Seattle Times.
  43. ^ Jenkins, Holman W. jr. (2019-11-05). "Boeing vs. Technological Chaos". The Wall Street Journal. Retrieved 2019-11-09.
  44. ^ Nicas, Jack; Kitroeff, Natalie; Gelles, David; Glanz, James (2019-06-01). "Boeing Built Deadly Assumptions Into 737 Max, Blind to a Late Design Change". The New York Times. ISSN 0362-4331. Retrieved 2019-06-07.
  45. ^ "Transport Canada safety official urges removal of MCAS from 737 Max". The Air Current. 2019-11-23. Retrieved 2019-11-24.
  46. ^ a b Gates, Dominic (March 17, 2019). "Flawed analysis, failed oversight: How Boeing and FAA certified the suspect 737 MAX flight control system". The Seattle Times.
  47. ^ Fehrm, Bjorn (2019-04-05). "Bjorn's Corner: ET302 crash report, the first analysis". Leeham News and Analysis.
  48. ^ Gates, Dominic (October 29, 2019). "Live coverage: Boeing CEO Dennis Muilenburg testifies to Congress about 737 MAX". The Seattle Times.
  49. ^ Travis, Gregory (April 18, 2019). "How the Boeing 737 Max Disaster Looks to a Software Developer". IEEE Spectrum. Archived from the original on April 24, 2019.
  50. ^ Bjorn, Fehrm (2019-04-03). "ET302 used the Cut-Out switches to stop MCAS". Leeham News and Analysis.
  51. ^ Mike Baker and Dominic Gates (May 10, 2019). "Boeing altered key switches in 737 MAX cockpit, limiting ability to shut off MCAS". The Seattle Times.
  52. ^ Sean Broderick (May 10, 2019). "Ethiopian MAX Crash Simulator Scenario Stuns Pilots". Aviation Week Network.
  53. ^ Daniel McCoy (Apr 24, 2019). "Boeing CEO: Nothing slipped through in original 737 MAX certification". Wichita Business Journal.
  54. ^ Dominic Gates (Apr 29, 2019). "Facing sharp questions, Boeing CEO refuses to admit flaws in 737 MAX design". Seattle Times.
  55. ^ May 29, CBS News; 2019; Pm, 6:50. "Boeing CEO says he would put his family in a 737 Max "without any hesitation"". www.cbsnews.com. Retrieved 2019-06-12.CS1 maint: numeric names: authors list (link)
  56. ^ Kitroeff, Natalie (2019-09-26). "Boeing Underestimated Cockpit Chaos on 737 Max, N.T.S.B. Says". The New York Times. ISSN 0362-4331. Retrieved 2019-09-26.
  57. ^ "Safety Recommendation Report: Assumptions Used in the Safety Assessment Process and the Effects of Multiple Alerts and Indications on Pilot Performance" (PDF). www.ntsb.gov. NTSB. 19 September 2019. Retrieved 2019-09-26. Lay summary.
  58. ^ Gelles, David; Kitroeff, Natalie (2019-10-11). "Review of 737 Max Certification Finds Fault With Boeing and F.A.A." The New York Times. ISSN 0362-4331. Retrieved 2019-10-11.
  59. ^ Laris, Michael (2019-10-18). "Messages show Boeing employees knew in 2016 of problems that turned deadly on the 737 Max". The Washington Post. Retrieved 2019-10-18.
  60. ^ "Hearing before the committee on transportation and infrastructure" (PDF). The boeing 737 MAX: examining the design development and marketing of the aircraft. House of representatives. October 30, 2019.
  61. ^ "After 18-Month Investigation, Chairs DeFazio and Larsen Release Final Committee Report on Boeing 737 MAX" (Press release). House Committee on Transportation and Infrastructure. 2020-09-16.
  62. ^ Kitroeff, Natalie (2019-09-26). "Boeing Underestimated Cockpit Chaos on 737 Max, N.T.S.B. Says". The New York Times. ISSN 0362-4331. Retrieved 2019-09-26.
  63. ^ a b c "Safety Recommendation Report: Assumptions Used in the Safety Assessment Process and the Effects of Multiple Alerts and Indications on Pilot Performance" (PDF). NTSB. September 19, 2019. Retrieved 2019-09-26. Lay summary.  This article incorporates public domain material from websites or documents of the National Transportation Safety Board.
  64. ^ "NTSB Issues 7 Safety Recommendations to FAA related to Ongoing Lion Air, Ethiopian Airlines Crash Investigations". NTSB. Retrieved 2019-09-30.
  65. ^ Hill, Andrew (October 6, 2019). "Boeing report highlights human factors no company should ignore". Financial Times.
  66. ^ Pasztor, Andy (September 26, 2019). "Plane Tests Must Use Average Pilots, NTSB Says After 737 MAX Crashes". The Wall Street Journal. Retrieved 2019-09-27.
  67. ^ "Boeing Failed to Predict That Slew of 737 Max Warning Alarms Would Confuse Pilots, Investigators Say". Time. Retrieved 2019-09-27.
  68. ^ George Leopold (March 27, 2019). "Software Won't Fix Boeing's 'Faulty' Airframe". EE Times.
  69. ^ "Why Boeing's emergency directions may have failed to save 737 MAX". The Seattle Times. 2019-04-03. Retrieved 2019-06-03.
  70. ^ Freed, Jamie; Johnson, Eric (November 30, 2018). "Optional warning light could have aided Lion Air engineers before crash: experts". Reuters.
  71. ^ Newburger, Emma (March 21, 2019). "Crashed jets reportedly lacked key safety features because Boeing charged extra for them". CNBC. Retrieved March 26, 2019.
  72. ^ Tabucho, Hiroko; Gelles, David (March 21, 2019). "Doomed Boeing Jets Lacked 2 Safety Features That Company Sold Only as Extras". The New York Times. Retrieved March 21, 2019.
  73. ^ Gelles, David; Kitroeff, Natalie (2019-05-05). "Boeing Believed a 737 Max Warning Light Was Standard. It Wasn't". The New York Times. ISSN 0362-4331. Retrieved 2019-05-11.
  74. ^ "FAA considered grounding some Boeing 737 Max planes last year: source". news.yahoo.com. Retrieved 2019-05-11.
  75. ^ Koenig, David; Krisher, Tom (2019-06-07). "Boeing wanted to wait 3 years to fix safety alert on 737 Max". AP NEWS. Retrieved 2019-06-11.
  76. ^ "Explanatory Note to TCDS IM.A.120 – Boeing 737" (PDF). European Union Aviation Safety Agency (EASA). May 24, 2019.
  77. ^ a b "Regulators knew before crashes that 737 MAX trim control was confusing in some conditions: document". Reuters. Retrieved 2019-09-17.
  78. ^ Gates, Dominic (2019-04-03). "Why Boeing's emergency directions may have failed to save 737 MAX". The Seattle Times. Retrieved 2019-09-27.
  79. ^ "Checklists come into focus as pace-setter for 737 Max return". The Air Current. 2019-10-09. Retrieved 2019-10-09.
  80. ^ Standard Operating Procedures and Pilot Monitoring Duties for Flight Deck Crewmembers (PDF). Advisory Circulars. FAA. January 10, 2017. AC 120-71B.
  81. ^ Glanz, James; Creswell, Julie; Kaplan, Thomas; Wichter, Zach (2019-02-03). "After a Lion Air 737 Max Crashed in October, Questions About the Plane Arose". The New York Times. ISSN 0362-4331. Retrieved 2019-07-27.
  82. ^ "Boeing 737 MAX: What Happened, And What Now?". Aviation Week Network. Retrieved 2019-08-22.
  83. ^ a b "My Testimony Today Before the House Subcommittee on Aviation". Sully Sullenberger. 2019-06-19. Retrieved 2019-06-20.
  84. ^ "My Letter to the Editor of New York Times Magazine". Sully Sullenberger. 2019-10-13. Retrieved 2019-10-14.
  85. ^ PLAINTIFF'S ORIGINAL PETITION, SWAPA vs. Boeing. 2019.
  86. ^ "Boeing altered key switches in 737 MAX cockpit, limiting ability to shut off MCAS". The Seattle Times. 2019-05-10. Retrieved 2019-10-15.
  87. ^ a b c "Vestigal design issue clouds 737 MAX crash investigations". 2019-04-04.
  88. ^ "Norwegian Flies Boeing 737 MAX Over Europe For Storage Purposes". Simple Flying. 2019-06-12. Retrieved 2019-06-17.
  89. ^ a b c ICI.Radio-Canada.ca, Zone Économie-. "Des révélations troublantes sur le Boeing 737 MAX 8". Radio-Canada.ca (in French). Retrieved 2019-11-11.
  90. ^ Arvai, Ernest (2019-11-11). "November 2019: More Bad News for Boeing over the Weekend". airinsight.com. Retrieved 2019-11-11.
  91. ^ "Boeing a-t-il fait preuve de négligence?" [Was Boeing negligent?] (in French). Radio-Canada info. April 1, 2019. Retrieved 2019-11-14.
  92. ^ a b c Jon Ostrower; "Vestigial design issue clouds 737 Max crash investigations", The Air Current, April 4, 2019. (retrieved November 21, 2019)
  93. ^ Hemmerdinger, Jon (2020-04-02). "Simulator tests demonstrate 737 Max manual trim difficulties". FlightGlobal.
  94. ^ a b "Angle of attack" (PDF). Aero magazine - Issue 12. Boeing. 2000. Retrieved 2019-07-27. Lay summary.
  95. ^ Leinfelder, Andrea (2019-08-22). "Did Boeing, aviation industry heed lessons of 2009 Air France crash?". Houston Chronicle. Retrieved 2019-09-01.
  96. ^ Useem, Jerry (2019-11-20). "The Long-Forgotten Flight That Sent Boeing Off Course". The Atlantic. Retrieved 2019-11-24.
  97. ^ Curt Devine; Drew Griffin. "Boeing relied on single sensor for 737 Max that had been flagged 216 times to FAA". CNN. Retrieved 2019-09-26.
  98. ^ Frankel, Todd C. (2019-03-17). "Sensor cited as potential factor in Boeing crashes draws scrutiny". The Washington Post.
  99. ^ a b Gates, Dominic (2019-09-10). "European regulator plans its own test flights of Boeing 737 MAX in sign of rift with FAA". The Seattle Times. Retrieved 2019-09-11.
  100. ^ Baker, Mike; Gates, Dominic (2019-03-26). "Lack of redundancies on Boeing 737 MAX system baffles some involved in developing the jet". The Seattle Times. Retrieved 2019-08-04.
  101. ^ Fehrm, Bjorn (2019-03-27). "Boeing presents MCAS fix to pilots, regulators and media". Leeham News and Analysis. Retrieved 2019-07-30.
  102. ^ "Optional warning light could have aided Lion Air engineers before crash: experts". Reuters. 2018-11-30. Retrieved 2019-11-13.
  103. ^ Fehrm, Bjorn (2019-11-15). "Bjorn's Corner: Analysing the Lion Air JT610 crash, Part 3". Leeham News and Analysis. Retrieved 2019-11-15.
  104. ^ MacGillis, Alec (2019-11-11). "The Case Against Boeing". ISSN 0028-792X. Retrieved 2019-11-11.
  105. ^ "Air Canada says their 737 Max jets have all safety features Boeing sells as extras". CBC.ca. March 21, 2019.
  106. ^ "Optional warning light could have aided Lion Air engineers before crash: experts". Reuters. 2018-11-30. Retrieved 2019-11-13.
  107. ^ "Boeing wanted to wait three years to fix safety alert on 737 Max". Los Angeles Times. Associated Press. 2019-06-07. Retrieved 2019-08-03.
  108. ^ a b c "Boeing Statement on AOA Disagree Alert" (Press release). Boeing. 2019-05-05. Retrieved May 7, 2019.
  109. ^ Gelles, David; Kitroeff, Natalie (2019-05-05). "Boeing Believed a 737 Max Warning Light Was Standard. It Wasn't". The New York Times. ISSN 0362-4331. Retrieved 2019-08-27.
  110. ^ Tabuchi, Hiroko; Gelles, David (2019-03-21). "Doomed Boeing Jets Lacked 2 Safety Features That Company Sold Only as Extras". The New York Times. ISSN 0362-4331. Retrieved 2019-08-27.
  111. ^ "Southwest is adding new Angle of Attack indicators to its 737 Max fleet". The Air Current. 2018-11-30. Retrieved 2019-06-05.
  112. ^ "Lion Air Report Analyzes Pilot Struggle With 737 MAX Trim System". Avionics. 2018-11-30. Retrieved 2019-07-15.
  113. ^ Zetlin, Minda (2019-03-24). "Boeing CEO Says Safety Is Highest Priority. The Company's Pricing Says Something Different". Inc. Retrieved 2019-07-27.
  114. ^ Pasztor, Andy; Tangel, Andrew; Sider, Alison (May 5, 2019). "Boeing Knew About Safety-Alert Problem for a Year Before Telling FAA, Airlines". The Wall Street Journal. Retrieved December 24, 2019.
  115. ^ "Boeing CEO Admits Mistake in Handling Warning-System Problem". Associated Press. June 16, 2019 – via VOA.
  116. ^ "Frequently Asked Questions". Boeing: 737 MAX FAQ.
  117. ^ Le Vie, Lisa R. (August 1, 2014). Review of Research On Angle-of-Attack Indicator Effectiveness (Report). NASA Langley Research Center (LaRC). hdl:2060/20140011419. NASA/TM–2014-218514.  This article incorporates text from this source, which is in the public domain.
  118. ^ Davis, Aaron C.; Lazo, Luz; Schemm, Paul (April 4, 2019). "Additional software problem detected in Boeing 737 Max flight control system, officials say". The Washington Post. Retrieved April 4, 2019.
  119. ^ Pasztor, Andy; Tangel, Andrew (October 8, 2019). "Friction Between U.S., European Regulators Could Delay 737 MAX Return to Service". The Wall Street Journal. Retrieved October 8, 2019.
  120. ^ a b Levin, Alan (2019-11-08). "Delays in Boeing Max Return Began With Near-Crash in Simulator". www.bloomberg.com. Retrieved 2019-11-09.
  121. ^ "Boeing finds yet another 737 MAX software issue". SlashGear. 2020-01-19. Retrieved 2020-01-20.
  122. ^ at 00:43, Gareth Corfield 9 Apr 2020. "Stop us if you've heard this before: Boeing's working on 737 Max software fixes for autopilot, stabilization bugs". www.theregister.co.uk. Retrieved 2020-04-09.
  123. ^ "Boeing: The "e-cab" – a test flight deck". www.boeing.com. Retrieved 2019-10-22.
  124. ^ "The "e-cab" – A Test Flight Deck". players.brightcove.net. Boeing. 2015-11-30. Retrieved 2019-10-22.
  125. ^ Levin, Alan; Johnsson, Julie; Courtney, Shaun. "Boeing needs up to three months to fix newly discovered 737 Max glitch". Los Angeles Times. Retrieved 2019-07-04.
  126. ^ Fehrm, Bjorn (June 28, 2019). "New pitch trim issue forces further changes to 737 MAX software". Leeham News and Analysis.
  127. ^ a b "Boeing Statement on 737 MAX software" (Press release). Boeing. June 26, 2019. Retrieved 2019-06-27.
  128. ^ Ostrower, Jon (June 27, 2019). "FAA and Boeing initially disagreed on severity of "catastrophic" 737 Max software glitch". The Air Current.
  129. ^ a b c Gates, Dominic (2019-08-01). "Newly stringent FAA tests spur a fundamental software redesign of Boeing's 737 MAX flight controls". The Seattle Times. Retrieved 2019-08-02.
  130. ^ "Latest 737 Max Fault That Alarmed Test Pilots Rooted in Software". Bloomberg News.
  131. ^ Broderick, Sean (August 1, 2019). "Software Fix Will Address Most Recent MAX Issue". Aviation Week & Space Technology.
  132. ^ Allard, André (July 3, 2019). "MAX's computer has reached its limit". Wings Over Québec.
  133. ^ Campbell, Darryl (2020-04-09). "The ancient computers in the Boeing 737 Max are holding up a fix". The Verge. Retrieved 2020-06-27.
  134. ^ "Boeing Fixing New Software Bug on Max; Key Test Flight Nears". Bloomberg. 2020-02-06.
  135. ^ O'Kane, Sean (2020-02-06). "Boeing finds another software problem on the 737 Max". The Verge. Retrieved 2020-02-07.

External linksEdit

Further readingEdit