ATL91LA003 · Grumman AA-5A
Grumman AA-5A · Accident: overrun during landing
From Mid-Carolina Regional Airport (RUQ) to an unrecorded destination
Event
- NTSB case
- ATL91LA003
- 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
- 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 AA-5A
- Aircraft type
- Grumman AA-5
- 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
- N7103L
- Operator
- Adkins, David · private individual
- Onboard fatalities
- Unknown
- Route
- From Mid-Carolina Regional Airport (RUQ), Salisbury, NCTo 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
- Landing · landing roll
- 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
- Overrun
- 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
- Pilot in command › Airspeed, excessive
- Pilot in command › Altitude, excessive
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT OVERSHOT THE RUNWAY WHILE ATTEMPTING A FULL-STOP LANDING. THE PILOT SAID THAT THIS WAS THE SECOND LANDING ATTEMPT. ON THE FIRST ATTEMPT, HE WAS TOO HIGH AND FAST FOR A SAFE LANDING. DURING THE NEXT APPROACH THE CARBURETOR HEAT LEVER WAS PLACED IN THE ON POSITION FOR THE LANDING. WHEN THE PILOT REALIZED THAT HE WAS AGAIN TOO HIGH AND FAST, HE ATTEMPTED A GO-AROUND. BUT THERE WAS NOT AN INSTANT POWER RESPONSE WHEN THE THROTTLE WAS ADVANCED. THE PILOT DECIDED TO CONTINUE THE LANDING ATTEMPT. THE AIRPLANE WENT OFF THE DEPARTURE END OF RUNWAY 8 AND COLLIDED WITH A RAILROAD EMBANKMENT; THERE WERE NO MECHANICAL PROBLEMS REPORTED. .
Probable cause
THE PILOT'S FAILURE TO ESTABLISH AN APPROACH PROFILE WHICH WOULD HAVE ALLOWED HIM TO MAKE A SAFE LANDING ON THE RUNWAY. THE PILOT MISJUDGED HIS ALTITUDE AND AIRSPEED THROUGHOUT THE APPROACH. A FACTOR TO THE ACCIDENT WAS THE COLLISION WITH THE RAILROAD BERM.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL91LA003
- Event ID
- 20001212X24405
- Case number
- ATL91LA003
- 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: 6eb1f4b78e55b63cf99f50289a5a9a958b7dbdf4a2fb423455b18f8c950f6bb2; retrieved 2026-09-21T15:34:23.228Z.