Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

August 19, 2008 · Piper PA-22-160 · N9403D

Jeannette, PA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 19, 2008
Injury Outcomes
No injuries (2 uninjured)
Location
Jeannette, PA
Aircraft
Piper PA-22-160
Tail Number
N9403D
Injuries
None
Aircraft Damage
Substantial
NTSB Number
MIA08LA168

The pilot stated that the airplane bounced on landing. He aligned the airplane with the centerline and applied upward pressure on the manual brake; however, there was no response from the brake. He looked down towards the firewall, and observed the brake cable had separated. He started "S" turning the airplane in an attempt to slow down and stop. The airplane was about 50 yards from the end of the runway with an embankment. He applied right rudder to turn the airplane off the right side of the runway. The airplane continued off the runway and the nose wheel collapsed. Examination of the brake lever cable revealed that it failed due to fatigue. The last annual inspection was completed 36 days before the accident. The airframe and power plant mechanic who performed the annual inspection stated that he also installed a brake booster on the airplane during the inspection. The mechanic stated that he did not totally remove the cable from the airplane during his examination; however, he did check the brake cable with a cloth and there were no snags from broken wires. The Federal Aviation Administration advisory circular that pertains to the inspection of the brake cables states, "in addition to passing a cloth over the area to check on wire snags that 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."

NTSB Probable Cause

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

Full 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."

Flight

Event TypeAccident
Event Time18:52 EDT
Nearest AirportGreensburg Jeannette Regional (0nm)
Runway20
Runway Length2605 ft
Runway Width50 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-22-160
Tail NumberN9403D
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-B2B · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 53 · Third Class · None

Conditions

ConditionsVMC
LightDusk
Wind340° @ 5 kt
Visibility15 sm
CeilingNone
Temperature / Dew Point63 F
Altimeter30.06 inHg
Observation Time22:50
Weather SourceWFAC

Appendix: Source Data