# Accident 20020427007619A: Piper PA34200T, Provo, UT, April 27, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 27, 2002, 10:52 local time
- Place: Provo, UT
- Airport: Provo Municipal Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.4497° N, 111.8553° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.4497&lon=-111.8553&mi=10
- Aircraft: N132CP, a cancelled registration (https://openairdocs.org/deregistered/N132CP-2002-10-08) (OpenAirDocs)
- Registry model: Piper PA-34-200T (registry code 7103406, https://openairdocs.org/model/piper-pa-34-200t) (OpenAirDocs)
- Registry engine: Continental TSIO-360 series (registry code 17019, https://openairdocs.org/engine/continental-tsio-360-series) (OpenAirDocs)
- Reported make and model: PIPER PA34200T
- People aboard: 2
- Fatal injuries: 2
- NTSB investigation: [NTSB FTW02FA130](https://openairdocs.org/ntsb/FTW02FA130) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020427007619A

## Narrative

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

(-23) AT THIS TIME WHAT IS KNOWN IS THAT THE PILOT WAS ATTEMPTING TO CONDUCT A GPS INSTRUMENT APPROACH TO SLC #2 AIRPORT (U42) AND FOR WHATEVER REASON WAS NOT ABLE TO OBTAIN A CLEARANCE FROM ATC TO DO THAT. INSTEAD ATC VECTORED HIM TO THE ILS APPROACH TO PROVO, UTAH AIRPORT (PVU). HE DID THAT APPROACH, BUT DURING THE APPROACH DESCENDED INTO VFR CONDITIONS AND THEN ATTEMPTED TO PROCEED TO SLC #2 AIRPORT VFR, BUT FLEW INTO THE MOUNTAIN. THIS IS A PRELIMINARY REPORT. NOT ALL THE FACTS FOR THIS ACCIDENT HAVE BEEN DETERMINED YET. IF ANY OF THE INFORMATION ON THIS REPORT PROVES TO BE SUBSEQUENTLY INACCURATE IT WILL BE CHANGED. AN AMENDED REPORT WILL BE FILED ONCE ALL OF THE RELEVANT FACTS IN THIS CASE ARE AVAILABLE AND UNDERSTOOD.

## 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 FTW02FA130](https://openairdocs.org/ntsb/FTW02FA130), Apr 27, 2002: Piper PA-34-200T (N132CP), Alpine, UT, destroyed, 2 fatal. Probable cause: The pilot's failure to maintain clearance with terrain and continued flight into known adverse weather conditions. Contributing factors were the fog and rain weather conditions.

## Other reports on N132CP (2)

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

- [Accident 19900418013289A](https://openairdocs.org/incident/19900418013289A), Apr 18, 1990: Piper PA34200T (N132CP), Bridgeport, CT, Substantial damage. Lost directional control landing in gusty crosswind. Left runway. Collapsed left gear.
- [Incident 19810108007989I](https://openairdocs.org/incident/19810108007989I), Jan 8, 1981: Piper PA34200T (N132CP), Washington, DC, Minor damage. Pilot lost power on right engine after takeoff. Returned, landed, engine power ok. Blew tire taxiing over ice.

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.