FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Delta Air Lines Flight 1253

28 Mar 2024 · Lakeland, GA, United States Possible conflict

Boeing 757-232 · Accident: turbulence encounter en route

From Hartsfield Jackson Atlanta International Airport (KATL) to Tampa International Airport (KTPA)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
DCA24LA135
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
Event fatalities
Unknown
Ground fatalities
Unknown
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
N6705Y
Onboard fatalities
Unknown
Route
From Hartsfield Jackson Atlanta International Airport (KATL), Atlanta, GATo Tampa International Airport (KTPA), Tampa, FL
Aircraft age
About 24 years (built 2000)
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
Defining eventThe 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
Turbulence encounter
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

  • Environmental issues › Conditions/weather/phenomena

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Delta Air Lines flight 1253 was cleared direct to KRVUR to join the DADES1 arrival at FL 330. While flying direct to KRVUR, the flight crew said that Federal Aviation Administration (FAA) Air Traffic Control (ATC) gave the flight permission to descend to FL 310. As the airplane was descending, it approached some clouds that were visible in the moon light, and the captain activated the seat belt sign, and made a brief announcement as a precaution. The flight crew said that they then requested that ATC allow them to deviate to the left to avoid the highest cloud peaks that they could see, however at no time did the weather radar indicate any significant moisture returns. The flight crew said they were unable to avoid entering the clouds and the flight briefly encountered “moderate” turbulence. As the flight exited those cloud tops, they then saw more clouds ahead, along with some indirect lightning nearby. The captain made an announcement to the cabin for the flight attendants (FAs) to take their jump seats, and about a minute later they entered the next set of cloud tops and experienced brief, but severe turbulence. The first officer (FO) said that the turbulence encounter lasted about 10 to 15 seconds with the altitude deviating a little, and the airplane rolling about 10 to 15 degrees. He also added that the auto throttle system, increased the thrust setting, which required that they reduce it manually.

After the turbulence event, the flight crew stated that they received a call from the cabin crew notifying them that a FA was injured. The injured FA stated that after completing cabin service they stowed the beverage carts in the back galley and within one minute of stowing the carts, they encountered “very severe” and unexpected turbulence. He said that the seatbelt sign was off, and he could not sit in the jump seats closest to him because they were all occupied by other flight attendants. He added that the flight was full and there were no passenger seats available as well, and the only available jump seats were far away. He said that as he reached to grab a handle near the carts he was suddenly thrown by the turbulence. He hit his head on the ceiling and came down on his right foot, resulting in a broken fibula.

After the turbulence ended the flight crew gathered more information from the cabin and made a pilot report (PIREP) to ATC indicating that there was an injured FA aboard and requested that emergency medical services personnel meet the airplane at the gate. The first officer added that from his perspective, there was no indication of possible turbulence in the vicinity, and if it wasn't for the moon light making the clouds visible, the seat belt sign would most likely have not been activated, because the radar showed no reflection of moisture in the clouds.

Probable cause

An inadvertent encounter with convective turbulence that resulted in a serious injury to a flight attendant.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA24LA135
Event ID
20240328194001
Case number
DCA24LA135
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates, cause areas, damage. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: eed7071138011cfe6c3575b124128056e7a980dd44441703893d649e07bebadf; retrieved 2026-09-16T18:37:48.201Z.