20000618035819I

Incident · Damage unknown

FAA incident report · Cessna 172G · Yuma, AZ · June 18, 2000

Date: June 18, 2000 · 20:30 local
Place: Yuma, AZ
Phase of flight: Descent
Operating rules: General operating rules (Part 91)
Damage: Damage unknown
Aircraft: N3804L
Reported as: Cessna 172G
Reported engine: Continental O300*
People aboard: 1
Fatal injuries: 0

N3804LRegistered now · Cessna 172GS/N 17253973 · Built 1965 Airframe modelCessna 172G Engine modelContinental 0-300 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23)On said date, the pilot of N3804L flew across country flight from; fallbrook, CA to Yuma, AZ. Approximately 14 miles from the Yuma airport the aircraft engine began to sputter and then finally quit about 5 miles away from the airport. The aircraft did not have sufficient altitude to glide to the airport and force-landing in a plowed filed. Investigation of the incident revealed that the pilot did not allow for sufficient fuel to complete the flight.

As the FAA filed it

(-23)ON SAID DATE, THE PILOT OF N3804L FLEW ACROSS COUNTRY FLIGHT FROM; FALLBROOK, CA TO YUMA, AZ. APPROXIMATELY 14 MILES FROM THE YUMA AIRPORT THE AIRCRAFT ENGINE BEGAN TO SPUTTER AND THEN FINALLY QUIT ABOUT 5 MILES AWAY FROM THE AIRPORT. THE AIRCRAFT DID NOT HAVE SUFFICIENT ALTITUDE TO GLIDE TO THE AIRPORT AND FORCE-LANDING IN A PLOWED FILED. INVESTIGATION OF THE INCIDENT REVEALED THAT THE PILOT DID NOT ALLOW FOR SUFFICIENT FUEL TO COMPLETE THE FLIGHT.