ATL90FA183 · Grumman AA5B
Grumman AA5B · Accident: in flight collision with terrain/water on approach
From Ada Regional Airport (ADH) to an unrecorded destination
Event
- NTSB case
- ATL90FA183
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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 AA5B
- 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
- N81099
- Operator
- Swanner, John · private individual
- Onboard fatalities
- Unknown
- Route
- From Ada Regional Airport (ADH), ADA, OKTo not recorded
- Aircraft age
- Not recorded
- 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 downwind
- First occurrenceThe 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
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Diverted attention
- Pilot in command › Proper altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT & PAX HAD RETURNED TO THE HOME FIELD AFTER A LONG WORK DAY THAT BEGAN BEFORE 9 AM. UPON ARRIVAL AT THE AIRPORT FOG HAD COVERED THE NORTH THRESHOLD & THE AREA ADJACENT TO THE RWY FROM THE SW TO THE NE. ANOTHER ACFT WAS ALSO ARRIVING IN THE LANDING PATTERN. THE PILOT MADE 2 ABORTIVE ATTEMPTS TO LAND VISUALLY BECAUSE HE HAD POSITIONED THE ACFT TOO CLOSE TO THE RWY. THE LAST RADAR POSITION OF THE ACFT WAS A LEFT DOWNWIND LEG FOR RWY 17. THE ACFT IMPACTED EAST OF THE FIELD WHILE IN A DESCENDING RIGHT TURN. FOG & LACK OF GROUND LIGHTS TO THE NORTH OF THE AIRPORT WERE REPORTED BY LOCAL WITNESSES. THE PILOT WAS PROBABLY TIRED, & DISTRACTED BY THE ADDITIONAL ACFT.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN THE PROPER ALTITUDE WHICH RESULTED IN THE INADVERTENT DESCENT INTO THE GROUND, AND HIS DIVERTED ATTENTION TO ANOTHER AIRPLANE. FACTORS IN THE ACCIDENT WERE FOG, DARK NIGHT, FATIGUE FROM LACK OF SLEEP, AND A LACK OF RECENT NIGHT LANDINGS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL90FA183
- Event ID
- 20001212X24178
- Case number
- ATL90FA183
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 7b2a9ca35040422a5f2b103d393404191e889cc2f11692f94539059f65972b69; retrieved 2026-09-21T02:08:36.294Z.