ERA22FA153 · American AA-1
American AA-1 · Incident: loss of control on ground while taxiing
Event
- NTSB case
- ERA22FA153
- 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
- Incident
- 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
- 0
- 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
- Instrument Meteorological Cond
American AA-1
- 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
- N5774L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 53 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
- Taxi
- 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 on ground
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot purchased the airplane about 6 months before the incident; however, he did not have a current Federal Aviation Administration (FAA) medical certificate and had not previously flown the airplane. A family member reported that the pilot often went to the airport at night to run the airplane’s engine and taxi around the airport property. In the early morning hours on the night of the incident, the airport was unattended and the weather conditions were conducive to low visibility in mist. Later that day, the airplane was found inverted in the grass off the end of a taxiway and down an embankment. The pilot was fatally injured. Examination of the incident site revealed that the airplane likely traveled off the end of the taxiway and went about 130 ft down an embankment before it came to rest inverted, sustaining substantial damage to the airframe in the process. Tire (skid) marks consistent with the left and right main landing gear tires braking were observed leading up to the edge of the taxiway at the top of the embankment. The postincident examination of the airplane also revealed that it was not configured for takeoff. Even the pitot tube cover had remained installed on the pitot tube. During the examination, no evidence of any preimpact failures or malfunctions of the airplane or engine were discovered that would have precluded normal operation. The pilot had moderate to severe atherosclerosis of two coronary arteries. While this condition placed him at an increased risk for a sudden cardiac event, the autopsy findings indicated that the pilot initially likely had initially survived the impact. Thus, the pilot’s cardiovascular disease was not a contributing cause to the incident. Toxicology testing revealed that the pilot had used cannabis. THC and 11-OH-THC were detected in his blood at low concentrations. While the pilot was found to have cannabis in his system, it could not be determined if the concentration would have been impairing and influenced his ability to control the airplane on the taxiway. The late-night taxiing of his airplane was typical behavior for the pilot. All evidence indicated that there was no intent for flight as the airplane was not configured for, or in a position to conduct a takeoff. It is likely that, with the pitot cover still on the pitot tube, which would have prevented use of the airspeed indicator, the pilot did not realize how fast he was taxiing. He also may not have realized in the darkness and reduced visibility due to mist that he was quickly approaching the end of the taxiway. This was supported by the presence of the skid marks leading up to the edge of the taxiway and the top of the embankment. Based on this information, it is likely that the pilot lost control of the airplane while taxiing and overran the taxiway edge, after which the airplane traveled down the embankment and came to rest inverted.
Probable cause
The pilot’s loss of control during taxi, which resulted in a taxiway overrun and subsequent impact with terrain. Contributing to the incident were the low visibility conditions that existed at the airport around the time of the incident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22FA153
- Event ID
- 20220311104764
- Case number
- ERA22FA153
- 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: 02c65b957f83da483c3a7214751bfb501d67b8a079c24035ec9fc7e52dc8e50a; retrieved 2026-09-15T07:41:56.016Z.