CHI04CA180 · Texas Helicopter M-74
Texas Helicopter M-74 · Accident: in flight collision with object during landing
From Clear Lake, MN to Clear Lake, MN
Event
- NTSB case
- CHI04CA180
- 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
Texas Helicopter M-74
- Aircraft type
- Texas M-74
- 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
- N10009
- Operator
- Gary Oleen
- Onboard fatalities
- Unknown
- Route
- From Clear Lake, MNTo Clear Lake, MN
- 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
- Landing
- 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 object
- 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 › Proper glidepath, not maintained
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 while attempting to land on a truck pad that was positioned in a field. The pilot reported he was starting to spray his fourth field when he observed that the fuel gauge on the helicopter was close to the "low/danger area." He returned to the truck to refuel. As he was approaching the truck pad for landing, "the helicopter started to settle and in spite of forward cyclic and full power, rotor RPM started to decay." He was not able to get the skids all the way on the pad and the helicopter fell backwards off the truck pad. The helicopter rolled to the right and nosed into the ground. It spun around and ended up facing the truck with its engine still running. The pilot shut down the helicopter and exited the aircraft.
Probable cause
The pilot failed to maintain a proper glidepath to the landing zone. A factor was the truck pad.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04CA180
- Event ID
- 20040727X01079
- Case number
- CHI04CA180
- 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: 48e5bacf4fc30d22db4add7677f27f257461436de4925cd89487de84fb90696e; retrieved 2026-09-22T07:08:20.329Z.