Piper PA-31P accident near Doylestown, Pennsylvania, September 8, 2013
On September 8, 2013 at about 2:30 pm local time, a 1975 Piper PA-31P, registered N57JK, was substantially damaged in an accident during landing (landing roll) near Doylestown, Pennsylvania (Doylestown Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A leaking parking brake valve, which allowed air to enter the left brake line and resulted in the eventual failure of the left wheel brake during the landing roll.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 8, 2013 · about 2:30 pm local time · cases in 2013
- Place
- Doylestown, Pennsylvania · Doylestown Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-31P, built 1975 · all PA-31Ps on the register
- Registration
- N57JK · no longer on the register · serial 31P-7530020
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Following a normal landing, the pilot felt no wheel braking action on the left wheel, and the brake pedal went to the floor. The pilot attempted to maintain directional control; however, the airplane departed the right side of the runway and traveled into the grass. The landing gear collapsed, and the airplane came to a stop, sustaining structural damage to the left wing spar. Postaccident examination confirmed that the left brake was inoperative and revealed a small hydraulic fluid leak at the shaft of the parking brake valve in the pressurized section of the cabin. Air likely entered the brake line at the area of the leak while the cabin was pressurized, rendering the left brake inoperative.
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
- Sys/Comp malf/fail (non-power) during landing (landing roll) defining event
- Runway excursion during landing (landing roll)
- Landing gear collapse during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft systems › Landing gear system › Master cylinder/brake valve › Malfunction other cases naming the landing gear
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 1,612 hours in all; 1,054 in this make and model; 21 in the last 90 days; 4 in the last 30 days; 1,424 as pilot in command
- Last flight review: April 10, 2013
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,952 hours
- Last inspection: annual inspection, November 2, 2012; 35 hours since
- Maximum gross weight: 7,800 lb
- Seats: 8
- Landing gear: retractable
- Engine 1: Lycoming TIGO-541SER (piston); 0 hours total
- Engine 2: Lycoming TIGO-541SER (piston); 0 hours total
The flight
- Departed from: CGE Cambridge MA at 1:45 pm
- Destination: DYL Doylestown PA
- Flight plan: IFR
- Runway 05, 3,004 ft by 60 ft
Weather at the time
- Light: daylight
- Wind: from 290° at 6 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 3,500 ft
- Temperature: 75°F (24°C), dew point 63°F (17°C)
- Altimeter: 29.87 inHg
- Observation at 2:54 pm from DYL
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on October 30, 2013. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | FAA Inspector Statement | PDF, 1 page | View Download |
| 3 | Correspondence with FAA | PDF, 2 pages | View Download |
| 4 | Photo 1: Wreckage, View from Front (FAA Digital Photo) | PDF, 1 page | View Download |
| 5 | Photo 2: Right Wing Structural Damage (FAA Digital Photo) | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N57JK: not on the register today · the record of its deregistration
- Piper PA-31 Navajo and Chieftain 934 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Lycoming TIGO-541SER 37 aircraft carry this series today · as the NTSB recorded it
- Engine: Lycoming TIGO-541SER 37 aircraft carry this series today · as the NTSB recorded it
- Doylestown Airport · nearest airport
- Cambridge-Dorchester Regional · departed from
- Accidents and incidents in Pennsylvania 1,836 since 1982 · 233 in the last ten years
- Pennsylvania 6,195 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA13LA409.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
