FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16LA374 · Piper PA-28R-201

13 Sept 2016 · Bowling Green, OH, United States Possible conflict

Bowling Green Flight Center Piper PA-28R-201 · Accident: system/component malfunction/failure (non-power) on approach

From Wood County Airport (1G0) to Wood County Airport (1G0)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN16LA374
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28R-201

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N786BG
Onboard fatalities
Unknown
Route
From Wood County Airport (1G0), Bowling Green, OHTo Wood County Airport (1G0), Bowling Green, OH
Aircraft age
About 10 years (built 2006)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern downwind
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The two commercial pilots, one of whom was a flight instructor, were planning to conduct touch-and-go landings; the flight instructor reported that he was providing "employee training" to the other pilot. After takeoff and upon returning to the downwind leg of the traffic pattern, the pilot receiving training activated the landing gear switch to lower the landing gear; however, the landing gear control circuit breaker opened. When the circuit breaker was reset, it immediately reopened, which disabled the gear warning system and landing gear annunciator lights. The pilots made a low pass over the runway and maintenance personnel told them that the landing gear appeared to be down. The flight instructor then landed the airplane, and as she was turning it off the active runway, the right main landing gear collapsed.

Postaccident examination of the airplane revealed that neither of the main landing gear were down and locked. Subsequently, the school's director of maintenance entered the airplane and used the emergency gear extension, and the landing gear dropped into the down-and-locked position, and the landing gear annunciator lights illuminated. Although he did not report resetting the circuit breaker, he had to have performed that action for the annunciator lights to illuminate. He later cycled the landing gear numerous times, and it operated normally. The circuit breaker remained closed, and all landing gear indications were normal.

During the postaccident examination, the left main gear down limit switch wire was found dislodged from the terminal. The wire did not appear to have been properly crimped because the crimp mark was not well defined. Based on maintenance records, a new down indicator switch had been spliced in place less than a month earlier. The electrical schematic showed the wire to be energized.

Maintenance personnel reexamined the airplane to determine why the landing gear indication circuit breaker was tripping. According to their report to Federal Aviation Administration, the left main gear down limit switch wire was spliced using the wrong type and gauge of wire. The spliced wires were soldered using heat shrink to cover the splices, which did not cover the wires completely. The three spliced down limit switch wires were bundled together in the left gear well, which allowed them to short, causing the landing gear circuit breaker to trip.

The pilots did not complete the Emergency Landing Gear Extension checklist, which calls for the emergency gear extension lever (which releases pressure in the hydraulic system and allows the gear to free fall) to be pushed down. The pilots should have completed the Emergency Landing Gear Extension checklist in an attempt to ensure that the landing gear were in the down-and-locked position, which could have prevented the right main landing gear from collapsing during the turn off the active runway.

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, which prevented the pilots from knowing whether the gear was down and locked.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16LA374
Event ID
20160919X12434
Case number
CEN16LA374
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 56f6cc6c2580e56c986e3d87cc98dbf2b709c702b1a59d18875ee13a1ec80537; retrieved 2026-09-16T04:16:49.069Z.