# Accident 20050102000439A: Piper PA46350P, Palo Alto, CA, January 2, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 2, 2005, 13:37 local time
- Place: Palo Alto, CA
- Airport: Palo Alto Airport-Santa Clara Cou
- Damage: Substantial damage
- Phase of flight: Go Round (Aborted VFR)
- Operating rules: General operating rules (Part 91)
- Location: 37.4611° N, 122.1150° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.4611&lon=-122.1150&mi=10
- Aircraft: N4165P, a cancelled registration (https://openairdocs.org/deregistered/N4165P-2006-02-02) (OpenAirDocs)
- Registry model: Piper PA 46-350P (registry code 7104620, https://openairdocs.org/model/piper-pa-46-350p) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA46350P
- Reported engine: LYC TIO540AE2A
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 988 total, 500 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB LAX05FA058](https://openairdocs.org/ntsb/LAX05FA058) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050102000439A

## Narrative

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

(-23) AT CRUISE ENROUTE TO PALO ALTO (PAO) PILOT (PIC) NOTICED A WARNING HORN INDICATING HIGH OIL TEMP, AND THE GAUGE WAS FLUCTUATING. A PRECAUTIONARY LANDING WAS MADE AT MODESTO, OIL LEVEL CHECKED AND TOPPED OFF, ENGINE RUN UP NORMAL SO DEPARTED IFR TO PAO. IN CRUISE NOTICED WARNING HORN AGAIN CONSIDERED LANDING AT LIVERMORE, BUT WEATHER WAS NOT ACCEPTABLE. CONTINUED TOWARDS PAO AND DISCUSSED WITH NORCAL ABOUT LANDING AT SAN JOSE, BUT OPTED TO CONTINUE TO PAO DUE TO ONLY AN ADDITIONAL 8 MIN FARTHER. CONTACTED PAO TOWER AND INDICATED LANDING WITH POWER OFF AND TOLD THE TOWER ABOUT INDICATION ISSUES. SET UP TO LAND ON RWY 31 WITH A STANDARD PATTERN, BUT TURNED TO BASE EARLY, CONTINUED PATTERN WITH POWER SET AT 20 INCHES OF MANIFOLD PRESSURE. SHE REALIZED SHE WAS HIGH BUT WAS CONCERNED ABOUT ENGINE FAILURE AND DID NOT WANT TO GO AROUND. TOUCHED DOWN BEYOND MIDDLE OF RWY ON DEPARTURE SIDE. REMEMBERS SLIDING AND SEEING THE END OF THE RWY APPROACHING. WAS CONCERNED ABOUT HITTING THE DIKE HEAD ON AND APPLIED POWER AND ATTEMPTED TO LIFT THE NOSE. THE AIRCRAFT PITCHED UP AND LEFT WING DIPPED DOWN. LEFT WING CONTACTED THE DIKE BROKE OFF AS AIRCRAFT CARTWHEELED OVER THE DIKE AND STOPPED FACING RWY 13.

## 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 LAX05FA058](https://openairdocs.org/ntsb/LAX05FA058), Jan 2, 2005: Piper PA-46-350P (N4165P), Palo Alto, CA, substantial damage. Probable cause: the pilot's misjudged distance and speed on final approach, which led to a long landing and a runway overrun. Also causal was the pilot's inadequate in-flight decision to continue flight with…

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.