ERA22FA261 · Piper PA-28RT-201
Piper PA-28RT-201 · Accident: loss of engine power (partial) during initial climb
From Northwest Florida Beaches International Airport (ECP) to Orlando Executive Airport (ORL)
Event
- NTSB case
- ERA22FA261
- 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
- 2 · 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-28RT-201
- 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
- N160LL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Northwest Florida Beaches International Airport (ECP), Panama City, FLTo Orlando Executive Airport (ORL), Orlando, FL
- Aircraft age
- About 43 years (built 1979)
- 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
- Initial climb
- 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 (partial)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a personal flight with two passengers aboard. Security camera video revealed that when the pilot arrived at the airplane prior to initiating the flight, he did not perform a complete preflight inspection, which should have included at least a cursory examination of the airplane’s engine and a check of the ground below it. Shortly after departure, the pilot declared an emergency, and the airplane made a 180° left turn back toward the airport. The airplane descended and impacted terrain about 1.7 miles from the runway threshold. Postaccident examination of the engine revealed that the crankcase was breached near the No. 4 cylinder. Also, the No. 4 connecting rod journal exhibited thermal damage and bearing material was found welded/smeared to the crankshaft journal. The No. 4 connecting rod cap, connecting rod bolts, and bearing pieces were found in the oil sump along with other metallic debris and a trace amount of oil. Examination of the oil system revealed that the oil pressure sensor was separated from the engine. The sensor’s rigid copper line was fractured at the fitting to the accessory section of the crankcase. The propeller exhibited chordwise scratching and angle-cut tree branches in the vicinity of the wreckage, which were indications that the engine did not lose total power. Examination of the rigid oil pressure line revealed that it fractured due to high-cycle fatigue. This was likely from excessive vibration due to insufficient support of the oil pressure sensor and rigid line. The oil pressure sensor, which was part of the avionics system, was installed about 3 flight hours before the accident. The installation manual for the avionics system stated that a flexible line should be used to install the oil pressure sensor in order to minimize vibration effects. Instead, a rigid line was installed, which would have been more susceptible to the effects of vibration, including high-cycle fatigue failure. Oil staining observed on the ramp area where the airplane was parked before the flight, a trail of oil leading from the parking area to the runway, and the oil observed on the airframe exterior at the accident site all suggest that the airplane was actively leaking oil both before and during the accident flight. Based on all available information, it is likely that the oil pressure sensor line fractured during the flight before the accident flight, which resulted in oil leaking from the engine. This oil leak ultimately resulted in oil starvation and loss of engine power during the departure from, and the pilot’s attempted return to the airport. Had the pilot noted and investigated the source of the oil leakage during the preflight inspection, he might have taken appropriate corrective action and avoided the accident.
Probable cause
Maintenance personnel’s failure to follow the avionics installation guidance for the oil pressure sensor, which resulted in the high-cycle fatigue failure of an line, oil starvation, and the subsequent loss of engine power. Contributing to the accident was the pilot’s failure to perform an adequate preflight inspection of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22FA261
- Event ID
- 20220606105200
- Case number
- ERA22FA261
- 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. 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: c3a7539b5db13dd6363dac1a7a4cd9f61fb4a7e0c9ce0c5a1f44c733c0b431e5; retrieved 2026-09-15T07:45:45.019Z.