FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12LA023 · Piper PA-28-235

8 Oct 2011 · Wadsworth, OH, United States

Piper PA-28-235 · Accident: system/component malfunction/failure (non-power) during landing

From Mid Ohio Valley Regional Airport (PKB) to Weltzien Skypark Airport (15G)

Report a problem

Event

NTSB case
CEN12LA023
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
API-reported fatalities
0 · all aircraft and ground
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 PA-28-235

Aircraft type
Piper PA-28
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
N9444W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mid Ohio Valley Regional Airport (PKB), Parkersburg, WVTo Weltzien Skypark Airport (15G), Wadsworth, OH
Aircraft age
Not recorded
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

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that, prior to the flight, he noted no anomalies with the airplane or its braking system. After touchdown, the pilot applied the brakes to slow the airplane to exit the runway, but the airplane did not slow down. The airplane then departed the runway surface and the right wing contacted the visual approach slope indicator system. The airplane came to rest upright adjacent to the runway. A postaccident examination of the airplane revealed that the left brake caliper was leaking hydraulic fluid; no fluid was found in the brake system’s reservoir. Hydraulic fluid was then added to the reservoir, and a leak was noticed at the brake caliper without any brake pressure being applied to the system. The brake caliper and brake plates were removed and the brake plates were found to be worn beyond service limits, which resulted in an overextension of the brake piston and failure of the piston seal. The failure of the piston seal resulted in the loss of hydraulic fluid.

Probable cause

The failure of the brake system during the landing roll, which was caused by a loss of hydraulic fluid as a result of a leak in the piston seal due to brake plates worn beyond their service limits.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12LA023
Event ID
20111017X00543
Case number
CEN12LA023
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, coordinates. 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: 124d2fc66a477f14095cfe6ea573c5e61114c0030d867bba7bba28bee4b1bd6d; retrieved 2026-09-15T16:51:02.453Z.