FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02LA036 · Grumman American AA-1C

29 Nov 2001 · Pompano Beach, FL, United States

Grumman American AA-1C · Accident: loss of engine power during initial climb

From Pompano Beach Airpark (KPMP) to Fort Lauderdale Executive Airport (KFXE)

Report a problem

Event

NTSB case
MIA02LA036
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-1C

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
N9515U
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pompano Beach Airpark (KPMP), Pompano Beach, FLTo Fort Lauderdale Executive Airport (KFXE), Fort Lauderdale, FL
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
Initial climb
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 engine power
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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(vs), 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

Before takeoff, the main fuel tank of the left wing was topped off and 7 gallons of fuel were added to the main fuel tank of the right wing. The left seat occupant (owner of a Grumman AA5 and a CFI) reported he had never flown the accident make and model airplane before and wanted a pilot familiar with the airplane to fly with him; as such the right seat occupant was pilot-in-command (PIC). The right seat occupant stated that he went along on the flight because the left seat occupant had not flown the airplane in some time, and he assumed the left seat occupant was PIC. Each occupant says the other performed a preflight of the airplane. The left seat occupant reported that both flew the airplane at various times during the flight. The right seat occupant reported he never touched the controls at any time during the flight. The flight departed, proceeded to the practice area where slow flight was performed. The flight then proceeded to the Pompano Beach Airpark Airport where 1 full stop landing was performed. The flight taxied back, departed, and remained in the traffic pattern where 2 touch-and-go (T & G) landings were performed. The left seat occupant stated that at 200 feet during the climbout of the second T & G landing, the engine began to run rough. He looked at the right seat occupant who appeared "frozen", and took the controls. The engine was developing some power and he banked the airplane in an attempt to return to the airport with the recognition that if the engine quit, he would roll the airplane to a wings level and land straight ahead. The next thing he recalls, they had crashed. Two air traffic controllers reported observing the wings rocking during the upwind leg, one reported seeing the airplane in a sharp right turn. Fire rescue from a station immediately adjacent to the airport did not respond; other stations responded. The fire rescue report indicates that the right seat occupant reported the left seat occupant was flying the airplane. Examination of the airplane revealed no evidence of preimpact failure or malfunction of the fuel vent or supply system. The carburetor heat control was found in the midrange position; however, the airbox was impact damaged. The carburetor heat control cable was separated from the control arm; incorrect securing hardware was noted. Examination of the flight controls revealed no evidence of preimpact failure or malfunction. The engine was removed from the airplane and placed on a test stand where it was noted to operate normally; no discrepancies were noted during the engine run. Testing of fuel from the source that fueled the airplane revealed no discrepancies.

Probable cause

The failure of the pilot-in-command to maintain airspeed (Vs), while maneuvering for an emergency landing, resulting in an inadvertent stall and subsequent in-flight collision with terrain. A contributing factor in the accident was the loss of engine power due to undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02LA036
Event ID
20011210X02371
Case number
MIA02LA036
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, coordinates. 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: 1fb37e66ffaa457b9600e559fc3400771c4d72ddbb63ba2ac46eeec458c751ab; retrieved 2026-09-21T09:43:29.585Z.