Fog at Sunrise — Tampa North
VFR departure into unexpected low-level IMC, spatial disorientation, and the decision to deploy CAPS
The scenario
Departing Tampa North Aero Park Airport (X39), Tampa, FL — Runway 14, climbing out on a 141° heading at sunrise. Elevation 68 ft MSL. You are a Private pilot with 180 hours total, current and within currency limits. The SR20 is familiar; you have 45 hours in type.
It is 0630 local, early morning in late spring. The preflight weather briefing showed scattered-to-broken clouds at 1,500 ft AGL, visibility 5–7 statute miles, light wind from the southeast. The briefing noted 'VFR conditions expected to improve by 0800 local as surface heating increases.' You filed no flight plan; this is a local VFR flight to a nearby practice area and back — a 45-minute round trip.
You are cleared to depart Runway 14. The runway is visible; the taxiway is clear. You line up, advance the throttle, and begin the takeoff roll. The Continental IO-360-ES fuel-injected engine spools smoothly; the constant-speed prop is in climb mode. Airspeed is alive. At 50 KIAS you rotate; the SR20 lifts off cleanly. You are climbing at 96 KIAS (Vy, best rate of climb).
At 200 ft AGL, the horizon ahead begins to blur. At 300 ft AGL, the ground below is no longer distinct — it is a gray-brown smear. At 400 ft AGL, you have no horizon. The fog that the briefing said would 'improve by 0800' has not improved; it has thickened. You are in instrument meteorological conditions — fog, visibility less than 1 statute mile, no ground reference, no horizon. You are a VFR pilot in IMC.
Aircraft: Cirrus SR20, solo, within limits. Glass panel (Avidyne Perspective), constant-speed prop, fuel-injected Continental IO-360-ES, side yoke. The defining feature: CAPS — the whole-airframe parachute system. The POH makes CAPS the primary response to loss of control, an unrecoverable spin, and (at adequate altitude) engine failure with no safe landing site.
Pilot: you — Private, VFR-only, 180 hours total, 45 hours SR20. You did not request an IFR clearance because the briefing said VFR conditions. You did not declare a go-or-divert on the weather because it looked VFR at the airport. You are now 400 ft AGL in fog with no ground reference and no horizon.
- {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
- {'label': 'Runways', 'value': '14/32'}
- {'label': 'Elevation', 'value': '68 ft'}
- {'label': 'Aircraft', 'value': 'SR20'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we enter the decision tree — what do you know about spatial disorientation and loss of control in VFR-into-IMC scenarios? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA17LA113 (2017): A Cirrus SR-20 on an IFR flight plan departed VFR at sunrise and encountered unexpected low-level fog during initial climb. The pilot became spatially disoriented and lost control. The probable cause was the pilot's inadvertent encounter with instrument meteorological conditions (fog) during initial climb, which resulted in loss of control due to spatial disorientation. The pilot did not deploy CAPS. The aircraft impacted terrain.
NTSB CEN16WA074 (2016, FATAL): A Cirrus SR-20 on a personal cross-country flight from Birmingham, England to Osnabrück, Germany encountered instrument meteorological conditions and disappeared from radar over the North Sea. The investigation is under the jurisdiction of the Dutch Safety Board. The probable cause has not been determined, but the pattern is consistent with VFR flight into IMC and loss of control.
NTSB ERA11WA368 (2011, FATAL): A Cirrus SR20 on a personal flight from Cannes to Verona collided with mountainous terrain near Cairo Montenotte, Italy in instrument meteorological conditions. The investigation is under the jurisdiction of the Agenzia Nazionale per la Sicurezza del Volo of Italy. The probable cause has not been released, but the pattern is consistent with VFR flight into IMC and loss of control.
Regional precedent NTSB CHI91DCJ01 (1991, FATAL): A Cessna 172 flown by a non-instrument-rated pilot on a VFR cross-country flight encountered snow flurries and then heavy snow, resulting in loss of ground contact and spatial disorientation. The accident resulted from continued VFR flight into IMC despite a preflight weather briefing that warned of icing and possible IFR conditions. The pilot did not declare an emergency or request vectors.
Regional precedent NTSB ANC93LA040 (1993, FATAL): A Piper PA-22 flown by a VFR-restricted pilot departed in instrument meteorological conditions, encountered whiteout conditions, and crashed inverted after the pilot became spatially disoriented during a 180-degree turn maneuver. The accident resulted from the pilot's attempt to conduct visual flight during IMC and failure to maintain control during the emergency turn.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa North Aero Park (X39). X39 has its own accident history (dominant pattern: LOSS_OF_CONTROL_INFLIGHT 27.3%, LOSS_OF_CONTROL_GROUND 18.2%), but these specific NTSB events happened elsewhere. The scenario is localized to X39 to make the departure environment and off-field reality consequential for you as a student here.
The consistent thread across all these events: VFR flight into IMC at low altitude is almost always fatal without immediate action. The decision window is measured in seconds. Spatial disorientation can occur within 20–30 seconds of losing the horizon. The SR20's CAPS system is the primary response to loss of control in IMC at low altitude — not control inputs. The airplane is not certified for intentional spin recovery. Declare an emergency immediately. Request vectors. If you are in a stall/spin risk at low altitude with no recovery options, deploy CAPS at the highest altitude possible — above 1,000 ft AGL is survivable; below 500 ft AGL is marginal.
Key lesson — VFR flight into IMC at low altitude is a loss-of-control trap. Spatial disorientation can occur within seconds of losing the horizon. The SR20's CAPS system is the primary response — not control inputs. Declare an emergency immediately upon recognizing IMC. Request vectors from ATC. Do not attempt a 180-degree turn at low altitude in fog without outside help. If you are in a stall/spin risk at low altitude with no safe landing site, deploy CAPS at the highest altitude possible. Off Runway 14 at X39, the climb-out environment is medium development, low-density development, and wooded wetland — poor forced-landing options. CAPS is your best option.
Debrief — teaching points
Spatial disorientation can occur within 20–30 seconds of losing the horizon.
The inner ear (vestibular system) is exquisitely sensitive to acceleration and gravity, but it is easily fooled in the absence of visual reference. When you lose the horizon in fog or clouds, your inner ear tells you the airplane is turning, pitching, or rolling — even if the instruments show level flight. This conflict between vestibular input and instrument indication is spatial disorientation (vertigo). It can occur in a glass-panel airplane just as easily as in a steam-gauge panel. The only cure is to trust the instruments and ignore the inner ear. But at low altitude in fog, the decision window is so short that disorientation can lead to loss of control before you can recover.
The SR20 is not certified for intentional spin recovery by control inputs.
The SR20 POH makes CAPS (the whole-airframe parachute system) the primary response to loss of control and unrecoverable spin — not control inputs. The airplane's slippery wing and high wing loading make it unforgiving in a stall/spin scenario. If you find yourself in a stall or spin at low altitude in IMC with no recovery options, CAPS deployment is the correct response. Do not attempt to recover by control inputs; deploy CAPS.
CAPS is most effective above 1,000 ft AGL.
The SR20's CAPS system requires roughly 1,000 ft AGL for full deployment and descent arrest to a survivable rate. Below 500 ft AGL, the parachute may not fully deploy before ground impact. The decision to deploy CAPS should be made as early as possible — at the first sign of loss of control or unrecoverable situation at low altitude. Waiting until 100 ft AGL is waiting too long.
Declare an emergency immediately upon recognizing VFR-into-IMC at low altitude.
The moment you realize you are in IMC at low altitude with no ground reference, declare an emergency on 121.5 (or the nearest frequency) and request immediate vectors. ATC can see you on radar and can guide you to an airport or clear air. The decision window is measured in seconds — do not waste time trying to diagnose or recover on your own. Ask for help immediately.
A 180-degree turn back to the airport at low altitude in IMC is high-risk.
The textbook recovery from VFR-into-IMC is a 180-degree turn back to the airport. But at low altitude (below 500 ft AGL) in fog, a 180-degree turn is a high-risk maneuver. You are relying entirely on instruments, and the SR20's side yoke and slippery wing make energy management unforgiving. A steep turn, nose-up pitch, and airspeed decay can lead to a stall at low altitude — a fatal scenario. If you attempt a turn back to the airport, keep it shallow and trust the instruments. Better yet, declare an emergency and request vectors from ATC.
VFR-into-IMC at low altitude is almost always fatal without CAPS deployment.
The NTSB accidents ERA17LA113, CEN16WA074, and ERA11WA368 show that VFR flight into IMC at low altitude is almost always fatal without immediate action. The SR20's CAPS system is the primary response. The decision to deploy CAPS should be made early — at 400 ft AGL, not 100 ft AGL. Spatial disorientation and loss of control can occur within seconds. Declare an emergency, request vectors, and if you are in a stall/spin risk at low altitude with no safe landing site, deploy CAPS.
Built from the real accident record
Scenario built from NTSB ERA17LA113 (2017 SR20 VFR-into-IMC spatial disorientation on initial climb), CEN16WA074 (2016 SR20 IMC encounter), ERA11WA368 (2011 SR20 terrain collision in IMC), and regional precedents CHI91DCJ01, ANC93LA040, FTW89FA151, BFO90DID01 (all VFR-into-IMC loss-of-control accidents). Anonymized and localized to X39 (Tampa North Aero Park).
NTSB reports: ERA17LA113 · CEN16WA074 · ERA11WA368 · CHI91DCJ01 · ANC93LA040 · FTW89FA151 · BFO90DID01
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.A — Preflight Assessment · PA.III.A — Normal Takeoff and Climb · PA.VIII.A — Spatial Disorientation · PA.VIII.C — Loss of Control Recovery · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.103 · §91.155 · §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 SR20 scenarios · More scenarios at X39