FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02LA264 · Bell 47G-2

25 Sept 2002 · Edmondson, AR, United States

Ag Copters Bell 47G-2 · Accident: in flight collision with object while maneuvering

From Edmondson, AR (no airport) to an unrecorded destination

Report a problem

Event

NTSB case
FTW02LA264
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
1 · 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
N5193B
Operator
Ag Copters
Onboard fatalities
Unknown
Route
From Edmondson, AR (no airport)To 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
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
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, transmission
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

  • Object › Wire, transmission
  • Pilot in command › Clearance, inadequate

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

NTSB narrative

The 5,450-hour commercial pilot had completed an aerial application on a cotton field, and was en route to the staging area when one of helicopter's main rotor blades contacted a wire as the pilot attempted to fly under a set of high voltage power lines. The helicopter impacted soft terrain, became inverted adjacent to the power lines where a post impact fire consumed most of the helicopter.

Probable cause

The pilot's failure to maintain clearance from the high voltage power lines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02LA264
Event ID
20021001X05251
Case number
FTW02LA264
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: d806e1f1a26bfaf10d4ff7fc643b9a5e64de6458cd5a317e1a7ca6e32c5035ef; retrieved 2026-09-20T19:45:24.760Z.