FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20FA119 · American Aviation AA 1 Undesignat

6 Mar 2020 · Boynton Beach, FL, United States

American Aviation AA 1 Undesignat · Accident: loss of control in flight while maneuvering

From Palm Beach County Park Airport (LNA) to an unrecorded destination

Report a problem

Event

NTSB case
ERA20FA119
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

American Aviation AA 1 Undesignat

Aircraft type
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
N5757L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palm Beach County Park Airport (LNA), Lake Worth, FLTo not recorded
Aircraft age
About 51 years (built 1969)
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
Maneuvering
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
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Radar data indicated that, after departure, the pilot climbed the airplane to about 1,700 feet mean sea level (msl) in a gradual right turn. The airplane then began to descend, and its groundspeed decreased until radar contact was lost. The last radar return indicated an altitude of 550 feet msl and a ground speed of about 43 knots near the accident site. A witness reported that the airplane's wings appeared to "waggle" up and down, and the airplane suddenly appeared to go inverted. The airplane’s nose pointed at the ground, and the airplane began to corkscrew rapidly while losing altitude and disappeared behind a tree line. Another witness heard what she thought sounded like a boat having engine trouble, then heard a loud thump. No evidence of any preimpact failures or malfunctions of the airplane or engine were discovered that would have prevented normal operation. The propeller blades did not exhibit any rotational signatures, consistent with the engine not producing power at the time of impact. There was no evidence of residual fuel inside either of the fuel tanks, the fuel selector valve, or the mechanical fuel pump, and the carburetor float bowl contained only about 2 drops of fuel. There was no odor of fuel on-scene, and no observed fuel blight near the wreckage. The airplane’s most recent documented annual inspection was about 4 years before the accident. An acquaintance of the accident pilot reported that the pilot, who was a mechanic, had been working on the airplane for about 1.5 years. The acquaintance communicated with the pilot 3 days before the accident, during which the pilot reported that he flew the airplane and that the airspeed indicator seemed to be indicating “high” and that the stall warning horn activated below 85 mph. The pilot reported that he “didn’t feel like [the airplane] was stalling but it did feel slow.” Review of maintenance records did not reveal any entries pertaining to the pitot-static system. Based on the available evidence, it is likely that the pilot did not verify the fuel quantity before he departed on the accident flight, which resulted in a total loss of engine power due to fuel exhaustion. It is also likely that, following the loss of engine power, the pilot failed to maintain airspeed and exceeded the airplane’s critical angle of attack, which resulted in an aerodynamic stall and loss of control. The extent to which the reported airspeed indicator/stall warning anomaly may have contributed to the accident could not be determined based on the available information.

Probable cause

The pilot's inadequate preflight fuel planning, which resulted in a total loss of engine power due to fuel exhaustion, and his exceedance of the airplane’s critical angle of attack following the loss of engine power, which resulted in an aerodynamic stall and loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20FA119
Event ID
20200306X90723
Case number
ERA20FA119
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, cause areas. 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: 6dc92898dac5565cc6af3047f64c01151e67233391017c63d6299add5c12ff56; retrieved 2026-09-15T07:12:30.018Z.