Friday, January 8, 2010

Snowing in Huntsville

At least according to Microsoft Flight Simulator it is. I decided to give up on the Mooney Bravo, switch back to the Skylane, and go ahead and start my long journey westward. First stop - Huntsville, Alabama.


Taking off from Dalton the weather looks great (better than it does looking out my window at least). No sign of any snow on the ground but we probably got less than an inch last night, so no big deal. In the picture above, you can see I-75 as it zig-zags through the gap in the ridge-line at Rocky Face.

As I crossed the larger mountains between Georgia and Alabama though it got cloudier and cloudier. My flight planned called for a 6,500 feet cruise altitude to clear all mountains comfortably, but that put me right in the clouds. Rather than climb (given that I was nearing my destination), I decided that once I was over the worst of the mountains, I'd dropped down to about 5,000 feet and try to get below the clouds. As I did, I found that it was snowing down there.
Yikes! This was a VFR flight plan (visual flight rules), which requires better visibility than this. I don't even know how to fly IFR (instrument flight rules) yet so that's no help. Hopefully closer to the ground and closer to the airport it will clear up enough for me to land. Otherwise, I suppose I have enough fuel to make it out of the storm and find an alternate airport.

Forgetting about the hills to the east of Huntsville, I continue to descend down to 2,500 feet at which point I looked down and saw the tops of trees not far below me, maybe 500 feet. I was flying over one of those ridges that's almost 2,000 feet above sea level. Good thing I didn't smack into a radio tower and instead was able to throttle up and climb back to 3,500 feet for more comfort but less visibility.

An IFR flight plan would have been nice, but at least I know VOR navigation. That got me to the airport (Madison Executive), where visibility was about 2-miles, not great but good enough to land. You can just barely see the runway and landing lights in the image above, at my 11:00 position. Or maybe you can't, but I could at full screen and with the light blinking.

Lining up would have been harder, but fortunately most of the roads in this area run north-south or east-west, not at angles like in Dalton, and I knew the runway ran straight north-south, so that helped with the turns.
On final approach I got too slow with full flaps deployed and set off the stall alarm. I was able to go full throttle for a few seconds though and hold the nose level or slightly downward to recover and continue my landing. The landing itself was a little choppy as you can see above, with my right rear landing gear touching down before the left. I made it down in one piece though, which is more than I can say for my last landing.

Anyway, here I am parked at Madison Executive Airport. Watching it snow.

Actual Death Experience in Chattanooga

Unlike my earlier near-death experience, I went all the way this time. I was doing more training flights with the Mooney, which I've decided I hate, and attempted to fly up to Chattanooga and land.

The weather wasn't bad, but the Mooney was bucking like a bronco, just pointing it's nose left-right, up-down, all over the place - just very hard to control. That's bad enough when you're trying to maintain level flight, but really a problem when you try to land.

I came in a little shallow but tried to make it over the buildings and houses short of the runway and failed. The Bravo was just misbehaving too badly for me to compensate given my experience level and I clipped a building just short of the runway - game over!

Unfortunately, I wasn't running the video recorder, and after a crash it kicks out and doesn't give you a chance to use replay, so there's not even a photo to commemorate my demise.

I think I'll switch back to the Skylane, or at least, my zombie will. It's not as fast but it flies like a comfortable old pair of shoes. (If shoes could fly, I mean).

Sunday, January 3, 2010

Still Flying in 2010

It's been a busy few days but everyone had a good Christmas and New Years. I decided to get in a little more Mooney Bravo practice before having to go back to work tomorrow. Here I am at about 4,000 feet over Dalton:

I'm still not sure if I like this plane or not. I definitely like the idea of going 200 knots, especially if I'm going to take longer and longer trips, and I like the turning visibility you get with a low wing. That is, when you're banking left or right and you look in the direction of the bank, you can actually see what you're turning towards. With high-wing planes like the Skyhawk and Skylane, all you see in a bank is the bottom of the wing.

On the other hand, the high-wing is nice when you're trying to look at the ground. In the Mooney at least the pilot sits slight forward of the wing, so you can look left and down and see what's under you, but visibility below is clearly better in the Cessnas. What they really need to invent is a plane with the wing at eye level and with windows above and below it. Yeah, that's it!

Anyway, Tom had mentioned in his comment to my last post about some volcanic activity in Puerto Rico that was causing visibility issues for air traffic. That comment was a few days ago, but I decided to check it out anyway, loading up a quick flight from San Juan Int'l in my trusty Skylane with real world weather turned on:
Nothing to report on takeoff. A little cloudy but other wise skies look blue. After gaining some altitude though the air below me got decidedly hazy:
I doubt FSX has a volcano simulator built into it but this may be it's effort to simulate the visibility data it's getting from its weather service. Hard to tell.

Anyway, back to comparing the Mooney to the Cessna. The main problem is that the Mooney is significantly harder to fly and harder to land. I've not crashed yet, but I've not had a really good landing either. Every one of my 5 landings in the Mooney have been nail-biters. I may rethink the switch and keep flying the Skylane a bit longer until I get more experienced.

Wednesday, December 30, 2009

Mooney, Mooney...

I'm working out a rough itinerary to take me westward, ultimately to California and back. Because some of the legs of this trip are likely to be longer than the flights I've made to date, I've decided to upgrade aircraft again, this time to the Mooney Bravo, a 200 knot sports car of a plane:


It's still a single piston engine, but it's supercharged and puts out 270 horse power, compared to 230 in the Skylane or 160 in the Skyhawk. It's also a low-wing design with retractable landing gear, so it's more aerodynamic. It's at least twice as fast as the Skyhawk I started with and a good 50% faster than the Skylane. It's probably going to be a little more challenging to fly, but hopefully I'm up to it.

For this plane, I'm going to try to learn proper procedures more so than I have been with the other planes. I want to handle the fuel mixture and other settings manually and learn how to keep track of manifold pressure and other data from instruments that tell you if the engine is running correctly or not. I had looked at a 2D view on the instrument panel and liked the design, but the 3D panel you see in the virtual cockpit (where you can look around), is uninspired. I'm a little spoiled from flying the Skylane which is a 3rd party add-on and looks a lot better than the default FSX planes.

This first test flight will just be a traffic pattern around the Dalton airport, with flaps at 10 degrees and gear down the whole way. I just want to see how she handles for takeoff and landing.

Flying the Bravo wasn't so bad, maybe a bit twitchier than the Cessna's. There's a trade-off for faster and more nimble in that you lose some stability. Landing the Bravo was harder than I thought it would be and my first landing was right on the corner of the runway, with at least one wheel in the grass.

You're going a little faster than in the Cessna's (75 knots versus about 60), and it's so responsive it's really easy to over-correct. I had intended a single flight but decided to touch-and-go and try another lap and another landing. Second landing was better:

This should be a good plane for my next big adventure. I'll be flying more around Dalton over the next week or two getting used to the handling before I set out for California. Tentatively I plan to fly to Huntsville, then down to New Orleans, Houston, San Antonio, El Paso and then work my way up past Meteor Crater, Arizona and on to the Grand Canyon. I'll probably stop by Vegas and then head to L.A. or maybe shoot up to Lake Tahoe, over to San Francisco and then work my way down the coast.

Saturday, December 26, 2009

Tile Proxy Test

Tried out a free download tonight. The program is called Tile Proxy and it runs in the background as FSX runs, acting as a Proxy Server and downloading image date from an on-line map provider (in my case, Yahoo Maps since Google apparently got wind of this and threatened to sue). Tile Proxy then converts that data to the format used by FSX and uploads it as you fly. It gives you something like the MegaScenery Earth visuals (see earlier posts), but at no charge. The drawback being that the imagery is not as good, it takes forever to load, and at least on my system, seems to reduce your frame rate making it more difficult to fly.

Once I got it installed and running I took off from Dalton Municipal and headed to town. On the way, I looked for and managed to find my parents house:
Unless you know exactly what to look for, this won't look like much, but trust me, it's down there. Next I flew over town and I think spotted the courthouse. On my way back towards the airport I spotted Heritage Point Park easily identifiable by its baseball fields arranged in circles of five:
I was going straight back to the airport but decided to check out Fort Mountain again. Here's some more Tile Proxy scenery of Murray County:

It's clearly better than the default FSX scenery, but unless I can get it to run more smoothly, I'm not sure it's going to be worth the effort. Anyway, I flew back over Fort Mountain. I was able to see the road leading up to the Fort area, but the resolution wasn't good enough to see much else:


After Fort Mountain I did decide to hang it up for the night and flew back to the airport and landed. The reduced frame rate made it pretty difficult. In fact, I almost stalled and repeated that Titusville Crash, but I reacted to the stall warning a lot faster this time, gunned the engine to full throttle and pointed the nose down (but not too much down because I wasn't more than 50 feet off the ground). That brought my airspeed up just enough that I could cut power again and complete the landing.

No final decision on this yet. I'll fly with it some more tomorrow and maybe try tweaking the settings a bit.

Milestones

Made another short flight this afternoon. This time I headed southeast and flew over Carter's Lake. As I was looping back northwest, I found myself at about 3,000 feet amongst mountains that weren't much lower than that. Up ahead, I spotted the mountain just to the south of Fort Mountain with its large TV antenna tower. I decided I need to buzz it!

As you can see, I'm not much higher than the trees on top of the mountain and lower than the top of the tower itself. Just call me Maverick.

Anyway, once past the tower, I banked back to the west to find the Dalton airport and land. I also cut power and started dropping altitude as I flew back over the valley floor and out of the mountains.

On my first landing attempt I turned to final approach too soon and was too high, probably 500 feet up as I crossed the end of the runway. I aborted, powered up and turned around for another pass. The second attempt was perfect, right on the numbers:

By "on the numbers", I mean I landed on the runway number "14" painted at the very end of the runway, rather than flying over that and landing somewhere further down the runway as I've been doing lately.

After logging this flight in, I realized that was my fiftieth successful landing. I also added up my flight time and realized I've flown over 25 hours total. Cool!

Fort Mountain Flyover

Needed to fly some today but didn't feel like more touch-and-go around Dalton and not ready to do another long distance trip yet, so I decided to fly over Fort Mountain and have a look. It's only about 20 miles from the Dalton Airport, so not a long flight. Here it is at my 11:00 with some clouds above it:
As I got closer I reduced power and dropped down so I could get a closer look. It definitely looks like a good place for a fort, but FSX doesn't have anything up there to look at.
I continued to descend and flew around the mountain and then back to Dalton. Landing was looking good until the end when I started over-correcting with theses sensitive controls, but I finally managed to get down on the runway and not too rough either. Also, no further problems with unexpected roll-overs, but we'll keep monitoring that.