Friday, December 25, 2009

Near Death Experience in Chattanooga

So I decided to fly around some more with the new Saitek flight controls. I did another pattern flight around Dalton earlier but then decided to fly up to Chattanooga and back. The flight up was uneventful and landing was pretty good. The main problem now is my chair rolling around while I try to push the rudder pedals. I definitely need to figure out some other kind of chair for flying.

Anyway, on take-off from Chattanooga I went to full power, accelerated and started to climb. Less than 500 feet up, I was climbing and with an increasing climb rate, so I felt like it was safe to retract the flaps.

As the flaps came back to fully retracted though, the plane rolled suddenly to the left. I jerked the yoke back to the right which had some effect but then the plane rolled even more dramatically to the left, all the way on it's side and started diving towards the airport (since wings don't lift too well when they are perpendicular to the ground).

In this cockpit view you can see I'm sideways, and if you zoom in you can see my altimeter is reading 1,000 feet, which is less than 300 feet up in the air since the runway is at 7-something.

Unbelievably, I managed to level off and pull up, probably about a hundred feet off the deck and start to climb again. Once I got her leveled, she didn't misbehave any more and the flight back to Dalton went fine. Probably one of my best landings in fact:

Not sure what to make of that. Was it an FSX glitch? An issue with the add-on (non-Microsoft) plane I was flying? An erroneous control input from the new flight yoke? Or do some planes suddenly go into a roll like that when flaps are retracted?

I replayed it several times and couldn't figure out anything I had done differently from prior takeoffs. I also Googled looking for answers but couldn't find anything.

Best guess is an issue with the Saitek yoke, since that's the only thing that's changed with my setup as of today, but I'm still not sure about it. I'll add an update if I figure this out, but for now I think I'm done flying for the evening.

(UPDATE: Still working on this, but in FSX I was checking the settings and saw that the toe brakes on the rudder pedals were set to control the X and Y axis, same as the yoke. Perhaps during the climb I pressed the left toe brake in error, sending me into a roll. I've reconfigured those to the brake function, so we'll keep flying and see if this happens again)

Dad Scores Big for Christmas

Wow! Everyone had a good Christmas morning, including yours truly. I got a Saitek Pro Flight Yoke and Rudder Peddle system - check it out:

No more clumsy cheap joystick for me. Hooking everything up was pretty easy. The yoke plugs into an open USB port and then everything else plugs into the yoke. Windows recognized them immediately although there's also software that comes with them so you can program different profiles for different games.
Flying with them was trickier than I thought though. Everything's more sensitive that my old joystick, so on my first landing attempt I was over-correcting to the point I thought I'd probably crash. I finally managed to get over the runway though and level the wings enough to land.

On my second attempt, I restrained myself and made smaller adjustments, which worked a lot better. That landing was much smoother:
I've still got to experiment with the settings before I get really comfortable with this, but I know I'm going to love them. The rudder peddles make taxiing a lot easier (as long as you don't over-steer), and are especially helpful on take-off when you're trying to steer the plane down the runway without banking the wings before liftoff. The yoke is a lot more precise than the joystick and has more buttons on it. The throttle quadrant is also nice for throttle control but the prop and fuel mixture controls didn't seem to work. I think I've got to reverse them or something but I'll experiment with that and see.

More updates to follow...

Thursday, December 24, 2009

Rainy Homecoming

Barely squeezed in enough time today to make that final flight from Atlanta back to Dalton. Took off with overcast skies and headed north. About mid-way the weather seemed like it was going to clear up, but then got even worse and started to rain:
Not sure how well you can see the streaks of rain in this image, but handling got choppier and visibility got pretty poor. It rained all the way into the Dalton airport, so my landing wasn't the best I've had, but it wasn't that bad either. I think there must have been a little bit of a cross-wind, because it was hard to stay lined up on the runway.

This is the tower view with the rain coming down as I clear the trees. I made it down OK and taxied off the runway. Home at last! Merry Christmas!

Wednesday, December 23, 2009

Epic Dynasty

Hmmm, wonder if I should get one of these for myself for Christmas:

This is an Epic Dynasty, cost over a million in real life, but only $12.50 on sale for Christmas. It's an all carbon fiber airframe so very light, very aerodynamic and built for speed. It's attached to a 1,200 horse power turbo-prop engine (basically a jet engine turbine with its drive shaft attached to the prop). It's also got a state-of-the-art glass cockpit with GPS, etc.

For more info in the real plane, check out www.epicaircraft.com. This baby will do almost 300 knots, so about twice as fast as the Skylane. It can also cruise a lot higher, like 31,000 feet. Not sure I'm ready for it, but it sure looks nice, even with a partially buried big blue blimp in the background.

Speaking of which, I've checked Google Earth and I'm totally unable to find a big blue blimp anywhere around Charlie Brown Airport. I'm really not sure what to make of it.

(UPDATE: Go to Google Earth at 33 46'56.45"N, 84 31'12.52"W and then use the history function (little watch face button that brings up a time slider) and back the date up to April 29, 2002. In that image, there's a blimp parked (docked?) just north of the airport, although it's not blue, and presumably the whole thing is above ground. I suppose Goodyear, MetLife, etc. use Charlie Brown to park their blimps before and after Falcon games or something)

Merry Christmas Charlie Brown

Heading back to Georgia this afternoon. Took off from Gainesville with the real weather still nice. Nothing but blue skies:

I climbed out heading north and got up to 12,000 feet, at which point I could see the Atlantic Ocean off to my right and the Gulf of Mexico off to the left. Pretty neat, but screenshots don't do it justice since you're just looking at a blue line on the horizon.

The engine didn't sound right at that altitude so I became concerned that there were adjustments I should make for the thin air (even though I had the fuel mixture on auto-adjust). I decided to drop back down to about 8,000 feet. Once I got the airplane trimmed out again and everything seemed to be running smoothly, I climbed into the back seat to take a break:

Again, this was done by moving my virtual head position back, and down a bit, until it seemed to be in about the right place for a back-seat passenger. Kind of weird with no pilot up there though.

I also experimented with opening the doors in flight which worked fine (in spite of the 100+ mph wind blowing against them). The open doors also seemed to have zero effect on flight performance.

Enough screwing around, we're getting close to Atlanta now. I still have air traffic turned down to minimum, but even then Atlanta is kind of busy. The ATC at Hartsfield called me to verify that I had seen another plane to my 4:00 a few hundred feet up and 4 miles off. I had not seen it at all, but found it once they pointed it out. It was a large Airbus passenger plane apparently heading into Macon. It's amazing how you can pass something that big and that close and not even notice it. Of course, with a high wing, visibility for what's above you isn't so great.

I started my descent and was looking around when I spotted this strange building south of Atlanta:

Looks like a grand stand with an airport behind it. As best I can tell (from a post flight check in Google Earth) this is probably supposed to be Atlanta Motor Speedway.

Further north I spotted Hartsfield and flew around it to the south and west. I've been using their VOR frequency to find Atlanta, but I'll be landing at Fulton County (Charlie Brown) Airport to the west of town.

Here's Hartsfield with some of the Atlanta skyline in the background:

There was a 737 taking off as I flew past but I didn't manage to get a good picture of that.

Charlie Brown, named after an Atlanta politician some time ago and not the Peanuts character, is about 10 miles NNW of Hartsfield. Finding it was not difficult and the tower instructed me to enter the pattern to the right and downwind to line up on runway 14.

I managed the pattern entry without a problem, but then became rather confused when I spotted a big blue half-a-blimp sticking out of the ground on the north side of the airfield:


Not sure what to make of that. I was so bothered by it though that I completely forgot that the airport was not at zero elevation like the coastal airports I've been used to. You generally fly the pattern at about 1,000 feet, but the altimeter is set at sea level, not ground level, and Charlie Brown is at 844 feet. As I got down to below 1,500 feet I realized something was wrong, but I was probably only a couple hundred feet off the ground before I figured out what I had done, gunned the engine, and began my 180 turn back toward the runway.



I then managed to climb too high and make a poor turn which put me at a rather awkward altitude and angle to land.

You can see the white lights mean I'm too high and I'm obviously not lined up. I could have aborted and flown around again, but I decided to go for it.

I angled hard left and pointed the nose back towards the ground. As I got closer, I angled hard right to get lined back up. I'm still too high, but my line is looking better:

More flaps, less power, keep the nose pointed down and level the wings. Pretty soon I was over the runway, still pretty high but it's a long runway and I had manage to get lined up correctly.

I just kept the nose down until the runway looked close enough to land on and then started nosing up. I probably touched down about the middle of the runway, but like I said, it's a long runway and my Skylane doesn't need that much room to stop.

You can see in this last image that I'm lined up perfectly. In spite of my altitude screw-up, I manged to pull of a nice landing to end the day.

I'm going to take a break now and then fly back to Dalton tomorrow (Christmas Eve) so I'll be home for Christmas.

MegaScenery Disney

Time is running out if I'm going to get back to Dalton by tomorrow night, so while I did go ahead with my planned Disney flyover (take 2, with MegaScenery installed), I opted not to fly back to Tampa, but to continue northward after.

Took off from Tampa using real weather, which was nice for a change, mostly blue sky with a gentle east to west wind. Flew towards Orlando using the Orlando VOR to find Disney (it's about 15-20 miles southwest of the airport). About 10 miles out I started spotting the landmarks and angled east to fly over Epcot first:



Epcot looks better than before - at least it's not out in a field anymore. This MegaScenery looks great for general landscape at anything above say 3,000 feet, but for specific landmarks where you need to get down low (1,000 feet or so), it's not so hot. At this low altitude, the scenery looks flat and photographic (which it is), and the 3D objects don't line up just right.

The Magic Kingdom is even worse:
I mean, at least it's not two buildings in a forest anymore, but look how far off the 3D space mountain is from the MegaScenery image!

So that was interesting, but a bit disappointing. From Disney I headed north towards Gainsville. Along the way I came to the end of my MegaScenery Florida area:

Kind of weird how it just stops like that all of a sudden. Further north, the graphics got even weirder. I accidentally switched into the 2D cockpit mode and when I switched back out the ground was all white. In exterior view, there were also these odd 2D clouds and diamond shapes in the sky:
I think the white diamond is the sun. Not sure about the black one, maybe another aircraft way up high? I guess you really shouldn't do LSD while operating an airplane...

I managed to fix the problem by temporarily going into windows mode and then going back full screen. That seemed to reset things which was good because I'm not sure I could have found the airport and landed on a featureless landscape. But find the airport I did, Gainsville Regional:

Even made one of my nicer landings with a perfect pattern flight around the airport and a straight down the middle of the runway approach with a nice gentle touchdown. Landing straight into a headwind didn't hurt I'm sure.

From here I think I'm going to bight the bullet and just fly all the way to Atlanta, that's 270 nautical miles or about two hours of flying. Probably do that later tonight.

Tuesday, December 22, 2009

Homeward Bound

Time to leave the keys if I'm going to get home in time for Christmas. I got off work early today, plan to take a furlough day tomorrow and thus don't have to go back until Monday. After I got home this afternoon I fired up the simulator and planned a flight from Key West to Tampa, a trip of just over 200 nautical miles.

So goodbye Margarita-ville. Here I am shortly after takeoff from Key West Int'l. I'm about 500 feet up and banking to the north. You can see those cruise ships still in port in the background.

Two-hundred nautical miles is a long way to fly, so I got a little interested in why nautical miles and regular miles are different, and why nautical miles per hour are called "knots" and not "nauts" or "nmph's" or something else.

One nautical mile per hour (1 knot) is the speed at which, traveling north or south on a meridian line, you will traverse 1 minute of latitude per hour. That works out to 1 knot = 1.151 miles per hour and thus one nautical mile = 1.151 regular miles.

Here I am about 50 nautical miles north of Key West. Up until this point the coast was just a thin line on the horizon but now I'm getting closer. That's Marco Island off to starboard.

Back to the lesson and the term "knot", which comes from the days of the British sailing fleet. They would measure speed by dropping a small wooden float thingy in the water attached to a line with knots tied in it at regular intervals.

While one sailor used an hour glass (or rather, a 28 second glass), another sailor let the line pay out and counted the knots. If you counted 10 knots during that time period you were traveling 10 knots or 10 nautical miles per hour.

Later more advanced and modern measuring techniques and more accurate, but only slightly so, than the old sailors technique.

Further north, at about the half-way point, I made landfall over Sanibel Island (Ft. Meyers area). I probably should have flown more directly to land since I just got that new Florida scenery, which doesn't do much good over the ocean.

Now that I'm over land, we'll see how it looks. Recall that over Key West, at low altitude (below 1,000 feet), even the MegaScenery left something to be desired.

Fortunately, a little higher (like my 4,500 foot cruising altitude), everything looks great.

Flying over Sanibel, I looked down from my right-side window. I believe that's Sanctuary Golf Course, based on a post-flight check on Google Earth.

The rest of the flight north was either along the coast line or a bit east over land. I was using a VOR station south of Tampa to navigate by. It's about 30 miles south of my destination airport, so the plan was to fly directly to the VOR, and then use the 14 degree outbound radian to navigate from the VOR to my landing point.


Here I am flying past Sarasota Int'l. Based on the readings from my VOR equipment, I'd say the tower is down there at that airport. Just thirty more nautical miles and I'll be to Tampa and to Peter O. Knight airport.

Knight is just south of downtown Tampa and right on the bay. (in Google Earth, look at 27 54'56.87"N, 82 26'54.33"W). At about 20 miles out I started descending down to a thousand feet and making preparations for landing, including calling in my position and landing intentions on the Knight traffic channel. There's no air traffic control there, so I don't have to request permission to land, just announce what I plan to do to other air traffic in the area.

The landing went well, although you can tell from this tower-view image that I'm a little high. Fortunately I had plenty of runway to work with and good brakes.

This airport should make a good jumping off point for a quick trip back to Disney. I'm curious what it looks like with the MegaScenery installed and specifically whether Space Mountain is in the correct position.

Anyway, I'm 200 nautical miles closer to home at least. After the Disney over-flight I'm going to head north again, probably to the pan-handle somewhere (maybe Panama City), and then a couple of hops up to Atlanta before the final leg back to Dalton, probably on Christmas Eve.