# Incident 20130717015829I: Piper PA-34-200, Palm Coast, FL, July 17, 2013

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 17, 2013, 13:00 local time
- Place: Palm Coast, FL
- Airport: Flagler County
- Damage: Minor damage
- Phase of flight: Maneuver
- Operating rules: Pilot school (Part 141)
- Operator: IHMS
- Location: 29.6019° N, 81.2083° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=29.6019&lon=-81.2083&mi=10
- Aircraft: N767PE, registered now (https://openairdocs.org/aircraft/N767PE) (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: 567 total, 88 in this make and model, 157 in the last 90 days
- NTSB investigation: [NTSB ERA13IA326](https://openairdocs.org/ntsb/ERA13IA326) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130717015829I

## Narrative

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

DURING A VMC DEMONSTRATION FLIGHT AT APPROXIMATELY 5000 FEET, 10 NM NE OF FLAGLER COUNTY AIRPORT, THE AIRCRAFTS RUDDER BEGAN TO OSCILLATE. NO EMERGENCY WAS DECLARED AND AFTER LANDING WITHOUT INCIDENT. INITIAL INSPECTION REVEALED THE RUDDER TRIM TAB CONTROL ROD WAS BROKEN AT THE ROD END ATTACH POINT AND NO FURTHER DAMAGE TO THE RUDDER WAS NOTED.

## 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 ERA13IA326](https://openairdocs.org/ntsb/ERA13IA326), Jul 17, 2013: Piper PA-34 (N767PE), Palm Coast, FL, incident, no damage. Probable cause: The installation of an incorrect rudder trim tab control rod by unknown maintenance personnel, which resulted in the rod failing in flight due to overload and subsequent uncontrolled rudder…

## Other reports on N767PE (3)

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

- [Incident 20240126000459I](https://openairdocs.org/incident/20240126000459I), Jan 26, 2024: Piper PA-34-200 (N767PE), Palm Coast, FL, Minor damage. During preflight aircraft was found airworthy with no defects noted. The brakes operated normally during the taxi. Flight was conducted without issue. During…
- [Incident 20130201002519I](https://openairdocs.org/incident/20130201002519I), Feb 1, 2013: Piper PA-34-200 (N767PE), Evb, FL, No damage. Flight was scheduled for a cross country flight to fort pierce (kfpr). Upon leveling off at 3000 feet the pilots visually identified smoke in the cockpit and…
- [Incident 20080904855769I](https://openairdocs.org/incident/20080904855769I), Sep 4, 2008: Piper PA34200 (N767PE), Daytona Beach, FL, Substantial damage. (-23) On September 4, 2008, while performing dual flight training the pilot lowered the landing gear in flight to perform slow flight training. The pilot…

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.