LAX00LA349 · Woodruff Lancair 360
Woodruff Lancair 360 · Accident: hard landing
From Chino Airport (CNO) to L05
Event
- NTSB case
- LAX00LA349
- 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
Woodruff Lancair 360
- Aircraft type
- Woodruff Lancair 360
- 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
- N360HW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chino Airport (CNO), Chino, CATo L05
- 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
- Landing gear, main gear › Separation
- Pilot in command › Airspeed(vref), not maintained
- Pilot in command › Flare, improper
- Pilot in command › Remedial action, inadequate
- Pilot in command › Stall/mush, inadvertent
- Terrain condition › Rock(s)/boulder(s)
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane bounced and veered off the left side of the runway. The pilot was on final and maintaining 85 knots as he initiated his flare. During the flare, he encountered wind shear and the airplane dropped from about 5 feet. The left main landing gear struck some large rocks and separated from the airplane. The pilot said a big upslope was near the runway. He estimated the winds to be from 010 degrees at 10 knots.
Probable cause
The pilot failed to maintain an adequate airspeed margin, resulting in a stall/mush and hard landing, and failed to maintain directional control and the left main landing gear separated when it struck a rock.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX00LA349
- Event ID
- 20001212X22021
- Case number
- LAX00LA349
- 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: ffc33137f6b01d843205251ad1ab9c721f873fee62c52985d301469a08aa03db; retrieved 2026-09-22T12:25:36.453Z.