# Incident 20121017023169I: Piper PA-28-161, Beverly, MA, October 17, 2012 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: October 17, 2012, 13:01 local time - Place: Beverly, MA - Airport: Beverly Municipal Airport - Damage: Minor damage - Phase of flight: Landing: Rollout - Operating rules: General operating rules (Part 91) - Location: 42.5841° N, 70.9161° W: Placed by OpenAirDocs at BEVERLY RGNL (BVY), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=42.5841&lon=-70.9161&mi=10 - Aircraft: N8234D, registered now (https://openairdocs.org/aircraft/N8234D) (OpenAirDocs) - Registry model: Piper PA-28-161 (registry code 7102803, https://openairdocs.org/model/piper-pa-28-161) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: PIPER PA-28-161 - Reported engine: LYCOMING 0-320 SERIES - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 69 total, 69 in this make and model, 11 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20121017023169I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON 10/17/2012 AT APPROXIMATELY 1300 (L),N8234D WAS CONDUCTING TAKEOFF AND LANDING PRACTICE AT THE KBVY AIRPORT. RUNWAY 16 WAS IN USE AND WINDS WERE CALM AT THE TIME OF THE INCIDENT. THE AIRCRAFT HAD COMPLETED THREE TOUCH AND GO LANDINGS AND WAS PLANNING A FULL STOP FOR LANDING NUMBER 4. THE AIRCRAFT TOUCHED DOWN IN THE VICINITY OF THE THIRD RUNWAY CENTERLINE STRIPE (APPROXIMATELY 780 FEET FROM THE DISPLACED THRESHOLD) AND BEGAN TO SKID TOWARD THE SOUTHWEST SIDE OF THE RUNWAY. INTERMITTENT SKID MARKS WERE DISCOVERED AND CONTINUED TO THE SOUTHERN END OF THE FIXED DISTANCE MARKER (APPROXIMATELY 1150 FEET). THE SKID MARKS WERE HEADING IN A SOUTHWESTERLY DIRECTION AND CONTINUED UNTIL THEY LEFT THE PAVED SURFACE OF THE RUNWAY. TIRE TRACKS COULD BE SEEN IN THE GRASS AREA DIRECTLY ADJACENT TO THE SOUTHWEST SIDE OF RUNWAY 16. THE TIRE TRACKS IN THE GRASS WERE DIRECTED TOWARD THE TAXIWAY C AIRPORT INFORMATION SIGN. WHILE FOLLOWING THE TIRE TRACKS, A RUNWAY EDGE LIGHT WAS DISCOVERED BROKEN FROM ITS MOUNT. THE LIGHT SHAFT WAS LAYING IN A DIRECTION CONSISTANT WITH BEING STRUCK BY THE AIRCRAFT MAKING THE TIRE TRACKS. THE TAXIWAY C RUNWAY INFORMATION SIGN WAS ALSO DISCOVERED ALONG THE TIRE TRACKS IN THE GRASS ADJACENT TO RUNWAY 16. DAMAGE DISCOVERED ON TOP OF THE TAXIWAY C AIRPORT INFORMATION SIGN WERE INDICATIVE OF A COLLISION WITH A METALLIC OBJECT.THE TIRE TRACKS CONTINUED TO THE NORTHWESTERN END OF THE TAXIWAY C THROAT AREA AND CONTINUED ON THE SOUTHWESTERN SIDE OF THE TAXIWAY C THROAT AREA FOR A DISTANCE OF APPROXIMATELY 3 FEET. NO SKID MARKS WERE PRESENT ON THE TAXIWAY C / RUNWYWAY 16 PAVED SURFACE AREA.A BROKEN TAXIWAY LIGHT WAS DISCOVERED LYING IN THE GRASS ON THE SOUTHWEST SIDE OF TAXIWAY C. NO TIRE TRACKS WERE FOUND LEADING TO THE FINAL RESTING POSITION OF THE BROKEN TAXIWAY LIGHT.IT WAS LATER DETERMINED THAT THE PILOT HAD REPORTEDLY LOST CONTROL OF THE AIRCRAFT UPON ATTEMPTING LANDING NUMBER 4. THE AIRCRAFT DRIFTED TO THE SOUTHWEST SIDE OF THE RUNWAY WHERE IT DEPARTED THE PAVED SURFACE. THE PILOT REPORTEDLY ATTEMPTED TO ARREST THE TURNING MOMENT BUT STATED THAT THE CORRECTIVE CONTROL INPUT WAS INEFFECTIVE. THE AIRCRAFT SUBSEQUENTLY STRUCK A RUNWAY EDGE LIGHT, THE TAXIWAY C AIRPORT INFORMATION SIGN AS WELL A TAXIWAY LIGHT. THE PILOT THEN REPORTEDLY EXECUTED A GO AROUND (A FACT CONFIRMED BY KBVY TOWER AUDIO TAPES, AS WELL AS A WRITTEN STATEMENT PROVIDED BY THE PILOT HIMSELF). THE PILOT WAS THEN CLEARED TO LAND ON RUNWAY 27 AND DID SO WITHOUT INCIDENT. ONCE ON THE GROUND, THE AIRCRAFT WAS MANUEVERED, UNDER ITS OWN POWER, TO THE BEVERLY FLIGHT CENTER RAMP. POST FLIGHT INSPECTION CONDUCTED BY THE PILOT REVEALED A SLIGHT DENT IN THE UPWARD DIRECTION ON THE LEFT INBOARD FLAP SURFACE, AS WELL AS A LARGE DENT ON THE LEFT LEADING EDGE OF THE STABILATOR. ## Other reports on N8234D (2) Matched to the same aircraft by N-number and date. - [Accident 20221031018009A](https://openairdocs.org/incident/20221031018009A), Oct 31, 2022: Piper PA-28-161 (N8234D), Beverly, MA, Substantial damage. This flight involved a private pilot student and CFI performing touch and goes at berverly mini. Airport(bvy) on 10, 31 2022. On the third landing the aicraft… - [Incident 20210324001679I](https://openairdocs.org/incident/20210324001679I), Mar 24, 2021: Piper PA-28-161 (N8234D), Beverly, MA, No damage. The student pilot was conducting his first unsupervised solo flight (fourth solo overall) in the traffic pattern. The student had just touched down on 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.