Skip to content

Atlas / NTSB / CEN16LA259

NTSB CAROL · Event

Event CEN16LA259

2016-07-07 Bridgeport, Texas, United States Airport · XBP None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot's unstabilized approach and uneven braking due to insufficient runway remaining, which resulted in a loss of directional control during landing. Contributing to the accident was the bound flap jackscrew, which jammed the flaps and led to the pilot’s inability to operate the airplane normally.

Factual narrative

On July 7, 2016, about 2030 central daylight time, Cessna 152 airplane, N5331B, was damaged during a landing at the Bridgeport Municipal Airport (KXBP), Bridgeport, Texas. The private rated pilot and pilot rated passenger were not injured and the airplane was substantially damaged. The airplane was registered to US Aviation Group LLC and was operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, which operated without a flight plan. The flight originated from Denton Enterprise Airport (KDTO), Denton, Texas, about 1945.According to the pilot, on the third touch-and-go to runway 18 at KXBP, the ground run was longer and the airplane had difficultly climbing away from the runway. He saw that the flaps were still at 30° despite the flap handle being in the up position. The pilot then maneuvered to land to runway 36 at KXBP, but was higher than normal while approaching the runway. He slipped the airplane down and the airplane floated down the runway. The airplane touched down near the end of the runway and the when the brakes were applied, the pilot lost control of the airplane. Swerving left and right, the airplane exited the side of the runway. The nose wheel got stuck in the soil and the airplane nosed over coming to rest inverted. The flap actuator motor, jackscrew, and flap tube assembly were sent to Textron Aviation for an examination. Under the auspices of inspectors from the Federal Aviation Administration, the jackscrew was unboxed and examined. The flap tube assembly on the flap actuator motor was found fully extended and bound. The tube assembly was freed mechanically, and the flap actuator motor was able to move the tube assembly normally. Further examination did not find a reason for why the tube assembly had become bound. No anomalies were detected with the jackscrew or the flap actuator While performing touch-and-go landings, the private pilot noticed that the ground run was longer than usual and that the airplane had difficultly climbing. He saw that the flaps were still at 30° despite the flap handle being in the "up" position. The pilot then maneuvered to land, but the airplane was higher than normal while approaching the runway. He slipped the airplane down, and the airplane floated down the runway. After the airplane touched down near the end of the runway, the pilot applied the brakes, but he then lost directional control, and the airplane exited the side of the runway. The nosewheel got stuck in the soil, and the airplane nosed over, coming to rest inverted. Examination of the flap assembly revealed that the flap tube assembly on the flap actuator motor was fully extended and bound. The tube assembly was freed mechanically, and the flap actuator motor was then able to move the tube assembly normally. Further examination did not reveal a reason why the tube assembly had become bound. No anomalies were noted with the jackscrew or the flap actuator motor. It is likely that the pilot was confused by the airplane's performance with 30° of flaps while on the approach because it was not what he was used to and that the bound flaps prevented him from getting the airplane to achieve sufficient airspeed for a proper approach and landing, which led to the unstabilized approach and long landing. The pilot's subsequent uneven application of braking resulted in the runway excursion. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
  • F Aircraft-Aircraft systems-Flight control system-TE flap actuator-Malfunction - F

Verbatim from NTSB's published report. Source file NTSB_2016_CEN16LA259.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion, unstabilized approach). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗