FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA414 · Cirrus Design Corp SR22

23 Jul 2011 · Palm Bay, FL, United States

Cirrus Design Corp SR22 · Accident: loss of control in flight during an emergency descent

From Albert Whitted Airport (SPG) to Valkaria Airport (X59)

Report a problem

Event

NTSB case
ERA11FA414
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

Cirrus Design Corp SR22

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
N122HB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Albert Whitted Airport (SPG), St. Petersburg, FLTo Valkaria Airport (X59), Valkaria, FL
Aircraft age
Not recorded
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
Emergency descent
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 control in flight
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 oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The surviving passenger stated that the pilot flew the airplane on an uneventful 56-minute flight earlier on the day of the accident. According to data from the multifunction display, the oil pressure was in the normal green arc range (30 to 60 psi) during the entire flight. After landing, no maintenance or servicing was performed. Before takeoff for the accident flight, the pilot performed a walk-around inspection of the airplane, which would require, in part, a check of the oil quantity.

According to GPS and other recorded flight data, about 17 minutes after takeoff, the oil pressure decreased below the lower end of the normal operating range; at the time, the airplane was flying in an easterly direction about 10 nautical miles west of an airport with runways of more-than-adequate length for the pilot to divert. Rather than divert, the pilot continued toward the destination. Although the oil temperature remained in the normal operating range, the oil pressure continued to decrease. Both indications would have been available to the pilot either on the multifunction display or on the analog combination oil pressure/oil temperature gauge.

While the airplane continued toward the destination, the oil pressure decreased to 10 psi, and the pilot maintained the engine power setting at 2,400 rpm (the maximum setting is 2,700 rpm). About 46 minutes after takeoff, with the engine rpm still set at 2,400 rpm, the pilot declared an emergency and advised the controller that smoke was coming from the engine. Unable to fly to suggested airports, the pilot initiated an approach for a forced landing to a large open area containing east/west- and north/south-oriented paved roads.

Witnesses reported that the engine was sputtering and “coughing” but did not note smoke trailing the airplane. For the last 1 minute 12 seconds of flight, the engine rpm decreased from 2,400 to 1,700. While descending with the autopilot disengaged and at 74 knots indicated airspeed, the airplane banked 55 degrees to the right, stalled, pitched nose-down, and impacted the ground.

Examination of the wreckage revealed oil covering the bottom left side of the fuselage from the engine firewall to the tailcone, consistent with the crankcase being pressurized and blowing oil out of the air/oil separator. Examination of the engine revealed that the oil gauge rod and cap assembly had separated from the oil filler tube and was found near the engine and propeller impact crater. Neither the oil gauge rod and cap assembly nor the oil filler breather tube were impact damaged, suggesting that the assembly was improperly secured. Although the No. 4 cylinder piston was fractured and the fracture surfaces exhibited widely spaced crack propagation marks consistent with progressive crack growth under cyclic stresses, the cyclic load was at or above the yield strength of the material. Therefore, the No. 4 cylinder piston did not contribute to the loss of engine oil supply. Examination of the ignition, lubrication, air induction, and fuel injection systems did not note any discrepancies that contributed to the catastrophic failure of the engine.

The catastrophic failure of the engine was consistent with oil starvation due to the crankcase becoming pressurized because of an unsecured oil gauge rod and cap assembly. Postaccident examination of the pistons, piston rings, and crankshaft nose seal did not indicate other typical scenarios of crankcase pressurization. A previous NTSB accident investigation of a different airplane with the same engine model determined that an unsecured oil cap allowed the crankcase to become pressurized and the oil to be vented overboard, causing subsequent catastrophic failure of the engine due to oil starvation.

The pilot’s decision to continue the flight with decreasing or low oil pressure rather than land at a suitable airport nearby and his continued operation of the engine at a high rpm setting contradicted the emergency procedures section of the pilot operating handbook and Federal Aviation Administration-approved flight manual, which contributed to the catastrophic failure of the engine.

Although the airplane was equipped with an airframe parachute, an acquaintance of the pilot reported that the pilot would only use it in the event of a structural issue that rendered the airplane uncontrollable. Otherwise, if it were controllable, the pilot intended to hand-fly the airplane to landing. If the pilot had deployed the airframe parachute, he may have increased the likelihood of a successful emergency landing.

Probable cause

The pilot’s failure to maintain adequate airspeed while maneuvering for a forced landing, resulting in an inadvertent aerodynamic stall. Contributing to the accident were the pilot’s failure to secure the oil gauge rod and cap assembly before flight and his decision not to land immediately following loss of oil pressure, which resulted in the total loss of engine power due to oil starvation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA414
Event ID
20110723X80555
Case number
ERA11FA414
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: 38cceaf1a5bcf431796d24a5cb5348874a19af814005c2a4534e0f7261bf621a; retrieved 2026-09-13T21:36:50.777Z.