transport-aviation

How Many Times Has United Airlines Crashed: A Verified Record and Context

Across its history, United Airlines has been involved in multiple notable accidents, a small number of which were fatal. Most flights complete safely, but the most significant e...

Mara Ellison
How Many Times Has United Airlines Crashed: A Verified Record and Context

What the Record Shows: United Airlines Crash History in Brief

Across its history, United Airlines has been involved in multiple notable accidents, a small number of which were fatal. Most flights complete safely, but the most significant events—such as United Flight 232 in 1989 and United Flight 173 in 1978—are well documented in official reports and research. Fatal accidents are rare in modern commercial aviation, and United’s record reflects both the inherent risks of flight and the continuous improvements in technology, training, and procedures that have reduced those risks over time. The following details distinguish accidents from incidents, define what counts as a crash, and place each event in context of the airline’s overall operations.

Defining a Crash: Terms and Context

Crash Versus Incident: Why the Distinction Matters

In aviation safety reporting, a crash typically refers to an accident involving an aircraft with substantial damage, often including loss of life or serious injury. An incident is any occurrence that affects safety but does not meet the threshold of an accident. Regulatory bodies such as the National Transportation Safety Board (NTSB) and the International Civil Aviation Organization (ICAO) use specific criteria to classify events. Understanding this distinction helps avoid confusion between minor events and major accidents. For United Airlines, the most widely referenced events meet the definition of a crash due to substantial damage and, in some cases, fatalities. Below is a concise summary of notable events in the airline’s history.

dtd>United 553 (Boeing 737)
Date Flight and Aircraft Location Outcome Key Source
June 28, 1972Chicago, Illinois, USA Crash with fatalities NTSB Report
November 3, 1978 United 173 (Douglas DC-8) Portland, Oregon, USA Crash with fatalities NTSB Report
July 19, 1989 United 232 (Douglas DC-10) Sioux Gateway Airport, Iowa, USA Crash with fatalities; partial success in control efforts NTSB Report
February 1, 2008 United 1175 (Boeing 777) Near Honolulu, Hawaii, USA In-flight engine failure; safe landing NTSB Report
January 26, 2024 United 676 (Boeing 777) San Francisco, California, USA Runway excursion on landing; no fatalities NTSB Preliminary Report

Historical Fatal Crashes: Details and Lessons

United Flight 232: The Sioux City Emergency

United Flight 232, a Douglas DC-10, suffered a catastrophic failure of its tail-mounted engine on July 19, 1989, leading to the loss of hydraulic controls. The crew managed a crash landing at Sioux Gateway Airport, saving many lives through exceptional airmanship. While 111 of the 296 aboard died, the event became a landmark case study in emergency training and crew resource management. The NTSB investigation emphasized procedural improvements, both for United and the broader industry, influencing how pilots train for total control failures.

United Flight 173: A Wake-Up Call

On December 28, 1978, United Flight 173, a Douglas DC-8, crashed while attempting an approach in Portland, Oregon, after the crew focused on troubleshooting a landing gear problem. The accident claimed 10 lives and prompted the airline and regulators to formalize crew resource management (CRM) practices, emphasizing communication and task management in the cockpit. This accident is frequently cited as a turning point for aviation safety culture, pushing standardized checklists and decision-making protocols into mainstream use.

United 553: An Earlier Tragedy

On December 8, 1972, United 553, a Boeing 737, crashed while approaching Chicago-Midway Airport in poor weather, killing 45 of the 62 onboard. Investigations highlighted descent rate and altitude awareness issues, contributing to changes in approach procedures and training. Though less discussed than later events, this accident reinforced the need for strict adherence to instrument approaches and altitude discipline, shaping modern standard operating procedures.

Nonfatal and Non-Crash Events: What Counts as a Problem

Not all serious events are crashes. Several high-profile United flights experienced significant mechanical issues without a crash, underscoring how modern aviation detects and mitigates failures. For example, in 2010, a Boeing 777 en route from Beijing crashed at Beijing airport upon landing; however, United’s incident in 2017 involving engine debris damage to a passenger window, while alarming, resulted in a safe landing and no injuries. Such events highlight robust systems that contain failures before they escalate into disasters.

Modern Safety Record and Scale of Operations

United Airlines operates a large global network, carrying hundreds of millions of passengers each year across thousands of daily flights. Given this scale, even rare events receive significant attention. Statistical analyses of commercial aviation show that fatal accidents have become increasingly rare over decades, due to technology, regulation, and improved training. United’s modern safety record, when viewed over a decade or longer, shows long intervals between serious incidents. The industry’s focus on learning from past crashes continues to drive enhancements in design, maintenance, and operations.

How United Stacks Up

When compared with peers of similar size, United’s accident record is consistent with major carriers that operate in complex environments. Rather than isolate one airline, aviation safety professionals look at trends: better engines, redundant systems, and data-driven maintenance have reduced loss-of-control events. The following compact comparison illustrates how the industry has evolved:

  • 1970s: Higher frequency of loss-of-control accidents; CRM introduced.
  • 1980s–1990s: Improved training and design led to fewer hull losses.
  • 2000s–2010s: Enhanced maintenance and real-time data monitoring reduced unscheduled events.
  • 2020s: Advanced materials, automation, and predictive analytics continue to lower risk.

Conclusion: Putting the Numbers in Perspective

United Airlines has been involved in several notable crashes, primarily in earlier decades of commercial aviation when systems and training were still evolving. The most prominent of these—Flight 232, Flight 173, and Flight 553—each contributed to major changes in safety practices and regulations. While the raw number of crashes may appear concerning, the context of operation scale, technological progress, and continuous safety improvements show a strong trend toward greater reliability. For travelers and observers, the key takeaway is that aviation safety is a success story built on learning from past events, not a reflection of current risk.

Related Reading

More pages in this topic cluster.

Understanding Airplane Crashes in and Around London

Airplane crashes near or involving London are rare but consequential events that reshape regulation, public confidence, and airport operations. This guide explains what determin...

Read next
Plane Crash on the Hudson River: What Happened and Why It Still Matters

On January 15, 2009, US Airways Flight 1549, an A320 en route from LaGuardia to Charlotte, lost both engines after striking a flock of Canada geese near New York City. Captained...

Read next
American Airlines Flight 5342: What Really Happened and Why It Matters

American Airlines Flight 5342 was a regularly scheduled passenger flight that became notable due to a significant in-flight incident that required an emergency diversion. This o...

Read next