LAX89LA254 · Piper PA-28-161
Piper PA-28-161 · Accident: loss of control in flight on approach
From McClellan-Palomar Airport (CRQ) to L32
Event
- NTSB case
- LAX89LA254
- 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-28-161
- Aircraft type
- Piper PA-28
- 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
- N2933D
- Operator
- Paul W. Searby · private individual
- Onboard fatalities
- Unknown
- Route
- From McClellan-Palomar Airport (CRQ), Carlsbad, CATo L32
- 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
- Approach · VFR go-around
- 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
- 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/mush; Tree(s)
- 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, not attained
- Pilot in command › Climb, not possible
- Pilot in command › Pull-up, excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A WITNESS INDICATED THE AIRPLANE WAS ABOUT HALF WAY DOWN THE RUNWAY WHEN THE PILOT INITIATED A GO-AROUND. HE SAID THE FLAPS APPEARED TO BE IN THE FULL UP POSITION, AND THE NOSE WAS VERY HIGH AND THE AIRPLANE APPEARED TO BE MUSHING. THE PILOT STATED HE HAD FULL THROTTLE BUT THE AIRPLANE WOULD NOT CLIMB. HE SAID THAT WHEN HE REALIZED HE WAS NOT GOING TO BE ABLE TO CLIMB OVER THE TREES, HE PULLED THE POWER OFF AND STALLED THE AIRPLANE INTO THE BUSHES AND TREES.
Probable cause
THE FAILURE OF THE PILOT-IN-COMMAND TO ATTAIN PROPER AIRSPEED DURING THE GO-AROUND. THE LACK OF AIRSPEED DID NOT PERMIT THE AIRPLANE TO CLIMB AND THE PILOT INTENTIONALLY STALLED THE AIRPLANE INTO THE TREES. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT DELAYING THE GO-AROUND AFTER HE MISJUDGED THE TOUCHDOWN POINT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89LA254
- Event ID
- 20001213X28879
- Case number
- LAX89LA254
- 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: f21f52a64fc910e153dbd635e3e84a00dadc38a1329f48342855ada2f0de34f8; retrieved 2026-09-22T00:06:17.856Z.