Inter-Island Helicopter McDonnell Douglas 369FF accident
McDonnell Douglas 369FF · Accident: airframe, component or system failure en route
From Port Allen Airport (PAK) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI07MA083
- 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
- 1 · 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
- Charter & commuter
- 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 369FF
- Aircraft type
- McDonnell Douglas 369
- Category
- Helicopter
- 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
- N911VC
- Operator
- Inter-Island Helicopter
- Onboard fatalities
- Unknown
- Route
- From Port Allen Airport (PAK), Hanapepe, HITo not recorded
- 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 135: Air Taxi & Commuter
- 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 · 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
- Airframe, component or system failure
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Manufacturer › Material defect
- Pilot in command › Tail rotor effectiveness, not possible
- Rotor system, tail rotor › Failure, total
- Rotor system, tail rotor › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter pilot reported that he was conducting a Part 135 air tour flight with 4 passengers on board the helicopter. The helicopter was about 1,500 feet above ground level with about 80 - 85 knots of airspeed when within a split-second he heard two loud "bangs." The nose of the helicopter pitched down and the helicopter yawed to the right. He applied left pedal but without effect. He attempted to "get more forward airspeed," but each time he did the helicopter nosed over and yawed to the right. The right yaw developed into a tight spin, and he realized that he "lost his tail rotor." The pilot executed an autorotation to a clearing located at a campground. The helicopter impacted the trees at the western edge of the clearing during the autorotation. The helicopter impacted the terrain on its right, front side. Inspection of the helicopter revealed that the tail rotor output shaft and the tail rotor blades separated from the tail rotor gearbox. The tail rotor assembly was inspected at the National Transportation Safety Board's Materials Laboratory. The inspection revealed that the tail rotor blade assembly fractured through the root fitting in the general area that coincided with a hole for the blade retention bolt. The root fitting contained a 1-inch nominal diameter longitudinal hub bore with a tapered (conical) hole bottom. A relief radius was located between the hub bore and the conical hole bottom. The inspection revealed crack arrest marks typical of a fatigue cracking that emanated from multiple origins at the relief radius between the hub bore and conical hole bottom. The relief radius measured approximately 0.001 inch, much less than specified by the engineering drawing (0.12 inch and 0.15 inch). On April 26, 2007, McDonnell Helicopters, Inc. (MDHI) issued mandatory Service Bulletin (SB) 369D-204, 369E-099, 369F-084, 369H-247, titled "Tail Rotor Blade Assembly, One Time Inspection." According to MDHI SB, before further flight, the tail rotor should be removed from helicopter models 369 (Army YOH-6A), 369 (Army OH-6A), 369H, 369HM, 369HS, 369HE, 369D, 369E, 369F, and 369FF. The hub bore should be visually examined with a flashlight. If the relief radius does not contain a smooth transition between the bore and conical bottom hole, the root fitting should be removed from service. On April 27, 2007, the Federal Aviation Administration issued emergency Airworthiness Directive (AD) 2007-09-51 that mandated inspection of the root fittings per the MDHI SB.
Probable cause
The fatigue failure of the tail rotor blade root fitting due to a manufacturing defect which resulted in the separation of the tail rotor system and loss of tail rotor control. A contributing factor to the accident were the trees that the helicopter struck during the autorotation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07MA083
- Event ID
- 20070322X00320
- Case number
- CHI07MA083
- 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: f4b06ab7e48a3f5c2452097944ea42f51b97cd7c604f60d70af0dc279df8fe2e; retrieved 2026-09-18T12:55:31.008Z.