FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15LA146 · Piper PA 28R-180

13 Feb 2015 · Haviland, KS, United States

Piper PA 28R-180 · Accident: loss of engine power (total) en route

From East Kansas City Airport (3GV) to Dalhart Municipal Airport (DHT)

Report a problem

Event

NTSB case
CEN15LA146
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 28R-180

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
N3918T
Operator
Unknown
Onboard fatalities
Unknown
Route
From East Kansas City Airport (3GV), Grain Valley, MOTo Dalhart Municipal Airport (DHT), Dalhart, TX
Aircraft age
About 48 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)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Pole
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

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot had purchased the airplane and had a mechanic perform a prepurchase inspection. During the inspection, the mechanic determined that a cylinder had recently been changed. The pilot subsequently departed at night for a cross-country flight to his base airport. The pilot reported that, during cruise flight at 8,500 ft mean sea level and about 2.2 hours into the flight, he heard an "explosion"; the airplane then decelerated and started rapidly descending. The pilot was unable to restart the engine and chose to perform forced landing on a road. The pilot placed the landing gear selector in the "down" position, but only the main landing gear extended, so he conducted the emergency landing gear extension procedures; however, the nose landing gear still did not extend. During the forced landing, the airplane impacted a highway sign pole, departed the road, impacted a culvert, traveled over a ditch, and came to rest about 50 ft from the road.

According to the mechanic who had recently replaced the No. 4 cylinder, he removed the cylinder and installed the replacement cylinder in accordance with the engine manufacturer overhaul manual directions. Specifically, he replaced the rod bolts and nuts and reinstalled the connecting rod. The mechanic initially reported that he performed the cylinder break-in procedures and that the cylinder functioned normally. However, he subsequently reported that the break-in flight time was not flown continuously as recommended in the service instruction.

Initial examination of the engine revealed that the No. 4 cylinder had separated from the crankcase. During subsequent disassembly and examination, a large hole in the crankcase was observed between the Nos. 3 and 4 cylinders. The No. 4 connecting rod was severely bent with the piston pin still in the connecting rod small end; the piston was fractured around the skirt and through the pin bosses. The remaining skirt portions exhibited a burnished appearance, consistent with contacting the bore. The upper right anchor through bolt exhibited stretching, and part of the fracture surface was separated in a flat pattern perpendicular to the length of the through bolt. Some of the cylinder through bolts were missing, but one 1/2-inch through bolt from the No. 4 cylinder was found, and it exhibited a granular appearance and was broken perpendicular to the length of the bolt. The upper sections of the No. 4 cylinder deck and a section of the upper right anchor bolt exhibited fretting, indicative of a loss of torque.

Based on the observed witness marks and damage, the No. 4 piston failed, which liberated the connecting rod. The connecting rod with the piston pin still in the small end bore contacted the camshaft and fractured it and the adjacent crankcase structure. The separated rear section of the camshaft and crankcase structure was displaced toward the No. 4 cylinder and led to its separation, which caused the engine to stop running; this scenario is consistent with the pilot's report of an explosion and engine stoppage. Further, the fretting damage and bolt failures indicated that the No. 4 cylinder likely separated from the crankcase due to a loss of torque on the cylinder bolts. The break-in procedures used by the mechanic were likely not a factor in the accident.

Probable cause

The loss of torque on the No. 4 cylinder through bolts, which led to the subsequent failure of the piston, the liberation of the connecting rod, the separation of the No. 4 cylinder from the crankcase in cruise flight, and the airplane’s subsequent impact with a pole during a night forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15LA146
Event ID
20150217X62326
Case number
CEN15LA146
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2015-02-14.
  • API snapshot SHA-256: 3264e30f07cbfc3fbe5589504c15b51a344f6e0bf8ce145a5f63997529ad8a96; retrieved 2026-09-16T02:05:24.856Z.