FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25LA223 · Piper PA22 150

7 Jun 2025 · Hebron, OH, United States

Piper PA22 150 · Accident: system/component malfunction/failure (non-power) during landing

From an unrecorded airport to Fairfield County Airport (LHQ)

Report a problem

Event

NTSB case
ERA25LA223
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA22 150

Aircraft type
Piper PA22
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N6804B
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Fairfield County Airport (LHQ), Lancaster, OH
Aircraft age
About 69 years (built 1956)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that the brakes functioned normally during taxi, and pretakeoff checks, with no anomalies noted. The flight was uneventful, and he entered the traffic pattern at his destination airport. After touchdown, he retracted the flaps, reduced engine power, and applied the brakes, and the airplane initially decelerated as expected. With about one-third of the runway remaining, total brake pressure was lost. He determined that insufficient runway remained to execute a go-around, so he elected to perform “S” turns in an attempt to slow the airplane. As the airplane approached the end of the runway, he applied right rudder to avoid a runway overrun. During the ensuing turn, the left wing impacted the ground, which resulted in substantial damage to the wing.

The mechanic who completed the most recent annual inspection of the airplane reported that, 10 days before the accident, he had installed a new brake booster in accordance with a supplemental type certificate (STC). The STC kit did not include the required “screw-vent”, so the mechanic temporarily installed a brake bleeder valve and instructed the owner not to fly the airplane before the correct screw-vent was installed. The brakes were bled multiple times, operationally checked, the maintenance logbook was signed, and the airplane was returned to service.

The pilot reported that, 5 days before the accident, the brakes were inoperative due to a lack of pressure during an attempted taxi. He stated that a local mechanic sanded the brake caliper and replaced the Orings/packing; however, no maintenance logbook entry was made, and the mechanic denied performing the work. The mechanic did report that he had examined the airplane, provided advice to the pilot, and observed several discrepancies, including a missing screw vent. Following the reported maintenance, the pilot stated that an operational check of the brakes was conducted with no anomalies noted.

Postaccident examination of the brake system by an FAA airworthiness inspector revealed a significant amount of air in the system and no brake pressure. After the brakes were bled and an operational check was conducted, brake engagement did not occur until the final 10% of brake handle travel, and full brake effectiveness was not achieved. The examination also identified the presence of an unapproved part and incomplete compliance with the supplemental type certificate. Additionally, evidence indicated that undocumented maintenance had been performed following installation of the STC.

Due to either an unapproved part, undocumented maintenance, and incomplete compliance with the STC, it is likely that the air in the brake system was a result of inadequate maintenance.

Probable cause

The airplane owner and pilot’s intentional allowance of unapproved maintenance and maintenance personnel’s failure to adequately maintain or service the brake system, which resulted in a total loss of brake pressure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25LA223
Event ID
20250609200286
Case number
ERA25LA223
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d75665a78d729a2c2b16693de8337ba7799ac6c5fa49741c2087ff5f40823bc3; retrieved 2026-09-16T19:56:48.137Z.