LAX00LA110 · Piper PA-34-200
Piper PA-34-200 · Accident: hard landing
From McClellan-Palomar Airport (CRQ) to L35
Event
- NTSB case
- LAX00LA110
- 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-34-200
- Aircraft type
- Piper PA-34
- 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
- N15202
- Operator
- Kenneth K. Gheysar · private individual
- Onboard fatalities
- Unknown
- Route
- From McClellan-Palomar Airport (CRQ), Carlsbad, CATo L35
- 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
- Hard landing
- 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
- 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(vref), inadequate
- Pilot in command › Flight manuals, disregarded
- Pilot in command › Stall/mush, encountered
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Approaching runway 26, the pilot was advised by airport personnel on the common traffic advisory frequency (CTAF) that the automated weather observing system (AWOS) indicated the wind was 13 knots with gusts to 28 knots. Also, its direction was variable from 170 to 230 degrees. The pilot reported that he slowed the airplane's approach speed to 90 knots and extended the flaps to the normal midrange position. About 30 feet above the runway he encountered a wind gust and lost control of the airplane. It impacted the runway, yawed sideways, and came to a stop with a collapsed landing gear and bent fuselage. The airplane's manufacturer suggests in its "Pilot's Operating Manual," that in crosswind or high-wind conditions, a higher than normal (90 knot) approach speed be used and the pilot should consider using no flaps.
Probable cause
The pilot's selection of a final approach airspeed in variance with the manufacturer's recommendations, which was too slow for the gusty and variable crosswind conditions, which resulted in a stall/mush and a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX00LA110
- Event ID
- 20001212X20525
- Case number
- LAX00LA110
- 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: 28a6ee64cf5207c319974b4bbad62a2eb01a66748934b522c59401fdaa129e59; retrieved 2026-09-21T20:18:02.819Z.