# Accident 19990214001409A: Cessna 172N, Marina, CA, February 14, 1999 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: February 14, 1999, 00:48 local time - Place: Marina, CA - Airport: Marina Municipal Airport - Damage: Substantial damage - Phase of flight: Forced Landing - Operating rules: General operating rules (Part 91) - Location: 36.7596° N, 121.6502° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=36.7596&lon=-121.6502&mi=10 - Aircraft: N7374D, registered now (https://openairdocs.org/aircraft/N7374D) (OpenAirDocs) - Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: CESSNA 172N - Reported engine: LYC O320H2AD - People aboard: 2 - Fatal injuries: 0 - Pilot flight hours: 708 total, 210 in this make and model, 35 in the last 90 days - NTSB investigation: [NTSB LAX99LA099](https://openairdocs.org/ntsb/LAX99LA099) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19990214001409A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ACFT EXPERIENCED EQUIPMENT PROBLEMS AND ENGINE FAILURE PRIOR TO CRASHING IN AN OPEN FIELD NORTH OF THE MARINA MUNICIPAL ARPT. OTHER CIRCUMSTANCES ARE UNKNOWN. (.19) ON FEBRUARY 14, 1999, AT 0048 HOURS PACIFIC STANDARD TIME, A CESSNA 172N, N7374D, CRASHED IN AN OPEN FIELD APPROXIMATELY 3/4 MILES NORTH OF THE MARINA MUNICIPAL AIRPORT IN FORT ORD, CALIFORNIA, AFTER EXPERIENCING A LOSS OF ENGINE POWER. THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE. THE PRIVATE INSTRUMENT RATED PILOT AND PASSENGER, THE SOLE OCCUPANTS, WERE NOT INJURED. THE AIRCRAFT WAS OPERATED BY THE SOCAL FLYING CLUB, LONG BEACH, CALIFORNIA, AS A PERSONAL FLIGHT CONDUCTED UNDER 14 CFR PART 91. THE FLIGHT ORIGINATED AT THE LONG BEACH AIRPORT AT 2030 ON FEBRUARY 13TH AND WAS EN ROUTE TO THE MONTEREY, CALIFORNIA, AIRPORT. NIGHT VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE DESTINATION AIRPORT. NO FLIGHT PLAN FILED. THE PILOT REPORTED THAT HE WAS ISSUED AN INSTRUMENT FLIGHT RULES (IFR) CLEARANCE TO MONTEREY BY THE OAKLAND AIR TRAFFIC CONTROL CENTER (ARTCC). HE ATTEMPTED THREE INSTRUMENT LANDING SYSTEM (ILS) APPROACHES INTO MONTEREY, BUT WAS "HAVING TROUBLE WITH THE AIRCRAFT NAVIGATION EQUIPMENT." AFTER THE SECOND APPROACH, THE PILOT WAS VECTORED TO AND CLEARED FOR THE ILS RUNWAY 10R APPROACH. HE INFORMED OAKLAND ARTCC THAT HE WAS LOW ON FUEL. THE REPORTED THAT HE BROKE OUT OF THE CLOUDS AND SAW AN AIRPORT BEACON AHEAD. HE RELAYED THROUGH ANOTHER AIRCRAFT THAT HE HAD MONTEREY IN SIGHT AND WANTED TO CANCEL HIS IFR CLEARANCE. HE FLEW TOWARD THE BEACON AND ATTEMPTED TO ACTIVATE THE AIRPORT'S PILOT-CONTROLLED LIGHTING. THE PILOT REPORTED THAT THE LIGHTS DID NOT ILLUMINATE AND HE REALIZED HE WAS APPROXIMATELY MID-FIELD OF THE RUNWAY AND TOO HIGH FOR A SAFE LANDING. HE INITIATED A GO-AROUND AND THE ENGINE QUIT. HE STATED THAT THE ENGINE DID NOT SPUTTER OR COUGH, BUT SEEMED TO QUIT SUDDENLY. THE PILOT REPORTED THAT HE HAD NOT EXPERIENCED ANY PREVIOUS PROBLEMS WITH THE ENGINE DURING THE FLIGHT. THE AIRCRAFT CRASHED APPROXIMATELY 7 NAUTICAL MILES NORTH OF THE MONTEREY AIRPORT, AND ABOUT 3/4 MILES NORTH OF THE MARINA AIRPORT. THE NOSE GEAR SHEARED OFF AND THE AIRCRAFT CAME TO REST INVERTED. THE AIRPLANE WAS EXAMINED FOLLOWING RECOVERY. THE MECHANIC REPORTED THAT HE PULLED THE WINGS OFF AND NOTED ONLY "3 DROPS" OF FUEL. HE STATED THAT THE GASCOLATOR AT THE FIREWALL CONTAINED 1/2 INCH OF FUEL AND THE CARBURETOR BOWL AND FUEL LINES WERE EMPTY. ACCORDING TO THE AIRCRAFT OWNER, THE HOBBS METER HAD ADVANCED 4.4 HOURS DURING THE ACCIDENT FLIGHT. (.4)THE PILOT ATTEMPTED THREE ILS APPROACHES, BUT REPORTED THAT HE WAS HAVING PROBLEMS WITH THE NAVIGATION EQUIPMENT DURING EACH APPROACH. AT THE END OF THE THIRD APPROACH HE ADVISED ARTCC THAT HE WAS LOW ON FUEL, WITH ONLY ABOUT 30 MINUTES REMAINING. THE PILOT RELAYED THROUGH ANOTHER AIRCRAFT THAT HE HAD VISUAL CONTACT WITH THE AIRPORT AND WAS BELOW THE CLOUDS. HE CANCELED IFR AND REPORTED THAT LANDING WAS ASSURED. HE SAW AN AIRPORT BEACON AHEAD, FLEW TOWARD IT, AND ATTEMPTED TO ACTIVATE THE PILOT-CONTROLLED LIGHTING. THE LIGHTS DID NOT ILLUMINATE AND THE PILOT REALIZED HE WAS ABOUT MIDFIELD OF THE RUNWAY AND TOO HIGH FOR A SAFE LANDING. HE INITIATED A GO-AROUND AND THE ENGINE QUIT. THE AIRCRAFT CRASHED ABOUT 7 MILES NORTH OF THE PILOT'S INTENDED DESTINATION AIRPORT AND ABOUT 3/4 MILES NORTH OF AN UNCONTROLLED AIRPORT. THE AIRCRAFT WAS EXAMINED FOLLOWING RECOVERY. NO FUEL WAS FOUND IN THE FUEL TANKS OR LINES, AND NO EVIDENCE OF LEAKAGE WAS OBSERVED. COMPARISON OF THE HOBBS METER READINGS BETWEEN DEPARTURE AND THE ACCIDENT R EVEALED THAT THE PILOT THAT HE HAD NOT EXPERIENCED ANY MECHANICAL PROBLEMS WITH THE ENGINE OR AIRCRAFT WERE TESTED WITH NO DISCREPANCIES FOUND. A FUNCTIONAL TEST OF THE GROUND NAVIGATIONAL AIDES WAS PERFORMED FOLLOWING THE ACCIDENT OF INSTRUMENT CURRENCY. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB LAX99LA099](https://openairdocs.org/ntsb/LAX99LA099), Feb 14, 1999: Cessna 172N (N7374D), Fort Ord, CA, substantial damage. Probable cause: Fuel exhaustion due to the pilot's becoming lost and disoriented during multiple attempts at completing an ILS approach. ## Other reports on N7374D (3) Matched to the same aircraft by N-number and date. - [Incident 19900520035399I](https://openairdocs.org/incident/19900520035399I), May 20, 1990: Cessna 172N (N7374D), Gila Bend, AZ. Unable to contact Gila Bend. Elected to land at airport nearby to refuel. Mistakenly landed on air force base. - [Incident 19840517067509I](https://openairdocs.org/incident/19840517067509I), May 17, 1984: Cessna 172N (N7374D), Fresno, CA, Minor damage. Unable to restart engine after it quit the second time. Landed in park. Out of fuel one mile south of airport. - [Accident 19811013074151A](https://openairdocs.org/incident/19811013074151A), Oct 13, 1981: Cessna 172N (N7374D), Santa Monica, CA, Substantial damage. Collided with N7775F at a taxiway intersection. Had stop sign at intersection. 7775F had right of way. From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.