10 Apr 2011: BENNETT MIDJET MUSTANG I

10 Apr 2011: BENNETT MIDJET MUSTANG I (N611JB) — Unknown operator

No fatalities • Ramona, CA, United States

Probable cause

The pilot's inability to maintain directional control during the landing roll due to the overload separation of the left brake master cylinder from the left rudder pedal assembly.

— NTSB Determination

Accident narrative

On April 10, 2011, about 0828 Pacific daylight time, a tail wheel equipped amateur built experimental Bennett Midjet Mustang 1, N611JB, sustained substantial damage while landing at the Ramona Airport (RNM), Ramona, California. The airline transport pilot, sole occupant of the airplane, sustained minor injuries. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight. The local flight originated from RNM about 0810.

In a written statement, the pilot reported to the Safety Board investigator-in-charge (IIC) that he was conducting a series of touch-and-go landings on runway 27, a 5,001-foot long and 150-foot wide asphalt runway. The pilot said that his first two takeoffs and landings were very smooth and uneventful. During his third takeoff, as the airplane ascended through about 30 feet, he heard a loud "snap" followed by the upper left rudder pedal collapsing. The pilot confirmed rudder continuity and noted that the "upper portion of the left rudder pedal seemed displaced well forward of its normal position, and at times binding but functional." The pilot stated that he noticed no degradation of the flight controls and suspected that the left brake master cylinder had possibly separated from the rudder pedal.

The pilot further reported that he conducted a normal tail-low wheel landing on runway 27, favoring the right side of the runway. As the tail wheel settled onto the runway, the airplane slightly moved to the right. The pilot stated that he inputted left rudder to correct the change in heading and the airplane "lurched hard to the left" as if he had "deliberately applied left brake along with the corrective rudder." Despite the pilot's control inputs, the airplane continued to the left and exited the runway surface. Subsequently, the airplane nosed over in soft muddy terrain, which resulted in substantial damage to the fuselage and both wings.

Postaccident examination of the airplane by the pilot revealed that the left brake master cylinder was separated from the left rudder pedal at the rudder attach point. The left rudder pedal and separated portion of the master cylinder attach point clevis were sent to the National Transportation Safety Board Materials Laboratory, Washington, DC, for further examination.

Examination of the components by a Senior Materials Engineer revealed that the left rudder pedal was fractured at the lug where it attached to the upper end of the brake master cylinder. The fracture surface was relatively rough and matte gray, features consistent with overstress fracture. The fracture surface was examined using a scanning electron microscope, and no evidence of fatigue or other progressive crack growth was observed.

The lower surface of the brake master cylinder attachment lug on the left rudder pedal had an impression corresponding to contact with the lower end of the clevis of the left master brake cylinder attachment fitting. A similar impression was observed on the lower surface of the brake master cylinder attachment lug on the right rudder pedal. Deformation consistent with contacting the lower surface of the rudder pedal lugs was observed at the base of the clevis in the upper attachment fittings of both the left and right brake master cylinders.

Contributing factors

  • cause Attain/maintain not possible
  • cause Master cylinder/brake valve — Failure

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.