21 Jul 2012: PIPER PA-22-150

21 Jul 2012: PIPER PA-22-150 (N4749A) — Unknown operator

No fatalities • Augusta, KS, United States

Probable cause

The loss of brake effectiveness on landing roll for reasons that could not be determined because a postaccident brake system examination did not reveal any anomalies, which resulted in a runway excursion.

— NTSB Determination

Accident narrative

On July 21, 2012, about 1120 central daylight time, a Piper PA-22-150, N4749A, was substantially damaged during a runway excursion while landing on runway 18 (4,201 feet by 60 feet, asphalt) at the Augusta Municipal Airport (3AU), Augusta, Kansas. The pilot and sole passenger sustained minor injuries. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, which was not operated on a flight plan. The local flight originated from 3AU about 1115.

The pilot reported that the preflight run-up was uneventful and the brakes worked normally at that time. After takeoff, she remained in the airport traffic pattern and returned for a full stop landing. The pilot stated that the approach and landing were normal; however, on rollout the brakes were completely ineffective. Upon reaching the end of the runway, she thought that the airplane was still traveling too fast to safely turn onto the taxiway. She elected to overrun the end of the runway and encountered a concrete culvert.

A postaccident examination conducted by Federal Aviation Administration inspectors was inconclusive with respect to the brake system. The examination did not reveal any anomalies consistent with a brake system failure. However, the main landing gear tires did not exhibit any flat areas indicative of a skidding tire, nor were any skid marks corresponding to the accident airplane observed on the runway pavement.

According to the pilot, the airplane was equipped with the original handbrake. There were no toe brakes installed. The pilot reported a total flight time of 136 hours, with 96 hours in Piper PA-22-150 airplanes.

Contributing factors

  • cause Inoperative

Conditions

Weather
VMC, wind 180/04kt, 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.