Oil Temperature Spike on Approach
Engine failure in a high-performance single over dense Tampa development — CAPS or a forced landing in an urban environment
The scenario
Approaching Tampa International Airport (KTPA), Runway 19R, on a descent from 3,500 ft MSL. Field elevation 26 ft MSL. You are 12 nm south of the field, descending through 2,800 ft MSL on a 002° heading, cleared to 2,000 ft MSL by Tampa Approach. The Cirrus SR22 is performing normally — fuel selector on RIGHT tank (left tank depleted during cruise), mixture at cruise lean, constant-speed prop in cruise configuration.
It is a hot, hazy Florida afternoon: OAT 31°C, dew point 20°C, altimeter 29.89. Visibility 6 SM in haze. Scattered clouds at 3,500 ft, no precipitation. The approach is routine — you have flown into KTPA twice before. Runway 19R is 11,002 ft of concrete, the longest at the field. The off-field environment is dense development — residential and commercial — in all directions around the airport.
At 2,200 ft MSL, 8 nm from the field, you notice the oil temperature gauge rising. It is now 220°F (normal is 180–220°F, yellow arc begins at 220°F). You are still descending, still on approach. The engine is running smoothly; no roughness, no vibration, no other anomaly. Just the oil temperature climbing. You have not yet contacted Tampa Approach to request vectors to the final approach course.
Aircraft: Cirrus SR22, solo, 65 gallons usable fuel (right tank selected, approximately 20 gallons remaining), within weight and balance limits. The airplane was last serviced 30 hours ago; the oil was changed at that time. Nothing was written up; the airplane was airworthy at departure.
Pilot: you — a Commercial pilot, current, roughly 800 hours total, 200 hours in type (SR22). You are familiar with the SR22's systems and the Perspective glass panel. You understand that the SR22 has a ballistic parachute (CAPS) as a backup for unrecoverable situations, but you have never deployed it and have no intention of doing so on a routine approach.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'SR22'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we enter the decision tree — what do you know about the SR22's engine, fuel system, and emergency systems? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN21LA057 (2020): A Cirrus SR22 on approach experienced erratic high oil temperature indications. The pilot, attempting to diagnose the problem, improperly adjusted the engine mixture control in response. This adjustment resulted in total loss of engine power. The pilot deployed the ballistic parachute (CAPS) and made a survivable landing. The probable cause was the pilot's improper adjustment of the engine mixture control. A contributing factor was a disconnected oil temperature connector that had been damaged during recent maintenance, providing false readings that prompted the pilot's incorrect response.
NTSB ERA20LA064 (2020): A Cirrus SR22 on a cross-country flight experienced total engine power loss due to a camshaft fatigue failure caused by a manufacturing defect. The pilot deployed CAPS and made a survivable landing in trees. The engine failure was catastrophic and unpreventable; CAPS was the correct response.
NTSB CEN20LA020 (2019): A Cirrus SR22 experienced total engine power loss due to detonation caused by improper magneto timing and a rich fuel mixture. The pilot deployed the ballistic recovery parachute and made a forced landing in a field. The combination of maintenance error (magneto timing) and improper mixture management led to detonation and total power loss.
NTSB CEN19LA320 (2019): A Cirrus SR22 experienced total engine power loss due to separation of the No. 1 connecting rod caused by piston pin bushing migration. The accident resulted from the mechanic's failure to follow manufacturer guidance during the most recent oil change, which would have detected bushing material in the oil. Post-maintenance inspection is critical.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa International Airport. KTPA has its own accident history (see field dominant patterns: forced landings, loss of control, gear-up landings, wire strikes), but these specific SR22 engine-failure events happened elsewhere. The scenario is localized to KTPA to make the off-field environment real and consequential: dense development in all directions, no open fields, no clear roads — an engine failure on approach to KTPA means a forced landing in an urban environment, not a field landing.
The consistent thread across all these events: engine failures in the SR22 are often preceded by warning signs (oil temperature anomalies, rough running, vibration) that the pilot must recognize and respond to correctly. Improper mixture adjustment, failure to follow maintenance procedures, and delayed emergency declarations are the human factors that turn a manageable situation into a catastrophic one. CAPS is a backup, not a substitute for early recognition and correct decision-making.
Key lesson — On approach to KTPA, an engine anomaly (oil temperature spike) is a critical warning. Declare an emergency immediately, request priority vectors to the nearest suitable runway, and do not attempt to diagnose or fix the problem in flight — let the ground handle it. If total power loss occurs, best glide is 88 KIAS; Runway 19R is 11,002 ft long and is reachable from most approach altitudes. If you cannot reach the runway, CAPS is the correct response over dense development. Do not attempt to land in a residential neighborhood if the parachute is available.
Debrief — teaching points
Oil temperature anomalies on approach are engine warnings — not minor gauge glitches.
The SR22's Continental IO-550-N is a high-performance, fuel-injected engine. Oil temperature is a critical parameter. A rising oil temperature on approach — especially one that does not respond to mixture adjustment or power reduction — indicates a serious problem: fuel starvation, improper fuel flow, mechanical failure, or a sensor malfunction. Do not continue the approach hoping it will resolve. Declare an emergency, request priority handling, and get the airplane on the ground. NTSB CEN21LA057 shows that a disconnected oil temperature sensor (damaged during maintenance) provided false readings that led the pilot to make incorrect mixture adjustments, which caused total power loss. Always verify that recent maintenance did not disturb engine instrumentation.
The SR22 fuel selector is LEFT / RIGHT — not BOTH. You must actively manage which tank is feeding the engine.
Unlike some other aircraft, the SR22 has no BOTH position on the fuel selector. You must choose LEFT or RIGHT. On a long flight, you switch tanks at planned intervals to balance fuel consumption. On approach, you should be on the tank with the most fuel remaining. If you are uncertain which tank is selected or how much fuel is in each tank, verify the selector position and check the fuel quantity indicators before descent. Fuel starvation from an improperly selected tank is a classic forced-landing scenario — see NTSB WPR24LA167, GAA19CA534, WPR12LA023. Verify fuel selector position and quantity before every descent.
On approach, enrich the mixture — do not lean it.
As you descend from cruise altitude, the mixture should be enriched to ensure adequate fuel flow and engine cooling. Leaning the mixture on descent is incorrect and can cause detonation, rough running, and overheating. The SR22 POH calls for mixture enrichment during descent. If you are unsure of the correct mixture position, reference the POH or ask ATC for a delay while you sort it out. Do not experiment with mixture adjustments on approach.
Best glide speed for the SR22 is 88 KIAS — establish it immediately if total power is lost.
If the engine fails completely, lower the nose to 88 KIAS immediately. This speed maximizes glide distance and gives you the best chance of reaching a runway or a suitable landing area. At 88 KIAS, the SR22 descends at roughly 500 fpm, giving you roughly 2 minutes of flight time from 1,200 ft AGL. That is enough time to reach Runway 19R from 3 nm out. Do not attempt to stretch the glide by flying slower — that reduces glide distance. Fly 88 KIAS and let the airplane do the work.
KTPA is surrounded by dense development — an engine failure on approach means a forced landing in an urban environment.
The off-field environment around KTPA is dense residential and commercial development in all directions. There are no open fields, no clear roads, no parks. An engine failure on approach to KTPA means you are landing in a neighborhood, on a street, or in trees — not in a field. This is not a worst-case scenario; it is the geographic reality. Runway 19R is 11,002 ft long — the longest at the field. If you can reach the runway, do so. If you cannot, CAPS is the correct response over dense development. Do not attempt a hard landing in a residential neighborhood if the parachute is available.
Declare an emergency early — do not wait for total power loss.
If an engine anomaly develops on approach (oil temperature spike, rough running, vibration, power loss), declare an emergency with ATC immediately. Do not wait to see if it resolves. ATC will provide priority vectors, priority landing clearance, and emergency services standing by. Early declaration buys you time, altitude, and options. Late declaration (after total power loss) leaves you with a forced landing and no margin. NTSB CEN21LA057 shows that early recognition and emergency declaration would have prevented the total power loss — the pilot had time to land safely if the emergency had been declared when the oil temperature first spiked.
Built from the real accident record
Scenario built from NTSB CEN21LA057 (2020 SR22 oil temperature anomaly / improper mixture adjustment / total power loss / CAPS deployment), ERA20LA064 (2020 SR22 camshaft fatigue / total power loss / CAPS), CEN20LA020 (2019 SR22 detonation / total power loss), and CEN19LA320 (2019 SR22 connecting rod failure). Localized to KTPA with off-field environment precedents WPR24LA167, GAA19CA534, WPR12LA023 (fuel starvation forced landings in urban/marginal terrain).
NTSB reports: CEN21LA057 · ERA20LA064 · CEN20LA020 · CEN19LA320 · WPR24LA167 · GAA19CA534 · WPR12LA023
ACS tasks: PA.V.A — Engine Failure During Takeoff · PA.V.B — Engine Failure During Climb · PA.V.C — Engine Failure During Cruise · PA.IX.C — Emergency Approach and Landing · PA.I.F — Weather Information · PA.II.B — Engine Starting / Systems Preflight
Relevant FARs: §91.3 · §91.13 · §91.185
Step through the full decision tree, make the calls, and see where each choice leads — then debrief it with your CFI.
Open the interactive scenario →All sample scenarios · More Cirrus SR22 scenarios · More scenarios at KTPA