FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA15CA197 · Hughes 269C

21 Jul 2015 · Atlanta, TX, United States

Hughes 269C · Accident: abnormal runway contact during landing

From Hall Miller Municipal Airport (ATA) to Hall Miller Municipal Airport (ATA)

Report a problem

Event

NTSB case
GAA15CA197
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 269C

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
N58397
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hall Miller Municipal Airport (ATA), Atlanta, TXTo Hall Miller Municipal Airport (ATA), Atlanta, TX
Aircraft age
About 36 years (built 1979)
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
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
Abnormal runway contact
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 pilot/owner, who is not rated in helicopters, reported that he departed the airport and flew the helicopter for 4 miles before landing in a parking lot in the city. During the landing flare the tail rotor blades impacted the ground and the helicopter sustained substantial damage to the tail rotor gear box and tail boom.

The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Probable cause

The non-helicopter rated pilot's improper landing flare, which resulted in impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA15CA197
Event ID
20150723X45724
Case number
GAA15CA197
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: 0ec02e245cfa221b4e0a2210a7d5c19184ee2225fd8b906efa67d7e50876a81d; retrieved 2026-09-16T02:34:05.971Z.