# Accident 20160908015089A: Piper Aircraft Inc PA46R-350T, Reserve, NM, September 8, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 8, 2016, 20:15 local time
- Place: Reserve, NM
- Airport: Reserve Airport
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 33.6942° N, 108.8508° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.6942&lon=-108.8508&mi=10
- Aircraft: N563WT, registered now (https://openairdocs.org/aircraft/N563WT) (OpenAirDocs)
- Registry model: Piper PA46R-350T (registry code 7104610, https://openairdocs.org/model/piper-pa46r-350t) (OpenAirDocs)
- Registry engine: Lycoming TIO-540-AE2A (registry code 41999, https://openairdocs.org/engine/lycoming-tio-540-ae2a) (OpenAirDocs)
- Reported make and model: PIPER AIRCRAFT INC PA46R-350T
- Reported engine: LYCOMING TIO-540-AE2A
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 760 total, 550 in this make and model, 35 in the last 90 days
- NTSB investigation: [NTSB GAA16CA505](https://openairdocs.org/ntsb/GAA16CA505) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160908015089A

## Narrative

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

ON 8 SEPTEMBER 2016, ^GIUSEPPE NIRTA,^ THE PIC, DEPARTED SOCORRO, NM (KONM) AIRPORT AT APPROXIMATELY 1930 MDT IN N563WT, A PA46-350T. THE WEATHER WAS VMC AND THE FLIGHT WAS CONDUCT UNDER VFR FLIGHT FOLLOWING WITH ATC.

THE DESTINATION WAS THE RESERVE, NM AIRPORT (T16). AT APPPROIMATELY 28NM FROM T16, THE PILOT LOCATED THE AIRPORT VIA A STANDARD GREEN/WHITE FAA LIGHT BEACON.

AT APPROXIMATELY 10NM FROM THE AIRPORT, THE PIC SELF-ANNOUNCED HIS LOCATION/POSITION AND INTENTIONS TO LAND ON RWY24. THE PIC ATTEMPTED TO ACTIVATE THE MIRLS (RUNWAY LIGHTS) WITH MULTIPLE CLICKS ON THE AIRCRAFT'S MICROPHONE. THERE WAS NO RESPONSE TO THESE CLICKS.

THE PIC CIRCLED THE AIRPORT MULTIPLE TIMES AND WAS UNABLE EACH TIME TO ACTIVATE THE RUNWAY LIGHTS. THE PILOT STATED THAT AFTER HIS ATTEMPTS TO ACTIVATE THE RUNWAY LIGHTS AROUND 2010 MDT, THE RUNWAY WAS "BARELY" VISIBLE WITH THE REMAINING DAYLIGHT (THERE WAS NO MOONLIGHT AVAILABLE AT THE TIME).

BASED ON HIS ONE AND ONLY PREVIOUS FLIGHT TO THE AIRPORT A YEAR EARLIER, THE PILOT DECIDED TO TRY TO LAND ON RWY 24 WITHOUT THE RUNWAY LIGHTS.

THE PIC THOUGHT THAT WITH HIS ONBOARD NAVIGATION SYSTEMS AND HIS KNOWLEDGE OF THE RUNWAY LOCATION RELATIVE TO OPERATING AIRPORT LIGHT BEACON, HE COULD SUCCESSFULLY/SAFELY LAND ON RWY 24 WITHOUT RUNWAY LIGHTS IN THE DARK.

THE PIC ENTERED THE TRAFFIC PATTERN FOR RWY 24 AND FLEW A COMPLETE TRAFFIC PATTERN, WHILE SIMULTANEOUSLY TRYING TO ACTIVATE THE RUNWAY LIGHTS.  ON HIS FINAL APPROACH TO THE RUNWAY, HE DID NOT SEE THE RUNWAY UNTIL IT WAS TOO LATE TO LAND.

THE PIC WENT AROUND AND FLEW A COMPLETE TRAFFIC PATTERN. ON THIS SECOND ATTEMPT TO LAND, HE MISSED THE EDGE OF RUNWAY 24 BY APPROXIMATELY 10 FEET TO THE RIGHT. HE UNINTENTIONALLY SET THE AIRCRAFT DOWN IN THE GRASS TO THE RIGHT SIDE OF THE RUNWAY. THE PIC TRIED TO  STEER THE AIRCRAFT BACK TO THE RUNWAY USING LEFT RUDDER. UPON PULLING ONTO THE RUNWAY, HE IMMEDIATELY CROSSED THE NARROW  50 FOOT WIDE RUNWAY AND DEPARTED THE LEFT SIDE OF THE RUNWAY. THE LEFT SIDE OF THE RUNWAY IS DOWNHILL AND UNDULATING. THE PIC IMMEDIATELY LOST CONTROL OF THE AIRCRAFT. THE AIRCRAFT NOSED DOWN AND CAME TO AN ABRUPT AND COMPLETE STOP.

THE PILOT SUSTAINED NO INJURIES WHATSOEVER. THE PIC SHUT DOWN ALL SYSTEMS IN THE AIRCRAFT AND EXITED THE AIRCRAFT SAFELY. THERE WAS NO POST-CRASH FIRE. THE AIRCRAFT WAS SUBSTANTIALLY DAMAGED.

## 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 GAA16CA505](https://openairdocs.org/ntsb/GAA16CA505), Sep 9, 2016: Piper PA46R (N563WT), Reserve, NM, substantial damage. Probable cause: The pilot’s failure to maintain directional control during landing with a crosswind.

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.