# Incident 20260124001179I: Piper PA-28-140, Fort Pierce, FL, January 24, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 24, 2026, 11:21 local time
- Place: Fort Pierce, FL
- Airport: Treasure Coast International A
- Damage: No damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 27.4975° N, 80.3726° W: Placed by OpenAirDocs at TREASURE COAST INTL (FPR), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=27.4975&lon=-80.3726&mi=10
- Aircraft: N1737T, registered now (https://openairdocs.org/aircraft/N1737T) (OpenAirDocs)
- Registry model: Piper PA-28-140 (registry code 7102802, https://openairdocs.org/model/piper-pa-28-140) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28-140
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 129 total, 74 in this make and model, 58 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260124001179I

## Narrative

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

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.

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.