FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX98LA194 · Scott DRAGONFLY

13 Jun 1998 · Mecca, CA, United States

Scott DRAGONFLY · Accident: loss of engine power en route

From Riverside Municipal Airport (RAL) to Chandler Municipal Airport (CHD)

Report a problem

Event

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

Scott DRAGONFLY

Aircraft type
Scott 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
N824JC
Onboard fatalities
Unknown
Route
From Riverside Municipal Airport (RAL), Riverside, CATo Chandler Municipal Airport (CHD), Chandler, AZ
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
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
Fuel exhaustion
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 › Aircraft preflight, inadequate
  • Pilot in command › Refueling, inadequate

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

NTSB narrative

The pilot had received approximately 2 hours of instruction in the accident aircraft before the accident flight. During climbout the fuel gage for the header tank was indicating a lowering trend, and when he leveled the aircraft to obtain another reading, he noted a lesser amount than expected. He attempted to make a precautionary landing at an alternate airport; however, 6 miles from the alternate airport the engine surged and lost power. The pilot attempted an unsuccessful restart, and made an emergency landing in a soft dirt field. The previous owner of the aircraft stated that on the day of the accident the aircraft was refueled out of a gas can, but he did not remember the amount of fuel. He stated that the aircraft carries approximately 16 gallons of fuel and the header tank has approximately 45 minutes of flight time. The previous owner stated that the transfer pump is supposed to be on at all times, and the fuel is transferred from the main tank to the header tank via a transfer pump. The header tank is supposed to remain full at all times through this procedure. A site gage is available and when the fuel drops below the green mark it indicates that the transfer pump is either not on or there is something wrong with it. When the transfer pump is off, a red caution light illuminates to let the pilot know that something is not working properly. According to a fueling log obtained from the local fuel company, two miscellaneous fuel sales were made on the day of the accident. One sale was for 10.8 gallons with no aircraft identifier, the other sale was for 5.2 gallons and was a cash sale in a gas can.

Probable cause

The pilot's inadequate preflight inspection and his failure to ensure sufficient fuel was in the airplane, which subsequently led to fuel exhaustion. A related factor was the soft terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX98LA194
Event ID
20001211X10353
Case number
LAX98LA194
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: c7e0593486c8d172394c1388945587d5893f65b1d39aec54cf36d20bfa8be394; retrieved 2026-09-22T17:40:49.760Z.