ValuJet Flight 597
Douglas DC-9-32 · Accident: airframe, component or system failure during takeoff
From Hartsfield Jackson Atlanta International Airport (ATL) to Miami International Airport (MIA)
Event
- NTSB case
- ATL95MA106
- 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
- Visual Meteorological Cond
Douglas DC-9-32
- Aircraft type
- Douglas DC-9
- 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
- N908VJ
- Operator
- ValuJet
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (ATL)To Miami International Airport (MIA), Miami, FL
- 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
- Takeoff · roll/run
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Compressor assembly, rotor disc › Failure
- Compressor assembly, rotor disc › Fatigue
- Other maintenance personnel › Maintenance, inspection, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
As ValuJet Flight 597 began its takeoff roll, a 'loud Bang' was heard by the occupants, the right engine fire warning light illuminated, the crew of a following airplane reported to the ValuJet crew that the right engine was on fire, and the takeoff was rejected. Shrapnel from the right engine penetrated the fuselage and the right engine main fuel line, and a cabin fire erupted. The airplane was stopped on the runway, and the captain ordered evacuation of the airplane. A flight attendant (F/A) received serious puncture wounds from shrapnel and thermal injuries; another F/A and 5 passengers received minor injuries. Investigation revealed that an uncontained failure of the right engine had occurred due to fatigue failure of its 7th stage high compressor disc. The fatigue originated at a stress redistribution hole in the disc. Analysis of fatigue striation measurements indicated that the fatigue crack had originated before the disc was last overhauled at a repair station (Turk Hava Yollari) in 1991, but was not detected. Also, investigation of the repair station revealed evidence concerning a lack of adequate recordkeeping and a failure to use 'process sheets' to document the step-by-step overhaul/inspection procedures. (See NTSB/AAR-96/03 for additional information)
Probable cause
failure of Turk Hava Yollari maintenance and inspection personnel to perform a proper inspection of a 7th stage high compressor disc, thus allowing the detectable crack to grow to a length at which the disc ruptured, under normal operating conditions, propelling engine fragments into the fuselage; the fragments severed the right engine main fuel line, which resulted in a fire that rapidly engulfed the cabin area. The lack of an adequate recordkeeping system and the failure to use 'process sheets' to document the step-by-step overhaul/inspection procedures contributed to the failure to detect the crack and, thus, to the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL95MA106
- Event ID
- 20001207X03623
- Case number
- ATL95MA106
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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. 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: 28bad8995e7b10b1cb5c04f0fdfb8c21753acfe6753a9908629189d4332afe75; retrieved 2026-09-18T18:00:11.800Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: operator. The NTSB narrative names the operator: "As ValuJet Flight 597 began its takeoff roll"