# Incident 20260608005409I: Piper PA-34-200, Fort Pierce, FL, June 8, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 8, 2026, 17:03 local time
- Place: Fort Pierce, FL
- Airport: Fort Pierce
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: Pilot school (Part 141)
- Operator: P39S
- Location: 27.4080° N, 80.3210° W: Placed by OpenAirDocs at Fort Pierce Airport, closed, within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=27.4080&lon=-80.3210&mi=10
- Aircraft: N56676, registered now (https://openairdocs.org/aircraft/N56676) (OpenAirDocs)
- Registry model: Piper PA-34-200 (registry code 7103405, https://openairdocs.org/model/piper-pa-34-200) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: PIPER PA-34-200
- Reported engine: LYCOMING I0360 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 2,458 total, 272 in this make and model, 226 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260608005409I

## Narrative

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

ON JUNE 8, 2026, I WAS CONDUCTING A COMMERCIAL MULTI-ENGINE TRAINING FLIGHT WITH A STUDENT IN A PIPER PA-44 SEMINOLE. DURING THE FLIGHT, THE LANDING GEAR WAS EXTENDED ON TWO OCCASIONS AND INDICATED NORMAL OPERATION EACH TIME, INCLUDING THREE GREEN GEAR POSITION LIGHTS, NO GEAR UNSAFE INDICATION, AND VISUAL CONFIRMATION OF THE NOSE GEAR IN THE DOWN-AND-LOCKED POSITION.

THE AIRCRAFT ENTERED THE TRAFFIC PATTERN AT FORT PIERCE (KFPR) AND LANDED ON RUNWAY 32 AT APPROXIMATELY 1701 LOCAL TIME. THE LANDING WAS UNEVENTFUL, AND THE LANDING GEAR INITIALLY SUPPORTED THE AIRCRAFT NORMALLY.

DURING A TOUCH-AND-GO LANDING, TAKEOFF POWER WAS APPLIED AND THE FLAPS WERE RETRACTED. DURING THE TRANSITION FROM THE LANDING ROLL TO TAKEOFF, THE NOSE LANDING GEAR COLLAPSED. THE THROTTLES WERE CLOSED, THE MIXTURE CONTROLS WERE MOVED TO IDLE CUTOFF, AND THE AIRCRAFT CAME TO REST APPROXIMATELY 10 TO 15 FEET LEFT OF THE RUNWAY CENTERLINE BETWEEN TAXIWAYS DELTA AND ECHO.

THE AIRCRAFT WAS SECURED AND BOTH OCCUPANTS EVACUATED WITHOUT INJURY. AIRPORT RESCUE PERSONNEL RESPONDED, AND THE AIRCRAFT WAS SUBSEQUENTLY RECOVERED AND MOVED TO A PARKING AREA FOR FURTHER EXAMINATION.

## Other reports on N56676 (5)

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

- [Incident 20250509004119I](https://openairdocs.org/incident/20250509004119I), May 9, 2025: Piper PA-34-200 (N56676), Vero Beach, FL, Minor damage. On 05/09/2025 aircraft, [privacy data omitted], was being operated for instruction. During the landing at Vero Beach regional airport (vrb) the aircraft…
- [Accident 19991108039169A](https://openairdocs.org/incident/19991108039169A), Nov 8, 1999: Piper PA34200 (N56676), Olive Branch, MS, Substantial damage. (.4)The CFI and private -rated student pilot were conducting to uch-and-go landings. After touch down the dual student retracted the flaps and reached for the…
- [Incident 19990809024189I](https://openairdocs.org/incident/19990809024189I), Aug 9, 1999: Piper PA34200 (N56676), Olive Branch, MS, Minor damage. Instructor stated that the student was fast on downwind, base, final and on landing. Student landed on nose gear, went airborne and came back down striking…
- [Accident 19970705017679A](https://openairdocs.org/incident/19970705017679A), Jul 5, 1997: Piper PA34200 (N56676), Mackinac Island, MI, Substantial damage. Aircraft flared high and stalled. (.4)the pilot said that on short final approach, the airplane encountered turbulence and that he held the airplane off the…
- [Incident 19920604022979I](https://openairdocs.org/incident/19920604022979I), Jun 4, 1992: Piper PA34200 (N56676), Allentown, PA, Minor damage. Right main gear collapsed on landing rollout. Found a broken stud assembly.

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.