FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FedEx Express Flight 597

4 Apr 2006 · Memphis, TN, United States

McDonnell Douglas DC10 10F · Accident: total loss of engine power (mechanical failure) en route

From Frederick W. Smith International Airport (MEM) to Seattle–Tacoma International Airport (SEA)

Report a problem

Event

NTSB case
DCA06FA033
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

McDonnell Douglas DC10 10F

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
N386FE
Onboard fatalities
Unknown
Route
From Frederick W. Smith International Airport (MEM), Memphis, TNTo Seattle–Tacoma International Airport (SEA), Seattle, WA
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
Total 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
Substantial

Cause areas

  • Miscellaneous, engine uncontained failure › Fatigue
  • Turbine assembly, shaft › Fractured
  • Turbine assembly, turbine wheel › Improper/poor weld

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

As the airplane climbed through about FL260, the No. 3 engine low pressure turbine (LPT) stage 1 disk burst when a fatigue crack that initiated in the forward seal tooth serration arm ruptured. Fragments from the burst disk partially severed the LPT case and struck the fuselage in multiple locations. The airframe vibration increased to a severe level until the LPT rotor separated from the engine, about 14 minutes 30 seconds after the uncontained LPT stage 1 disk burst, when the high pressure turbine aft shaft and the fan mid shaft failed due to contact damage and torsional loading. Metallurgical examination of the portion of the LPT stage 1 disk that was imbedded in the right wing found that the disk burst due to a mixture of high cycle and low cycle fatigue. The fracture was located in the vicinity of the forward seal tooth serration, although the exact fracture origin could not be identified because the entire seal tooth and part of the seal tooth arm were missing at the fracture location. Examination of the forward seal tooth serration revealed the presence of two previous weld repairs that extended into the forward arm. Review of the manufacturing records revealed that the disk had been dabber weld repaired twice to correct anomalies and non-conformances found during the original manufacturing process. The dabber weld procedures did not authorize welding in the forward seal tooth serration, therefore, the weld repair performed on the failed LPT stage 1 disk did not conform to the approved repair instructions. Based on testing and analysis of sample, post-manufacture dabber weld repaired disks, the suspect population of CF6 disks was confined to those that had been repaired at original manufacture. Records indicated that, in addition to the accident disk, four other disks had been dabber weld repaired at original manufacture to correct forward seal tooth serration anomalies and non-conformances. None of these disks are any longer in service. Based on the estimated crack propagation rate, it is likely that either no crack existed at the last inspection of the disk or the crack size was below the reasonably detectable threshold. After the disk burst, the flight crew completed all required checklists; however, the crew could not manually shutdown the affected engine because the burst disk fragments had severed the fire shutoff valve cable, the power off cable, and the emergency shutoff cable. The engine eventually shutdown on its own due to airflow disruptions within the engine. The flight crew’s procedural coordination and use of available resources, consistent with cockpit resource management best practices, helped to ensure the safe landing of the airplane.

Probable cause

The rupture of a fatigue crack in the forward air seal tooth serration of the No. 3 engine low pressure turbine stage 1 disk that initiated due to an improper weld repair performed during original manufacture. The improper weld repair changed the material properties of the disk near the weld feature, resulting in an accelerated crack propagation rate that allowed the crack to grow to rupture before the next inspection interval. Contributing to the severity of the accident was the inability of the flight crew to shutdown the engine as a result of the damage caused by a liberated piece of the low pressure turbine stage 1 disk when it punctured the right wing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA06FA033
Event ID
20060504X00511
Case number
DCA06FA033
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: d0dcb142b539d4635a34b117b1b6dd350de4b7d31bc514758d256944132d1fba; retrieved 2026-09-18T14:54:16.035Z.