LAX03LA056 · Nicholson LANCAIR 320
Nicholson LANCAIR 320 · Accident: total loss of engine power (mechanical failure) en route
From Chino Airport (CNO) to French Valley Airport (F70)
Event
- NTSB case
- LAX03LA056
- 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
Nicholson LANCAIR 320
- Aircraft type
- Nicholson LANCAIR 320
- 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
- N364M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chino Airport (CNO), Chino, CATo French Valley Airport (F70), MURRIETA/TEMECU, 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
- En route · climb to cruise
- 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
- Total loss of engine power (mechanical failure)
- 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
- Fluid, oil › Loss, total
- Lubricating system, oil line › Disconnected
- Owner/pilot mechanic › Maintenance, installation, improper
- Powerplant › Seized
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The day before the accident the pilot/builder of the experimental airplane had installed an air/oil separator on the airplane. In the process, he had removed a high-pressure oil line from the oil cooler and then reattached it "firmly" with a screw clamp "as best he could." A taxi test was conducted with the engine cowling removed to check for oil leaks, and none were found. During climb out, at 6,500 feet, the engine lost oil pressure, and the pilot decided to make an emergency landing on an interstate highway. During final approach, the engine seized, and the airplane struck the roof of a motor home and came to rest on its belly. According to the pilot, the engine seized after the "hi presssure oil line to oil cooler was pushed or pulled off, draining all oil" from the engine.
Probable cause
The pilot/builder's improper maintenance procedure for reattaching a high-pressure oil line, which resulted in the oil line disconnecting during flight, followed by a loss of oil and engine seizure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03LA056
- Event ID
- 20030103X00008
- Case number
- LAX03LA056
- 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: e6dd96cef0ce1cbbeadf1f373ef814f2ade6c6a03589f9bae302be18092ebc25; retrieved 2026-09-22T09:45:05.135Z.