Casualties unknown

Aircraft Crashes After Go-Around; No Fuel Found in Tanks (N7374D)

Fort Ord, CA, US

On February 14, 1999, a Cessna 172N (registration N7374D) was involved in an aviation accident near Fort Ord, CA. Investigators recorded the probable cause as: Fuel exhaustion due to the pilot's becoming lost and disoriented during multiple attempts at completing an ILS approach. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 1 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

During a flight with navigation difficulties, the pilot attempted three ILS approaches, reported low fuel, canceled IFR, and initiated a go-around when too high. The engine quit and the aircraft crashed north of the intended airport; no fuel was found in the tanks.

Accident Sequence

The pilot conducted three instrument landing system (ILS) approaches, reporting issues with the navigation equipment during each approach. Following the third approach, the pilot informed the air route traffic control center (ARTCC) that fuel was low, with approximately 30 minutes remaining. The pilot relayed via another aircraft that visual contact with the airport was established and that the aircraft was below the clouds. The pilot canceled the instrument flight rules (IFR) flight plan and stated that landing was assured.

After spotting an airport beacon ahead, the pilot flew toward it and attempted to activate the pilot-controlled lighting system. The lights did not illuminate, and the pilot realized the aircraft was midfield of the runway and too high for a safe landing. The pilot initiated a go-around, during which the engine ceased operation. The aircraft crashed approximately 7 miles north of the intended destination airport and about three-quarters of a mile north of an uncontrolled airport.

Post-Accident Examination

Following recovery, the aircraft was examined. No fuel was present in the fuel tanks or fuel lines, and no evidence of fuel leakage was observed. Comparison of Hobbs meter readings indicated that the pilot had flown 4.4 hours during the accident flight. The pilot reported no mechanical issues with the engine or aircraft prior to the accident. The aircraft's navigation radios underwent testing with no discrepancies identified. Ground navigational aids were functionally tested after the accident, and no discrepancies were noted. The pilot did not provide evidence of instrument currency.

All Cessna 172 accidents →

Frequently asked questions

What happened in the 14 Feb 1999 Cessna 172N accident near Fort Ord, CA?

During a flight with navigation difficulties, the pilot attempted three ILS approaches, reported low fuel, canceled IFR, and initiated a go-around when too high. The engine quit and the aircraft crashed north of the intended airport; no fuel was found in the tanks.

What aircraft was involved and where did it happen?

The accident on 14 Feb 1999 involved a Cessna 172N, registration N7374D, at Fort Ord, CA.

What was the probable cause of the accident?

Fuel exhaustion due to the pilot's becoming lost and disoriented during multiple attempts at completing an ILS approach.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001205X00190. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.