Sunday, November 8, 2009

Getting Real (or at least Medium Real)

As I've mentioned in prior posts, I've been flying the sim thus far on the "easy" setting. I've not fully understood what that meant or how that compared to medium, hard, etc., but I knew it wasn't as real as I wanted the simulation to be.

Of course, a computer simulation has some unreality that works against you, like lack of realistic controls, no peripheral vision, no sense of motion, etc., so a little unreality that works in your favor, like being able to switch to an external view of the plane, is not all bad.

Nevertheless, I decided I was ready for something more so I crank up the reality setting to medium, plus turned on crash detection and some other features. I left "auto rudder" engaged since I don't have rudder pedals, and left "auto mixture" turned on, since I don't have a real throttle set with mixture lever, but I turned on damage detection from hard maneuvers and engine stress, plus turned off unlimited fuel and a couple of other cheats.

I decided on a short test flight, starting from the Dalton airport, taking off, flying the pattern and landing again. This time, while selecting the free flight options, I looked a little closer and realized you can set your start position at the airport. The default is "active runway" which is what got me in trouble on a recent flight. This time, I selected to be parked near the hangers:

I'm in cockpit view, looking over to my right at the main building and fuel pumps. From there, I taxied around towards the runway and saw that the windsock showed a slight breeze coming from the south. Forgot to get a picture of that, but I did taxi to the correct runway, stop at the hold line and check that the sky was clear in both directions and then pulled out onto runway 14:


I've mentioned trim in earlier posts so here's more of the cockpit view, including a view of the trim tab, which I've adjusted to the take-off setting of around 5 degrees nose-up trim:
Add Image

The trim wheel is just below the yolk to the right. You can't see the mouse pointer for some reason, but when you point to it you get the little pop-up text that tells you how it's set.

With trim set correctly, I throttled up, headed down the runway, rotated and took to the air. As I passed the hangers and tower, I looked to the right and took this image:
Add Image
You can see that I'm airborne and climbing.














Next, as I gained more altitude, I took this image looking left towards Fort Mountain:

If you're from this area, the mountain range is easily recognizable. I'll continue this account in a series of post since the number of photos I'm trying to include is starting to make it difficult to edit. I must be doing something wrong, because I keep accidentally deleting images and I'm having a hard time getting them in the right place.

Pancake Day Flying

Yesterday was the 50th annual pancake breakfast hosted by the Kiwanis Club of Dalton, of which I'm a member. The breakfast is our annual fundraiser for local children's charities. I normally get there at 5 AM, but this year they put me on a swing shift, so I didn't get there until about 6:45 and worked until 11 AM.

My friend and former college roommate, Tom, came to town for the event and to do some geo-caching, but I also showed him FSX and did a couple of flights.

First I took off from Dalton in the Cessna with realistic weather turned on. Oddly, it seemed cloudier in the simulator than it did looking out the window. It was definitely windy though. I took off heading SSW, climbed out and turned back towards Dalton and flew up to Chattanooga to land. I was explaining the "red over white" light system used by some airports but when we got to Chattanooga I realized they use a different system that I don't know how to read yet. I had to eyeball my approach but the cross-wind kept pushing me off the runway, so while I landed successfully, it wasn't pretty.

Next I switched back to Florida to show off the MegaScenery. Took off from the Shuttle Landing Facility and flew across the waterway to Titusville where I successfully located and circled over my father-in-law's house. Definitely an Aha! moment that made the scenery purchase worth the money. Here's a picture:
This is looking over my left shoulder at La Cita Country Club in Titusville. I'm not going to identify the house but if you've been there you should be able to spot it.

My father-in-law, like my own father, was a private pilot back in the day. I'll have to show him this some time.

Friday, November 6, 2009

Head Tracking Systems

I've recently subscribed to Computer Pilot magazine and was reading an article last night about a product called TrackIR (naturalpoint.com). The product comes with an infrared camera and light unit that sits on top of your computer screen and some reflective stickers you put on a baseball cap (or on your forehead I guess), and software that allows the camera to track your head movements based on the reflected infrared light.

For flight simulation, the advantage is that you can turn your head a little to the left to look left and FSX responds by shifting the view on screen to the left. Currently, I'm using the hat switch on my joystick (sort of a joystick on the joystick) for this purpose, but that can be distracting when you'll also trying to maneuver, say for landing. Also, the hat switch only gives you look left/right and look up/down. FSX also supports keystrokes for shifting your whole head left/right/up/down/back/forward which would simulate leaning it towards the instruments or raising up in your seat to get a better view over the hood, etc. The key combinations for those motions are ctrl-shift-enter and such, which are naturally hard to use when you're maneuvering the airplane. There aren't enough buttons on the joystick to map those commands to, and even if they were it would be tough to use them except in straight and level flight.

TrackIR on the other hand tracks your head movement and can accomodate all of those motions naturally without you having to remember what buttons to press. The only problem is that it costs $150, and if I had $150 I'd probably spend it on a flight yoke or rudder peddles first.

Then today, was on Dino Cattaneo's blog (where I downloaded those new planes) and saw a reference to FreeTrack (free-track.net), which is a freeware software that lets you do the same thing with a web came ($20-30) and some LED's on a hat. Should be a lot cheaper, so I may check this out.

Thursday, November 5, 2009

Add-on Planes for FSX

Not that I need them, but I figured out how to add airplanes from third-party developers to FSX. I had read about some really good free-ware planes from Dino Cattaneo (see indiafoxtecho.blogspot.com). I got on his blog and downloaded the T-45 Goshawk jet trainer and the F-14 Tomcat, neither of which I plan to fly any time soon. He's also working on an F-35 Lightning II, but that was not ready yet.

At some point, when my flight training has progressed a lot further, I'll try flying military planes including jets. The T-45 would probably be a good one to train on, and is actually equipped for carrier landings. Here's what it looks like (with gear and tailhook down):

I had some initial difficulty getting FSX to recognize them, but finally got it to work. It seems odd that Microsoft, knowing what a large third-party developer network exists for FSX, did not see fit to have some kind of import utility for add-on planes. It's really up to the developer to either have a zip file and tell you where to dump the files or to take the time to actually create a setup.exe file to do it all for you.

Wednesday, November 4, 2009

Navigational Error

Well, this is embarrassing. I got all the kids to bed and Charlotte wasn't feeling well, so she went to be as well. I figured I'd get a short flight in before I turned in myself and decided to repeat an earlier flight from Dalton to Chattanooga, land, taxi to the end of the runway, turn around, take back off and fly back to Dalton. To make things a little more interesting I decided to do it with the current time (night) and with real world weather downloaded from the internet.

I selected my usually trainer plane, the Cessna Skyhawk, and the Dalton airport and started it up. Boy, was it dark. Looking around you could only see the runway lights blinking but I figured I could see more once I got in the air. I learned something the other day that makes take-offs easier. I've mentioned how you trim the airplane for a certain speed so you don't have to constantly hold the stick back during a climb for instance. It had not occurred to me before, but since you know the take-off is going to involve a long climb, why not trim the airplane BEFORE you head down the runway? In fact, there's a "Take Off" marker on the trim wheel that even tells you the ideal trim setting for the initial climb-out. I spent a minute adjusting the trim and then throttled up and headed down the runway.

I quickly got airborne and then only had to make slight adjustments to trim to get my climb just right. After that, I started looking around, but where I expected to see the big city lights of downtown Dalton, all I saw was darkness. Are we having a blackout or something, what gives? As I climbed higher, I got into the cloud cover which reduced visibility further. I could sort of see out the right side of the plane and started scanning for another airport that is off to the east on the route from Dalton to Chattanooga, but couldn't find it anywhere. I decided that if I descended from my current 4000 feet down to say 2000 feet, which should still be high enough to clear the ridge just east of Chattanooga, I could see better. Well, I tried that, but once out of the clouds I still could not see Chattanooga, but instead could see a ridge-line ahead that looked higher than it should.

At that point, it occurred to me for the first time to check the compass. Instead of flying a heading of approximately 330 degrees (NNW), I was flying the opposite heading of 150 degrees (SSE). Every other time I've taken off from Dalton, the computer has positioned me at the end of runway 33, heading north, but not this time. Probably on the earlier flights I had "fair weather" which meant no significant wind, which meant take-off direction didn't matter and the northward direction was the default. This time, with real weather and I guess a northward blowing wind, it put me on runway 15, heading south (same physical runway, just at the other end of it). In the real world, I would have taxied from the hangers to the runway and would have known where I was, but in the simulator I just took off assuming I was heading northward.

I quickly went to full throttle to avoid hitting the mountains (same range as Fort Mountain only farther south, just below Carter's Lake actually), and made a quick 180, heading back towards Dalton on my original intended course, but now with no intention of going to Chattanooga. I decided if I could get the plane back on the ground in Dalton I would call it a night.

After a few minutes I finally saw the lights of Dalton ahead and spotted the airport off to my right. I adjusted course, flew around south of the airport and then flew the "downwind leg" parallel to the runway to position for landing. Since I had taken off southward, presumably into the wind, I figured I'd better land into the wind as well since that results in a slower ground speed and thus a safer touch-down.

I flew out over Dalton, did another 180, made some more adjustments to line up on the runway, lowered flaps and headed in. One advantage of flying at night is that you can see the landing lights a lot better. At the end of the runway they have two sets of lights which can turn red or white. If you're on the proper glide slope, the top set (furthest away) will be red and the lower (closer) set will be white. "Red over white, you'll be all right". If you're too low, it's "red over red, you'll soon be dead", and if you're too hight, it's "white over white, you're out of sight" or something like that.

Anyway, I was red over white when I lined up, but then it went red over red so I had to throttle up, level off and even climb a bit to get back in the zone. I cut throttle again, added more flap and tried to bring it on in but then I got white over white, so I was too high. I slowed down more and probably over-compensated again as I ended up landing a little hard and right at the end of the runway. Since I only need about half the runway to coast to a stop, "too high" is a relative term. It really means too high if you need the whole runway to stop. I should have just ignored that white over white and continued the descent rate I was on and I would have been fine.

Anyway, I lived to fly another day, and as the saying goes, "a good landing is one you can walk away from; a great landing is one where you can still use the airplane again afterwards". I guess I'll file this one under great landing then and go to bed.

Monday, November 2, 2009

Slooooow Flying

I'm definitely getting better at the landings. I tried the "slow flight" training exercise this evening, but the instructor was too impatient, so I went to free flight and just practiced on my own. I was able to trim the aircraft out to a nice 80 knot climb to 5000 feet, then level off and increase speed to 100 knots and trim it out for that speed and to hold that altitude. I then tried to back it down to about 65 knots, and was mostly successful, although I dropped down to about 50 knots at one point and set off the stall alarm. Just drop the nose a bit and add throttle and I got out of that one. Whew!

After a little more tweaking I settled for about a 70 knot cruise and was able to trim it out for level flight at that speed. I then throttled up and turned back towards Dalton. I managed to trim it nicely for a 90 knot decent at about 300 feet per minute. That got me back over Dalton about 2000 feet above the airport. I turned for final approach and got into a nice 65-70 knot descent losing about 500 feet per minute until I got almost to the runway. Then I killed all power, and flared out with about a 100 feet per minute drop over the runway. I actually stalled the plane a couple feet above the runway, but otherwise it was a pretty smooth landing. I was also nicely lined up on the runway, which hasn't always been the case. Once you figure out how to trim the plane for a certain speed and decent rate, you can pretty much let the plane handle that part and concentrate and steering to the runway correctly. When you're having to simultaneously hold the nose up, adjust throttle, and try to bank left and right to line up, things tend to get messy quick.

Sunday, November 1, 2009

Flying Lessons Discovered

Aha! There are flying lessons in FSX. On the missions screen there's a tab on the right for training. I noticed it just recently and checked it out. At first I thought they were just written tutorials staring with the basics of flight and going from there, but they actually have missions you can click on after reading through the ground school lessons.

Today I pretty much started my flight training over again with the lesson and straight and level flight. This is surprisingly difficult. On my earlier flights I thought I was doing OK, but really I was constantly gaining or losing altitude. In a simulator, that's no big deal as long as you don't hit the ground (which is still not a big deal, really), but in the real world other pilots, ground controllers, and of course the FAA kind of expect you to maintain a constant altitude.

Without fully understanding the concept of trim, you spend your time making manual adjustments which tend to be over-corrections resulting in a wobbly, parabolic sort of flight path. I've spent about two hours just trying to fly around at either a constant altitude or at a constant speed with a steady rate of accent or descent. I'm getting better at it, but I'm not there yet.

I just had my worst landing so far. I've still go the reality level set at easy, so it didn't count as a crash, but in the real world that's what it would have been. I was wobbling all over the place and banking left and right trying to hit the runway. I finally came down on the left side of the runway, angling towards the right side, and landed with a slight bank to the right and at a pretty fair clip. Ouch!

I've learned that, counter to what you'd think, you don't really use the yoke or joystick to climb or descend. You use them to change the aircraft's pitch, but you really use the throttle to climb and descend. For climbing, especially on take-off, you use full throttle (on the Cessna Skyhawk anyway), and after climbing gradually off the runway until you reach 80 knots, you pull back on the stick to maintain that 80 knots. Actually, I think the ideal climb-out speed for the Skyhawk is 74 knots, but 80 is a bit safer and provides better visibility out the front since the climb angle is not so steep.

For descents, instead of nosing down, you reduce throttle, and actually nose up to hold a set descent speed, so 90 knots for descent from altitude, but more like 65 knots for final landing approach (with flaps). You then use the throttle to increase or decrease your descent rate.

I'm still having a lot of fun with this, but I've clearly got a lot to learn about flying.