20250917013289A

Accident · Substantial damage

FAA accident report · Piper PA-28R-201T · Smyrna, TN · September 17, 2025

Date
September 17, 2025 · 17:39 local
Place
Smyrna, TN
Airport
Smyrna
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N47742
NTSB investigation
NTSBERA25LA351
Reported as
Piper PA-28R-201T
Reported engine
Continental TSIO-360 series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Commercial pilot
Pilot’s flight hours
2,851 total

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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 omittedwould 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.

As the FAA filed it

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.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other reports on N47742 · 1

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