FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Delta Air Lines Flight 1036

23 Jun 2003 · Tampa, FL, United States

Boeing 757-232 · Accident while standing

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

Report a problem

Event

NTSB case
MIA03FA130
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
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
Visual 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
N633DL
Onboard fatalities
Unknown
Route
From Tampa International Airport (KTPA), Tampa, FLTo Hartsfield Jackson Atlanta International Airport (KATL), 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
Standing · engine(s) start-up
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
Miscellaneous/other
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

  • Passenger › Evacuation, initiated
  • Passenger › Instructions, written/verbal, disregarded

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

NTSB narrative

The airplane was pushed back from the gate and the left engine was started with no discrepancies reported. During the starting of the right engine, numerous passengers saw torching aft of the tailpipe. A commotion ensued which drew the attention of the three of the four flight attendants who reported seeing an orange glow either inside or outside the airplane. The captain later reported there were no abnormal engine indications in the cockpit, but he then secured the right engine. The captain secured the left engine after simultaneously noticing passengers on the ramp and illumination of entry door lights. A flight attendant reported a male passenger (who was bigger than her) approached her at door 2L and attempted to open the door by partially rotating the 2L door handle. The door did not open completely but was 'cracked.' The flight attendant eventually opened the door fully and locked it against the fuselage. The male passenger exited immediately, followed by several other passengers. She then opened the 2R door and passengers exited it as well. Passengers also evacuated the airplane via the 3L and 3R doors, which a flight attendant opened. Readout of the flight data recorder revealed that at the time the fuel cutoff switch for the right engine was recorded to be in the "run" position, the recorded fuel flow was 1,696 PPH. Within approximately 2 seconds of the right engine fuel cutoff switch being in the "run" position, the fuel flow was recorded to be 3,136 PPH. The maximum recorded fuel flow of 6,272 PPH occurred 2 seconds before the fuel cutoff switch was recorded to be in the "cutoff" position, or 24 seconds after the fuel cutoff switch was in the "run" position. In contrast, within 4 seconds of the left engine fuel cutoff switch being in the "run" position for engine start, the recorded fuel flow was 544 PPH. Further review of the previous eight engine starts revealed the left and right fuel flows were nearly matched, with no recorded fuel flow value greater than 580 PPH within the first 4 seconds after the fuel cutoff switch was recorded to be in the "run" position. The flight crews are trained that during hot starts, the fuel flow almost immediately exceeds 700PPH. The engine start procedures checklist indicates the engine start is to be aborted if abnormally high or fluctuation fuel flow is noted.

Probable cause

a torching of the right engine caused by an abnormally high flow fuel during engine start for undetermined reasons. The torching resulted in an unwarranted evacuation of the airplane and serious injuries to three passengers . A contributing factor in the accident was the failure of the flightcrew to abort the engine start due to abnormally high fuel flow indication during the right engine start.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03FA130
Event ID
20030702X00998
Case number
MIA03FA130
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, coordinates, 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: af1ffc01143371e54be923efdd4ff4b9a363d3176a40336335c266b32d60b7a4; retrieved 2026-09-18T15:45:38.981Z.