# Accident 19890618015989A: Cessna 172E, Grass Valley, CA, June 18, 1989

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 18, 1989, 16:45 local time
- Place: Grass Valley, CA
- Airport: Nevada County Airpark
- Damage: Substantial damage
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 39.1794° N, 120.9792° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=39.1794&lon=-120.9792&mi=10
- Aircraft: N3618S, a cancelled registration (https://openairdocs.org/deregistered/N3618S-1991-08-16) (OpenAirDocs)
- Registry model: Cessna 172E (registry code 2072412, https://openairdocs.org/model/cessna-172e) (OpenAirDocs)
- Reported make and model: CESSNA 172E
- Reported engine: CONT O300D
- People aboard: 4
- Fatal injuries: 0
- Pilot flight hours: 2,795 total, 1,740 in this make and model, 27 in the last 90 days
- NTSB investigation: [NTSB LAX89LA221](https://openairdocs.org/ntsb/LAX89LA221) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19890618015989A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ENGINE STOPPED ON INITIAL CLIMBOUT. STRUCK BRIDGE ABUTMENT UPON LANDING MAGNETOS ARCING.

## 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 LAX89LA221](https://openairdocs.org/ntsb/LAX89LA221), Jun 18, 1989: Cessna 172E (N3618S), Grass Valley, CA, substantial damage. Probable cause: FAILURE TO PERFORM MAINTENANCE INSPECTIONS PRESCRIBED BY THE MAGNETO, ENGINE AND AIRCRAFT MANUFACTURERS. THE HIGH DENSITY ALTITUDE AND TERRAIN CONDITIONS WERE CONTRIBUTING FACTORS.

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.