Leeham News and Analysis

Updates 1 and 2: Key reason for Jeju 2216’s tragedy: the airport localizer construction and location

Update, Dec. 30: Reuters published this graphic, which is superb and self-explanatory. The full story is here.

Update 2. Dec. 31: A new Reuters article has some important detail about the location of the localizer vis-a-vis the runway and apron. Excerpts:

• Comments in the airport’s operating manual, uploaded early in 2024, said the embankment was too close to the end of the runway and recommended that the location of the equipment be reviewed during a planned expansion.
• “Unfortunately, that thing was the reason that everybody got killed, because they literally hit a concrete structure,” Captain Ross Aimer, the chief executive of Aero Consulting Experts, told Reuters. “It shouldn’t have been there.”
• Muan International Airport’s Operations Manual said the navigation equipment, or localisers, had been installed too near the end of the runway, or just 199 m (218 yards) from the crash site.
• South Korean officials have previously said the structure was about 250 m (273 yards) from the end of the runway itself, though a paved apron extends past that.
• The runway design did not meet industry best practices, however, said John Cox, chief executive of Safety Operating Systems and a former 737 pilot, adding that they preclude any hard structure like a berm within at least 300 m (330 yards) of the end of the runway.

By Scott Hamilton

Commentary

Dec. 30, 2024, © Leeham News: The Dec. 29 (local time) accident of Jeju Flight 2216 is a tragedy that didn’t have to happen.

It’s far too soon to say what caused the emergency on the airplane. Within hours a host of theories emerged about the cause. The airport fire chief blamed the accident on a bird strike (singular). I’ve never heard of a single bird strike bringing down an airliner. Multiple bird strikes have brought down airliners going back to the propeller days. In recent history, US Airways 1549—the flight that Capt. Chesley Sullenburger and co-pilot Jeff Skiles safely landed in the Hudson River—is the most famous example.

Korean and assisting investigators will reveal if 2216 suffered multiple strikes that caused power to both engines to quit, as happened with 1549. The flight data recorder (FDR) and cockpit voice recorder (CVR) should put this to rest. The analysis of these should also reveal why the landing gear, slats and flaps were not extended. The cockpit resource management (CRM) will be analyzed as well to understand the coordination between the two pilots.

Whatever the reason for the emergency landing, the incontrovertible cause for the disaster that befell the plane was the presence of a berm and concrete structure of the runway localizer a short distance from the end of the runway. This structure should never have been constructed in this manner. Having been done, it should have been later removed and replaced by a structure that would not have been disastrous to the emergency flight.

I’m optimistic that the initial readout of at least one of the flight recorders will be available this week. One of the recorders was damaged and is being sent to the US National Transportation Safety Board in Washington (DC) for analysis. (It was not revealed which one at this writing.)

In the meantime, a wide list of topics will be investigated. These include but are not limited to:

Read more