FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX92LA179 · Homebuilt DRAGONFLY

19 Apr 1992 · Parker, AZ, United States

Homebuilt DRAGONFLY · Accident: airframe, component or system failure en route

From Prescott Regional Airport - Ernest A. Love Field (PRC) to Chino Airport (CNO)

Report a problem

Event

NTSB case
LAX92LA179
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

Homebuilt DRAGONFLY

Aircraft type
Homebuilt DRAGONFLY
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
N235JS
Operator
Moon, Maurice D. · private individual
Onboard fatalities
Unknown
Route
From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Chino Airport (CNO), Chino, 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 · 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
Airframe, component or system failure
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

  • Lubricating system › Leak

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

WHILE IN CRUISE FLIGHT, OVER DESERT TERRAIN, THE PILOT OBSERVED OIL FLOWING OVER HIS WINDSHIELD FROM A RUPTURE OF THE LUBRICATING SYSTEM. THE APPEARANCE OF OIL WAS FOLLOWED BY A REDUCTION IN ENGINE OIL PRESSURE. THE PILOT ELECTED TO EXECUTE THE EMERGENCY LANDING ON A NARROW DIRT ROAD THAT TRANSITS A STATE PARK. THE AIRPLANE'S RIGHT CANARD STRUCK HIGH VEGETATION DURING THE LANDING FLARE AND THE AIRPLANE SPUN OFF THE ROAD. THE PILOT EXITED THE WRECKAGE PRIOR TO THE ERUPTION OF A POST-CRASH FIRE.

Probable cause

AN OIL LEAK FROM AN UNIDENTIFIED SOURCE. THE HIGH VEGETATION ALONG THE FORCED LANDING AREA CONTRIBUTED TO THIS ACCIDENT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX92LA179
Event ID
20001211X14458
Case number
LAX92LA179
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: 38170a20bed56279915cd3778fcce0365966ad17bf13d3f849a53d4913a3f89c; retrieved 2026-09-23T03:13:20.449Z.