LAX87DVM04 · Rand KR-2
Rand KR-2 · Accident: loss of engine power en route
From Watsonville Municipal Airport (WVI) to an unrecorded destination
Event
- NTSB case
- LAX87DVM04
- 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
Rand KR-2
- Aircraft type
- Rand KR-2
- 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
- N75JL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Watsonville Municipal Airport (WVI), Watsonville, 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 · 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
- Loss of engine power
- 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
- Tree(s)
- 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
SHORTLY AFTER TAKE-OFF ON RUNWAY 19, THE ENGINE BEGAN 'SPUTTERING' AND LOSING POWER. THE PILOT TRIED ADJUSTING MIXTURE AND THROTTLE CONTROLS. THE ENGINE CONTINUED 'SPUTTERING' AND LOSING POWER AND THE PILOT INITIATED AN EMERGENCY DESCENT. HAVING GAINED NO MORE THAN 200' AGL, AND DUE TO TERRAIN FACTORS THE PILOT ATTEMPTED TO DESCEND OVER A LINE OF TREES AND LAND IN A FIELD. THE PILOT COULD NOT MAINTAIN SUFFICIENT ALTITUDE TO CLEAR THE TREES AND COLLIDED WITH THE TERRAIN. THE PILOT DISASSEMBLED THE ENGINE AND FOUND NO BROKEN PARTS. HOWEVER, HE NOTED AN UNIDENTIFIED WHITE CHALKY SUBSTANCE IN AND AROUND THE 'LEFT' TWO CYLINDERS. THE LOSS OF POWER WAS NOT DETERMINED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX87DVM04
- Event ID
- 20001213X31216
- Case number
- LAX87DVM04
- 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: 46296ef9f4a45c7c5f78a10a3a50fa3ec30093a657f73eeed41a3d1fbb536f74; retrieved 2026-09-22T00:50:01.783Z.