# Incident 20170310002319I: Piper PA-32R-300, Woods Cross, UT, March 10, 2017

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 10, 2017, 22:30 local time
- Place: Woods Cross, UT
- Airport: Skypark
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 40.8681° N, 111.9275° W: Placed by OpenAirDocs at SKYPARK (BTF), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.8681&lon=-111.9275&mi=10
- Aircraft: N9687K, registered now (https://openairdocs.org/aircraft/N9687K) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-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 PA-32R-300
- Reported engine: LYCOMING TI0-540 SER
- People aboard: 4
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 22,641 total, 665 in this make and model, 8 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170310002319I

## Narrative

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

ON MARCH 10, 2017 N9687K EXPERIENCED A COLLAPSE OF THE NOSE GEAR UPON LANDING AT SKYPARK AIRPORT IN WOODS CROSS, UT

THE PIC STATED THAT THEY WERE ENROUTE FROM ST. GEORGE, UT TO SALT LAKE CITY, UT AND UPON PASSING DELTA, UT HE NOTICED THAT HIS BATTERY VOLAGE WAS READING LOW AT 11.2. HE STATED THAT HE ATTEMPTED TO TROUBLESHOOT THE PROBLEM BUT WAS UNABLE TO RESOLVE IT SO HE TURNED OFF ALL NON-ESSENTIAL ELECTRICAL EQUIPMENT AND CONTINUED.

AS HE APPROACHED SALT LAKE CITY'S AIRSPACE HE CONTACTED APPROACH AND INFORMED THEM OF THE SITUATION AND THAT HE WOULD BE PROCEEDING TO SKYPARK AIRPORT (BTF) DUE TO THE HIGH PROBABLITY OF LOSING THE RADIOS. DURING THIS TIME THE BATTERY DIED AND HE LOST ALL ELECTRICAL EQUIPMENT.

THE PILOT PROCEEDED TOWARD BTF AND UTILIZED HIS IPAD AND CELL PHONE TO CONTACT THE AIRPORT MANAGER TO INFORM HIM OF THE SITUATION. THE PILOT THEN ATTEMPED TO LOWER THE LANDING GEAR AND MADE AN APPROACH TO THE RUNWAY. DURING THE LANDING THE PILOT DID NOT FEEL COMFORTABLE AND EXECUTED A GO-AROUND. THE PILOT AGAIN CONTACTED THE AIRPORT MANAGER AND THE AIRPORT MANAGER STATED THAT THE GEAR DID NOT APPEAR TO BE DOWN AND LOCKED. THE PILOT MANEUVERED THE AIRCRAFT TO SEE IF HE COULD GET THE GEAR DOWN AND MADE A LOW PASS SO THAT THE AIRPORT MANAGER COULD TAKE A LOOK AT IT AGAIN. THE AIRPORT MANAGER STATED THAT THE MAIN GEAR APPEARED TO BE DOWN BUT THE NOSE WAS ONLY PARTWAY DOWN.

AFTER THIS ATTEMPT THE PILOT BECAME CONCERNED ABOUT HIS FUEL LEVEL AND DETERMINED TO LAND. UPON LANDING THE NOSE GEAR COLLAPSED AND THE AIRCRAFT SLID DOWN THE RUNWAY ON THE NOSE APPROXIMATELY 800 FEET BEFORE COMING TO A REST JUST RIGHT OF THE CENTERLINE.

THE PILOT SECURED THE AIRCRAFT AND THE PILOT AND PASSENGERS EVACUATED.

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.