What happened
The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.
At 15:30 LCL on 10/08/2020, privacy data omitted was informed by the roc of an accident involving N8788D at pym. The aircraft was a PA-18-150 which was landing on runway 24, and ground looped, ending up on its back. 2 POB, minor injuries, taken for treatment by local EMT?s. privacy data omitted Inspector privacy data omitted was enroute to obtain photos. After collecting multiple photos of the accident scene from inspector privacy data omitted, I granted permission for the aircraft to be moved to a secure hangar on the airport as it was blocking the only operational runway. NTSB was notified.
On 10/9/2020 I travelled to pym to inspect N8788D. I also met with one of the maintenance personnel privacy data omitted from alpha one who provided the maintenance records. Significant damage was noted. The aircraft had flipped on its back after loss of control on landing. The asst. Airport manager, privacy data omitted was also present. No video was available of the accident. Photos of the aircraft in-situ were obtained by privacy data omitted of privacy data omitted who responded the day of the accident.
The aircraft substantial sustained damage to the wings, lift struts, empennage and vertical tail as a result of the flip. There was impact damage noted on the right main gear, with some yellow paint transfer. The aircraft apparently swerved off the runway and struck a taxiway light, causing it to nose over. The cabin showed evidence of crushing. The right wingtip sustained damage and the spinner and prop did as well. The prop showed evidence of s-bending. Engine mounts were found to be buckled and bent. Substantial crushing damage to vertical stabilizer and evidence that the empennage was structurally compromised by buckling were also observed. All control continuity was checked, no pre-impact abnormalities noted for the aircraft.
I called the pilot, privacy data omitted at privacy data omitted. He described the events as follows:
They were conducting a fire patrol for the county of Plymouth, finishing a 2 hr flight. The back-seater, privacy data omitted privacy data omitted needed to land to take a break. The pilot was aware of the forecasted winds and had been watching the conditions at pym by checking the AWOS throughout the flight. Pym was using runway 24, since the intersecting runway was closed that day due to construction. The winds were consistently 300 degrees at 12-15 knots with gusts of 20. He said he had a few other options for airports to land at, but elected to try it, as it did not seem outside of his personal limits. As he approached the airport, he could see and hear a local PC-12 taxiing and getting its clearance to depart. He talked to the pilot of the PC-12 and gave him room to depart. He did not feel that vortices were a factor as the strong crosswind would have pushed them off the runway. Final approach was done with ½ flaps and 75 mph approach speed. He touched down mains first, with the tail high. The aircraft began to weathervane to the right on roll out, then he applied too much rudder and it swerved left. The pilot then decided to apply full power and go-around. At that moment, the pilot described that he believed he struck a runway light with the main gear which caused a large nose forward pitch. He believed he was actually airborne at the time he hit the light as there were no tire marks immediately next to the light. He felt the mains impact the ground and the prop dug in, causing it to pitch forward onto its back. All occupants were conscious after impact. A mechanic, privacy data omitted, ran over to them and helped them both get out, and secured the fuel and electrical switches.
The pilot has 1600 hrs in tailwheel aircraft with 1400 hrs in his own RV-7 which he built in 2014. He had approximately 25 hrs in the PA-18 at the time of the accident. He said there were absolutely no mechanical issues with the aircraft and this incident was entirely pilot error. He was completely aware of the local wind conditions and opted to ?give it a try?
As the FAA filed it
AT 15:30 LCL ON 10/08/2020, ^PRIVACY DATA OMITTED^ WAS INFORMED BY THE ROC OF AN ACCIDENT INVOLVING N8788D AT PYM. THE AIRCRAFT WAS A PA-18-150 WHICH WAS LANDING ON RUNWAY 24, AND GROUND LOOPED, ENDING UP ON ITS BACK. 2 POB, MINOR INJURIES, TAKEN FOR TREATMENT BY LOCAL EMT?S. ^PRIVACY DATA OMITTED^ INSPECTOR ^PRIVACY DATA OMITTED^ WAS ENROUTE TO OBTAIN PHOTOS. AFTER COLLECTING MULTIPLE PHOTOS OF THE ACCIDENT SCENE FROM INSPECTOR ^PRIVACY DATA OMITTED^, I GRANTED PERMISSION FOR THE AIRCRAFT TO BE MOVED TO A SECURE HANGAR ON THE AIRPORT AS IT WAS BLOCKING THE ONLY OPERATIONAL RUNWAY. NTSB WAS NOTIFIED.
ON 10/9/2020 I TRAVELLED TO PYM TO INSPECT N8788D. I ALSO MET WITH ONE OF THE MAINTENANCE PERSONNEL ^PRIVACY DATA OMITTED^ FROM ALPHA ONE WHO PROVIDED THE MAINTENANCE RECORDS. SIGNIFICANT DAMAGE WAS NOTED. THE AIRCRAFT HAD FLIPPED ON ITS BACK AFTER LOSS OF CONTROL ON LANDING. THE ASST. AIRPORT MANAGER, ^PRIVACY DATA OMITTED^ WAS ALSO PRESENT. NO VIDEO WAS AVAILABLE OF THE ACCIDENT. PHOTOS OF THE AIRCRAFT IN-SITU WERE OBTAINED BY ^PRIVACY DATA OMITTED^ OF ^PRIVACY DATA OMITTED^ WHO RESPONDED THE DAY OF THE ACCIDENT.
THE AIRCRAFT SUBSTANTIAL SUSTAINED DAMAGE TO THE WINGS, LIFT STRUTS, EMPENNAGE AND VERTICAL TAIL AS A RESULT OF THE FLIP. THERE WAS IMPACT DAMAGE NOTED ON THE RIGHT MAIN GEAR, WITH SOME YELLOW PAINT TRANSFER. THE AIRCRAFT APPARENTLY SWERVED OFF THE RUNWAY AND STRUCK A TAXIWAY LIGHT, CAUSING IT TO NOSE OVER. THE CABIN SHOWED EVIDENCE OF CRUSHING. THE RIGHT WINGTIP SUSTAINED DAMAGE AND THE SPINNER AND PROP DID AS WELL. THE PROP SHOWED EVIDENCE OF S-BENDING. ENGINE MOUNTS WERE FOUND TO BE BUCKLED AND BENT. SUBSTANTIAL CRUSHING DAMAGE TO VERTICAL STABILIZER AND EVIDENCE THAT THE EMPENNAGE WAS STRUCTURALLY COMPROMISED BY BUCKLING WERE ALSO OBSERVED. ALL CONTROL CONTINUITY WAS CHECKED, NO PRE-IMPACT ABNORMALITIES NOTED FOR THE AIRCRAFT.
I CALLED THE PILOT, ^PRIVACY DATA OMITTED^ AT ^PRIVACY DATA OMITTED^. HE DESCRIBED THE EVENTS AS FOLLOWS:
THEY WERE CONDUCTING A FIRE PATROL FOR THE COUNTY OF PLYMOUTH, FINISHING A 2 HR FLIGHT. THE BACK-SEATER, ^PRIVACY DATA OMITTED^ ^PRIVACY DATA OMITTED^ NEEDED TO LAND TO TAKE A BREAK. THE PILOT WAS AWARE OF THE FORECASTED WINDS AND HAD BEEN WATCHING THE CONDITIONS AT PYM BY CHECKING THE AWOS THROUGHOUT THE FLIGHT. PYM WAS USING RUNWAY 24, SINCE THE INTERSECTING RUNWAY WAS CLOSED THAT DAY DUE TO CONSTRUCTION. THE WINDS WERE CONSISTENTLY 300 DEGREES AT 12-15 KNOTS WITH GUSTS OF 20. HE SAID HE HAD A FEW OTHER OPTIONS FOR AIRPORTS TO LAND AT, BUT ELECTED TO TRY IT, AS IT DID NOT SEEM OUTSIDE OF HIS PERSONAL LIMITS. AS HE APPROACHED THE AIRPORT, HE COULD SEE AND HEAR A LOCAL PC-12 TAXIING AND GETTING ITS CLEARANCE TO DEPART. HE TALKED TO THE PILOT OF THE PC-12 AND GAVE HIM ROOM TO DEPART. HE DID NOT FEEL THAT VORTICES WERE A FACTOR AS THE STRONG CROSSWIND WOULD HAVE PUSHED THEM OFF THE RUNWAY. FINAL APPROACH WAS DONE WITH ½ FLAPS AND 75 MPH APPROACH SPEED. HE TOUCHED DOWN MAINS FIRST, WITH THE TAIL HIGH. THE AIRCRAFT BEGAN TO WEATHERVANE TO THE RIGHT ON ROLL OUT, THEN HE APPLIED TOO MUCH RUDDER AND IT SWERVED LEFT. THE PILOT THEN DECIDED TO APPLY FULL POWER AND GO-AROUND. AT THAT MOMENT, THE PILOT DESCRIBED THAT HE BELIEVED HE STRUCK A RUNWAY LIGHT WITH THE MAIN GEAR WHICH CAUSED A LARGE NOSE FORWARD PITCH. HE BELIEVED HE WAS ACTUALLY AIRBORNE AT THE TIME HE HIT THE LIGHT AS THERE WERE NO TIRE MARKS IMMEDIATELY NEXT TO THE LIGHT. HE FELT THE MAINS IMPACT THE GROUND AND THE PROP DUG IN, CAUSING IT TO PITCH FORWARD ONTO ITS BACK. ALL OCCUPANTS WERE CONSCIOUS AFTER IMPACT. A MECHANIC, ^PRIVACY DATA OMITTED^, RAN OVER TO THEM AND HELPED THEM BOTH GET OUT, AND SECURED THE FUEL AND ELECTRICAL SWITCHES.
THE PILOT HAS 1600 HRS IN TAILWHEEL AIRCRAFT WITH 1400 HRS IN HIS OWN RV-7 WHICH HE BUILT IN 2014. HE HAD APPROXIMATELY 25 HRS IN THE PA-18 AT THE TIME OF THE ACCIDENT. HE SAID THERE WERE ABSOLUTELY NO MECHANICAL ISSUES WITH THE AIRCRAFT AND THIS INCIDENT WAS ENTIRELY PILOT ERROR. HE WAS COMPLETELY AWARE OF THE LOCAL WIND CONDITIONS AND OPTED TO ?GIVE IT A TRY?
NTSB investigation
The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.
Other reports on N8788D · 1
Matched to the same aircraft by N-number and date.