# Accident 19911003044599A: Cessna 172N, Palo Alto, CA, October 3, 1991

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 3, 1991, 09:54 local time
- Place: Palo Alto, CA
- Airport: Palo Alto Airport-Santa Clara Cou
- Damage: Substantial damage
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Location: 37.4497° N, 122.0993° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.4497&lon=-122.0993&mi=10
- Aircraft: N3318E, registered now (https://openairdocs.org/aircraft/N3318E) (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
- Fatal injuries: 0
- Pilot flight hours: 140 total, 140 in this make and model, 56 in the last 90 days
- NTSB investigation: [NTSB LAX92LA003](https://openairdocs.org/ntsb/LAX92LA003) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19911003044599A

## Narrative

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

DRIFTED NOSE HIGH OFF RUNWAY ON TAKEOFF. STALL MUSHED. STRUCK TREES. RUDDER TRIM 50 PERCENT OFF NEUTRAL.

## 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 LAX92LA003](https://openairdocs.org/ntsb/LAX92LA003), Oct 3, 1991: Cessna C-172N (N3318E), Palo Alto, CA, substantial damage. Probable cause: AN INFLIGHT LOS OF CONTROL DUE TO THE FAILURE OF THE STUDENT PILOT TO CORRECTLY CONFIGURE THE RUDDER TRIM FOR TAKEOFF.

## Other reports on N3318E (2)

Matched to the same aircraft by N-number and date.

- [Incident 20120108000749I](https://openairdocs.org/incident/20120108000749I), Jan 8, 2012: Cessna 172N (N3318E), Hawthorne, CA, Substantial damage. Airman landed after hours, tower was closed. During taxi to parking, aircraft landing light began turning on and off. Airman reached down to work landing…
- [Accident 20071117827099A](https://openairdocs.org/incident/20071117827099A), Nov 17, 2007: Cessna 172N (N3318E), Atwater, CA, Substantial damage. (-23) On 11/17/2007 the student pilot [privacy data omitted] was conducting his first solo flight at Castle Airport (mer) in Atwater, CA when the accident…

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.