Delta Air Lines Boeing 757-232 accident
Boeing 757-232 · Accident: in flight encounter with weather en route
From Orlando International Airport (MCO) to Hartsfield Jackson Atlanta International Airport (ATL)
Event
- NTSB case
- ATL91LA123
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Boeing 757-232
- Aircraft type
- Boeing 757
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N605DL
- Operator
- Delta Air Lines
- Onboard fatalities
- Unknown
- Route
- From Orlando International Airport (MCO), Orlando, FLTo Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Weather condition › Thunderstorm
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOTS REPORTED THAT THEY WERE DEVIATING AROUND TWO THUNDERSTORM CELLS LOCATED 20 TO 25 MILES EAST OF THEIR POSITION. AS THEY CAME OUT OF THE BOTTOM OF A CIRRUS LAYER, THEY OBSERVED A DISSIPATING CUMULUS CLOUD IN THEIR FLIGHT PATH. THIS CLOUD WAS NOT OBSERVED ON THEIR WEATHER RADAR, AND AVOIDANCE WOULD HAVE REQUIRED AN ABRUPT, VIOLENT MANEUVER. THE FLIGHT CREW ACTIVATED THE SEAT BELT SIGN JUST PRIOR TO CLOUD PENETRATION. THE FLIGHT EXPERIENCED A TURBULENCE EPISODE OF ABOUT FOUR SECONDS IN DURATION. A FEMALE PASSENGER, WHO WAS ENTERING THE LAVATORY AT THE TIME CAUGHT HER FOOT IN THE LAVATORY DOOR, BREAKING HER ANKLE.
Probable cause
TURBULENCE IN CLOUDS, WHICH WAS ASSOCIATED WITH A DISSIPATING THUNDERSTORM.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL91LA123
- Event ID
- 20001212X17434
- Case number
- ATL91LA123
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ae29ca938cb2149091c32c2076ee59e4dbea03878297a8c7bd10a13a97fd1dd7; retrieved 2026-09-18T18:53:58.707Z.