FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15CA364 · Hughes 269B

19 Sept 2015 · Hartford, AL, United States

Eagel Aviation Academy Hughes 269B · Accident: collision during takeoff/landing

From Defuniak Springs Airport (54J) to Hartford, AL

Report a problem

Event

NTSB case
ERA15CA364
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

Hughes 269B

Aircraft type
Hughes 269
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
N141LL
Onboard fatalities
Unknown
Route
From Defuniak Springs Airport (54J), DeFuniak Springs, FLTo Hartford, AL
Aircraft age
About 48 years (built 1967)
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 91: General Aviation
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
Takeoff
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
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 was departing from a field at a family farm and attempted to clear an adjacent driveway when the left skid toe caught on the top of a wire fence. The pilot applied aft cyclic in an attempt to climb; however, the helicopter rolled to the left and impacted the ground. The main rotor, tail rotor, and airframe sustained substantial damage. Subsequent examination of the helicopter did not reveal any preimpact mechanical malfunctions which would have precluded normal operation. The pilot reported about 3,900 hours of total flight experience in rotorcraft, which included 160 hours in the same make and model as the accident helicopter. He further reported that the accident could have been prevented had he conducted a walk around of the takeoff area to better evaluate prospective hazards.

Probable cause

The pilot's inadequate preflight planning, and his subsequent failure to attain adequate altitude during takeoff, which resulted in a collision with a wire fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15CA364
Event ID
20150921X21024
Case number
ERA15CA364
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: 97816a367b31379178b5c78af12dd2ef1c7555232d350e7dcda948213fc9e694; retrieved 2026-09-16T02:47:34.581Z.