FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

K & S Helicopters Mdhi 369E accident

21 Jan 2005 · Pahoa, HI, United States

Mdhi 369E · Accident: airframe, component or system failure en route

From Hilo International Airport (ITO) to an unrecorded destination

Report a problem

Event

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

Mdhi 369E

Aircraft type
Mdhi 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
N142MK
Onboard fatalities
Unknown
Route
From Hilo International Airport (ITO), Hilo, 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

  • Rotor system, tail rotor blade abrasion strip › Debonded
  • Rotor system, tail rotor blade abrasion strip › Fatigue
  • Rotor system, tail rotor blade abrasion strip › Separation

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

NTSB narrative

The helicopter impacted small trees during an autorotational landing that was preceded by the in-flight separation of a tail rotor blade abrasion strip. According to the pilot, the helicopter developed a "sudden vibration in the tail rotor pedals followed immediately by a loud 'crack' or 'snap', and then an extremely loud banging noise and a sharp vibration in both airframe as well as the tail rotor pedals." The pilot made an off-airport autorotational landing to a clearing, but during the landing flare, the tail section snagged a tree. Post-accident examination of the tail rotor blades revealed that the leading edge abrasion strip debonded from one of the blades. Based on the surface finish, the debonding was most probably an adhesive failure at the interface with the abrasion strip. The cause of the bond failure is unknown, but could be the result of in-service conditions, a production problem, or undetected impact damage. The adhesive is the primary means of holding the strip to the blade, but there are also two rivets on the inboard end of the blade that serve as a secondary securing method. The abrasion strip fractured at the outboard rivet and the fracture surface revealed evidence of fatigue cracking indicating that the abrasion strip was completely debonded for a period of time. In addition, dark sooty deposits were visible in the bond area on both sides of the blade. Maintenance records indicated that the helicopter underwent a 100-hour inspection approximately 62 hours prior to the accident. The inspection calls for a visual examination of the tail rotor blades to ensure no separation of the bond around the edges or at the tip end of the blade exist. The inspection process calls for a dye-penetrant inspection or tap test only if a debond is suspected. However, detection of the debond during the visual only 100-hour inspection would depend on whether the separation intersected on the strip edges. The preflight examination procedures called for the pilot to visually examine the tail rotor blades to ensure there is no debonding along the abrasion strip-to-airfoil bond line. The pilot reported that he inspected the abrasion strip prior to the accident flight, but did not notice any evidence of an abrasion strip debond. The blade accumulated 2,379.7 total hours of operation, and 1,820.6 hours since its last overhaul.

Probable cause

the in-flight separation of the tail rotor blade abrasion strip due to a degraded adhesive bond and fatigue fracture of the metallic abrasion strip. The ultimate cause for the degraded bond is unknown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA074
Event ID
20050208X00151
Case number
LAX05LA074
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-01-22.
  • API snapshot SHA-256: c1c9a7a0ac758b5b4e14691d08892f1581ad8133b9d2bd5860dadee6c2bfb0e0; retrieved 2026-09-18T15:07:54.011Z.