LLMpediaThe first transparent, open encyclopedia generated by LLMs

United Air Lines Flight 173

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Expansion Funnel Raw 30 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted30
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
United Air Lines Flight 173
NameUnited Air Lines Flight 173
CaptionDouglas DC-8 similar to the accident aircraft
DateDecember 28, 1978
TypeFuel exhaustion resulting in crash landing
Occurrence typeAccident
SitePortland International Airport vicinity, Portland, Oregon
Aircraft typeDouglas DC-8-61
OperatorUnited Airlines
Tail numberN9611U
OriginJohn F. Kennedy International Airport
StopoverDenver Stapleton International Airport
DestinationPortland International Airport
Occupants189
Passengers181
Fatalities10
Injuries24

United Air Lines Flight 173 was a scheduled United Airlines Douglas DC-8 flight that crashed on December 28, 1978, near Portland International Airport after fuel exhaustion during a prolonged approach. The accident killed ten people and injured twenty-four, prompting major changes in cockpit resource management and airline safety culture. The crash and ensuing inquiry involved numerous agencies and individuals from Federal Aviation Administration and National Transportation Safety Board to airline management and aviation manufacturers.

Flight and crew

Flight 173 originated at John F. Kennedy International Airport with a scheduled stop at Stapleton International Airport in Denver, Colorado before proceeding to Portland. The flight was operated with a four‑engine Douglas DC-8 crewed by an experienced captain, first officer, and flight engineer; crew members had prior assignments with United Airlines and training overseen by airline training departments and industry regulators. The roster included pilots who had flown for carriers such as Trans World Airlines and American Airlines earlier in their careers, and maintenance records referenced work by Boeing and engine overhaul by Pratt & Whitney affiliates. Air traffic control interaction involved personnel from Federal Aviation Administration facilities at Denver and Portland, and company dispatch coordination with United operations control.

Accident

During the approach to Portland International Airport the flight crew responded to a landing gear indication anomaly and subsequently reported a landing gear problem, initiating a holding pattern while troubleshooting. While the crew focused on diagnosing the suspected landing gear malfunction and consulting checklists, the aircraft remained in the hold consuming fuel. Communications included exchanges with controllers at Portland Air Traffic Control Tower and coordination with United dispatch and company maintenance. As fuel dwindled, the flight experienced fuel exhaustion on two engines and then a complete loss of power leading to a forced landing attempt in a residential area near the airport. The aircraft collided with trees and structures, resulting in a post‑impact fire that caused multiple fatalities and injuries and extensive emergency response by Portland Fire & Rescue and Multnomah County emergency services.

Investigation and findings

The National Transportation Safety Board conducted a formal investigation examining cockpit voice recorder and flight data recorder information, maintenance logs, fuel receipts, and crew training records. The NTSB established a timeline from the landing gear indication through the holding pattern and determined fuel burn rates consistent with DC‑8 performance tables provided by McDonnell Douglas data archives and engine manufacturer specifications. Investigators interviewed air traffic controllers from the FAA facility and evaluated company procedures from United Airlines operations manuals. The NTSB issued a probable cause report attributing the accident to fuel exhaustion and highlighted human factors identified in contemporary studies by NASA and academic researchers at institutions such as Massachusetts Institute of Technology and Stanford University that had been contributing to aviation safety literature.

Causes and contributing factors

The NTSB identified the immediate cause as fuel exhaustion following an extended diversion of attention to a suspected landing gear problem, compounded by inadequate fuel monitoring. Contributing factors included breakdowns in cockpit communication among the captain, first officer, and flight engineer, influenced by hierarchical cockpit culture then common at legacy carriers including United Airlines. The report cited deficiencies in crew resource management, decision‑making under stress as analyzed in studies at University of California, Berkeley and Ohio State University, and operational oversight issues involving airline dispatch procedures and FAA fuel reserve guidance. Maintenance and design aspects, including the DC‑8 systems and gear indication circuitry referenced in manufacturer advisories from McDonnell Douglas and component suppliers, were evaluated but not singled out as primary causal elements.

Safety changes and legacy

The crash of Flight 173 became a seminal case driving the adoption of formalized Crew Resource Management training across major airlines such as United Airlines, Delta Air Lines, American Airlines, Pan American World Airways, and international carriers influenced by International Civil Aviation Organization guidance. Airlines incorporated CRM curricula developed with input from NASA and academic centers, emphasizing assertiveness, communication, and decision making between captains and junior crew, reflecting recommendations later echoed by the NTSB and the Federal Aviation Administration. The accident also influenced revisions to fuel reserve policies, cockpit checklist design, and pilot training standards promulgated by FAA rulemaking and industry groups like Air Transport Association of America. Flight 173 is cited in aviation safety literature alongside other influential accidents such as the 1977 Tenerife airport disaster and Air Florida Flight 90 as pivotal in transforming safety culture, training, and regulatory oversight globally.

Category:Airliner accidents and incidents in the United States Category:1978 in Oregon