A jet carrying 187 people suffered a landing gear failure during its takeoff roll, yet every passenger and crew member walked away without life-threatening injuries. The event sits within a pattern of gear-related structural failures that federal investigators have traced, in separate cases, to procedural lapses and certification gaps. From an MD-82 that broke apart on a Miami runway to a Boeing 787 whose nose gear collapsed in Frankfurt, the record shows that what happens before a plane ever leaves the gate can determine whether an emergency ends in evacuation or catastrophe.
Gear failures during takeoff and why preflight checks keep failing
Landing gear collapses rarely happen in isolation. When the National Transportation Safety Board examined an MD-87 runway excursion, investigators concluded that a jammed flight control and failure to implement preflight procedure caused the jet to veer off the runway. That finding pointed directly at the human side of the equation: a crew that did not complete a required verification step before the aircraft began its takeoff roll.
The question this raises for the 187-passenger event is whether a similar procedural gap played a role. Operators that build independent dual sign-off into their gear-pin verification process, completed within a tight window before pushback, would in theory catch mechanical faults before they become emergencies at high speed. No public NTSB docket or final report has been released for the specific 187-passenger takeoff, so direct confirmation of what went wrong in the cockpit or on the ramp is not yet available. Flight data recorder transcripts, crew statements, and maintenance logs remain absent from federal databases.
That gap in the public record matters because the pattern across other investigated events is consistent. When preflight procedures break down, structural failures during the most energy-intensive phase of flight, the takeoff roll, become far more dangerous. The fact that everyone aboard this aircraft escaped is an outcome that owes as much to engineering margins and rapid crew response as it does to luck.
Miami, Frankfurt, and Dallas: the structural failure record
Three separate events in the federal and international record illustrate how landing gear problems escalate. RED Air flight 203, an MD-82, experienced a landing gear failure and post-crash fire at Miami International Airport. The gear collapsed during the landing roll, the aircraft skidded off the runway, and fire broke out. Passengers evacuated successfully, but the aircraft was destroyed. The NTSB opened a full investigation, and docket materials are accessible through the agency’s public search portal.
A more recent case unfolded at Frankfurt Airport, where a Boeing 787 Dreamliner operated by Lufthansa suffered a nose landing gear collapse, injuring several ground workers and damaging the aircraft during preparations for a long-haul flight. The event involved a modern widebody with contemporary design standards, complicating any assumption that aging airframes are the sole risk factor for gear failures. Investigators in Germany and technical teams from the manufacturer focused on whether the collapse reflected a maintenance error, a component defect, or a procedural misstep during towing and parking.
Decades earlier, American Flight 70, a DC-10, crashed during a rejected takeoff at Dallas/Fort Worth International Airport on May 21, 1988. The NTSB investigation placed blame in part on Federal Aviation Administration procedures rather than solely on the airline or the crew, forcing a reexamination of how certification and testing standards applied to braking systems and high-speed abort scenarios. Regulators faced questions about whether the assumptions built into performance charts and emergency procedures accurately reflected real-world runway conditions and aircraft loads.
Taken together, these cases span different aircraft types, different decades, and different airports, yet they share a thread: gear-related structural failures during ground operations expose weaknesses in both hardware and the procedural systems meant to catch problems before they become emergencies. The RED Air MD-82 and the Lufthansa 787 show that the problem is not confined to older fleets. The Dallas DC-10 crash shows that accountability sometimes reaches beyond the airline to the regulator itself.
What investigators still need to answer about the 187-passenger event
Several questions about the specific incident involving 187 people remain open. No NTSB investigation docket or final report has been published for this event in federal records. Without flight data recorder readouts or cockpit voice recorder transcripts, outside analysts cannot determine whether the gear buckled because of a manufacturing defect, a maintenance oversight, or a procedural failure during preflight checks.
Direct statements from the airline involved and from FAA certification officials have not appeared in official NTSB communications. That silence leaves a gap between what passengers experienced and what the public can verify about the cause. The NTSB’s investigation database, which covers U.S. civil aviation accidents across decades, contains detailed factual reports and analysis for the Miami, Frankfurt-adjacent, and Dallas cases, but nothing comparable yet for the 187-passenger takeoff.
Key unknowns include the exact speed at which the crew recognized the problem, whether any cockpit alerts or abnormal indications appeared before the failure, and how much runway remained when the takeoff was rejected. Investigators will also want to know whether maintenance teams had documented prior anomalies with the same landing gear assembly, and if so, whether those entries triggered follow-up inspections or component replacements.
Another unresolved issue is how emergency procedures unfolded inside the cabin. Passengers reported a sudden deceleration and the smell of burning rubber, but public accounts do not clarify whether the crew initiated a full evacuation, used only selected exits, or kept everyone on board until fire crews confirmed there was no active blaze. Those choices matter because they influence injury patterns and inform future guidance on when to deploy slides after a high-energy rejected takeoff.
Regulators, airlines, and the limits of procedural fixes
The structural failures in Miami, Frankfurt, Dallas, and now the 187-passenger event underscore a tension in modern aviation safety: how much risk can be managed through checklists and training, and how much depends on deeper design changes. After the DC-10 crash, regulators updated performance assumptions and emergency guidance, but the recurrence of gear-related incidents suggests that incremental procedural fixes have limits.
Airlines have responded by tightening preflight verification steps, emphasizing cross-checks for gear pins, hydraulic pressures, and brake temperatures. Simulator training now routinely includes high-speed abort scenarios, giving crews practice in making split-second decisions about whether to continue or reject a takeoff. Yet the MD-87 case, in which a jammed control surface went undetected despite required checks, shows that even well-designed procedures can fail when time pressure, distraction, or organizational culture erodes compliance.
Manufacturers, for their part, have explored more robust gear assemblies, better fault monitoring, and clearer cockpit indications when loads or positions fall outside expected ranges. However, the Frankfurt 787 collapse demonstrates that even newer systems can fail under ground-handling conditions that may not have been fully anticipated in certification tests. That raises questions about whether current standards adequately reflect the stresses imposed by frequent cycles, tight turnaround schedules, and the growing weight of long-range aircraft.
For regulators, the 187-passenger incident will be a test of how quickly lessons from past investigations can be translated into enforceable changes. If the eventual findings mirror earlier patterns-pointing to missed checks, ambiguous procedures, or certification gaps-pressure will mount for more prescriptive rules on gear inspections, towing practices, and abort decision-making thresholds. If, instead, the cause lies in a previously unknown design vulnerability, the response may focus on retrofits and software updates across affected fleets.
A narrow escape and the stakes of what comes next
For the people on board, the landing gear failure during takeoff was a frightening but ultimately survivable ordeal. The absence of life-threatening injuries stands in sharp contrast to the destroyed MD-82 in Miami and the catastrophic fire that followed, and to the DC-10 in Dallas that never became airborne. That contrast should not obscure how close the 187-passenger jet may have come to a far worse outcome.
Until investigators release a full account, the event remains a warning rather than a resolved case study. It reinforces what the broader record already shows: that the safety margin during takeoff is thin, that landing gear is a critical single point of vulnerability, and that the effectiveness of procedures on paper is measured only in the seconds when something goes wrong. The next steps-completing the investigation, publishing the findings, and acting on them-will determine whether this near miss becomes another entry in a long list of similar failures or the catalyst for changes that prevent the next one.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
