ERA12CA418 · Grumman American AVN. CORP. AA-1C
Grumman American AVN. CORP. AA-1C · Accident: loss of control in flight on approach
From Morristown Municipal Airport (KMMU) to Brandywine Regional Airport (KOQN)
Event
- NTSB case
- ERA12CA418
- 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 AVN. CORP. AA-1C
- Aircraft type
- Grumman American AA-1
- 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
- N9675U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Morristown Municipal Airport (KMMU), Morristown, NJTo Brandywine Regional Airport (KOQN), West Chester, PA
- 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 go-around
- 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
- Loss of control in flight
- 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 stated that, before entering the airport traffic pattern, he obtained the weather information, which indicated wind from 280 degrees at 10 knots, gusting to 15 knots. He flew the traffic pattern to runway 27, and stated that the airplane was aligned with the runway centerline when it was about 30 feet above the runway threshold. About 15 feet above the runway, the pilot felt the airplane yaw to the left, which he corrected with right rudder. The airplane then began to sink quickly, so the pilot applied full throttle while maintaining wings level in an attempt to go around. After the engine achieved full power, the airplane landed "hard" near the left side of the runway, bounced, and headed about 40 degrees left of the runway centerline. The airplane touched down once again and traveled onto a ramp where it impacted two parked airplanes. The accident airplane incurred substantial wing and fuselage damage. Postaccident examination of the airplane revealed no preexisting mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control during an attempted go-around, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12CA418
- Event ID
- 20120628X73336
- Case number
- ERA12CA418
- 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: 4581146eeac5aabb0c7bc9e245e129cd675b9d55d7225fac1875082878e41594; retrieved 2026-09-15T18:39:47.031Z.