Mcdonnell Douglas Helicopters 369E accident near Columbus, Ohio, August 19, 2006
On August 19, 2006 at about 8:39 pm local time, a Mcdonnell Douglas Helicopters 369E, registered N554CP, was substantially damaged in an accident near Columbus, Ohio. It was a public-use flight (local) under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The uncontained engine failure due to the fatigue failure of the gas producer turbine tie bolt.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 19, 2006 · about 8:39 pm local time
- Place
- Columbus, Ohio · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Mcdonnell Douglas Helicopters 369E
- Registration
- N554CP · no longer on the register · serial 0542E
- Damage
- Substantial damage
- Flight
- Public-use flight (local) · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The public-use helicopter was conducting a routine patrol flight when it experienced an uncontained engine failure. The pilot immediately performed an autorotation and run-on landing to an open parking lot area without further incident. The helicopter was damaged with several punctures with outward deformation consistent with projectile damage originating from an uncontained engine failure. Inspection of the engine revealed that portions of the 1st-stage gas producer wheel had departed the engine. The gas producer turbine tie bolt (part number 23068265, serial number NM81907) was identified as the primary failed component. The tie bolt fractured immediately adjacent to the torque nut. Further examination revealed fracture features consistent with fatigue, initiating at the thread root radius. The microstructure, chemistry, and hardness of the turbine tie bolt met engineering drawing specifications. No material anomalies were detected at the fracture surface. Damage to the fracture surface precluded the determination if the failure was associated with low or high cycle fatigue. The tie bolt had completed 3,427 cycles, about 38 percent, of its published life limit of 9,000 cycles. The failure was the first documented since the tie bolt was redesigned during the late 1990s. The redesigned tie bolt incorporated a thicker and stiffer cross-section that had a higher resonant frequency. The manufacturer reviewed the testing and analysis that was preformed when the tie bolt was redesigned. Their review confirmed that the current life limit of 9,000 cycles was within design guidelines. Additionally, the stress modeling and analysis performed during the component redesign was reviewed and no discrepancies were noted. The manufacturer also reviewed the reengineered tie bolt service history and several tie bolts with between 5,000 and 9,000 cycles were taken out of service for examination. Component examinations and database reviews failed to show any similar failures within the fleet. The tie bolt installation required that the bolt length be measured in order to determine the exact stretch of the bolt after the nut was torqued to specification. The original stretch requirement was used with the redesigned tie bolt to eliminate confusion during assembly. A subsequent service bulletin and FAA airworthiness directive mandated that the older design be removed from service, but the installation stretch requirement was not modified. To mitigate future tie bolt fractures, Rolls-Royce reduced the stretch requirement on the tie bolt during the assembly process. As a result, the mean stress on the tie bolt was reduced. The reduced stretch is also expected to increase both high and low cycle fatigue margins in the part. The assembly instructions were updated with the new stretch callout during the first quarter of 2008.
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: commercial pilot
- Ratings: single-engine land; rotorcraft: helicopter
- Flight time: 973 hours in all; 826 in this make and model; 110 in the last 90 days; 36 in the last 30 days; 906 as pilot in command
- Last flight review: July 1, 2005
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 6,639.7 hours
- Last inspection: 100-hour inspection, August 1, 2006; 41.4 hours since
- Maximum gross weight: 3,000 lb
- Seats: 4
- Landing gear: fixed
- Engine: Rolls-Royce 250-C20B (turboshaft); 0 hours total
- Fire in flight and on the ground
- Operator: City Of Columbus Police Department
The flight
- Departed from: OH52 Columbus OH at 8:00 pm
- Destination: OH52 Columbus OH
Weather at the time
- Light: daylight
- Wind: from 310° at 11 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 4,700 ft; scat at 3,600 ft
- Temperature: 82°F (28°C), dew point 70°F (21°C)
- Altimeter: 29.90 inHg
- Observation at 8:53 pm from OSU, 5 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 1 |
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.
