ERA20CA155 · Grumman AA5 B
Grumman AA5 B · Accident: collision during takeoff/landing on approach
From Statesboro Bulloch County Airport (TBR) to Cypress Lakes Airport (GA35)
Event
- NTSB case
- ERA20CA155
- 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
Grumman AA5 B
- Aircraft type
- Grumman AA5
- 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
- N314JG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Statesboro Bulloch County Airport (TBR), Statesboro, GATo Cypress Lakes Airport (GA35), Bloomingdale, GA
- Aircraft age
- About 45 years (built 1975)
- 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
- 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
- Environmental issues › Conditions/weather/phenomena
- 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, he was returning to his home airport. The accident occurred during the landing attempt; the pilot could not recall the approach or accident sequence due to his injuries. According to a witness who lived near the airport, he heard the airplane and saw it fly over the midfield before it entered the left downwind leg of the traffic pattern for runway 13. He noted that the engine power was "pulled back." A few minutes later, the witness heard an impact. The airplane impacted trees and terrain on the left side of the runway and came to rest about 1,000 ft past the runway's approach end. The airplane sustained substantial damage to the fuselage, both wings, and the empennage. A Federal Aviation Administration inspector who examined the wreckage stated that he found no preaccident anomalies with the airplane that would have precluded normal operation. According to a report from an airport 10 miles southeast of the accident site, the wind was gusting to 18 knots.
Probable cause
The pilot's failure to maintain airplane control during landing with a gusting quartering tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA155
- Event ID
- 20200421X64410
- Case number
- ERA20CA155
- 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: 07b6d62da6f8f75c0edd954b812c51e49dca37611a11f09a0b641d0291482820; retrieved 2026-09-16T11:29:41.185Z.