# Accident 20160913017819A: Piper PA-28R-201, Bowling Green, OH, September 13, 2016 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: September 13, 2016, 09:00 local time - Place: Bowling Green, OH - Airport: Wood County - Damage: Substantial damage - Phase of flight: Landing: Touchdown - Operating rules: Pilot school (Part 141) - Operator: LF8S - Location: 41.5869° N, 83.8081° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=41.5869&lon=-83.8081&mi=10 - Aircraft: N786BG, registered now (https://openairdocs.org/aircraft/N786BG) (OpenAirDocs) - Registry model: Piper PA-28R-201 (registry code 7102816, https://openairdocs.org/model/piper-pa-28r-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-28R-201 - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Airline transport, commercial pilot, flight instructor - Pilot flight hours: 5,993 total, 535 in this make and model, 42 in the last 90 days - NTSB investigation: [NTSB CEN16LA374](https://openairdocs.org/ntsb/CEN16LA374) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20160913017819A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. THIS WAS AN EMPLOYEE TRAINING FLIGHT WITH A CREW OF ^PRIVACY DATA OMITTED^ AND ^PRIVACY DATA OMITTED^ IN N786BG, PA28R-201 ON THE MORNING OF 9/13/2016. AT APPROXIMATELY 7:40AM ^PRIVACY DATA OMITTED^ PERFORMED A NORMAL TAKEOFF AND REMAINED IN THE TRAFFIC PATTERN FOR AN INTENDED LANDING. ON MID-FIELD DOWNWIND LEG ^PRIVACY DATA OMITTED^ RAN THE LANDING CHECKLIST. AS HE CYCLED THE LANDING GEAR LEVER DOWN THE GEAR SOUNDED AND FELT AS THOUGH THEY WERE EXTENDING FOR A NORMAL DOWN CYCLE AND THEN THE "CONT" CIRCUIT BREAKER POPPED OUT. THE AIRCRAFT GAVE EVERY PHYSICAL INDICATION THAT IT FELT LIKE THE GEAR WAS INDEED EXTENDED, THE DRAG ASSOCIATED WITH IT WAS EVIDENT. AS A RESULT OF THE CONTROL CIRCUIT BREAKER RELEASE DISABLING THE GEAR WARNING SYSTEM, THE CREW WAS NOT ABLE TO SEE ANY GREEN LANDING GEAR ANNUNCIATOR LIGHTS OR HAVE ANY OTHER VISUAL OR AURAL INDICATIONS ASSOCIATED WITH THE GEAR AND COULD NOT DETERMINE IF IT WAS LOCKED. WHEN THE DIRECTOR OF MAINTENANCE ARRIVED AT THE RUNWAY THEY DISCUSSED THE CONTROL CIRCUIT BREAKER AND HE REQUESTED THEY RESET IT. ^PRIVACY DATA OMITTED^ TRIED TO PUSH THE CIRCUIT BREAKER BACK IN AND IT POPPED OUT INSTANTLY, NOT ALLOWING A RESET. WE REPORTED THIS INFORMATION TO MAINTENANCE OVER THE RADIO. MAINTENANCE AGREED THAT WE SHOULD TRY A LOW PASS TO DETERMINE IF THE LANDING GEAR WAS EXTENDED AND SEE WHAT POSITION THE GEAR WAS IN. THE CREW SET UP FOR A NORMAL RE-ENTRY TO THE TRAFFIC PATTERN, BRIEFED THE LOW PASS PROCEDURE AND THEN PERFORMED IT. THE PIC LOW PASS WAS AT APPROXIMATELY 70 KNOTS AT EYE-LEVEL TO THE MAINTENANCE OBSERVER AND MAINTENANCE SEEMED PLEASED WITH THE OBSERVATION, REPORTING THAT THE LANDING GEAR APPEARED DOWN. THE AIRCRAFT CLIMBED OUT AND REMAINED IN THE TRAFFIC PATTERN FOR A LANDING. THE CREW BRIEFED THAT THEY WOULD ATTEMPT TO LAND AT A SLOW BUT SAFE AIRSPEED TO PREVENT SIGNIFICANT DAMAGE IF THERE WAS ANY GEAR SITUATION. THE CREW DISCUSSED POSITION OF THE FLAPS, SPEED CONTROL, AND THE POSSIBILITY OF INITIATING A GO-AROUND IF THEY FELT ANY INDICATION OF THE GEAR NOT HOLDING ON LANDING. THE LANDING TOUCHDOWN WAS EXTREMELY GENTLE, THEY DID NOT FEEL ANY INDICATION OF A GEAR FAILURE. ALL 3 WHEELS WERE ON THE RUNWAY AND THE AIRCRAFT WAS DECELERATING GRADUALLY. THE PIC MADE SURE NOT TO BRAKE HARD OR APPLY ANY OTHER FORCES TO THE AIRCRAFT, AND CONTINUED TO RETRACT THE CONTROL YOKE AFT AS THEY DECELERATED. THE AIRCRAFT RIGHT GEAR SIMPLY COLLAPSED AS THEY BEGAN A SUBTLE LEFT TURN TO EXIT THE RUNWAY TO TAXIWAY CONNECTOR B3 AT AN EXTREMELY SLOW SPEED. AT THAT TIME THE AIRCRAFT GENTLY TURNED TO REST FACING NORTH ON RUNWAY 28 WITH THE RIGHT GEAR COLLAPSED. THE CREW DID NOT PERFORM THE EMERGENCY CHECKLIST, THE CHECKLIST STATES TO UTILIZE THE EMERGENCY GEAR EXTENSION LEVER, THIS WAS NOT ACCOMPLISHED. THE CREW REVIEWED PORTIONS OF THE EMERGENCY CHECKLIST, BUT FELT THAT SINCE THE LANDING GEAR CONTROL BREAKER WAS POPPED, THEY COULD NOT CYCLE THE GEAR (FIRST CHECKLIST PROCEDURE)(ACTIVATION OF THE EMERGENCY GEAR LEVER IS THE FINAL PROCEDURE). ## 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 CEN16LA374](https://openairdocs.org/ntsb/CEN16LA374), Sep 13, 2016: Piper PA-28R-201 (N786BG), Bowling Green, OH, substantial damage. Probable cause: The pilots’ failure to complete the Emergency Landing Gear Extension checklist and maintenance personnel’s failure to correctly repair spliced wires on the left main landing gear down limit switch,… ## Other reports on N786BG (1) Matched to the same aircraft by N-number and date. - [Accident 20170718012509A](https://openairdocs.org/incident/20170718012509A), Jul 18, 2017: Piper PA-28R-201 (N786BG), Bowling Green, OH, Substantial damage. The pilot was receiving instruction toward his initial flight instructor rating. The flight started with practice of maneuvers in the practice area and ended… 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.