# Accident 20020607012109A: Piper PA24250, Provo, UT, June 7, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 7, 2002, 21:34 local time
- Place: Provo, UT
- Airport: Provo Municipal Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.2192° N, 111.7233° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.2192&lon=-111.7233&mi=10
- Aircraft: N146P, registered now (https://openairdocs.org/aircraft/N146P) (OpenAirDocs)
- Registry model: Piper PA-24-250 (registry code 7102404, https://openairdocs.org/model/piper-pa-24-250) (OpenAirDocs)
- Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA24250
- NTSB investigation: [NTSB FTW02LA173](https://openairdocs.org/ntsb/FTW02LA173) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020607012109A

## Narrative

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

(-23) ENGINE SPUTTERED AND THEN QUIT 200 FEET OFF RUNWAY DURING TOUCH AND GO OPERATION. PILOT DID NOT GET GEAR DOWN IN TIME AND BELLIED IN SOUTH OF RUNWAY AND SLID 100 FEET. UPON INSPECTION OF AIRCRAFT BOTH R/H AND L/H TANKS WERE EMPTY. VERY LITTLE FUEL WAS PRESENT IN CARBURETOR BOWL, BOOST PUMPS, GASKELATOR/SUMP OR FUEL LINES. ONCE AIRCRAFT WAS RECOVERED AND LANDING GEAR DEPLOYED, ENGINE WAS RUN APPROXIMATELY 4 MINUTES ON EACH TANK WITH NO PROBLEMS NOTED. ALSO AIRCRAFT SAT FOR 2 DAYS WITH NO LOSS OF FUEL FROM THE TANKS. 06/12/2002 INSPECTED FUEL CELLS IN WINGS FOR COLLAPSE AND FUEL VENT CLOGGING, NONE NOTED. PILOT DEPARTED BOUNTIFUL, UT WITH FULL FUEL ONBOARD AND FUELED AIRCRAFT IN MESQUITE, NV (RECEIPT SHOWS 33.15 GALLONS) AND VISUALLY VERIFIED BOTH CELLS WERE FULL. HE FLEW 1 HR AND 30 MINS WHEN ENGINE QUIT DURING TOUCH AND GO OPERATION.

## 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 FTW02LA173](https://openairdocs.org/ntsb/FTW02LA173), Jun 8, 2002: Piper PA-24-250 (N146P), Provo, UT, substantial damage. Probable cause: the total loss of engine power for reasons undetermined.

## Other reports on N146P (3)

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

- [Accident 20080307011339A](https://openairdocs.org/incident/20080307011339A), Mar 7, 2008: Piper PA24250 (N146P), Bountiful, UT, Substantial damage. (-23) At the completion of a night cross country flight, the pilot configured the aircraft for entry into the landing pattern by slowing to 100 knots and…
- [Accident 20070523009839A](https://openairdocs.org/incident/20070523009839A), May 23, 2007: Piper PA24250 (N146P), Winslow, AR, Substantial damage. (-23) Pilot stated that while enroute to Winslow AZ airport, about 20 miles west, he noticed the airspeed decrease along with a decrease in RPM. He also said…
- [Incident 20060512007559I](https://openairdocs.org/incident/20060512007559I), May 12, 2006: Piper PA24250 (N146P), Bountiful, UT, Minor damage. (-23) The pilot was conducting takeoff and landing operations on runway 34 at Bountiful Skypark airport in woods cross, Utah. The incident occurred on 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.