FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07LA193 · Hughes 369D

5 Jul 2007 · Comfrey, MN, United States

Teryjon Aviation Hughes 369D · Accident: loss of engine power while maneuvering

From MN to an unrecorded destination

Report a problem

Event

NTSB case
CHI07LA193
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
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 369D

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
N500NC
Onboard fatalities
Unknown
Route
From MNTo 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 137: Agricultural
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 · aerial application
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
Loss of engine 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

  • Fuel system, line fitting › Loose

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

A helicopter sustained substantial damage on impact with terrain during a forced landing following a loss of engine power during an aerial application spray run. The pilot reported that he "was able to land square on the skids, but the helicopter still bounced. The landing gear spread hitting the tanks, and snapping the uprights above the tanks. At that point, forward leg stuck in the ground, making the helicopter pitch forward. The blade in front made contact with the ground. The rotor system came around cutting the boom faring and tail off." The pressure line which connects to the Pg boss on the fuel control was found to be finger tight during an examination of the wreckage.

Probable cause

The loss of engine power due to the loose pressure line during aerial application maneuvers which resulted in a hard forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07LA193
Event ID
20070711X00910
Case number
CHI07LA193
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, 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: a4466c00bde7015c3e7ad84b430189072892017922bbdf867d7a97f47a38119b; retrieved 2026-09-22T03:41:24.071Z.