CEN11FA008 · Grumman American Aviation Corp AA-5A
Grumman American Aviation Corp AA-5A · Accident: abnormal runway contact during landing
From Downtown Airport (3DW) to Downtown Airport (3DW)
Event
- NTSB case
- CEN11FA008
- 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
- 1 · 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 Aviation Corp AA-5A
- Aircraft type
- Grumman American 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
- N9695U
- Operator
- Coby Collins
- Onboard fatalities
- Unknown
- Route
- From Downtown Airport (3DW), Springfield, MOTo Downtown Airport (3DW), Springfield, MO
- 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 · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he decided to land near the runway numbers instead of landing at the touchdown zone 1,000 feet from the approach end of the runway to provide additional separation from another airplane that had just landed. While on short final, the pilot determined that he might be short of the runway by 3 or 4 feet so he raised the nose of the airplane to extend the glidepath. The airplane stalled and bounced hard on the runway. The airplane bounced a second time and the pilot attempted to execute a go-around. He pushed the throttle full in, but the airplane veered off the left side of the runway. He attempted to direct the airplane back onto the runway, but it continued in the grass for about 280 feet. The airplane returned to the runway, but then veered off the right side of the runway as the pilot raised the flaps. The airplane became airborne again but also stalled again and subsequently struck the ground in a nose-low attitude. A postimpact fire ensued and consumed the majority of the airplane. The postaccident inspection of the airframe and engine revealed no preimpact anomalies. The pilot reported that there was no mechanical malfunction or failure of the airplane during the accident flight.
Probable cause
The pilot's failure to maintain control of the airplane during an attempted go-around, which led to an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11FA008
- Event ID
- 20101007X85314
- Case number
- CEN11FA008
- 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. 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: c1ad202a4e54719ac695a6e176fdf515b47342850eb990ff7b705c764e98771b; retrieved 2026-09-13T21:04:41.262Z.