eFlight
Accidents · NTSB ERA23LA112 · Final report

Piper PA-31-350 accident near Middlefield, Ohio, January 18, 2023

On January 18, 2023 at about 2:03 pm local time, a 1977 Piper PA-31-350, registered N101MA, was substantially damaged in an accident during landing (landing roll) near Middlefield, Ohio (Geauga County airport). It was a business flight under charter and air-taxi rules (Part 135). No one was hurt; 6 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

A runway overrun during a precautionary landing following a total loss of right engine power due to detonation and subsequent oil starvation. Contributing was the pilot’s failure to lower the flaps and the excessive airspeed at touchdown.

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

What the record shows

Date
January 18, 2023 · about 2:03 pm local time · cases in 2023
Place
Middlefield, Ohio · Geauga County · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 6 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-31-350, built 1977 · all PA-31-350s on the register
Registration
N101MA · registry record · serial 31-7752186
Damage
Substantial damage
Flight
Business flight · charter and air-taxi rules (Part 135)

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

While enroute in instrument meteorological (IMC) conditions, the pilot of the twin-engine, piston-powered airplane declared an emergency following a loss of power to the right engine. The pilot secured the engine and was provided vectors by air traffic control for an instrument approach procedure at the nearest airport, which he successfully completed. The pilot reported that he flew the approach and landing with the wing flaps retracted and visually acquired the runway about 500 ft above the ground. The airplane touched down on the first third of the runway at 120 knots. The pilot knew he would not be able to stop the airplane on the 3,500-ft-long runway but committed to the landing rather than risking a single-engine go-around in IMC. After landing, the airplane continued beyond the departure end of the runway and impacted a berm, collapsing the landing gear and resulting in substantial damage to the airplane. Examination of the engine revealed catastrophic damage consistent with detonation and oil starvation. The damage to the No. 5 cylinder was consistent with a subsequent overpressurization of the crankcase, which likely expelled the crankshaft nose seal and the oil supply. Detonation of the cylinder(s) can create excessive crankcase pressures capable of expelling the crankshaft nose seal. The crankshaft nose seal displacement likely created a rapid loss of oil and the resulting oil starvation of the engine. The fractured connecting rod and high-temperature signatures were consistent with oil starvation. No source or anomaly that would result in engine detonation was identified. According to the Pilot’s Operating Handbook (POH) for the accident airplane, during a single-engine inoperative approach, the pilot should maintain an airspeed of 116 kts indicated (KIAS) or above until landing is assured. Once landing is assured, the pilot should extend the gear and flaps, slowly retard the power on the operative engine, and land normally. The airplane’s best single-engine rate of climb speed (blue line) was 106 KIAS, and its minimum controllable airspeed with one engine inoperative (Vmca) was 76 KIAS. The maximum speed for full flap extension (40°) was 132 KIAS. The POH also stated that a single-engine go-around should be avoided if at all possible. The pilot’s decision to commit to the landing was reasonable given the circumstances and the guidance provided by the POH; however, it is likely that his decision to conduct the landing without flaps and the airplane’s excessive airspeed at touchdown resulted in the runway overrun.

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. Runway excursion during landing (landing roll) defining event
  2. Loss of engine power (partial) during enroute

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Capability exceeded
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Failure other cases naming the engine
  • Personnel issues › Action/decision › Action › Lack of action › Pilot
  • Aircraft › Aircraft systems › Flight control system › TE flap control system › Not used/operated other cases naming the flight controls

Pilot

  • Certificate: airline transport pilot, flight instructor
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 9,275 hours in all; 750 in this make and model; 155 in the last 90 days; 76 in the last 30 days; 8,965 as pilot in command; 1,100 on instruments
  • Last flight review: June 29, 2022
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 17,154 hours
  • Last inspection: 100-hour inspection, December 12, 2022; 42 hours since
  • Maximum gross weight: 7,448 lb
  • Seats: 8
  • Landing gear: retractable
  • Engine 1: Lycoming TIO-540-J2BD (piston); 1,370 hours total
  • Engine 2: Lycoming TIO-540-J2BD (piston); 1,370 hours total
  • Operator: Pablo Air Charters LLC

The flight

  • Departed from: KYNG Youngstown OH at 8:35 am
  • Flight plan: IFR
  • Runway 11, 3,500 ft by 65 ft

Weather at the time

  • Light: daylight
  • Wind: from 260° at 6 knots
  • Visibility: 0.5 statute miles
  • Sky: overcast at 1,000 ft
  • Temperature: 36°F (2°C), dew point 32°F (0°C)
  • Altimeter: 29.97 inHg
  • Observation at 9:15 am from POV, 16 miles away

Weather report (METAR): METAR KPOV 181415Z AUTO 26006KT 2 1/2SM OVC010 02/00 A2997 RMK AO2 T00220000 PWINO=

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers5

Photographs from the investigation 7 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

7 documents, released by the NTSB on October 3, 2024. 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.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N101MA the same tail number, which may have belonged to a different aircraft at the time

1983-03-24LAX83FJA05 · accident near Nr Lihue Arpt, HI · destroyed · fatal

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/ERA23LA112.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.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.