FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA017 · Hughes 369HS

21 Oct 2003 · Evansville, MN, United States

Hughes 369HS · Accident: in flight collision with terrain/water while maneuvering

From Lake Christina, MN to an unrecorded destination

Report a problem

Event

NTSB case
CHI04LA017
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
N49TJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake Christina, 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
In flight collision with terrain/water
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

  • Pilot in command › Altitude/clearance, misjudged

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

NTSB narrative

The helicopter was substantially damaged during an in-flight collision with a lake while conducting an aerial application pass. The local flight was operating from a temporary load site near the lake shoreline. The pilot stated: "The conditions were calm winds, sun coming up over the trees to the east, glassy water condition. During the spray run I must [have] lost my depth perception with the water surface and allowed the skids to contact the water. The aircraft decelerated rapidly ... [and] water came up over the bubble as the aircraft pitched forward." The pilot also noted that he should have "looked at the trees along the shoreline for a vertical reference instead of at the water. With glassy water it is hard to judge distance." He reported there were no malfunctions with the aircraft or engine prior to the accident.

Probable cause

The pilot's misjudgment of clearance from the surface of the lake during the aerial application pass. The low altitude operation, glassy water, and his visual perception were contributing factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA017
Event ID
20031024X01812
Case number
CHI04LA017
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: 40c4b865f04eaecec1a640c1635f298b41e3c661ab3961e8fea3bb6028cd8d61; retrieved 2026-09-21T19:20:09.516Z.