Anomaly on Climb — Control and Energy Management in the SR22
An engine indication anomaly during initial climb triggers spatial disorientation and a control challenge. Decision-making under pressure in a high-performance airplane.
The scenario
Departing Tampa North Aero Park Airport (X39), Tampa, FL — Runway 14, a touch-and-go landing followed by initial climb. Elevation 68 ft MSL. The runway is short (3,541 ft) and the off-field environment in all directions is poor: medium development, low-density development, and wooded wetland. There is no open field for an emergency landing.
It is a clear morning in late spring: OAT 24°C, dew point 16°C, altimeter 29.95, winds calm to light. Scattered clouds at 3,500 ft. Visibility 10 SM. VFR conditions, unremarkable weather. You are on a personal cross-country flight, solo, full fuel, within limits.
You execute a touch-and-go landing on Runway 14, landing smoothly and applying power for the go-around. As you rotate and begin the initial climb, passing through 200 ft AGL, the Perspective glass panel displays an engine manifold air pressure (MAP) warning. The engine is running, but the indication is anomalous — the MAP is showing higher than normal for the power setting you have selected. The warning is unexpected and you have not seen it before in this airplane.
Aircraft: Cirrus SR22, Continental IO-550-N (310 hp), constant-speed prop, fuel selector LEFT (you have been flying on the left tank since departure). The airplane was maintained and last flown three days ago; nothing was written up. You are at 200 ft AGL, climbing at 101 KIAS (Vy), heading 141° (the reciprocal of Runway 32), and the engine is running.
Pilot: You — a Commercial pilot with an Instrument rating, roughly 1,200 hours total, 400 hours in the SR22. You are current and proficient. You have never seen a MAP anomaly in this airplane. The warning is unexpected and you are not immediately sure what it means or what to do about it.
- {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
- {'label': 'Runways', 'value': '14/32'}
- {'label': 'Elevation', 'value': '68 ft'}
- {'label': 'Aircraft', 'value': 'SR22'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you know about the SR22's engine instruments, CAPS, and loss-of-control recovery? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA23FA258 (2023): A Cirrus SR22T experienced an engine manifold air pressure exceedance during initial climb after a touch-and-go landing. The pilots received a crew alerting system warning and lost control of the aircraft. They deployed the ballistic recovery parachute at an altitude too low for effective deployment (roughly 400 ft AGL). The probable cause was the pilots' failure to maintain aircraft control following the anomalous engine indication. The accident was fatal.
The pilots in ERA23FA258 did not immediately return to the airport when the MAP anomaly appeared. Instead, they continued the climb and attempted to diagnose the problem in flight. At low altitude with divided attention, they lost control. The parachute deployment was late and the altitude was insufficient for effective recovery.
NTSB CEN20LA379 (2020): A Cirrus SR22 on a personal flight with three passengers encountered instrument meteorological conditions at night. The non-instrument-rated pilot continued flight, resulting in spatial disorientation and loss of control. The accident was fatal. The probable cause was the pilot's continued flight into dark night instrument meteorological conditions without adequate training or recency.
NTSB WPR20FA019 (2019): A Cirrus SR22 stalled during landing approach while maneuvering in the traffic pattern at low airspeed. The pilot exceeded the critical angle of attack while maneuvering for landing. The accident was fatal. The probable cause was the pilot's exceedance of the airplane's critical angle of attack.
The regional precedents (CHI91DCJ01, ANC93LA040, FTW89FA151) all involved VFR pilots encountering deteriorating weather or unexpected conditions and continuing flight despite warning signs. Spatial disorientation developed rapidly, and the pilots did not make early return/divert decisions.
Tampa North Aero Park Airport (X39) is a non-towered field with poor off-field environment in all directions: medium development, low-density development, and wooded wetland. There is no open field for an emergency landing. An engine failure on the Runway 14 departure leaves no safe alternate landing surface. The only option is a return to X39 or a CAPS deployment.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa North Aero Park (X39). This scenario is localized to X39 to make the off-field environment real and consequential for you as a student here. The decision to return immediately when an anomaly appears is not optional — it is the only safe choice at this field.
Key lesson — An anomalous engine indication at low altitude during initial climb is not a problem to investigate in the air — it is a problem to return to the airport and have a mechanic investigate on the ground. The SR22 is a high-performance airplane with high energy and fast response; divided attention at 200–500 ft AGL can lead to spatial disorientation and loss of control within seconds. Early decision-making — return to the airport immediately — is the entire lesson. CAPS is a recovery system, not a primary option; use it when loss of control is unrecoverable and altitude is sufficient for effective deployment. At Tampa North Aero Park (X39), the off-field environment is poor in all directions; there is no alternate landing surface. The airport is your only option.
Debrief — teaching points
An anomalous engine indication at low altitude is a return-to-airport event, not an investigate-in-flight event.
The SR22's Continental IO-550-N is a high-performance, fuel-injected engine with a constant-speed prop and a sophisticated fuel control system. A MAP exceedance or other anomalous engine indication during initial climb suggests a fuel control unit issue, prop governor malfunction, or induction system problem — none of which should be diagnosed in the air at 200 ft AGL. The correct response is immediate return to the airport and a maintenance inspection on the ground. Divided attention at low altitude is dangerous; the decision to return must be made immediately, not after investigation.
Spatial disorientation in a high-performance airplane develops rapidly at low altitude.
The SR22 is a fast, responsive airplane. When attention is divided — between an anomalous engine indication, the flight path, and the instruments — spatial disorientation can develop within seconds. At 200–500 ft AGL, you have no margin for error. The real accident NTSB ERA23FA258 involved pilots who lost control during initial climb after a MAP anomaly. They did not immediately return to the airport; they continued the climb and attempted to diagnose the problem. Spatial disorientation followed, and the CAPS deployment was too late. Recognize divided attention early and refocus on the flight path, or declare a precautionary return immediately.
CAPS is a recovery system, not a primary option — it requires altitude to be effective.
The SR22's ballistic recovery parachute (CAPS) is the POH's primary response to loss of control, unrecoverable spin, and engine failure without a safe landing option. However, CAPS requires altitude to be effective. Deployment at 400 ft AGL is marginal; deployment at 350 ft AGL is near the limit of survivability; deployment below 300 ft AGL is unlikely to provide effective recovery. The goal is to avoid loss of control in the first place by making early decisions: return to the airport when an anomaly appears, do not investigate in the air, and do not allow divided attention to develop spatial disorientation. CAPS is the last resort, not the first response.
The SR22 is a high-energy airplane — energy management is critical at low altitude.
The SR22 climbs fast, floats on landing, and builds airspeed quickly in a descent. At low altitude, this high energy can work against you if you are not actively managing the flight path. During a go-around or initial climb, maintain a stable pitch attitude and airspeed. Do not allow the airplane to climb steeply or to develop an unusual attitude. If an anomaly appears, reduce power and establish a descent back to the airport at best glide speed (88 KIAS). The high energy of the SR22 means that recovery from an unusual attitude at low altitude is difficult; prevention is the only safe strategy.
At Tampa North Aero Park (X39), the off-field environment is poor in all directions — there is no alternate landing surface.
X39 is surrounded by medium development, low-density development, and wooded wetland. There is no open field, no road, no park. An engine failure on the Runway 14 departure leaves no safe alternate landing surface. The only option is a return to X39 or a CAPS deployment. This geographic reality makes early decision-making non-negotiable: if an anomaly appears at 200 ft AGL on the Runway 14 departure, you must return to the airport immediately. There is no 'glide to an alternate field' option. The airport is your only safety net.
Built from the real accident record
Scenario built from NTSB ERA23FA258 (2023 SR22T engine MAP exceedance, loss of control, low-altitude CAPS deployment), CEN20LA379 (2020 SR22 spatial disorientation / IMC), WPR20FA019 (2019 SR22 stall on approach), and regional precedents CHI91DCJ01, ANC93LA040, FTW89FA151 (VFR-into-IMC spatial disorientation). Real events occurred at other airports — NOT at Tampa North Aero Park (X39).
NTSB reports: ERA23FA258 · CEN20LA379 · CEN20LA336 · WPR20FA019 · CHI91DCJ01 · ANC93LA040 · FTW89FA151
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.A — Preflight Inspection · PA.II.B — Engine Starting / Systems Preflight · PA.III.A — Normal Takeoff and Climb · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.103 · §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 X39