FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA254 · Beech A36 UNDESIGNAT

22 May 2016 · Griffin, GA, United States

Beech A36 UNDESIGNAT · Accident: runway excursion during landing

From Fort Worth Meacham International Airport (FTW) to Cedar Ridge Airport (GA62)

Report a problem

Event

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

Beech A36 UNDESIGNAT

Aircraft type
Beechcraft 36
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
N36SR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fort Worth Meacham International Airport (FTW), Fort Worth, TXTo Cedar Ridge Airport (GA62), Griffin, GA
Aircraft age
About 39 years (built 1977)
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 · landing roll
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
Runway excursion
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 › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • 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

According to the pilot, during landing with fifty percent flaps, in gusting wind conditions, the airplane was too fast as she approached the runway and she aborted the landing. She reported that during the second approach with flaps in the same configuration, she touched down normally, applied the brakes during the landing roll, but could not stop the airplane before exiting the departure end of the runway. The airplane crossed a highway and collided with an embankment. The airplane sustained substantial damage to the fuselage.

The pilot reported that there were not any mechanical malfunctions or anomalies with any portion of the airplane that would have prevented normal flight operations.

According to the Automated Weather Observation System (AWOS) that was available to the pilot for the accident airport, the weather at the time of the accident was reported as: K6A2 221855Z AUTO 34008G14KT 10SM CLR 25/12 A2995 RMK AO2. The pilot landed on runway 18.

Probable cause

The pilot's decision to land with a tailwind, resulting in a runway overrun and collision with a highway road embankment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA254
Event ID
20160523X75408
Case number
GAA16CA254
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: 8039f50c8651a582ba9708695d58359b0f65929ba7e22e90d30fce761cdd1c0b; retrieved 2026-09-16T03:25:32.605Z.