OpenAirDocs.org

20091123052859I

Incident · Substantial damage
Open the Markdown

FAA incident report · Cessna 172P · Zelienople, PA · November 23, 2009

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
November 23, 2009 · 08:30 local
Place
Zelienople, PA
Airport
Zelienople Municipal Airport
Phase of flight
Taxi
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N62104
Reported as
Cessna 172P
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
4,800 total0 in this make and model0 in the last 90 days
N62104Registered now · Cessna 172PS/N 17275213Airframe modelCessna 172P

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

While taxiing to RW35 the aircraft depart the taxiway and collided with 3-taxiway lights and destroyed the taxiway idenification sign. The pilot continued to taxi to runway 35 and on the left turn to runway 35 the aircraft collided with 4-taxiway lights and destroyed the runway 35 idenification sign. When the pilot finally arrived at the runway he stopped the aircraft and exited the aircraft with the aircraft engine still running. Then the pilot asked the mechanic that had arrived on the scene, to help him get the aircraft lined up for takeoff. The mechanic stated, the pilot told him that he was in a hurry and had to get going. The pilot had no idea of what just had happened and was completely unaware of the damage to the aircraft. The mechanic told the pilot to get back into the aircraft and shut the engine off and that he could fly the damaged aircraft. The damaged aircraft was towed back to the ramp with significient damage to the propeller, engine, and the right landing gear strut.

As the FAA filed it

WHILE TAXIING TO RW35 THE AIRCRAFT DEPART THE TAXIWAY AND COLLIDED WITH 3-TAXIWAY LIGHTS AND DESTROYED THE TAXIWAY IDENIFICATION SIGN. THE PILOT CONTINUED TO TAXI TO RUNWAY 35 AND ON THE LEFT TURN TO RUNWAY 35 THE AIRCRAFT COLLIDED WITH 4-TAXIWAY LIGHTS AND DESTROYED THE RUNWAY 35 IDENIFICATION SIGN. WHEN THE PILOT FINALLY ARRIVED AT THE RUNWAY HE STOPPED THE AIRCRAFT AND EXITED THE AIRCRAFT WITH THE AIRCRAFT ENGINE STILL RUNNING. THEN THE PILOT ASKED THE MECHANIC THAT HAD ARRIVED ON THE SCENE, TO HELP HIM GET THE AIRCRAFT LINED UP FOR TAKEOFF. THE MECHANIC STATED, THE PILOT TOLD HIM THAT HE WAS IN A HURRY AND HAD TO GET GOING. THE PILOT HAD NO IDEA OF WHAT JUST HAD HAPPENED AND WAS COMPLETELY UNAWARE OF THE DAMAGE TO THE AIRCRAFT. THE MECHANIC TOLD THE PILOT TO GET BACK INTO THE AIRCRAFT AND SHUT THE ENGINE OFF AND THAT HE COULD FLY THE DAMAGED AIRCRAFT. THE DAMAGED AIRCRAFT WAS TOWED BACK TO THE RAMP WITH SIGNIFICIENT DAMAGE TO THE PROPELLER, ENGINE, AND THE RIGHT LANDING GEAR STRUT.

Other reports on N62104 · 1

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

Incident 19880322019409ILevel Off Touchdown · Zelienople, PABounced and porpoised on landing. Damaged prop and nose gear. First solo in type.Mar 22, 1988 · Minor damage