Hurt on a flight? Start a free case evaluation
RESQ.com. When your future is at stake. (800) 300-0001 Free case evaluation Call Now
United Airlines Plane Crashes: How to Verify the Record, Understand Fatalities, and Interpret Investigation Findings

Home / Blog / united airlines plane crashes

United Airlines Plane Crashes: How to Verify the Record, Understand Fatalities, and Interpret Investigation Findings

Published by The Ledger Law Firm · · general information, not legal advice

Build a classified United Airlines crash ledger

A United Airlines crash record needs two labels before it needs a number: who operated the aircraft and how the event was classified. Count a documented crash only after you decide whether the record concerns a United-operated flight and whether the event was an accident involving a crash rather than an incident, emergency, or safe landing. That rule keeps a dramatic event from becoming an inaccurate historical total.

Build the ledger with fields that keep its inclusion rule visible:

  • the operator named in the record and any other operator involved;
  • the event classification, such as crash, incident, or safe landing;
  • the flight, aircraft, date, and location;
  • the people aboard and any fatalities or injuries stated in the record; and
  • the investigation status and event-specific finding.

Then keep unlike entries separate. An engine event with no injuries, a safe landing, or a collision involving another operator should not be counted as a United-operated crash without an explicit classification rule.

United Airlines Flight 328 shows why classification matters. The NTSB record describes the February 20, 2021 event as an incident: a right-engine fan-blade separation and engine fire occurred shortly after takeoff from Denver, but the two pilots, eight crewmembers, and 229 passengers were not injured. That event belongs in an incident record unless your stated method deliberately includes incidents.

United Airlines Flight 169 also needs separate treatment. The flight struck a light pole while approaching Newark, landed safely, and was to be investigated by the FAA and NTSB, with the NTSB leading. A safe landing after contact with an object is not automatically the same category as a crash.

The distinction works in the other direction, too. United Flight 718 and TWA Flight 2 collided in midair over the Grand Canyon while flying at the same altitude on intersecting courses, and both aircraft fell to the ground. Because two operators were involved, you should identify the United-operated flight without treating the event as an accident involving United alone.

Build a dated record instead of relying on one total

A dated event ledger gives you a more reliable account than an isolated crash total. Record each event in its own row or entry, then keep the following fields together:

  • Date and location
  • Flight number, aircraft type, and registration when available
  • Operator relationship, including whether United operated the flight
  • Classification, such as accident or incident
  • Occupants and fatalities, with the denominator that gives the figure meaning
  • Aircraft damage and survival information when recorded
  • Investigating authority and whether the investigation record was completed
  • Probable cause, contributing factors, or an explicit unresolved status

The United Airlines Douglas DC-3-197 accident record is dated Monday, November 4, 1940. It lists 10 fatalities among 10 occupants, says the aircraft was destroyed and written off, and identifies a completed Civil Aeronautics Board investigation record. The aircraft crashed into the west side of Bountiful Peak at the 6,700-foot level during a snowstorm after a failure of navigational equipment.

The aviation-safety.net record for United Airlines accident N1819U identifies July 19, 1989, at Sioux Gateway Airport in Iowa, with 111 fatalities among 296 occupants. It records the aircraft as destroyed and identifies the NTSB investigation record as completed. The NTSB material identifies the flight as United Airlines Flight 232.

Use the ledger as a control against accidental double counting. If two records describe the same flight, compare the date, registration, location, operator, and investigating authority before combining them. If an entry lacks a fatality figure, leave that field marked as unreported in the specific record rather than treating the missing number as zero.

A fatality figure belongs beside the event that produced it, not in a detached headline. An NTSB excerpt for Flight 173 does not provide a fatality total in that excerpt, so you should not fill the blank with an estimate or borrow a number from another account. A fuller accident record may contain additional details, but each figure still needs its own flight, date, and occupant denominator.

A historical total is defensible only when the inventory is complete for its stated period, operator definition, and classification rule. If the inventory covers selected records, describe the entries as documented examples rather than presenting them as the complete number of United Airlines fatal crashes. That distinction matters when you compare older records with modern events, or when you are trying to determine whether a particular flight belongs in the count.

A careful count also keeps fatalities, occupants, survivors, and serious injuries in separate fields. Those measures answer different questions. A record that lists 111 fatalities among 296 occupants should not be merged with a different account that identifies particular passenger and crew groups unless the relationship between the figures is stated.

A fatality figure is meaningful only when its event and occupant denominator remain attached.

What the documented fatal crashes show

Documented fatal crashes show different event patterns, which is why a list of fatalities should not be treated as an explanation by itself. United Trip 4 struck a hill during a nighttime approach to Cheyenne, Wyoming, and all 12 people aboard were killed. That entry establishes the event and fatality count; it does not, by itself, establish a broader pattern about every United operation.

The United Airlines Douglas DC-3-197 record provides a different set of details. The record lists 10 fatalities among 10 occupants and describes a crash into Bountiful Peak during a snowstorm after a failure of navigational equipment. The same record states that communications operators at Tintic, Plymouth, and Salt Lake City, Utah, failed to detect the range malfunction and immediately notify those concerned. It also states that the pilot of Trip 16 failed to follow fully the established radio-range technique required by the procedure established by United and approved by the Civil Aeronautics Administration.

The wording matters. A record may identify equipment failure, crew conduct, communication failures, weather, or several contributing circumstances. Keep each investigation finding tied to the event it addresses instead of reducing every event to a single cause.

A selected historical example can answer what happened in that entry without answering how often every possible event occurred. Keep the event date, aircraft identity, operator relationship, fatality denominator, and investigation finding attached to the same record. That structure lets you expand the inventory later without changing the meaning of the earlier entries.

The United-operated DC-6 accident shows why its chain of events matters. The crew believed a fire had started in the forward cargo hold and discharged at least one bank of carbon-dioxide extinguisher bottles. An incorrect procedure left the cabin pressure-relief valves closed, allowing a hazardous concentration of carbon dioxide to enter the cockpit. The concentration reduced the pilots to confused consciousness and probably caused loss of consciousness.

The board determined that the probable cause was crew incapacitation from carbon-dioxide gas in the cockpit. That finding describes the particular accident. It does not turn the record into a universal statement about United Airlines, every DC-6, or every cockpit emergency.

Flight 232 is another documented fatal crash, but its account belongs with the engine failure and hydraulic-control findings discussed below. Treating each event as its own record lets you preserve the date, aircraft, occupants, fatalities, and investigative conclusion without claiming that a selected group of examples is a complete historical inventory.

Flight 173: a completed Portland accident record

United Airlines Flight 173 crashed near Portland International Airport on December 28, 1978, after the crew dealt with a landing-gear malfunction and remained at low altitude for about 1 hour. The NTSB report places the crash about 6 nautical miles southeast of the airport in a wooded, populated area of suburban Portland, Oregon. The aircraft was destroyed, and the report states that there was no fire.

The recorded occupant and injury figures give the event human context. Flight 173 carried 181 passengers and 8 crewmembers. Eight passengers, the flight engineer, and a flight attendant were killed, while 21 passengers and 2 crewmembers were seriously injured. Stating the groups separately avoids turning the fatality figure into an unexplained total.

The NTSB determined that Flight 173’s probable cause was the captain’s failure to properly monitor and respond to the aircraft’s low fuel state and the crewmember’s fuel advisories. That finding connects the crash to the recorded fuel state, cockpit response, and advisories during the approach.

Flight 173 therefore supports several distinct entries in your record: the date and Portland location, the landing-gear problem and low-altitude delay, the occupants and injuries, the aircraft damage, and the NTSB’s probable-cause finding. Keeping those entries distinct helps you identify what the final investigation established without suggesting that the finding alone answers every question about responsibility or legal significance.

Flight 232: engine failure, hydraulic loss, and the NTSB findings

United Airlines Flight 232 suffered a catastrophic No. 2 engine failure on July 19, 1989, during cruise flight. The failure caused the loss of all three hydraulic flight-control systems before the aircraft crashed during an attempted landing at Sioux Gateway Airport in Sioux City, Iowa.

Flight 232 had 285 passengers and 11 crewmembers aboard. One flight attendant and 110 passengers were fatally injured. A separate aviation-safety.net record states that 111 occupants were killed and 185 survived, giving 296 occupants in total. The two figures describe the same event while using different groupings, so preserve the denominator and the source context rather than merging them into an unexplained number.

The NTSB attributed Flight 232’s accident to inadequate consideration of human-factors limitations in United’s engine-overhaul inspection and quality-control procedures. Those procedures failed to detect a fatigue crack in the stage 1 fan disk. This is an event-specific investigative finding about the overhaul process and the engine component involved; it is not a general conclusion about every United aircraft or every maintenance decision.

The NTSB also concluded that Flight 232 could not have been successfully landed on a runway after all hydraulic flight controls were lost. In those circumstances, the NTSB described the flight crew’s performance as highly commendable and as greatly exceeding reasonable expectations. The finding recognizes the severe control problem while keeping the crew assessment separate from the probable-cause analysis.

When you organize Flight 232, keep four questions apart: what failed, what the loss of hydraulic control caused during the attempted landing, what injuries and deaths were recorded, and what the NTSB determined about the overhaul inspection and quality-control procedures. That structure prevents a complex investigation from being reduced to either a single mechanical phrase or a single assignment of blame.

Why Flight 328 and Flight 169 should not automatically be counted as crashes

United Airlines Flight 328 and United Airlines Flight 169 illustrate two events that should be classified before they are counted. These two events illustrate why classification matters:

Event What happened Outcome recorded Classification implication
Flight 328 A right-engine fan-blade separation and subsequent engine fire occurred shortly after takeoff from Denver on February 20, 2021. The two pilots, eight crewmembers, and 229 passengers were not injured. The NTSB record describes the event as an incident, not a crash.
Flight 169 The flight struck a light pole while approaching Newark. The Boeing 767 landed safely. The FAA statement describes an event for investigation, not an automatic crash classification.

The shared lesson is narrow but useful: an engine fire with no reported injuries and a safe landing after contact with a light pole should not automatically be counted as a crash. Apply the classification rule you stated at the beginning, then preserve the event in the appropriate incident or emergency record if it does not meet that rule.

For a consistent comparison, define “major” here as a United-operated crash with at least one recorded fatality, and treat incidents and safe landings separately. Compare the dates of qualifying events in NTSB accident records, matching the operator, flight, event date, classification, and investigation status. Flight 328 and Flight 169 show why an event’s visibility does not settle its classification.

The FAA statement for Flight 169 said the FAA and NTSB would investigate, with the NTSB leading. Treat that investigation status as a status at the time of the statement, not as a completed finding. For Flight 328, keep the engine event and the absence of reported injuries attached to the incident classification. Do not use either event as proof of a complete crash total or as a conclusion about current airline safety.

When you encounter another United flight in a news account, begin with the same test rather than assuming that the headline supplies the correct category. Match the flight number to the operator, identify whether the aircraft crashed or landed, and separate an early report from a completed investigation finding.

Compare event-level investigation findings

Use a separate findings column for conclusions and uncertainty. The entries do not all answer the same question:

  • Flight 173: The NTSB determined that the probable cause involved the captain’s failure to properly monitor and respond to the low fuel state and the crewmember’s fuel advisories.
  • Flight 232: The NTSB attributed the accident to inadequate human-factors consideration in United’s engine-overhaul inspection and quality-control procedures, including the failure to detect a fatigue crack in the stage 1 fan disk.
  • Flight 232’s landing: The NTSB concluded that a successful runway landing was not possible after all hydraulic flight controls were lost and described the crew’s performance as greatly exceeding reasonable expectations.
  • The Grand Canyon collision: The investigation’s probable-cause account says the pilots did not see each other in time but could not determine why; it identified clouds, cockpit visibility, distraction, human visual limits, and inadequate air-traffic advisories as possible contributing factors.

This format preserves the status of each statement. A determined probable cause is not the same as a possible factor, and a conclusion about landing possibility is not a conclusion about responsibility. Keeping the identified action attached to the relevant party also prevents these event-level findings from becoming a conclusion about United Airlines’ overall safety or a legal conclusion.

An event ledger can show what a recorded event involved, who was aboard, what fatalities or injuries the record states, and what an investigation concluded or left as a possible factor. It cannot, by itself, establish an airline-wide safety ranking, decide civil liability, or show that a particular reader has a legal claim. A fatality figure describes recorded human impact; it does not identify who may be legally responsible.

Flight 173 and Flight 232 demonstrate why the findings column matters. Their records involve different operational circumstances, aircraft systems, and investigative conclusions, so they should remain separate entries rather than being reduced to a single explanation.

If an event affected you or your family, preserve relevant information promptly and seek a qualified aviation attorney or responsible authority rather than treating this historical account as a case-specific legal conclusion.

Track preliminary and final findings without treating uncertainty as proof

NTSB timing can vary by investigation. The NTSB typically publishes preliminary reports within weeks and often publishes final reports 12 to 24 months after an accident. ResQ Legal’s aviation-accident guidance gives a more specific general range - about two weeks for a preliminary report and approximately 18 to 24 months for a final report - that fits within those broader ranges. Both are general timing ranges, not a promise for a particular accident.

A preliminary report can help you identify the event and follow early information, but it should not be treated as the final explanation. A final report may establish a probable cause and contributing factors after additional investigation. Until the final finding is issued, label an account as preliminary, developing, disputed, or unknown when that is what the record supports.

A useful status line contains three parts: the event date, the investigation stage, and the exact conclusion available at that stage. For example, you might record that an event was reported, that a preliminary account was available, or that a final report had identified a probable cause. Do not replace an unresolved question with a confident explanation simply because a later account seems plausible.

The same discipline helps with the question of whether a particular United flight belongs in the crash history. First classify the event. Then identify the investigating authority and report stage. Finally record the finding with its limits. We advise families that they do not have to wait for a final report to ask what their options are, even though the investigation may continue for months.

Keep the date of each update beside the status it describes. An early account and a later final finding may concern the same event but answer different questions. Preserving both stages helps you see which details changed, which remained established, and which questions are still open.

Protect health and information immediately after a crash or injury

Safety and emergency medical care come before record-building after an aviation accident. If you can leave the aircraft or accident scene safely, move away from immediate hazards and follow emergency-personnel instructions. Aviation accident scenes can contain fire, fuel, damaged aircraft components, unstable structures, and other dangers, so avoid approaching them unnecessarily.

Use this sequence when circumstances allow:

  1. Find a safe place away from the aircraft and follow emergency instructions.
  2. Get checked by medical professionals even if you feel fine, because some injuries can be hidden.
  3. Notify local law enforcement and emergency services so the incident can be documented and medical assistance can be dispatched.
  4. If it is safe, photograph the accident site, aircraft, visible injuries, and surrounding area.
  5. Collect contact details from witnesses when doing so does not interfere with emergency care or safety.
  6. Inform the NTSB or FAA based on the nature of the incident.

A photograph or witness contact is useful only when obtaining it is safe. Do not enter a restricted area, approach unstable wreckage, delay medical treatment, or interfere with emergency personnel to gather information.

Information preservation should follow the same practical order. Keep the flight details, boarding or travel records, medical records, photographs, witness contacts, communications, and official notices together with the dates you received or created them. The purpose is to keep the account coherent while facts are still developing, not to decide fault on your own.

An aviation law firm can act quickly to demand preservation of evidence such as maintenance records, training files, inspection history, company messages, radar data, air-traffic-control recordings, crew schedules, and electronic aircraft data. Those categories show why information outside your possession may matter. Write down what you know, identify what someone else controls, and avoid assuming that a public crash report contains every record relevant to an injury.

Medical care and documentation serve different needs. Medical professionals address your condition; photographs and witness details preserve what was visible; official investigators develop the event record; and legal review addresses how the facts may apply to your circumstances. Keep those functions separate.

Address immediate safety and health needs before building the event record.

Know when the record calls for qualified help

Qualified help becomes especially important when a United Airlines event has caused an injury or death, when the operator or event classification is unclear, when investigation findings are still developing, or when important records may need preservation. Those circumstances warrant a case-specific assessment by a qualified aviation attorney.

You do not need to wait for a final report before asking what options may be available. We advise families to seek an evaluation while preserving the event details, medical information, witness contacts, and official records already within their control. A developing investigation can change the factual picture, so keep later updates separate from what was known earlier.

A historical crash entry can help you identify the flight and locate official records, but it cannot determine whether your injury or family situation supports a legal claim. If the event is personally connected to you, bring the dated record and the information you preserved to a qualified aviation attorney rather than relying on a fatality total or a preliminary explanation alone.

Organize the record for a case-specific review

A case-specific review starts with an organized event record, not with a guess about the final outcome. Put these items in one place:

  • Flight number, travel date, route, aircraft information, and operator details
  • Medical records, diagnoses, treatment dates, and related expenses
  • Photographs of the scene, aircraft, visible injuries, and surrounding area when safely obtained
  • Names and contact details for witnesses
  • Communications with the airline, airport, authorities, insurers, or other involved parties
  • Official notices, investigation updates, and any report identifying the event classification
  • Notes showing which records may require preservation, including maintenance, training, inspection, radar, air-traffic-control, crew, or electronic aircraft data

Use dates and specific descriptions for each item. General information about United Airlines crashes can help you separate a confirmed accident from an incident or safe landing, but a qualified professional must assess individual suitability under the facts, timing, location, and applicable rules of your situation.

If an injury or death has made this history personal, keep the record together and ask for a case-specific review without waiting for every investigation question to be resolved.


Questions about counting and responding to United Airlines crashes

What should a family preserve before a United Airlines crash investigation is complete?

Preserve flight and travel details, medical records, treatment dates, photographs taken safely, witness contact information, communications, official notices, investigation updates, and records showing the event classification. Note what may be held by others, such as maintenance, training, inspection, radar, air-traffic-control, crew, or electronic aircraft data. Do not delay emergency care or enter a hazardous scene to collect information.

Can an NTSB probable-cause finding prove that United Airlines is legally responsible?

No. A probable-cause finding explains an investigated event and may identify equipment, procedures, conduct, or contributing circumstances, but it does not by itself establish civil liability or prove that a particular person has a legal claim. Responsibility can depend on additional facts, applicable rules, involved parties, location, timing, and the specific injury or death.


Were you hurt on a flight?Tell us what happened. The consultation is free.
Free case evaluation