LAX90LA134 · Aeronca 7AC
Aeronca 7AC · Accident: loss of control in flight during landing
From P52 to P52
Event
- NTSB case
- LAX90LA134
- 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
- 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
- Visual Meteorological Cond
Aeronca 7AC
- Aircraft type
- Aeronca 7
- 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
- N82805
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From P52To P52
- 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
- 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 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 performance, landing capability › Exceeded
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Compensation for wind conditions, not possible
- Pilot in command › Go-around, not performed
- Pilot in command › Planned approach, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
GROUND WITNESSES AT THE AIRPORT REPORTED TO FAA INSPECTORS FROM THE SCOTTSDALE, ARIZONA, FSDO THAT THE PILOT WAS ATTEMPTING A LANDING WITH A DIRECT CROSS WIND THE WITNESSES ESTIMATED AT ABOUT 30 KNOTS. THE PILOT REPORTEDLY LOST CONTROL OF THE AIRCRAFT NEAR THE TOUCH DOWN POINT ON THE RUNWAY AND COLLIDED WITH THE GROUND ON THE NORTH SIDE OF THE AIRPORT. REPEATED REQUESTS FOR THE COMPLETION OF A PILOT/OPERATOR AIRCRAFT ACCIDENT REPORT FORM MET WITH NO RESPONSE FROM THE PILOT.
Probable cause
THE FAILURE TO THE PILOT TO MAINTAIN CONTROL OF THE AIRCRAFT. CONTRIBUTING TO THE ACCIDENT WAS THE DECISION OF THE PILOT TO ATTEMPT A LANDING IN A CROSS WIND CONDITION WELL BEYOND THE CAPABILITY OF THE AIRCRAFT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90LA134
- Event ID
- 20001212X22942
- Case number
- LAX90LA134
- 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. 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: d78b7bb685a22b3fa606e54c6115457629752fd6f7a3a52aa224385dc68f3074; retrieved 2026-09-21T15:43:50.670Z.