Skip to content

Atlas / NTSB / CHI03LA011

NTSB CAROL · Event

Event CHI03LA011

2002-10-20 Plymouth, Michigan, United States Airport · 1D2 None 1 aircraft Status: Completed

Registry · N56655

FAA Aircraft Registry record.

Make / Model

PIPER PA-32-300

Year of manufacture

1973 · 29 years old at event

Engine

LYCOMING TI0-540 SER (310 hp)

Seats / Engines

6 seats · 1 engine

Last airworthiness date

19730927

ADS-B equipped

Yes — Mode-S A74059

Registrant of record

WHITE JAMES T

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot not maintaining directional control during landing and the inoperative right main landing gear brake. Contributing factors were the failed brake master cylinder seal, resulting in a hydraulic leak, the inadequate preflight by the pilot, the fuel fire, and the pilot intentionally operating the airplane with a known brake system problem.

Factual narrative

On October 20, 2002, about 1120 eastern daylight time, a Piper PA-32-300, N56655, piloted by a private pilot, sustained substantial damage when it went off the right side of the runway and struck a part of the visual approach slope indicator (VASI) system. The airplane was landing on runway 36 (2,556 feet by 75 feet, asphalt), at the Canton-Plymouth Mettetal Airport (1D2), Plymouth, Michigan. when the accident occurred. The 14 CFR Part 91 personal flight was operating in visual meteorological conditions. The pilot and passenger were not injured. The flight departed Paul C. Miller - Sparta Airport (8D4), Sparta, Michigan, at 1030. The pilot reported that upon landing on runway 36, the winds were 270 at 8 knots. He stated that upon touching down he realized he was moving a little fast; the airplane didn't settle and seemed to float. He applied braking to slow down but the right brake was not working. The pilot attempted to slow the airplane by using left braking and right rudder. The pilot reported that the aircraft then veered to the right (east side) and went off the runway. The pilot noted that he attempted to bring the airplane back onto the runway. The aircraft subsequently struck the VASI system with the left wing and the airplane caught fire. The pilot and his passenger safely exited the aircraft and the fire was put out by the pilot and airport staff. The pilot made a flight the day prior to the accident and reported that the brakes were working fine. The pilot stated "Had I known the brake fluid was low again, and that I did not have complete brake function, I wouldn't have made the flight." He reported that he had maintenance performed on the brakes on August 8th and September 25th of 2003, at which time the mechanic bled the lines and added fluid. The pilot reported that, subsequent to the accident, a seal within the brake master cylinder was found to be defective. He reported that this allowed the fluid level to be low and air to enter the brake lines. The airplane received substantial damage when it struck a visual approach slope indicator light after a loss of control during landing. A fire subsequently erupted and was extinguished by the pilot and airport personnel. The pilot reported that during the landing his right brake was not working. He stated that he attempted to stop using the left brake and compensating with rudder. The aircraft veered to the right, departed the runway, and struck a visual approach slope indicator light. The pilot stated he had maintenance performed on the brakes twice in the previous 2 months, at which time the mechanic bled the lines and added fluid. He stated that he had flown the airplane the day before with no problems. Subsequent to the accident, a seal in the brake master cylinder was found defective. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2002_CHI03LA011.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 (loss of control, maintenance). 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 ↗