FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX90LA169 · Piper PA-30

11 May 1990 · El Monte, CA, United States

Piper PA-30 · Accident: loss of control in flight during landing

From San Gabriel Valley Airport (EMT) to an unrecorded destination

Report a problem

Event

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

Piper PA-30

Aircraft type
Piper PA-30
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
N505GM
Operator
Jonathan D. Smalldridge · private individual
Onboard fatalities
Unknown
Route
From San Gabriel Valley Airport (EMT)To not recorded
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
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

  • Pilot in command › Powerplant controls, improper use of
  • Pilot in command › Raising of flaps, not performed

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

NTSB narrative

THE PILOT STATED HE WAS ON A LOCAL FAMILIARIZATION FLIGHT WITH A SWISS NATIONAL FRIEND, REPORTED TO BE A CERTIFICATED PRIVATE PILOT. HE SAID HE PLANNED TO DO A TOUCH AND GO LANDING, BUT NEGLECTED TO RECONFIGURE THE AIRCRAFT AFTER LANDING FOR THE TAKEOFF PORTION. HE APPLIED FULL TAKEOFF POWER WITH FULL FLAPS DOWN AND MIXTURES LEANED. THE OWNER/PILOT WAS FLYING THE AIRCRAFT FROM THE RIGHT FRONT SEAT. THE AIRCRAFT BECAME AIRBORNE PREMATURELY AND STARTED TO ROLL TO THE RIGHT, HIS REACTION WAS TO RETRACT THE LANDING GEAR AND RETARD THE THROTTLES. AT ABOUT THAT TIME, THE RIGHT WING STRUCK THE RUNWAY AND STARTED THE CRASH SEQUENCE.

Probable cause

THE FAILURE OF THE PILOT IN COMMAND TO ADEQUATELY CONFIGURE THE AIRCRAFT FOR THE TAKEOFF PORTION OF A TOUCH AND GO.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX90LA169
Event ID
20001212X23172
Case number
LAX90LA169
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: c53b2726075b5de124fbf6c89d3a3e96515b7f6b1d741a06b098576ec34f477b; retrieved 2026-09-21T23:54:03.250Z.