CEN09CA339 · Bell 47G 2
Continental Helicopter Services Bell 47G 2 · Accident: collision during takeoff/landing
From San Marcos Regional Airport (KHYI) to San Marcos Regional Airport (KHYI)
Event
- NTSB case
- CEN09CA339
- 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
Bell 47G 2
- Aircraft type
- Bell 47
- 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
- N8420E
- Operator
- Continental Helicopter Services
- Onboard fatalities
- Unknown
- Route
- From San Marcos Regional Airport (KHYI), San Marcos, TXTo San Marcos Regional Airport (KHYI), San Marcos, TX
- 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
- 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
- Collision during takeoff/landing
- 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 propeller/rotor
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot said that he was landing the agricultural helicopter at the edge of a large field to pick up communications radios from his ground crew. During his landing approach under power lines, he saw a vehicle approaching that he had not seen before. The pilot said that he then raised the helicopter to allow the vehicle to pass underneath. The tail rotor blades then struck a wire at about 20 feet above the ground and the helicopter began to spin. The pilot said that he lost control and the helicopter struck the surface of the field and rolled on its side. There was no postcrash fire, but the helicopter was substantially damaged. The pilot was seriously injured.
Probable cause
The pilot's failure to maintain clearance from power lines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA339
- Event ID
- 20090607X15237
- Case number
- CEN09CA339
- 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. 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: 5a2333e16582787a5bc97d246c43dee86debd95aa76af2765d3f42a56b8c93cc; retrieved 2026-09-15T11:18:54.785Z.