FTW90DPJ05 · Bell 47G-4A
Bell 47G-4A · Accident: airframe, component or system failure while maneuvering
From Bixby, OK (no airport) to Bixby, OK
Event
- NTSB case
- FTW90DPJ05
- 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
- 0
- 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-4A
- 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
- N2238W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bixby, OK (no airport)To Bixby, OK
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Miscellaneous rotorcraft › Failure, partial
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER THE AG PILOT FINISHED HIS LOAD, HE HEADED BACK TO THE TRUCK FOR HIS FINAL LOAD. AS HE PASSED UNDER A POWERLINE HE HEARD A LOUD BANG OR POP, AND THE HELICOPTER YAWED TO THE RIGHT. HE SAID HE HEARD THE WHEAT HITTING THE SKID BOOMS, AND THEN THE HELICOPTER IMPACTED HARD ON THE TOES OF THE SKIDS. HIS SEAT BELT FAILED AND HE WAS THROWN THROUGH THE FRONT OF THE HELICOPTER. HE SAID HE RECEIVED MINOR INJURIES. THE HELICOPTER WAS DEMOLISHED BY IMPACT AND POST-IMPACT FIRE. THE FAA INVESTIGATORS SAID THAT DUE TO THE DAMAE CAUSED BY THE IMPACT, DAMAGED CAUSED BY THE FIRE, AND DAMAGE CAUSED BY MOVEMENT OF THE WRECKAGE, THEY COULD NOT FIND A COMPONENT FAILURE THAT MIGHT HAVE CAUSED THE ACCIDENT. THE FIRST SKID MARKS STARTED UNDER THE POWERLINES, BUT THE POWER LINES WERE NOT DAMAGED.
Probable cause
LOSS OF CONTROL DUE TO UNDETERMINED MECHANICAL FAILURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW90DPJ05
- Event ID
- 20001212X22912
- Case number
- FTW90DPJ05
- 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. 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: 080c5b1ead9ea0b04538d0d9278203b565f7acd328ed013c4c31747a8f44cb99; retrieved 2026-09-21T23:55:12.108Z.