FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX94LA380 · Singer KITFOX IV

12 Sept 1994 · Apple Valley, CA, United States

Singer KITFOX IV · Accident: total loss of engine power (non-mechanical) during an emergency descent

From Laughlin Bullhead International Airport (IFP) to Apple Valley Airport (APV)

Report a problem

Event

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

Singer KITFOX IV

Aircraft type
Singer KITFOX
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
N93CM
Operator
Thomas G. Singer · private individual
Onboard fatalities
Unknown
Route
From Laughlin Bullhead International Airport (IFP), Bullhead City, AZTo Apple Valley Airport (APV), 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
Emergency descent
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 (non-mechanical)
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

  • Fluid, fuel › Exhaustion
  • Pilot in command › Fuel consumption calculations, inaccurate
  • Pilot in command › Refueling, not performed

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

NTSB narrative

THE PILOT REPORTED THAT HE SHOULD HAVE REFUELED PRIOR TO TAKING OFF FOR THE CROSS-COUNTRY FLIGHT. EN ROUTE, HE OBSERVED THE FUEL TANK SIGHT GAGES AND BELIEVED THEY INDICATED OVER 2 HOURS OF FUEL REMAINED. AFTER FLYING FOR 2.2 HOURS, FUEL EXHAUSTION OCCURRED. THE PILOT MADE A FORCED LANDING ON A DIRT ROAD AND, DURING THE ROLL-OUT, THE AIRPLANE COLLIDED WITH BRUSH AND NOSED OVER. THE PILOT FURTHER REPORTED THAT HE HAD BUILT THE AIRPLANE, AND THE FUEL CONSUMPTION RATE WAS HIGHER THAN EXPECTED. HE STATED THAT HE HAD BEEN 'OVERLY ENTHUSED' WITH THE AIRPLANE AND ENGINE'S PERFORMANCE.

Probable cause

fuel exhaustion due to the pilot's failure to refuel prior to departure, and his inaccurate en route fuel consumption calculations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX94LA380
Event ID
20001206X02303
Case number
LAX94LA380
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: ad3e45520ac3bea7582d072f22ef3419821178a99ed5ea4e4aa52763ea42813d; retrieved 2026-09-23T00:40:03.339Z.