LAX97LA131 · Zenair 601
Zenair 601 · Accident: loss of engine power en route
From O17 · Grass Valley, CA to an unrecorded destination
Event
- NTSB case
- LAX97LA131
- 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
- 1 · 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
Zenair 601
- Aircraft type
- Zenair 601
- 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
- N4073T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From O17 · Grass Valley, CATo not recorded
- 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 · 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
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
No witnesses observed the aircraft when it impacted terrain in a pasture. A witness who lives about 1 mile from the accident site reported that the aircraft's engine was cutting out as it flew over his location. Another witness, inside his home near the accident site, did not hear the engine at all; he reported hearing only a whoosh and a thump. The pilot purchased the aircraft 7 months prior and this was his first flight in the aircraft. He had not had any checkout, and according to his logbook, had not piloted an aircraft in the previous 4 months. The last maintenance entry in the aircraft logbook was an annual inspection performed 18 months prior. A toxicology analysis performed by the FAA's Civil Aeromedical Institute detected impairing amounts of the drug Diphenhydramine in the pilot's blood and urine.
Probable cause
Loss of engine power for undetermined reasons. Factors in the accident were the pilot's lack of recent experience, lack of experience in the type aircraft, and physical impairment due to drugs.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX97LA131
- Event ID
- 20001208X07583
- Case number
- LAX97LA131
- 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: 65b1e003b4b6291983df9dda203f4a12b96ab8a2bbba8f431986a8be58d692ab; retrieved 2026-09-20T23:01:06.863Z.