FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA358 · Hughes 369 D

11 Sept 2024 · Canton, MI, United States

Helicopter Powerline Services Hughes 369 D · Accident: system/component malfunction/failure (non-power) while maneuvering

From Ann Arbor Municipal Airport (ARB) to Ann Arbor Municipal Airport (ARB)

Report a problem

Event

NTSB case
CEN24LA358
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
0
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
General aviation
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

Hughes 369 D

Aircraft type
Hughes 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
N8969F
Onboard fatalities
Unknown
Route
From Ann Arbor Municipal Airport (ARB), Ann Arbor, MITo Ann Arbor Municipal Airport (ARB), Ann Arbor, MI
Aircraft age
About 46 years (built 1978)
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 133: Rotorcraft Ext. Load
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
Maneuvering · low-altitude flying
Defining eventThe 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
System/component malfunction/failure (non-power)
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

  • Aircraft › Aircraft propeller/rotor

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

NTSB narrative

On September 11, 2024, about 1400 eastern daylight time, a Hughes 369D helicopter, N8969F, sustained substantial damage when it was involved in an accident near Canton, Michigan. The commercial pilot was uninjured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 rotorcraft external load flight. The purpose of the low-level flight was to support powerline maintenance work. The helicopter was operating from an off airport landing zone and conducting Class B cargo delivery to a powerline structure about 300 yards from the landing zone. While in flight, the pilot, who was stationed in the left seat, noticed an “intermittent and unusual vibration” with the helicopter. The pilot performed a precautionary landing to the landing zone, and he shut down the helicopter without further incident. The pilot performed a postflight inspection on the main rotor system and he observed a crack in the yellow main rotor blade (main rotor blades are typically marked with various colors to easily identify and reference each individual blade). The yellow main rotor blade, which was painted white, had sustained a chordwise crack outboard of the root fitting, near the doubler. The crack appeared to propagate from the blade’s trailing edge through both the upper and lower skins, stopping short of the leading-edge spar area. The helicopter sustained substantial damage to the yellow main rotor blade. There was no further damage sustained to the helicopter. The main rotor blades did not strike any birds, objects, or terrain during the accident flight. The yellow main rotor blade was removed from the helicopter, and it was transported to the NTSB Materials Laboratory, Washington, District of Columbia, for further examination. The yellow main rotor blade was manufactured by MD Helicopters (part number 369D21100-523 and serial number 009999-K364). At the time of the accident, the yellow main rotor bade had accumulated 3,289.9 hours and 12.4 hours had elapsed since the last inspection was performed on the yellow main rotor blade. At the time of the accident, the airframe, which was manufactured in 1978, had accumulated 18,318.8 hours. The helicopter was equipped with a Rolls-Royce 250-C20B turboshaft engine. The Federal Aviation Administration (FAA) Type Certificate for the helicopter, H3WE, is currently held by MD Helicopters, Mesa, Arizona. The FAA-approved MD Helicopters MD 500D (Model 369D) Rotorcraft Flight Manual discusses abnormal vibrations in the emergency procedures section and states: Indications: Sudden, unusual, or excessive vibrations occurring during flight. Conditions: The onset of unusual or excessive vibrations in the helicopter may be an indication of problems in the rotor or drive train systems. Procedures: Land as soon as possible. No further flights should be attempted until the cause of the vibration has been identified and corrected.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN24LA358
Event ID
20240916195126
Case number
CEN24LA358
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas, destination. 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: 69a63fc2e59e5e1b324652db044f2efdc0086979f5ab4d1d79d02c8089d9ed03; retrieved 2026-09-16T19:16:23.215Z.