FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 602 · Boeing 757-232

31 Jan 1997 · Atlanta, GA, United States

Boeing 757-232 · Incident: partial loss of engine power (mechanical failure) en route

From Hartsfield Jackson Atlanta International Airport (ATL) to Dallas Fort Worth International Airport (DFW)

Report a problem

Event

NTSB case
ATL97IA035
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
Incident
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

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
N611DL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hartsfield Jackson Atlanta International Airport (ATL)To Dallas Fort Worth International Airport (DFW), Dallas, TX
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 · climb to 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
Partial loss of engine power (mechanical failure)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Turbine assembly › Fatigue

Approximate · Estimated position: the centre of Atlanta, GA, the place the record names. Not the accident site.

NTSB narrative

After takeoff, the left engine experienced an uncontained failure of the Stage 1 High Pressure Turbine (HPT). The airplane returned safely and made a precautionary landing. After further examination of the engine, it was determined that the 'HPT disk blade retention lug had separated because of a low cycle fatigue fracture'. Both a Service Bulletin, PW2000 A72-592, and an Airworthiness Directive, TAD 97-11-51T, were issued to address this problem in this and other Pratt and Whitney engines.

Probable cause

failure of the Stage 1 High Pressure Turbine due to a fatigue fracture in a disk blade retention lug.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL97IA035
Event ID
20001208X07257
Case number
ATL97IA035
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. 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: 09de6ae52453157b3a7c08ed63ba5404b8126bde65f5b901d0ee786c363a15bc; retrieved 2026-09-18T17:42:43.707Z.