aviation-safety

What to Know About the DC Plane Crash on Wikipedia

The Wikipedia coverage of the Air Florida Flight 90 crash in Washington, D.C., on January 13, 1982, offers a detailed, fact-based account of a major urban aviation disaster. Thi...

Mara Ellison
What to Know About the DC Plane Crash on Wikipedia

The Wikipedia coverage of the Air Florida Flight 90 crash in Washington, D.C., on January 13, 1982, offers a detailed, fact-based account of a major urban aviation disaster. This summary presents the essential verified details while framing the event through official investigations and long-term consequences. The article explains how a poorly deiced aircraft failed shortly after takeoff, colliding with traffic and a bridge in freezing conditions. Readers gain an answer-first overview backed by investigative records, timelines, and lasting policy impacts that reshaped aviation safety and emergency response in the region.

Key Event Details

On the afternoon of January 13, 1982, an Air Florida Boeing 737-222 crashed in Washington, D.C., shortly after liftoff from National Airport in heavy snow and freezing rain. The commuter flight, bound for Tampa with a stop in Orlando, carried 74 passengers and 5 crew. Within a minute of takeoff, it struck the 14th Street Bridge and then crashed into the Potomac River near the Pentagon. The accident claimed 78 lives, including four motorists on the bridge, and injured multiple survivors who were pulled from the icy river.

Flight Data Snapshot

AttributeVerified DetailSource Type
AircraftBoeing 737-222 (registration N62AF)Official NTSB report
RouteNational Airport (DCA) → Tampa (TPA) with Orlando (MCO) stopFlight manifest
Departure Time16:00 EST, January 13, 1982ATC logs
Fatalities78 total (74 aboard + 4 bridge occupants)NTSB/FAA records
WeatherHeavy snow, freezing rain, low visibilityMETAR/TAF data

Immediate Causes and Contributing Factors

The National Transportation Safety Board (NTSB) determined the primary cause was pilot failure to deice the aircraft properly in freezing precipitation. The flight crew followed company procedures that inadvertently left dangerous ice on the wings and tail. Contributing factors included inadequate anti-icing protocols at the airline, delayed communication of rapidly changing weather, and ATC workload. The small initial deviation—ice increasing drag and reducing lift—became catastrophic when an engine failed and the crew reacted too slowly to maintain control.

Critical Timeline

  • 14:00 — Flight pushback and preflight activities at National Airport under freezing conditions.
  • 15:55 — Ground crew completes late partial deicing due to traffic and communication gaps.
  • 16:00 — Flight 90 takes off, encounters immediate control difficulties.
  • 16:01 — Aircraft strikes the 14th Street Bridge, causing localized damage.
  • 16:02 — Crashes into the Potomac River; immediate rescue operations begin.
  • 16:30 — First survivor rescued; extensive multi-agency response follows.

Rescue and Emergency Response

The rescue effort became a defining image of the disaster, with emergency responders working on ice-choked waters beneath freezing temperatures. Survivors and bystanders formed human rescue chains on the bridge to pull victims from the river. Helicopters from multiple agencies executed daring hoist operations in low visibility. The rapid coordination among police, fire, EMS, and federal agencies likely saved additional lives, yet the exposure and cold delayed treatment for many survivors, complicating medical outcomes.

Investigations and Official Findings

The NTSB investigation produced a thorough report outlining mechanical, procedural, and human factors. Cockpit voice recorder transcripts revealed confusion about flap settings and takeoff speeds under ice-contaminated conditions. Flight data recorder analysis showed the aircraft never achieved a stable climb. The investigation reinforced the need for clearer anti-icing checklists, better crew resource management, and improved dissemination of terminal area weather changes. Regulators subsequently tightened rules around ground deicing in cold weather operations.

Investigation Outcomes

CategoryFindingImpact
Pilot ProceduresInadequate flap setting and speed checksRevised training and checklist requirements
Deicing ProcessLate and incomplete wing anti-icingStricter ground deicing protocols
Weather InformationTimely updates not consistently relayedImproved ATC and airline weather sharing
Emergency CoordinationMulti-agency response effective but improvableEnhanced regional disaster planning

Long-Term Safety and Policy Impact

The crash directly influenced aviation safety reforms across the United States. Regulators introduced more robust ground deicing procedures, required explicit confirmation of anti-icing measures before takeoff, and improved the sharing of terminal weather information. Airline training programs enhanced emphasis on ice-related performance loss and crew assertiveness. The National Transportation Safety Board used this accident to advocate for broader changes in cold-weather operations, influencing later guidance that remains referenced in current aviation guidance documents.

Legacy and Memorial

  • National memorials along the Potomac honor the victims, including the Arlington Memorial Bridge vicinity.
  • Revised FAA Advisory Circulars on ground deicing reflect lessons learned from this crash.
  • Survivor advocacy and family groups contributed to ongoing improvements in victim support and crash victim compensation frameworks.
  • The event remains a case study in human factors, engineering, and emergency management programs.

Common Misconceptions and Clarifications

Some discussions mistakenly attribute the crash solely to weather, overlooking procedural and training gaps. Others overstate the role of airframe icing without acknowledging the sequence of human and operational failures. The Wikipedia article emphasizes the systemic nature of the accident, showing how weather, maintenance schedules, company procedures, and individual decision-making interacted. Understanding these layers helps clarify how preventable errors can cascade into tragedy even in routine operations.

Comparative Context

Compared with other U.S. icing-related accidents in the early 1980s, the DC plane crash stands out for its location in a major urban area and the visible, immediate rescue response. While accidents involving ice and takeoff performance have occurred elsewhere, this crash uniquely influenced regional policy and public awareness in the national capital. Subsequent investigations of similar events frequently reference the lessons drawn from this accident when recommending procedural changes and training updates.

Related Reading

More pages in this topic cluster.

Drone Airport Cancel: What This Status Means for Operators and Airspace Users

Drone airport cancel status indicates a planned or immediate suspension of drone operations at a specific airfield or vertiport, typically issued to manage airspace risk, coordi...

Read next
Understanding North Carolina Plane Crash Reporting and Safety Context

When a plane crash occurs in North Carolina, multiple agencies move quickly to secure the site, preserve evidence, and inform the public. These investigations are led by the Nat...

Read next
Southwest Airlines Near Miss: What It Means and How the Airline Responds

A near miss in aviation is an incident where safety margins were unacceptably small but no collision, ground contact, or loss of control occurred. For Southwest Airlines, these...

Read next