ERA20LA322 · Piper PA28R 180
Piper PA28R 180 · Accident: loss of engine power (total) en route
From Patrick Leahy Burlington International Airport (BTV) to Carroll County Regional Jack B Poage Field (DMW)
Event
- NTSB case
- ERA20LA322
- 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 PA28R 180
- Aircraft type
- Piper PA28
- 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
- N3790T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Patrick Leahy Burlington International Airport (BTV), Burlington, VTTo Carroll County Regional Jack B Poage Field (DMW), Westminster, MD
- Aircraft age
- About 53 years (built 1967)
- 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
- En route · cruise
- 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
- Loss of engine power (total)
- 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 power plant
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a personal cross-country flight, the owner seated in the right front seat noted the No. 2 cylinder exhaust gas temperature had decreased about 1/2 of its value. The pilot-in-command (PIC) and owner both then felt a vibration and positive control of the airplane was transferred to the owner as was briefed before departure. An emergency was declared with air traffic control while (best glide speed) airspeed was maintained. The PIC reported there were no suitable airports nearby and proceeded to a diversion airport 77 miles away.
While continuing toward the diversion airport, the oil pressure decreased to zero. Realizing the flight would not reach the airport, the pilot maneuvered for a forced landing to a residential street and collided with a powerline. The accident site was located less than 2 nautical miles north-northeast from the approach end of the intended runway at the diversion airport.
Postaccident examination of the engine revealed that all anchored-thru or free-thru studs that secured the No. 2 cylinder to the crankcase exhibited fatigue. The fatigue originated at the roots of the threads and propagated though about 70% to 80% of the diameter of the studs before finally fracturing due to overstress. The fatigue-fractured studs led to the cylinder separating from the engine, the loss of oil supply, and subsequent total loss of engine power.
Although the pilot was not aware of the extent of the problem with the No. 2 cylinder, about the time the problem arose, the flight was about 30 nautical miles west-northwest of an international airport with available runways of sufficient length. As the flight continued in a southerly direction, about the time and location the oil pressure decreased to zero, another airport with a runway of more than adequate length was located 20 nm closer than the intended diversion airport. Thus, had the pilot diverted to the nearest airport immediately after the loss of the No. 2 cylinder, or diverted to an airport about 20 nautical miles closer than his intended airport after the oil pressure decreased to zero, it is likely an uneventful on-airport forced landing could have been performed.
Twelve years after the engine was overhauled, or 3 years and 270 hours prior to the accident, the No. 2 cylinder was removed to replace a fractured anchored-thru stud. After the fractured anchored-thru stud was replaced, the cylinder was installed. Several entries indicated that the hardware that clamped the crankcase halves together on the top portion of the engine was re-torqued. It is likely that during installation of the No. 2 cylinder following replacement of the fractured anchored-thru stud, the anchored-thru and free-thru studs were inadequately torqued, which resulted in fatigue fracturing of all studs followed by cylinder separation, oil exhaustion, and resulting total loss of engine power.
Probable cause
The inadequate torquing of anchored-thru and free-thru studs during installation of the No. 2 cylinder, resulting in their fatigue fracture and subsequent total loss of engine power. Contributing to the undershoot landing was the pilot’s failure to divert to closer airports than the original diversion airport after experiencing engine performance issues.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA322
- Event ID
- 20200921X74933
- Case number
- ERA20LA322
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-09-21.
- API snapshot SHA-256: 724b75a1c861b4b11cf383f2de8685c74b7611e08064f5916c9c816f7714a16e; retrieved 2026-09-16T13:04:55.056Z.