Boeing 747-132 accident near Lake Michigan, October 21, 2004
On October 21, 2004 at about 1:29 am local time, a Boeing 747-132, registered N709CK, was substantially damaged in an accident near Lake Michigan. It was flown under scheduled airline rules (Part 121). No one was hurt; 5 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The number one engine separated from the airplane during climb due to the uncontained separation of a portion of the second stage turbine disk rim after the second stage turbine vanes contacted the disk. The second stage turbine vanes contacted the second stage turbine disk due to the operator's inadequate inspection of the high pressure turbine module and the improper repair of the module by unknown maintenance personnel.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 21, 2004 · about 1:29 am local time
- Place
- Lake Michigan · map
- Type
- Accident
- Injuries
- No one was hurt; 5 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Boeing 747-132 · all 747-132s on the register
- Registration
- N709CK · registry record · serial 20247
- Damage
- Substantial damage
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative final · quoted from the NTSB record
The Boeing 747-132, operated as an unscheduled domestic cargo flight under 14 CFR Part 121, was climbing through 15,000 feet mean sea level when the number one engine separated from its forward and aft engine mounts resulting in substantial damage to the airplane. The flight diverted to an alternate airport where it landed without further incident. Examination of the engine revealed an uncontained separation of an approximately 180-degree arc of the second stage turbine disk rim. The missing section of the rim coincided with circumferential rub marks on the second stage turbine disk that corresponded to rub marks on the rear inner rails of the second stage turbine vanes. The rubbed areas of the disk and vanes did not exhibit heat cracking consistent with a relatively long time period of rubbing relative to a sudden disk-to-vane contact. The fan rotor bearing did not exhibit rotational distress. The engine did not exhibit any evidence of a blade separation, case rupture, or any other uncontainment. The second stage retaining bolts are coated with a baked-on antiseize compound, FelPro C-200, during manufacture. Metallurgical exam of the second stage turbine bolts revealed cracking in the head-to-shank fillet radius and the presence of silver consistent with Silver Goop. Silver Goop is an anti-seize compound not authorized by the engine manufacturer for use in the high-pressure turbine area but is authorized in the low-pressure compressor area due to the catalytic properties of silver with wet FelPro C-200 resulting in a corrosive mixture that can contribute to bolt fractures. The induced loads from the second stage disk rim separation were estimated to have been 3.6 - 6.6 times greater than to those induced by a fan blade separation. The accident operator purchased an engine as-is and that according to maintenance records was not preserved when it was removed from an airplane belonging to another operator about 5 years prior to the accident. The high-pressure turbine (HPT) module was removed from this engine and installed on one of the accident operator's other engines prior to it being removed and then installed on the accident airplane engine. The accident operator's examination of the HPT was limited to a visual inspection that would not have detected a vane shift or ascertained the integrity second stage turbine vane assembly.
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
Pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land
- Flight time: 10,015 hours in all; 4,000 in this make and model; 180 in the last 90 days; 73 in the last 30 days; 8,000 as pilot in command
- Medical certificate: Class 1
- Seat: left
- Injury: no injuries
Co-pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land
- Flight time: 8,300 hours in all; 247 in the last 90 days; 56 in the last 30 days
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rgt
- Injury: no injuries
Flight Engineer
- Injury: no injuries
The aircraft
- Airframe total time: 93,548.7 hours
- Last inspection: continuous airworthiness programme, October 1, 2004; 94.1 hours since
- Seats: 7
- Landing gear: retractable
- Engine 1: Pratt & Whitney JT9D-7A (turbofan); 0 hours total
- Engine 2: Pratt & Whitney JT9D-7A (turbofan); 0 hours total
- Engine 3: Pratt & Whitney JT9D-7A (turbofan); 0 hours total
- Engine 4: Pratt & Whitney JT9D-7A (turbofan); 0 hours total
The flight
- Departed from: ORD Chicago IL at 1:10 am
- Destination: JFK New York NY
- Flight plan: IFR
- A second pilot was aboard
Weather at the time
- Light: night
- Visibility: 10 statute miles
- Sky: overcast at 1,700 ft; clear
- Temperature: 52°F (11°C), dew point 46°F (8°C)
- Altimeter: 30.12 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 5 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
