# Incident 20020902024139I: Piper PA36300, Tucker, OK, September 2, 2002

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 2, 2002, 15:30 local time
- Place: Tucker, OK
- Damage: Minor damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: Agricultural (Part 137)
- Operator: JSVG
- Location: 35.3037° N, 94.7302° W: Placed by OpenAirDocs: center of Tucker, OK, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.3037&lon=-94.7302&mi=10
- Aircraft: N4329F, registered now (https://openairdocs.org/aircraft/N4329F) (OpenAirDocs)
- Registry model: Piper PA-36-300 (registry code 7103612, https://openairdocs.org/model/piper-pa-36-300) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA36300
- Reported engine: PWA PT6A20
- Pilot flight hours: 4,558 total, 420 in this make and model, 350 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020902024139I

## Narrative

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

(-23) WHILE TURNING TO MAKE A TRIM PASS WITH 4 TO 5 GALLONS OF CHEMICAL REMAINING THE PILOT NOTICED A DECREASE IN POWER. THE PILOT MADE AN EMERGENCY LANDING 100 YARDS FROM RIVER BANK, 4 MILES EAST OF THE KERR LOCK AND DAM. PILOT STATED THE ENGINE WAS STILL RUNNING AFTER THE AIRCRAFT COME TO A COMPLETE STOP. THE AIRCRAFT LEFT MAIN LANDING GEAR WAS BROKEN FROM THE FUSELAGE, AND THE ENGINE SUSTAINED A PROP STRIKE.

## Other reports on N4329F (1)

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

- [Incident 20090620009979I](https://openairdocs.org/incident/20090620009979I), Jun 20, 2009: Piper PA36300 (N4329F), Dyer, AR, Substantial damage. (-23) The pilot of N4329F on the morning of Saturday, June 20, 2009 was treating a field just outside of Dyer, AR with herbicide. He stated he had treated the…

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.