FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Aurora Aviation Services McDonnell Douglas Helicopter 369E accident

6 Mar 2010 · Delta Junction, AK, United States

McDonnell Douglas Helicopter 369E · Accident: loss of engine power (total) en route

From Healy, AK to Wingsong Estates Airport (AK09)

Report a problem

Event

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

McDonnell Douglas Helicopter 369E

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
N26TC
Onboard fatalities
Unknown
Route
From Healy, AKTo Wingsong Estates Airport (AK09), Delta Junction, AK
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
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
Loss of engine power (total)
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot reported that he was in cruise flight when he heard a “pop” and the engine lost all power. He initiated an autorotation to a clearing, but was unable to reach it and had to land in an area with trees. The helicopter struck treetops during the descent and landed hard, sustaining structural damage. A postaccident inspection, including running the engine in a test cell, disclosed ample uncontaminated fuel, and no evidence of any preimpact mechanical problems with the helicopter’s engine or systems.

Probable cause

A total loss of engine power in flight for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC10LA020
Event ID
20100308X72409
Case number
ANC10LA020
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, coordinates. 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: 168a0199f045b114c31b3787021de3f3abdfa71a5fc1923f7899385f2e55f66c; retrieved 2026-09-15T13:43:35.949Z.