19 Aug 2008: PIPER PA-22-160 — Tri Pacer Flyers LLC

19 Aug 2008: PIPER PA-22-160 (N9403D) — Tri Pacer Flyers LLC

No fatalities • Jeannette, PA, United States

Probable cause

Failure of the brakes to function due to inadequate inspection of the brake cable by maintenance personnel.

— NTSB Determination

Accident narrative

On August 19, 2008, about 1852 eastern daylight time, a Piper PA-22-160, N9403D, registered to Tri Pacer Flyers LLC, operating as a 14 Code of Federal Regulations Part 91 personal flight went off the right side of runway 20 on landing roll out at Greensburg Jeannette Regional Airport (5G8), Jeannette, Pennsylvania. The airplane received substantial damage. Visual meteorological conditions prevailed and no flight plan was filed. The private pilot and one passenger reported no injuries. The flight originated from William T. Piper Memorial Airport (LHV), Lock Haven, Pennsylvania, at 1730.

The pilot stated he over flew 5G8 and obtained the landing direction from the windsock. He entered the traffic pattern on a left downwind leg for runway 20, and made two visual approaches with go-arounds due to the airplane being too high. On the third approach, he landed the airplane 600 feet past the landing threshold. The airplane bounced and touched down on the runway about 1,300 feet past the landing threshold. He aligned the airplane with the centerline of the runway and applied upward pressure on the manual brake to slow the airplane down. There was no response from the brake. The pilot reapplied upward pressure on the brake and there was no response. He looked down towards the firewall, observed the brake cable had separated, and he started "S" turning the airplane on the runway in an attempt to slow down and stop. He then realized he was about 50 yards from the end of the runway and there was an embankment. He applied right rudder to turn the airplane off the right side of the runway. The right main landing gear came up off the runway, and the propeller and left wing tip collided with the runway. The airplane continued off the runway and the nose wheel collapsed.

Examination of the airplane by Federal Aviation Administrator (FAA) inspectors revealed the firewall was buckled. The brake lever cable was removed and forwarded to the National Transportation Safety Board Materials Laboratory for examination. The cable was separated at about mid length. Scanning electron microscope examinations of one end of the brake cable revealed fatigue features on the wires on about two thirds of the cable wires with the remaining wires fractured due to overstress. Further examination of the cable uncovered an additional area of broken wires about midway between the brake handle end and the separation area. Multiple broken wires were visible when the cable was manually flexed as shown in the illustration in advisory circular (AC) 43.13.1B for cable inspections.

Review of the airplane logbooks revealed the last annual inspection was conducted on July 14, 2008. In addition, according to the airport manager at LHV, who is the manager for Tri Pacer Flyers LLC, a brake booster was installed on the airplane during the annual inspection, and no anomalies were noted with the brake cable.

The airframe and power plant mechanic who performed the annual inspection stated he did not remove the brake cable entirely from the airplane during his inspection and installation of the brake booster nor did he use a magnifying glass to inspect the brake cable. He stated he pulled the cable up one side to the pulley at the bottom of the firewall and inspected the brake cable all the way up to the brake handle. He used a cotton rag to detect any broken wires by running the rag over the cable and there were no snags.

The notes section of the Piper Aircraft Inspection Report for the PA-22 series references FAA Advisory Circular 43.13-1B for cable inspections. For cable inspections the AC reports the following in chapter 7 section 149, paragraph d.

"Close inspection in these critical fatigue areas, must be made by passing a cloth over the area to snag on broken wires. This will clean the cable for a visual inspection, and detect broken wires if the cloth snags on the cable. Also, a very careful visual inspection must be made since a broken wire will not always protrude or stick out, but may lie in the strand and remain in the position of the helix as it was manufactured. Broken wires of this type may show up as a hairline crack in the wire. If a broken wire of this type is suspected, further inspection with a magnifying glass of 7 power or greater, is recommended. Figure 7-16 shows a cable with broken wires that was not detected by wiping, but was found during a visual inspection. The damage became readily apparent when the cable was removed and bent as shown in figure 7-16."

Contributing factors

  • Fatigue/wear/corrosion
  • cause Inadequate inspection
  • cause Maintenance personnel
  • cause Brake — Failure

Conditions

Weather
VMC, wind 340/05kt, vis 15sm

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.