GAA19CA021 · Aviat S 2C
Grayout Aerosports Aviat S 2C · Accident: controlled flight into terrain/object (CFIT) on approach
From Atlanta Speedway Airport (HMP) to Atlanta Speedway Airport (HMP)
Event
- NTSB case
- GAA19CA021
- 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
Aviat S 2C
- Aircraft type
- Aviat S
- Category
- Airplane
- 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
- N126BB
- Operator
- Grayout Aerosports
- Onboard fatalities
- Unknown
- Route
- From Atlanta Speedway Airport (HMP), Hampton, GATo Atlanta Speedway Airport (HMP), Hampton, GA
- Aircraft age
- About 17 years (built 2001)
- 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
- Approach · VFR pattern final
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- 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
- Environmental issues › Physical environment
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The biplane pilot reported that, while performing a reconnaissance flight to determine the viability of landing the biplane on the infield section of the racing track for an upcoming airshow, he made several passes and saw no power wires. He added that, during an approach to the proposed landing area, the biplane struck a power wire. The pilot aborted the approach, performed a quick controllability check, and decided to land at a nearby airport. The pilot landed the biplane without further incident.
The airplane sustained substantial damage to the left ailerons.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the biplane that would have precluded normal operation.
Probable cause
The pilot’s failure to see and avoid power wires during approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA021
- Event ID
- 20181009X95832
- Case number
- GAA19CA021
- 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: aeeb9f9e6fa5a387b1d5f42ed05b74b7607f60b4108dcad3fed317bf3081b8a0; retrieved 2026-09-16T08:19:37.085Z.