Mcdonnell Douglas MD-10-30F incident near Portland, Oregon, February 13, 2012
On February 13, 2012 at about 8:00 pm local time, a Mcdonnell Douglas MD-10-30F, registered N304FE, suffered minor damage in an incident during takeoff near Portland, Oregon (Portland Intl Jetport airport). It was flown under scheduled airline rules (Part 121). The NTSB record does not give the injuries. The weather was conditions the NTSB did not record.
The NTSB's probable cause their words, unchanged
The fracture of the fan mid shaft due to a stress corrosion cracking initiated by local regions of corrosion pitting, which resulted from oil migration within the shaft and its subsequent degradation.
Source: NTSB aviation accident database, copy made October 12, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 13, 2012 · about 8:00 pm local time · cases in 2012
- Place
- Portland, Oregon · Portland Intl Jetport · cases near this airport · map
- Type
- Incident
- Injuries
- The NTSB record does not give the injuries.
- Weather
- conditions the NTSB did not record
- Aircraft
- Mcdonnell Douglas MD-10-30F · all MD-10-30Fs on the register
- Registration
- N304FE · registry record · serial 46992
- Damage
- Minor damage
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative final · quoted from the NTSB record
On February 13, 2012, a FedEx McDonnell Douglas (Boeing) MD10-30, registration number N304FE, equipped with three General Electric (GE) CF6-50 turbofans engines, performed a rejected take-off due to a failure of the No. 1 (left) engine. No injuries were reported. The incident flight was a regularly scheduled domestic cargo flight, operated under the provisions of Title 14 CFR Part 121, from Portland to Oakland, California. Examination of the airplane revealed no damage or penetration of the cowlings and no damage to the airplane; however, examination of the engine revealed three penetration holes and tears in low pressure turbine case and a single hole located in the turbine rear frame. Disassembly of the incident engine found that the fan mid shaft had fractured and the aft section of the fan mid shaft exhibited a spiral crack angled 45° to the longitudinal axis that measured about 69.5-inches in total length (about 3½ revolutions around the shaft) and extended about 20.5-inches axially in length. Metallurgical examination of the fan mid shaft found that it had fractured entirely in an intergranular mode. The initiation of the spiral fracture was comprised of numerous discolored, thumbnail shaped cracks initiating from the inner diameter surface of the fan mid shaft, some of which had progressed through the fan mid shaft thickness. The morphology of the cracks was consistent with a stress corrosion cracking mechanisms typical of high strength steel such as the fan mid shaft parent material. Localized areas of corrosion pitting, scaling, and loss of the anti-corrosion coating were observed throughout the inner diameter of the fan mid shaft. Examination of the debris within the shaft identified it as an ester based engine oil residue, typical of the kind of oil used in turbine engines. The stress corrosion cracking observed on the fan mid shaft was caused primarily due to the breakdown of a synthetic oil product inside the FMS during both storage and engine operation. The exact source or mechanism by which the oil entered the dry cavity between the fan mid shaft and the center vent tube is unknown.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Uncontained engine failure during takeoff defining event
- Powerplant sys/comp malf/fail during takeoff
- Fire/smoke (non-impact) during takeoff
- Engine shutdown during takeoff
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Maintenance personnel
- cause Personnel issues › Task performance › Maintenance › Installation › Maintenance personnel
- factor Aircraft › Aircraft power plant › Engine (turbine/turboprop) › (general) › Related maintenance info other cases naming the engine
The aircraft
- Seats: 385
- Landing gear: fixed
- Engine: Ge CF6-50C2 (turbofan); 0 hours total
- Operator: Federal Express Corporation
The flight
- Departed from: PDX Portland OR
- Destination: OAK Oakland CA
- Flight plan: IFR
Weather at the time
- Light: not reported
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- N304FE on the register today · the tail number may have moved to another aircraft since
- Mcdonnell Douglas MD-10 15 registered today · the model family and its accident history
- Mcdonnell Douglas 254 aircraft on the register
- Engine: Ge CF6-50C2 10 aircraft carry this series today · as the NTSB recorded it
- Portland International Jetport · nearest airport
- Portland International · departed from
- Oakland San Francisco Bay Airport · bound for
- Accidents and incidents in Oregon 1,862 since 1982 · 277 in the last ten years
- Oregon 7,012 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ENG12IA012.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
