LAX06CA019 · Harmel RV6A
Harmel RV6A · Accident: hard landing
From Mesquite Airport (67L) to Oceanside Municipal Airport (OKB)
Event
- NTSB case
- LAX06CA019
- 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
Harmel RV6A
- Aircraft type
- Harmel RV6
- 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
- N221MH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mesquite Airport (67L), Mesquite, NVTo Oceanside Municipal Airport (OKB), Oceanside, CA
- 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, inadvertent
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 on landing and nosed over after separation of the nose wheel. The pilot said he was on final approach at 70 mph over the runway numbers. He leveled out the airplane for touchdown and believed his main landing gear were on the ground for about 100 yards; however, he was mistaken, and in fact, the airplane had not touched down. He released backpressure on the elevator control believing he was on the ground and the airplane's nose wheel touched down on the runway and the airplane began to porpoise. The pilot attempted to ride out the ensuing oscillations, but they only worsened. The nose wheel broke off and the airplane drifted to the right side of the runway where it exited the paved surface. The nose landing gear strut dug into the dirt and the airplane nosed over.
Probable cause
the pilot-induced oscillations encountered on landing following the pilot's misjudged landing flare and premature release of elevator backpressure during touchdown.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06CA019
- Event ID
- 20051122X01869
- Case number
- LAX06CA019
- 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: 7754fa51482b4bc2b01d6155154fa7483be6ab8046564d4e226761a1c9e2f19a; retrieved 2026-09-22T05:17:52.747Z.