# Accident 20050925025269A: Piper PA28140, Wilson Creek, NV, September 25, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 25, 2005, 20:56 local time
- Place: Wilson Creek, NV
- Damage: Substantial damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 38.0667° N, 114.5667° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.0667&lon=-114.5667&mi=10
- Aircraft: N5031T, a cancelled registration (https://openairdocs.org/deregistered/N5031T-2007-06-13) (OpenAirDocs)
- Registry model: Piper PA-28-140 (registry code 7102802, https://openairdocs.org/model/piper-pa-28-140) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA28140
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 44 total, 44 in this make and model
- NTSB investigation: [NTSB LAX05LA318](https://openairdocs.org/ntsb/LAX05LA318) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050925025269A

## Narrative

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

(-23) ON SEPTEMBER 25, 2005, PILOT DEPARTED HOME BASE, CEDAR CITY, UT AT OR ABOUT 1640 LOCAL WITH REPORTEDLY FULL TANKS. HE FLEW TO ELKO, NY AND DID A TOUCH AND GO LANDING AT OR ABOUT 1940. THEN FLEW TO ELY WHERE HE WANTED TO LAND BUT FAILED TO ACTIVATE THE RUNWAY LIGHTS. CONTINUED TO THE WILSON CREEK VOR AND CONTACTED SALT LAKE CENTER FOR ASSISTANCE TO FLY DIRECT TO CEDAR CITY. CENTER HELPED DETERMINE THE AMOUNT OF FUEL NEEDED TO CDC AND OFFERED AN ALTERNATIVE AIRPORT FOR LANDING. SHORTLY AFTER RECEIVING RADAR VECTORS, THE PILOT REPORTED HE WAS GLIDING AND OUT OF FUEL. RADIO CONTACT WAS LOST. THE AIRCRAFT CRASHED INTO THE WILDERNESS AND APPARENTLY STAYED IN A TREE. PILOT WAS ABLE TO DEPART THE AIRPLANE AND CLIMB OUT OF THE TREE IN THE MORNING. HE WAS FOUND BY LOCALS OF THE AREA AND RETURNED TO SAFETY.

## 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 LAX05LA318](https://openairdocs.org/ntsb/LAX05LA318), Sep 26, 2005: Piper PA-28-140 (N5031T), Pioche, NV, substantial damage. Probable cause: controlled flight into mountainous terrain due to the pilot's inadequate preflight planning and preparation and his inadequate in-flight decisions, which created a low fuel state emergency situation…

## Other reports on N5031T (3)

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

- [Incident 20050808016189I](https://openairdocs.org/incident/20050808016189I), Aug 8, 2005: Piper PA28140 (N5031T), Livingston, MT, Minor damage. (-23) On August 8, 2005, PA-28-140, N5031T attempted a landing on runway 4 on a NE heading at the Livingston, Montana airport. Just at touchdown a strong right…
- [Incident 19940718032869I](https://openairdocs.org/incident/19940718032869I), Jul 18, 1994: Piper PA28140 (N5031T), Willard, UT. Narrative: N5031T was on an IFR training flight and was on return flight to slc #2 airport after shooting a practice adf approach into the brigham city airport…
- [Incident 19890415029069I](https://openairdocs.org/incident/19890415029069I), Apr 15, 1989: Piper PA28140 (N5031T), Heber, UT, Minor damage. Right tire went flat on landing rollout. Veered off runway and struck a runway light.

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.