GAA20CA034 · Bell 47G 5
Wilbur Ellis Bell 47G 5 · Accident: hard landing
From King City, CA to King City, CA
Event
- NTSB case
- GAA20CA034
- 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 5
- 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
- N7060J
- Operator
- Wilbur-Ellis
- Onboard fatalities
- Unknown
- Route
- From King City, CATo King City, CA
- Aircraft age
- About 49 years (built 1970)
- 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 · flare/touchdown
- 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
- Hard landing
- 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 › Task performance
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 pilot reported that, while conducting an agricultural application flight, he planned to fly over the top of a power pole. He applied full-up collective to climb over the pole, but the helicopter struggled to gain altitude. He added that, after the helicopter cleared the pole, the main rotor speed reduced and the helicopter "quit flying," so he decided to conduct a run-on landing on the field. The helicopter landed hard, and the main rotor blades struck the tailboom. The helicopter sustained substantial damage to the tailboom. The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation.
Probable cause
The pilot's failure to maintain a proper descent rate, which resulted in a hard landing and the main rotor blades striking the tailboom.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA20CA034
- Event ID
- 20191018X20936
- Case number
- GAA20CA034
- 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: a36b8ba2b06abc9eb7ecb8a635ec3a7ae160e0b3cd20542c2a5245eecef37150; retrieved 2026-09-16T10:25:10.425Z.