The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ERA25LA223 · Final report

Piper PA22 accident near Hebron, Ohio, June 7, 2025

On June 7, 2025 at about 5:09 pm local time, a 1956 Piper PA22, registered N6804B, was substantially damaged in an accident during landing (landing roll) near Hebron, Ohio (Buckeye airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 7, 2025 · about 5:09 pm local time
Place
Hebron, Ohio · Buckeye · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA22 150, built 1956 · all PA22s on the register
Registration
N6804B · registry record · serial 22-4099
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Sys/Comp malf/fail (non-power) during landing (landing roll) defining event
  2. Dragged wing/rotor/float/other during landing (landing roll)

The NTSB's findings

  • Aircraft › Aircraft systems › Landing gear system › Landing gear brakes system › Failure
  • Personnel issues › Task performance › Maintenance › Modification/alteration › Maintenance personnel
  • Personnel issues › Task performance › Maintenance › Unauthorized maint/repair › Unknown/Not determined
  • Personnel issues › Task performance › Maintenance › Unauthorized maint/repair › Maintenance personnel
  • Personnel issues › Task performance › Maintenance › Unauthorized maint/repair › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 145 hours in all; 56 in this make and model
  • Last flight review: November 18, 2024
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,005 hours
  • Last inspection: annual inspection, May 28, 2025
  • Maximum gross weight: 2,000 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 1,006 hours total

The flight

  • Destination: LHQ Lancaster OH
  • Flight plan: none
  • Runway 19, 2,764 ft by 25 ft

Weather at the time

  • Light: daylight
  • Visibility: 3 statute miles
  • Sky: a few clouds at 3,800 ft
  • Temperature: 75°F (24°C), dew point 63°F (17°C)
  • Altimeter: 29.88 inHg
  • Observation at 12:54 pm from VTA, 5 miles away

Weather report (METAR): KVTA 071654Z AUTO 00000KT 3SM HZ FEW038 SCT048 24/17 A2988 RMK AO2 SLP111 T02390167

Injuries

FatalSeriousMinorNone
Flig1
Passengers1

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA25LA223.