FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL05CA120 · Grumman American AA-1B

2 Jul 2005 · Durham, NC, United States

Grumman American AA-1B · Accident: loss of control on ground/water during takeoff

From Lake Ridge Aero Park Airport (8NC8) to Lake Ridge Aero Park Airport (8NC8)

Report a problem

Event

NTSB case
ATL05CA120
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 American AA-1B

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
N100XX
Onboard fatalities
Unknown
Route
From Lake Ridge Aero Park Airport (8NC8), Raleigh, NCTo Lake Ridge Aero Park Airport (8NC8), Raleigh, NC
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
Takeoff · rejected takeoff
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
Loss of control on ground/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 › Directional control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

After a routine run-up the pilot began a short field takeoff from a private grass runway. Approximately 1300 feet into the takeoff roll, the airplane lifted off the runway but failed to accelerate to an airspeed that would allow for a positive rate of climb. The airplane settled back onto the runway surface and began to "skip off the runway." Approximately 1000 feet from the end of the runway the pilot chose to abort the takeoff and brought the throttles back to idle. Approximately 300 feet from the end of runway 32, the airplane began to veer to the left side of the runway and the left wing struck the ground. The airplane rested about 250 feet from the end of the runway. The pilot did not report a mechanical problem with the airplane, and the post-accident examination failed to disclose a mechanical problem with the airplane.

Probable cause

The pilot's failure to maintain directional control. Factors were soft and wet terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL05CA120
Event ID
20050802X01142
Case number
ATL05CA120
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-07-03.
  • API snapshot SHA-256: 0d34b682b65b6a6da800d7960d7ffae1d69628cccee600d009b04aa3c331228e; retrieved 2026-09-22T05:41:15.854Z.