What Is 1965 United Airlines flight 389 crash
Content on WhatAnswers is provided "as is" for informational purposes. While we strive for accuracy, we make no guarantees. Content is AI-assisted and should not be used as professional advice.
Last updated: April 15, 2026
Key Facts
- Flight 389 crashed on August 16, 1965, at 10:19 PM
- All 30 on board (25 passengers, 5 crew) perished
- The aircraft was a Douglas DC-8-12, registration N8032U
- Crash occurred 1.7 miles short of runway 27R at O'Hare
- No survivors; cause attributed to pilot error and descent below minimums
Overview
United Airlines Flight 389 was a scheduled domestic passenger flight from New York's LaGuardia Airport to Chicago's O'Hare International Airport. On August 16, 1965, the flight ended in tragedy when the aircraft crashed into Lake Michigan during its final approach.
The Douglas DC-8-12, operating as Flight 389, descended below the minimum safe altitude and struck the water just 1.7 miles from the runway threshold. Poor visibility and possible miscommunication contributed to the accident, which claimed all 30 lives on board.
- August 16, 1965, at 10:19 PM: The crash occurred during nighttime hours in marginal weather conditions over Lake Michigan.
- All 30 fatalities: There were 25 passengers and 5 crew members on board, none of whom survived the impact.
- Flight route: The aircraft departed from LaGuardia Airport, New York, bound for O'Hare International Airport, Chicago.
- Aircraft type: A Douglas DC-8-12, a four-engine jetliner operated by United Airlines, registered as N8032U.
- Crash location: The plane struck Lake Michigan approximately 1.7 miles short of runway 27R at O'Hare Airport.
Investigation and Findings
The National Transportation Safety Board (NTSB) conducted a thorough investigation into the cause of the crash, analyzing flight data, weather conditions, and crew communications.
- Pilot error: The NTSB concluded that the flight crew descended below the minimum descent altitude without visual contact with the runway environment.
- Descent below minimums: The aircraft was cleared for a non-precision approach but descended to 600 feet, well below the 1,000-foot minimum.
- Weather conditions: Visibility was reduced due to fog and haze, with ceilings around 1,000 feet, complicating visual acquisition of the runway.
- Navigation aids: The crew relied on the VOR/DME approach to runway 27R, but failed to maintain proper altitude discipline.
- Communication issues: There was no evidence of distress calls or emergency transmissions before impact, suggesting a sudden or unnoticed descent.
- Final report: Released in 1966, the NTSB report cited the captain’s decision to continue descent without required visual references as the probable cause.
Comparison at a Glance
Flight 389 compared to similar incidents of the era reveals patterns in approach-related accidents during the jet age’s early years.
| Incident | Date | Aircraft | Fatalities | Primary Cause |
|---|---|---|---|---|
| United 389 | August 16, 1965 | DC-8-12 | 30 | Pilot error, descent below minimums |
| Eastern 304 | April 27, 1965 | DC-8-05 | 58 | Thunderstorm encounter, loss of control |
| Braniff 250 | May 3, 1966 | DC-9-14 | 42 | Wind shear from thunderstorm |
| Pan Am 214 | December 8, 1963 | Boeing 707 | 81 | Lightning strike, fuel tank ignition |
| TWA 553 | March 9, 1967 | DC-9-15 | 85 | Air traffic control error, mid-air collision |
These cases highlight the evolving challenges of jet aviation in the 1960s, including weather interpretation, instrument approach discipline, and air traffic coordination. Flight 389 stands out for its clear attribution to procedural deviation during approach, a common factor in many accidents of that decade.
Why It Matters
The crash of Flight 389 had lasting implications for aviation safety, contributing to changes in pilot training and instrument approach procedures.
- Improved training: Airlines began emphasizing strict adherence to minimum descent altitudes during non-precision approaches.
- Enhanced instrumentation: The incident accelerated the adoption of ground proximity warning systems in commercial fleets.
- Procedural reforms: The FAA revised approach clearance protocols to reduce ambiguity in altitude assignments.
- Weather reporting: Better real-time weather updates were integrated into air traffic control systems.
- Safety culture: The accident underscored the need for crew resource management, though formal CRM programs came later.
- Historical significance: Flight 389 is cited in aviation safety studies as a key example of controlled flight into terrain (CFIT).
The lessons from United 389 helped shape modern aviation safety standards, reducing approach-related accidents in subsequent decades.
More What Is in Daily Life
Also in Daily Life
- Difference between bunny and rabbit
- Is it safe to be in a room with an ionizer
- Difference between data and information
- Difference between equality and equity
- Difference between emperor and king
- Difference between git fetch and git pull
- How To Save Money
- Does "I'm 20 out" mean youre 20 minutes away from where you left, or youre 20 minutes away from your destination
More "What Is" Questions
Trending on WhatAnswers
Browse by Topic
Browse by Question Type
Sources
- WikipediaCC-BY-SA-4.0
Missing an answer?
Suggest a question and we'll generate an answer for it.