ERA15LA062 · Cirrus Design CORP. SR22T
Header Bug Cirrus Design CORP. SR22T · Accident: loss of engine power (total) en route
From Sarasota Bradenton International Airport (SRQ) to Orangeburg Municipal Airport (OGB)
Event
- NTSB case
- ERA15LA062
- 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
Cirrus Design CORP. SR22T
- Aircraft type
- Cirrus SR22
- 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
- N227RR
- Operator
- Header Bug
- Onboard fatalities
- Unknown
- Route
- From Sarasota Bradenton International Airport (SRQ), Sarasota, FLTo Orangeburg Municipal Airport (OGB), Orangeburg, SC
- Aircraft age
- Built the same year (2014)
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The private pilot was conducting a personal cross-country flight with three passengers on board. The pilot reported that, during the preflight inspection, he checked the quantity of engine oil and verified that there was an adequate supply of engine oil on board. During cruise flight, about 9,000 ft mean sea level (msl), the oil pressure indication decreased to 0, which resulted in both audible and visual warnings. The engine power then reduced to idle, and the pilot's attempts to restore engine power by moving the throttle were not successful. The pilot subsequently diverted to a nearby airport about 7.5 nautical miles (nm) away. He stated that he descended the airplane slightly faster than the published best glide airspeed. When the airplane was at 800 ft msl and he realized it would not be able to land at the intended runway, he deployed the ballistic parachute. The airplane descended under the canopy, hit trees, descended to the ground, and then came to rest about 3/4 nm from the approach end of the intended runway.
A postaccident examination and test run of the engine revealed no evidence of preimpact mechanical failures or malfunctions. Further, normal engine oil pressure was noted during the engine run; however, subsequent examination of the oil pressure transducer revealed that it was faulty and would have resulted in an erroneous oil pressure indication, as reported by the pilot. Further, although the pilot indicated that the engine lost power following the loss of oil pressure indication, which was supported by data downloaded from the onboard recording devices that showed decreased readings for fuel flow, exhaust gas temperature, and cylinder head temperature, the loss of engine power was consistent with the pilot's operation of the engine controls not with a mechanical malfunction or failure of the engine.
Although the pilot reported that he descended the airplane slightly above the published best glide speed after first locating the alternate airport, the recorded data indicated that he descended at an indicated airspeed far greater than the published best glide speed for the majority of the descent. If the pilot had slowed to and maintained the published best glide speed either at the time of the first abnormal indication or after first locating the alternate airport, it is likely that the airplane would have been able to reach the intended runway and land successfully.
Further, although the pilot reported that he deployed the parachute at 800 ft msl, it was actually deployed when the airplane was at 453 ft msl, or about 340 ft above ground level (agl), excluding the treetop heights. Although the successful deployment of the parachute has been demonstrated at less than 400 ft agl, the low-altitude deployment likely contributed to the severity of the accident by not allowing the parachute to fully deploy and adequately decelerate the airplane into an approximately level attitude.
Probable cause
The pilot’s improper decision to descend the airplane at an airspeed greater than the published best glide speed following an erroneous oil pressure indication, which resulted in an off-airport landing. Contributing to the erroneous oil pressure indication was the faulty oil pressure transducer. Contributing to the severity of the accident was the pilot’s late deployment of the ballistic parachute system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15LA062
- Event ID
- 20141201X83413
- Case number
- ERA15LA062
- 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, coordinates. 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: 465539af48a582f497778c6c437fa2cf02caee730efc985f43832f7acb2b899c; retrieved 2026-09-16T01:57:05.592Z.