# Accident 19951120037809A: Piper PA32300, Fullerton, CA, November 20, 1995

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 20, 1995, 06:34 local time
- Place: Fullerton, CA
- Airport: Fullerton Municipal
- Damage: Destroyed
- Phase of flight: Final Approach-IFR
- Operating rules: General operating rules (Part 91)
- Location: 33.8760° N, 117.9630° W: Placed by OpenAirDocs from the FAA’s distance and direction from , within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.8760&lon=-117.9630&mi=10
- Aircraft: N888JK, a cancelled registration (https://openairdocs.org/deregistered/N888JK-2013-09-17) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- Reported engine: LYC IO540K1G5D
- People aboard: 2
- Fatal injuries: 3
- Pilot flight hours: 1,200 total, 30 in the last 90 days
- NTSB investigation: [NTSB LAX96FA050](https://openairdocs.org/ntsb/LAX96FA050) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19951120037809A

## Narrative

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

ON BELOW MINIUN APPROACH COLLIDED WITH TREES, POLES AND APARTMENT. PARAPLEGIC CFI LACKED SPECIAL RUDDER EQUIPMENT.

## 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 LAX96FA050](https://openairdocs.org/ntsb/LAX96FA050), Nov 20, 1995: Piper PA-32-300 (N888JK), Fullerton, CA, destroyed, 3 fatal. Probable cause: the pilot-in-command's failure to follow IFR procedures in that he descended below the minimum descent altitude and failed to execute a missed approach. Contributing to the accident was the…

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.