LAX03CA257 · Lancair 235
Lancair 235 · Accident: hard landing
From Camarillo International Airport (CMA) to Page Municipal Airport (PGA)
Event
- NTSB case
- LAX03CA257
- 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
- Unknown
- 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
Lancair 235
- Aircraft type
- Lancair 235
- 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
- N235WC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Camarillo International Airport (CMA), Camarillo, CATo Page Municipal Airport (PGA), Page, AZ
- 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
- 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 › Flare, misjudged
- Pilot in command › Porpoise/pilot-induced oscillation, encountered
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane porpoised during landing, and the nose landing gear collapsed. During final approach, the airplane's ground speed increased and a higher than normal sink rate developed. The pilot was unable to slow the descent in time to prevent a hard landing. After a series of bounces, the nose gear collapsed and the airplane skidded down the runway. The fuel lines broke and a fire erupted. The estimated density altitude was 7,700 feet msl.
Probable cause
The pilot's misjudged landing flare, which resulted in a hard landing and his improper recovery from a bounced landing. Inadvertent entry into a porpoise pilot-induced oscillation, and high density altitude were contributing factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03CA257
- Event ID
- 20030822X01385
- Case number
- LAX03CA257
- 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, coordinates. 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: 47312bc8dc74b562ab40465970f2bdab0ab6df9de5b4fb9887ed815ebca24014; retrieved 2026-09-22T08:53:04.016Z.