# Incident 20120904021049I: Piper PA-28RT-201, Appleton, WI, September 4, 2012 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: September 4, 2012, 18:43 local time - Place: Appleton, WI - Airport: Outagamie County Regional - Damage: Minor damage - Phase of flight: Taxi - Operating rules: General operating rules (Part 91) - Location: 44.2798° N, 88.3883° W: Placed by OpenAirDocs: center of Appleton, WI, within about 6 miles (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=44.2798&lon=-88.3883&mi=10 - Aircraft: N2895L, registered now (https://openairdocs.org/aircraft/N2895L) (OpenAirDocs) - Registry model: Piper PA-28RT-201 (registry code 7102818, https://openairdocs.org/model/piper-pa-28rt-201) (OpenAirDocs) - Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs) - Reported make and model: PIPER PA-28RT-201 - Reported engine: LYCOMING I0360 SER A&C - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 178 total, 50 in this make and model, 15 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20120904021049I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ^PRIVACY DATA OMITTED^ PRIVATE PILOT 3452258, WAS THE PILOT IN COMMAND OF N2895L WHEN IT DEPARTED THE TAXIWAY AND IMPACTED A TAXI SIGN AT THE INTERSECTION OF N AND N3 TAXIWAYS. ^PRIVACY DATA OMITTED^ WAS OUT ON A 0.6 HRS INSTRUCTIONAL FLIGHT IN THE PATTERN AT ATW AIRPORT WITH ^PRIVACY DATA OMITTED^(FLIGHT INSTRUCTOR) PRIOR TO THE INCIDENT. SHE DROPPED HIM OFF ON THE GA RAMP,AND WAS HEADED OUT TO DO SOME SOLO PATTERN WORK. SHE REQUESTED TAXI TO RWY 12, HER INSTRUCTIONS WERE TO TAXI TO RWY 12 VIA NOVEMBER "N" AND BRAVO "B" AND INSTRUCTED TO HOLD SHORT OF RWY 12. ACCORDING TO ^PRIVACY DATA OMITTED^ SHE NEGOTIATED THE LEFT TURN BUT COULD NOT TURN RIGHT, WHICH RESULTED IN HER DEPARTING THE TAXIWAY AND IMPACTING THE TAXI SING. ^PRIVACY DATA OMITTED^ STATED THE RIGHT BARKE PEDAL WOULD NOT MOVE ANY FURTHER AND APPEAR TO BE INEFFECTIVE. INSPECTOR DANIEL R. OSKAR CHECKED THE BRAKES IN BOTH PILOT POSITION, AND THEY WERE FUNCTIONAL. THE NOSE WHEEL STEERING ALSO APPEARED TO OPERATE CORRECTLY. INSPECTOR OSKAR QUESTIONED ^PRIVACY DATA OMITTED^AND HER INSTRUCTOR TO SEE IF EITHER ONE OF THEM WAS AWARE OF THE HORIZONTAL BAR ABOVE THE RUDDER PEDALS IN THE PA-28R-201 AIRCRAFT AND THEY WERE NOT. IT IS NOT UNCOMMON FOR PILOTS TO GET THEIR TOES ON THIS BAR WHEN TRYING TO APPLY THE BRAKES, RENDERING THE PEDAL(S) INEFECTIVE. IT APPEARS THAT THIS WAS THE CAUSE OF THE EXCURSION OFF THE TAXIWAY. ## Other reports on N2895L (4) Matched to the same aircraft by N-number and date. - [Incident 20061114027079I](https://openairdocs.org/incident/20061114027079I), Nov 14, 2006: Piper PA28RT201 (N2895L), Plymouth, FL, Minor damage. (-23) On November 14, 2006 at approximately 1700 hours local time, a Piper arrow iv, registration N2895L, contacted the runway surface at orlando, apopka… - [Incident 20051108026699I](https://openairdocs.org/incident/20051108026699I), Nov 8, 2005: Piper PA28RT201 (N2895L), Orlando, FL, Minor damage. (-23) Pilot advised that he failed to lower his landing gear because the majority of his 335 flight hrs was flying fixed landing gear aircraft. FAA… - [Incident 20050325005879I](https://openairdocs.org/incident/20050325005879I), Mar 25, 2005: Piper PA28RT201 (N2895L), Winston Salem, NC, Minor damage. (-23) Pilot was on a flight from orlando exec. To Winston-Salem, NC in Piper N2895L. Most of the flight was in IMC conditions at 9000'. The pilot was cleared… - [Incident 20001222036479I](https://openairdocs.org/incident/20001222036479I), Dec 22, 2000: Piper PA28RT201 (N2895L), Orlando, FL, Minor damage. (-23) Incident occurred while performing touch and go landings for a complex aircraft sign off. Upon downwind for the second approach, pilot started prelanding… 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.