FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA444 · Hughes 369HS

18 Aug 2014 · Saint Peter, MN, United States

Tery Jon Aviation Hughes 369HS · Accident: low altitude operation/event while maneuvering

From Saint Peter, MN to Saint Peter, MN

Report a problem

Event

NTSB case
CEN14CA444
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 369HS

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
N369GN
Onboard fatalities
Unknown
Route
From Saint Peter, MNTo Saint Peter, MN
Aircraft age
About 40 years (built 1974)
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 · 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
Low altitude operation/event
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
Wire
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 oper/perf/capability
  • Personnel issues › Psychological

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

NTSB narrative

During an application flight, the pilot maneuvered the helicopter in order to conduct another pass, maintaining vigilance of the high lines and trees in the vicinity of his operations. The pilot stated that he did not see the 2 wires spanning from across the road into the bean field where he was applying insecticide. He flew right into the wires which subsequently entangled around the mast of the helicopter. During the forced landing to the field, the "controls locked up" and the helicopter spun to the right 3 times before impacting the ground. The helicopter was substantially damaged. The pilot reported no preimpact mechanical failures or malfunctions with the helicopter that would have precluded normal operation.

Probable cause

The pilot did not see the wires resulting in the subsequent wire collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA444
Event ID
20140821X05028
Case number
CEN14CA444
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: 53d270c7bb7e49b35d9b68a66bd6399a94544da16d4b5f7fe1dac3d90bb97b1a; retrieved 2026-09-16T01:40:00.601Z.