# Accident 20250917013289A: Piper PA-28R-201T, Smyrna, TN, September 17, 2025

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 17, 2025, 17:39 local time
- Place: Smyrna, TN
- Airport: Smyrna
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.0097° N, 86.5202° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.0097&lon=-86.5202&mi=10
- Aircraft: N47742, registered now (https://openairdocs.org/aircraft/N47742) (OpenAirDocs)
- Registry model: Piper PA-28R-201T (registry code 7102813, https://openairdocs.org/model/piper-pa-28r-201t) (OpenAirDocs)
- Registry engine: Continental TSIO-360 series (registry code 17019, https://openairdocs.org/engine/continental-tsio-360-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28R-201T
- Reported engine: CONT MOTOR TSIO-360 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 2,851 total
- NTSB investigation: [NTSB ERA25LA351](https://openairdocs.org/ntsb/ERA25LA351) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20250917013289A

## Narrative

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

ON 9/17/2025, ^PRIVACY DATA OMITTED^ DEPARTED MQY TO CONDUCT TRAFFIC PATTERN WORK IN ^PRIVACY DATA OMITTED^ TO INCLUDE SOFT LANDING PRACTICE. ^PRIVACY DATA OMITTED^ WAS THE SOLE MANIPULATOR OF THE CONTROLS AND ACTED AS PIC FOR THE BEGINNING OF THE FLIGHT. AFTER THE COMPLETION OF A SOFT FIELD LANDING, THEY DEPARTED FOR ANOTHER PATTERN WITH THE UNDERSTANDING THAT ^PRIVACY DATA OMITTED^WOULD DEMONSTRATE A SOFT FILED LANDING ON THE NEXT APPROACH. AS THEY TURNED CROSSWIND AFTER DEPARTURE, THEY NOTICED ANOTHER AIRCRAFT IN THE PATTERN THAT WAS MUCH SLOWER. TO MAINTAIN SEPARATION, DEVONAL REDUCED POWER AND SET THE AIRCRAFT FOR SLOW FLIGHT BY ADDING FLAPS. ON DOWNWIND FOR RUNWAY 32, ^PRIVACY DATA OMITTED^ PASSED THE CONTROLS TO RELIFORD. THEY CONDUCTED A 2-WAY TRANSFER OF CONTROLS (I HAVE THE CONTROLS, YOU HAVE THE CONTROLS) AND ^PRIVACY DATA OMITTED^ ASSUMED THE POSITION AS SOLE MANIPULATOR OF THE CONTROLS AND PIC. ON FINAL, ^PRIVACY DATA OMITTED^ PERFORMED A GUMPS BEFORE LANDING FROM MEMORY. ^PRIVACY DATA OMITTED^ STATED THAT HE BELIEVED THE LANDING GEAR WAS ALREADY DOWN BECAUSE PER HIS NORMAL PROCEDURES GEAR ALWAYS GOES DOWN BEFORE FLAPS. NEITHER PILOT UTILIZED NOR REFERENCED A CHECKLIST PRIOR TO LANDING. AS THEY APPROACHED THE GROUND RELIFORD HAD A FEELING THAT THEY WERE SUPER LOW BUT COULD NOT REACT PRIOR TO TOUCHING DOWN GEAR UP. THE AIRCRAFT CAME TO REST ON THE RUNWAY APPROXIMATELY 241 YARDS FROM THE APPROACH END OF RUNWAY 32. PICTURES TAKEN OF THE COCKPIT AFTER THE ACCIDENT SHOWED THE LANDING GEAR HANDLE IN THE UP POSITIONS. AFTER THE AIRCRAFT WAS CLEARED TO BE MOVED FORM THE RUNWAY, THE AIRCRAFT WAS LIFTED WITH A CRANED, POWER APPLIED, THE LANDING GEAR WAS EXTENDED AND LOCKED, AND THEN THE AIRCRAFT WAS TOWED WHILE UTILIZING THE LANDING GEAR WITHOUT FURTHER INCIDENT.

## 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 ERA25LA351](https://openairdocs.org/ntsb/ERA25LA351), Sep 17, 2025: Piper PA28R (N47742), Smyrna, TN, substantial damage. Probable cause: The pilot’s failure to extend the landing gear before landing.

## Other reports on N47742 (1)

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

- [Incident 19800719062199I](https://openairdocs.org/incident/19800719062199I), Jul 19, 1980: Piper PA28R200 (N47742), Palm Springs, CA, Minor damage. Unable to extend right gear before landing. Found bolt installed incorrectly, jamming gear.

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.