Outgrace, home
Technology & AICase lessons

What the 737 MAX return teaches about review scope

The FAA's public record on the 737 MAX return shows how a review's written scope decides what gets checked. Accident-cause sources are not covered here.

The FAA's own account of the 737 MAX return is short, and it is still the most useful public record a product leader can read on how a safety review gets scoped. The agency says its review took 20 months and followed two accidents, Lion Air Flight 610 and Ethiopian Airlines Flight 302, which cost 346 lives aboard the two flights. Administrator Steve Dickson then signed an order paving the way for the aircraft to return to commercial service, according to the FAA's return-to-service statement. Most product leaders will never certify an aircraft. They do approve software changes, hardware revisions and the documents that travel with them, and the record shows what happens when the boundary of a review is unclear. The lessons here are about that boundary, not about aviation alone. The public sources we could check do not explain the technical cause of the accidents, so this piece does not attempt it.

  1. Undated

    Two accidents

    Lion Air Flight 610 and Ethiopian Airlines Flight 302. The FAA says its review followed them and that they cost 346 lives aboard the two flights. The statement gives no dates for either.

  2. 20 months

    Safety review

    The FAA says the review took 20 months. Its later statement on proposed revisions describes that review as covering the automated flight control system.

  3. Undated

    Return order

    Administrator Steve Dickson signs the order that paves the way for return to commercial service. The excerpt does not give the signing date.

  4. 16 Feb 2021

    FSB comments close

    The FAA's deadline for public comment on the proposed update to the Flight Standardization Board report. The draft remains subject to comment, so it could still change.

  5. 24 Feb 2021

    MMEL comments close

    The deadline for comment on proposed updates to the Master Minimum Equipment List, which defines when airlines may fly without certain systems or components.

  6. Undated

    Backup unit notice

    Boeing tells the FAA it recommends that certain 737 MAX operators temporarily remove aircraft from service over a manufacturing issue affecting the backup power control unit. The excerpt gives no date.

The timeline follows the order of the FAA's statements, not a verified chronology. Several entries carry no date in the excerpt we hold, so the sequence of the backup unit notice against the return order cannot be fixed from these sources. A reader who needs exact dates should pull the FAA's original documents, including the Airworthiness Directive the agency published, before repeating any of them.

The decision that mattered: what the review covered

The FAA's statement on the Flight Standardization Board and minimum equipment documents draws a line that is worth reading slowly. It says none of the proposed revisions involve the aircraft's automated flight control system, which the agency describes as the subject of a 20-month review and certification. The sentence is a scope statement. It tells the reader what the draft updates may touch and, by implication, what they may not. Product leaders should treat every boundary of that kind as a decision someone signed, not as background. The useful question is not whether the review was thorough. It is whether the thing that changed sits inside the box the review was given.

The draft updates, according to the FAA, mainly reflect differences between the original 737 MAX and the new 737-8200 series. The 737-8200 carries up to 200 passengers and has an additional exit door, and the FAA has proposed additional training for those changes. A door or a seating count can look minor in a design review. It still changes what crews must know and what airlines must teach. In our experience, the changes that cause the most trouble are often the ones that never appear in the design file as design changes at all. A training manual that quietly assumes the older configuration is one example. The FAA's response, extra training for the new variant, shows the regulator counted these differences as worth writing down.

The FAA also says Administrator Steve Dickson personally took the recommended pilot training and flew the MAX. The statement does not say what he changed as a result, or whether anything changed at all. It does show a habit worth copying: the person approving the product used it before approving the paperwork. A product leader can apply that without any aviation context. Use the product, or the training that teaches it, before you sign the release note.

The record has gaps that matter. The NTSB investigation report and the findings of the US House Transportation Committee would normally sit alongside the FAA's statements, and neither is in the sources we checked. The House Transportation and Infrastructure page we reviewed lists other bills and contains no material on MCAS. The Department of Transportation inspector general's site states that the NTSB is an independent establishment, not part of the Department, which is one more reason not to treat the FAA's account as the whole picture. The same site carries a finding on ground-based navigation aids. That concerns a different system, and we have not used it. Anyone repeating the causes of the accidents needs the investigation documents first.

The design and certification of this aircraft included an unprecedented level of collaborative and independent reviews by aviation authorities around the world.

FAA, return-to-service statement, faa.gov

Lessons

Write the scope down, and name what sits outside it. The FAA's statement that the proposed Flight Standardization Board and minimum equipment revisions do not involve the automated flight control system means something only if someone can see the scope it refers to. A product team should keep a one-page boundary for every review: the systems inside, the systems outside, and the named person who made the call. When a later change touches something on the outside list, the review should reopen by default.

Keep training and manuals on the same change log as the design. The FAA says airlines use the Flight Standardization Board report to develop pilot training. A change in that report is therefore a training change, whether or not anyone calls it one. Assign one owner to each change that reaches a user's hands, including instructions and manuals, and check that the owner has seen the design difference before the release is signed.

Treat comment windows as hard deadlines. The FAA set comment deadlines of February 16, 2021 for the Flight Standardization Board draft and February 24, 2021 for the minimum equipment list draft. A team that learns of a deadline late may have lost its chance to comment at all. Put every external comment date in the release calendar with an owner, and a separate date by which the internal reply must be finished.

Count build problems in the same register as design changes. Boeing told the FAA it recommends that certain 737 MAX operators temporarily remove aircraft from service over a manufacturing issue affecting the backup power control unit. A build defect of that kind does not sit in the design file, yet it lands on the same operators, the same schedules and the same regulator. Give supplier and build defects the same review rigour and the same named owner as design decisions.

Know who keeps the authority to approve. The FAA says it retained authority to issue airworthiness certificates for MAX aircraft built since the grounding order. Authority a regulator keeps for itself is a visible choice, and it tells you where the risk was judged to sit. A product organisation should be as explicit. Write down which approvals a new owner may give alone, which need a second signature, and which return to the person who set the boundary in the first place.

A smaller company cannot borrow a regulator's powers, and should not try. What transfers is the discipline: a written scope, a list of everything that changed since the last approved version, an owner for every document and training change, and a named person who holds the release decision. What does not transfer is the regulatory structure itself. Certificates, foreign validation and approved training programmes belong to aviation authorities. A company that needs advice on its own exposure to such rules should take it from a specialist adviser or the relevant regulator.

On Monday, pull the last three releases and ask three questions of each: what changed, which review covered it, and who wrote the training or manual change that went with it. Any change without an answer to the second question goes on a list for the next board pack. That list, written by the people who did the work, will tell you more about your own review scope than any summary a committee produces.

Newsletter

The Briefing

One email a week: the leaders we profiled, the ideas worth stealing, and nothing else.

Weekly, free, one click to leave. Read our privacy policy.