Pushing the limits - An Inadvertent IMC Story

Flightplan: VFR Ardmore (NZAR) to Taumarunui (NZTM).pln (2.1 KB)

Today I had some time to kill, so thought I’d take my favorite light twin, the Blackbird C310R on a local New Zealand flight to visit a few airfields I have fond memories of from my VFR hour building days.

The route I had planned was NZAR - NZRA - NZTT - NZTM, 112nm point to point, which shouldn’t have taken more than an hour in the 310. I loaded up at Ardmore with real world weather enabled, and whilst the skies were grey, I didn’t give it too much thought as the trip south certainly looked certainly looked do-able from ground level.

The first leg to Raglan was uneventful, other than 20 something knots of westerly winds bouncing me around as it ricocheted off the hilly terrain below. I made a full stop landing on Raglan’s runway 23, backtracked- grabbed a coffee, then lined up for a full length departure.

As I turned south again, I realised my mistake in not checking the weather forecast. A wall of rain lined the horizon east to west, and I decided to punch through it, hoping it was just a frontal shower band and would be clear on the other side.

This is where things became dicey. I become enveloped in IMC, and despite engaging autopilot to level the aircraft and attempt to maintain situational awareness, I found myself caught in updrafts that carried me from 3000 feet up to 6000 feet.

Of course the decision to continue would be a death sentence in the real world, but seeing as the simulated environment allows for such flying without consequence, I continued to push on towards my destination, switching to the terrain map on my GNS unit to nervously monitor my terrain clearance with zero reference to the ground. (Please never try this for real!)

Approaching Taumarunui, which is very much a VFR only airfield, I momentarily broke out the cloud only to see rising terrain all around the aircraft. It was going to be impossible to make a safe approach to land, so I bugged out, and following the valleys course, applied full power and commenced a climb back up to 6000 feet.

The nearest airfield function on the GNS750 showed me Taupo (NZAP) was 40 miles away, so I set heading, knowing that I could at least get down to around 1800 feet over the large adjacent lake to pick up visual reference with it’s shoreline, and then follow that to the runway.

Visibility on the ATIS was down to 3nm, but thankfully the plan worked, and the runway 35 lights came into view as I used the GPS to line myself up on an approach course.

I think I’ll wait for the weather to clear before re-flying this route in clearer conditions! What was meant to be a relaxing sim session turned into a rather stressful event :face_with_spiral_eyes:

PS- There’s been a lot of chat in another topic about the 310 flaps being too draggy on landing. The 310 has split type flaps as opposed to fowler type flaps which function almost exclusively as drag generators when deployed. It marvels me at how immersive flying the 310 is on a desktop setup, and takes me right back to the fond memories of flying in IRL. Blackbird have done an outstanding job recreating the experience!

10 Likes

Nice story and shots. Reminds me of when I got lost over the Irish sea … in a storm … in a Toprudder 103 solo

Scary Weather - YouTube

1 Like

I’ve been exploring the South Island recently, same situation. Didn’t bother with a forecast, got stuck in rain. Decided to try climbing from 9000 to 12000 to see if I could get above the cloudbank. It was a very slow autopilot VS climb for my PA44 Seminole. Or maybe I missed something. I don’t exactly know what I’m doing yet when it comes to setting throttle, prop, and fuel mixtures manually for various stages of flight. And I also don’t like using ‘automixture’ because darn it, I have a throttle quadrant and I’m not afraid to use it!

It’s funny how the various checklists will simply state ‘Cruise: set mixture, set propellor’ … okay, set them to what? Am I supposed to know? Well, I don’t. I have about an hour to kill with MSFS, not several months of ground school.

But back to the story, while I’m climbing, I see a break in the clouds to my left (port?) side. So I move my heading bug in that direction. I didn’t realise my slow climb was also very close to the stall point. As soon as the autopilot initiated the turn and the bank started, my left wing stalled and I dropped out of the sky like a brick! My first actual and unintentional spinning stall! At that point I really wish I knew what I was doing. Unfortunately my brief attempts to recover were unsuccessful, and I learned my lesson to check the weather, and to respect the boundaries of the ‘lower and slower’ GA aircraft I generally prefer to fly.

1 Like

What a difference a day makes. The skies have cleared here now, and I was easily able to refly the route from Ardmore to Tauramanui in an aeroclub C172, taking in all the scenery I missed out on yesterday.

It’s amazing how the dynamic nature of real world weather can affect ones gameplay experience so much.

3 Likes

At least you didn’t have to deal with spatial disorientation :wink:

1 Like

The 310 is a nice IFR platform; I’ve done a lot of good old /A (radio nav only) Vatsim flights in it in low IMC. Fun stuff.

2 Likes

Oh, you been flying the 310 IRL? Nice!

Thanks for the story!

So you say the 310 flaps generate drag, but not so much lift?
I just did a few circuits. And yes, that is my experience compared to the 172: Almost no nose-up when extending flaps. With the C172 I have to work to hold it down.

For the C310 I liked to advice to deploy gear and first notch of flaps at the same time. Almost no effect on pitch, just starts slowing down.

1 Like

Oh, I just recognized your name when I went back a YouTube video I saved. :wink:

1 Like