OpenAirDocs.org

20260124001179I

Incident · No damage
Open the Markdown

FAA incident report · Piper PA-28-140 · Fort Pierce, FL · January 24, 2026

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
January 24, 2026 · 11:21 local
Place
Fort Pierce, FL
Airport
Treasure Coast International A
Phase of flight
Landing: Rollout
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N1737T
Reported as
Piper PA-28-140
Reported engine
Lycoming 0-320 series
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Student
Pilot’s flight hours
129 total74 in this make and model58 in the last 90 days
N1737TRegistered now · Piper PA-28-140S/N 28-7125054 · Built 1970Airframe modelPiper PA-28-140Engine modelLycoming 0-320 seriesReciprocating

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.

Fort Pierce, FL (fpr): P28A, landed runway 10L and veered left off of taxiway F3 into the grass for unknown reasons. Aircraft recovered and taxied to the run-up area to inspect the aircraft then later departed. POB:1, injuries: none, damage: none. 01/24/2026.

Pilot statement: I was contacted by my instructor regarding the incident at kfpr on the morning of Saturday, January 24, 2026, and I would like to provide a clear and accurate account of the events, along with the requested pilot and aircraft information.

After landing at kfpr, I exited the runway and began braking while attempting to turn onto taxiway f. during the turn, I experienced an unexpected reduction in rudder responsiveness, which resulted in the aircraft briefly departing the paved surface, with one wheel entering the grass area. Upon recognizing the situation, I immediately advised tower control that I was still on the runway.

I brought the aircraft to a stop to troubleshoot, applied light power, and was able to regain normal rudder control. I then taxied the aircraft back onto the taxiway and proceeded toward the run-up area, where I was approached by airport staff. After confirming normal aircraft operation and no further abnormalities, I departed kfpr and returned to F45 without any additional incidents.

As the FAA filed it

FORT PIERCE, FL (FPR): P28A, LANDED RUNWAY 10L AND VEERED LEFT OFF OF TAXIWAY F3 INTO THE GRASS FOR UNKNOWN REASONS. AIRCRAFT RECOVERED AND TAXIED TO THE RUN-UP AREA TO INSPECT THE AIRCRAFT THEN LATER DEPARTED. POB:1, INJURIES: NONE, DAMAGE: NONE. 01/24/2026.

PILOT STATEMENT: I WAS CONTACTED BY MY INSTRUCTOR REGARDING THE INCIDENT AT KFPR ON THE MORNING OF SATURDAY, JANUARY 24, 2026, AND I WOULD LIKE TO PROVIDE A CLEAR AND ACCURATE ACCOUNT OF THE EVENTS, ALONG WITH THE REQUESTED PILOT AND AIRCRAFT INFORMATION.

AFTER LANDING AT KFPR, I EXITED THE RUNWAY AND BEGAN BRAKING WHILE ATTEMPTING TO TURN ONTO TAXIWAY F. DURING THE TURN, I EXPERIENCED AN UNEXPECTED REDUCTION IN RUDDER RESPONSIVENESS, WHICH RESULTED IN THE AIRCRAFT BRIEFLY DEPARTING THE PAVED SURFACE, WITH ONE WHEEL ENTERING THE GRASS AREA. UPON RECOGNIZING THE SITUATION, I IMMEDIATELY ADVISED TOWER CONTROL THAT I WAS STILL ON THE RUNWAY.

I BROUGHT THE AIRCRAFT TO A STOP TO TROUBLESHOOT, APPLIED LIGHT POWER, AND WAS ABLE TO REGAIN NORMAL RUDDER CONTROL. I THEN TAXIED THE AIRCRAFT BACK ONTO THE TAXIWAY AND PROCEEDED TOWARD THE RUN-UP AREA, WHERE I WAS APPROACHED BY AIRPORT STAFF. AFTER CONFIRMING NORMAL AIRCRAFT OPERATION AND NO FURTHER ABNORMALITIES, I DEPARTED KFPR AND RETURNED TO F45 WITHOUT ANY ADDITIONAL INCIDENTS.