# Accident 20000603014579A: Piper PA32260, Clinton, OK, June 3, 2000 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: June 3, 2000, 15:00 local time - Place: Clinton, OK - Airport: Clinton Municipal Airport - Damage: Substantial damage - Phase of flight: Missed Approach IFR - Operating rules: General operating rules (Part 91) - Location: 35.5004° N, 98.9709° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=35.5004&lon=-98.9709&mi=10 - Aircraft: N3869W, a cancelled registration (https://openairdocs.org/deregistered/N3869W-2022-11-05) (OpenAirDocs) - Registry model: Piper PA-32-260 (registry code 7103206, https://openairdocs.org/model/piper-pa-32-260) (OpenAirDocs) - Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs) - Reported make and model: PIPER PA32260 - Reported engine: LYC O540E4B5 - People aboard: 2 - Fatal injuries: 0 - Pilot flight hours: 3,000 total, 200 in this make and model, 75 in the last 90 days - NTSB investigation: [NTSB FTW00LA263](https://openairdocs.org/ntsb/FTW00LA263) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20000603014579A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) WHEN BANKING A/C IN THE BASE LEG OF SHORT FINAL TO CLINTON MUNI AIRPORT THE ENGINE QUIT. PILOT SWITCHED FUEL TANKS BUT THE ENGINE WOULD NOT RESTART. ATTEMPTED TO LAND IN A FIELD SHORT AND RIGHT OF THE RUNWAY. A/C BOUNCED ONCE THEN ON SECOND IMPACT THE NOSE GEAR COLLAPSED. (.4) ON JUNE 3, 2000, AT 1500 CENTRAL DAYLIGHT TIME, A PIPER PA-32-260 AIRPLANE, N3869W, WAS SUBSTANTIALLY DAMAGED DURING A FORCED LANDING AT THE CLINTON MUNICIPAL AIRPORT, NEAR CLINTON, OKLAHOMA. THE PRIVATE PILOT, WHO WAS THE REGISTERED OWNER AND OPERATOR OF THE AIRPLANE, AND HIS PASSENGER WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE 14 CODE OF FEDERAL REGULATIONS PART 91 PERSONAL FLIGHT AND NO FLIGHT PLAN WAS FILED. THE LOCAL FLIGHT ORIGINATED FROM THE CLINTON MUNICIPAL AIRPORT. ACCORDING TO THE FAA INSPECTOR, THE AIRPLANE'S ENGINE LOST TOTAL POWER AS THE PILOT WAS MANEUVERING THE AIRPLANE ON FINAL APPROACH TO RUNWAY 17. DURING THE ENSUING FORCED LANDING THE AIRPLANE CONTACTED A DIRT TERRACE AND CAME TO A STOP UPRIGHT. THE NOSE GEAR COLLAPSED, AND THE AIRPLANE CAME TO A STOP UPRIGHT. FOLLOWING THE ACCIDENT, THE PILOT REPORTED THAT "HE WAS NOT SURE IF THE FUEL SELECTOR WAS IN THE DETENT FOR THE SELECTED TANK AND HE DID NOT HAVE TIME TO CHECK PRIOR TO LANDING." THE FAA INSPECTOR REPORTED THAT THE ENGINE FIREWALL WAS STRUCTURALLY DAMAGED, AND BOTH WINGS WERE COMPRISED AT THEIR RESPECTIVE ATTACHING POINTS TO THE FUSELAGE. THERE WAS ALSO DAMAGE TO THE "STRUCTURE AT THE MAIN LANDING GEAR ATTACH POINTS". THIS DAMAGE WAS INITAILLY REPORTED TO THE NTSB AS MINOR. SUBSEQUENTLY, ON OCTOBER 3, 2000, THE DAMAGE WAS REPORTED AS SUBSTANTIAL. ADDITIONALLY, MULTIPLE ATTEMPTS TO OBTAIN A COMPLETED NTSB FORM 6120.1/2, PILOT/OPERATOR AIRCRAFT ACCIDENT REPORT, FROM THE PILOT/OWNER WERE UNSEUCCESSFUL ## 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 FTW00LA263](https://openairdocs.org/ntsb/FTW00LA263), Jun 3, 2000: Piper PA-32-260 (N3869W), Clinton, OK, substantial damage. Probable cause: The pilot's improper setting of the cockpit fuel selector, which resulted in a total loss of engine power and forced landing. ## Other reports on N3869W (1) Matched to the same aircraft by N-number and date. - [Accident 20200603007759A](https://openairdocs.org/incident/20200603007759A), Jun 3, 2020: Piper PA-32-260 (N3869W), Fargo, ND, Substantial damage. Pilot and student had just finished a pre-flight of the aircraft. Smoke was noticed coming from the engine cowling during the start sequence. Visible flames… 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.