aviation-safety

Air Florida Flight 90 Crash (1982): Verified Facts, Timeline, and Lasting Lessons

On January 13, 1982, Air Florida Flight 90, a Boeing 737-200, crashed shortly after takeoff from Washington National Airport in a dense winter storm. People remember it both as...

Mara Ellison
Air Florida Flight 90 Crash (1982): Verified Facts, Timeline, and Lasting Lessons

Overview and Immediate Context

On January 13, 1982, Air Florida Flight 90, a Boeing 737-200, crashed shortly after takeoff from Washington National Airport in a dense winter storm. People remember it both as a local disaster in the United States’ capital region and as a case study in how procedural and decision-making failures can undermine safety. This page provides a long‑form, evergreen explanation of the crash’s circumstances, investigation findings, and lasting impact on aviation safety.

Flight and Aircraft Details

Flight Information

Air Florida Flight 90 was a regularly scheduled domestic passenger flight from Washington National Airport (DCA) to Fort Lauderdale–Hollywood International Airport (FLL) with a planned stop in Tampa (TPA). The flight typically operated with a cockpit crew of two and a cabin crew responsible for passenger safety. On the day of the accident, the airplane was a Boeing 737‑200, a narrow‑body twin‑engine jet common in U.S. short‑ and medium‑haul service in the early 1980s.

Aircraft Registration and Condition

  • Registration: N62AF
  • Manufacturer and model: Boeing 737‑200
  • Age at time of accident: Approximately 5 years old
  • Maintenance status: The aircraft was within approved maintenance programs; no outstanding safety directives directly linked to the accident were identified

Accident Timeline and Sequence of Events

The accident sequence unfolded in a matter of minutes in severe winter weather. The following timeline captures the key moments based on official investigations.

Time (approximate) Event Why It Matters
16:00 local Flight 90 begins pushback and requests clearance Sets up departure in adverse weather
16:16 Cleared for takeoff from Runway 36 Official authorization under instrument conditions
16:18–16:20 Takeoff roll; aircraft becomes airborne briefly, then settles back onto runway and crashes into 14th Street Bridge Critical phase where multiple errors culminate in loss of control
16:21 Emergency declared; rescue operations begin Response efforts under difficult weather and traffic conditions

The airplane failed to gain and maintain sufficient altitude during the initial climb. After briefly becoming airborne, it descended, struck runway edge lights, collided with the 14th Street Bridge, and fell into the Potomac River. The sequence highlighted how weather, crew decisions, and aircraft performance interacted catastrophically.

Weather, Performance, and Contributing Factors

Weather Conditions at Washington National

Near‑freezing temperatures produced ice and sleet on airport surfaces. A persistent precipitation layer reduced visibility and created icing conditions on exposed structures. These conditions degrade aerodynamic performance and increase takeoff distance, which were critical in a heavily loaded aircraft operating with conservative performance margins.

Aircraft Performance and Takeoff Calculations

Investigators found that the computed takeoff speeds and thrust settings did not adequately account for the combined effects of ice on wings and engines, as well as the weak engine performance in cold weather. Misapplied performance data and an incorrect assumption about remaining runway length reduced the margin for safe continuation of the takeoff.

Operational and Procedural Issues

  • Failure to deice the aircraft surfaces in a thorough and timely manner
  • Use of incorrect performance data during calculations
  • Inadequate coordination between cockpit and ground personnel
  • Insufficient pilot response to abnormal indications during the takeoff roll

Investigation Findings and Official Conclusions

The National Transportation Safety Board (NTSB) led the investigation and concluded that the probable cause centered on the flight crew’s failure to use engine anti‑icing and to properly calculate takeoff performance under icing conditions. Contributing factors included airport failure to deice the aircraft promptly and ATC procedures that did not adequately address known weather‑related risks at the time. The report emphasized that multiple small failures aligned to produce a severe outcome.

Casualties, Rescue, and Aftermath

Of the 74 passengers and 4 crew aboard, 78 people died, including four occupants of vehicles on the 14th Street Bridge who were struck by the airplane. Five passengers and one flight attendant survived after rescue operations in the freezing river. The accident spurred changes in emergency coordination and cold‑weather operational guidance across U.S. airports.

Metric Detail Source Type
Passengers and crew onboard 78 Official inventory
Fatalities 78 Investigation report
Survivors 5 passengers, 1 flight attendant Investigation report
Bridges and vehicles affected 14th Street Bridge; multiple vehicles Official narratives

Safety, Policy, and Enduring Impact

In the wake of the crash, regulators and the industry introduced stronger safeguards for cold‑weather operations. Key changes included more stringent deicing procedures, clearer performance calculation guidance under icing conditions, and improved coordination requirements between flight crews and ground staff. The accident became a benchmark case in crew resource management and decision‑making, emphasizing that compliance with procedures and timely communication are as vital as technical skill.

Lessons Learned and Relevance Today

Air Florida Flight 90 remains a reference point in aviation safety training because it illustrates how procedural shortcuts, misunderstood performance data, and environmental pressures can combine into disaster. Modern training programs use the accident to teach checklist discipline, assertive communication, and risk assessment in marginal weather. For travelers and professionals, the crash underscores the importance of robust procedures, especially when conditions challenge aircraft performance and human judgment alike.

Summary of Key Verified Details

Attribute Verified Detail Source Type
Date January 13, 1982 Official records
Location Washington National Airport (DCA), 14th Street Bridge, Potomac River Investigation maps
Aircraft Boeing 737‑200, registration N62AF Registration databases
Occupants 78 total (74 passengers, 4 crew) Official inventory
Fatalities 78 NTSB accident report
Primary cause Failure to use anti‑icing and incorrect takeoff performance calculations in icing conditions NTSB final report

Related Reading

More pages in this topic cluster.

Savannah Aircraft Crash: What We Know and How These Incidents Are Investigated

Savannah aircraft crash incidents refer to aviation accidents or serious occurrences associated with Savannah, Georgia, typically involving local airports such as Savannah/Hilto...

Read next
What Happens When a Pilot Is Arrested at an Airport: Procedures, Consequences, and Real Cases

When a pilot is arrested at an airport, it raises immediate questions about safety, professionalism, and how the aviation system responds. This guide explains the typical proced...

Read next
How Old Was the UPS Plane That Crashed: Verified Age and Key Facts

On September 3, 2010, UPS Airlines Flight 6, a Boeing 747–400F registered as N571UP, crashed near Dubai while operating a scheduled cargo service. The aircraft was 28 years ol...

Read next