Monday, December 7, 2009

Cessna Skylane 182Q Test Flight

OK, so this guy at the North Palm Beach airport made me an offer I couldn't refuse on a Cessna Skylane 182Q. (Actually, Carenado, a maker of add-on planes for FSX had a 30% off sale). I didn't have much time for flying tonight, but I did take the new plane out for a quick circle around the airport to see how it handled.

The 182 is very similar to the 172 I've been flying but slightly larger with a larger engine and better aerodynamics. It flies higher, faster and carries a heavier load (four adults with full fuel is doable in the 182 whereas the 172 is better suited to two adults and a couple of kids)

The first thing I noticed is that the graphics are better than the default Microsoft 172. There's more detail on the outside of the plane and the instrument cluster looks more photographic and less computer animated. Performance wise, as soon as I throttled up for takeoff I could tell I had a lot more power under the hood. The torque pulled on the plane noticeably to the point that it was tough to compensate with no rudder pedals.

Once airborne, I could tell the rate of climb was much faster as well, almost 1,000 feet per minute easy. In fact, I had a hard time stopping it at 1,000 feet. I almost had to cut power back to idle to keep it from climbing further, but I got it under control and flew the pattern back around to land on the same runway where I started.

Landing was about the same, although again it almost has too much power to handle, at least based on my being used to flying its smaller sibling. After touchdown I used replay to grab some images and noticed that unlike the 172 which has only a pilot shown in the cockpit, the 182 has two animated figures, a pilot and co-pilot/passenger. By animated, I mean they look around and move a bit while you're watching from the exterior view. Pretty neat, but I'm hoping you can turn the passenger off. He looks fine on the test flight (presumably he's the seller I'm buying this bird from), but the rest of this trip is supposed to be solo.

As I continue my journey in the new airplane I'll find time to write a full review for the benefit of anyone else interested in Carenado products (www.carenado.com).

Sunday, December 6, 2009

Orlando to West Palm

I mostly spent this afternoon doing chores around the house. Got the basement floor mopped four times in preparation for sealing. I also installed a new doorbell out front for the wife, cooked dinner, and picked the Christmas tree up after it fell over this evening. We've got a ten foot tree and I think our stand might be a little small for that.

Anyway, after dark I found myself with a little time and decided to leave Orlando and continue my journey south. For my destination, I selected West Palm Beach. I've been there for scuba diving a number of times plus it makes a nice jumping off point if one were to want to fly east, say to the Bahamas.

I switched back to real world weather, which was cloudy per weather.com and loaded up the sim for an afternoon takeoff. I forgot to contact the tower and request clearance, but no matter. Soon I was airborne and heading south. Here's a view of Orlando International as I pass just to the east at about 5,000 feet:


Continuing south I managed to get the plane perfectly trimmed out straight and level at 5,000 feet and about 95 knots. My flight plan would take me almost due south from Orlando to Lake Okeechobee. There's a VOR on the southeastern shore that I was using to navigate to and which I would also use to fly outbound from to West Palm.

As I flew south, I realized that the sun was setting pretty quick. I forget it's winter. I had planned to land around dusk, but it looks like it'll be a night landing. It'll take me about an hour to fly to the lake and then 15-20 minutes to fly east to the airport. I did take advantage of the sunset to get some nice pictures:

Here's a neat view looking west with the sunset visible through the cockpit. You can't really tell from this angle, but one oddity on this flight was that my path took me almost directly over the line between MegaScenery Earth photoreal scenery to my left and the default fairly random scenery to my right.

A little while later as I approached the northern shore of the lake it started getting a lot cloudier and the sun got down on the horizon. The effect made for a nice purplish sky.

In this next shot, you can sort of see the north end of the lake under the cloud bank as the sun goes down. Not a nice day for getting a good view of the whole lake, which is huge.

The direct path south to the VOR would have taken me over the lake, but since I knew my final destination was on the east coast, I opted to fly around the eastern edge of the lake. I dialed the VOR gauge to 87 degrees outbound and waited for the needle to line up (which happens when I cross radian 87 from the VOR). I then banked to the left and made some adjustments to line up on that radian. My destination airport would be 25 miles outbound on that course.

As I flew eastward it started getting pretty dark and I started descending. I have also noticed on this trip that while FSX sometimes displays text on screen to indicate other aircraft (type, altitude, distance), even when you can't physically see the other plane, that doesn't always seem to be the case.

The skies around West Palm were more crowded that even Orlando and I spotted the wingtip lights of several planes that were not otherwise identified by FSX. That got me worried and a little paranoid about mid-air collisions so I started scanning the skies a lot more to make sure I was clear.

Anyway, I found the airport easily enough and got on the radio. Some airports aren't really controlled so instead of requesting clearance to land you just announce your intention to land so other airplanes in the area will know where you are and what you're doing. In FSX all of this is selected from menus and then, in a nice pilot voice that you can select from the options menus, you announce your call sign, distance and direction from the airport, altitude, and what you're going to do (inbound to a land on runway 26 left) for example.

I then got my airspeed down to about 75 knots and my altitude down to 1,000 feet and started flying the pattern. As I turned on final approach I found the runway dead ahead. Excellent! Then I noticed that my heading was 330 degrees, not 260 degrees, so I was lined up on the wrong runway. Dang! I throttled up, gained altitude, and banked off to the right to put a little more distance between me and the airport so I could line up correctly.

This time my turn put me a little off to the right but at least approaching the correct runway. I adjusted the throttle to set my descent rate and banked left and right to get lined up correctly. This was one of my better landings except that I'm still have trouble getting directly lined up down the center of the runway. Not sure how well you can see in this shot because it's so dark, but I'm flared out just right for touchdown:


Anyway, time for some sleep. I'll probably stay in West Palm this week looking for the dock where we'd leave from on scuba trips and just generally scouting out the area and maybe doing some more touch-and-go practice.

Then I think I'll head east and check out the islands...

Saturday, December 5, 2009

Disney After Humans

Amazingly, the storm passed and the skies cleared after just a few minutes. OK, I took control of the weather so I could fly without worrying about it. I took back off from Executive Airport planning to head southwest and find Disney World.

As I took off and started climbing out over Orlando I noticed something interesting. This part of Orlando appears to still be within the MegaScenery Earth territory I downloaded, so the ground is a photographic image. But because it's a city, there are also 3D buildings. What's strange is when there's a 3D model of one house, and just the flat 2D image of the house next door.

Anyway, I turned to a heading a 225 degrees and then tried to dial in the 225 radian from the Orlando VOR. I was off to the northwest of my correct line, so I turned south until I found it and then resumed by original heading. By then I was a couple of miles out with Disney estimated at 18 miles.

At 16 miles, I happened to look out my right side and saw the big globe of Epcot going by. I banked hard to the right to get a better look and grab a picture:

It was at this point that I realized Disney wasn't going to look as nice as I'd hoped. They seem to have sold off most of their property, including everything right around Epcot, and let it return to farmland.

I continued my right turn, knowing that the Magic Kindom itself was north of Epcot and should be within sight. I found it easily enough, cut power and descended to 1,000 feet for a flyby.

As with Epcot, the Magic Kindom seemed to have been taken over by nature. It reminded me of that Life After Humans show where they digitally simulate famous places as nature takes back over (assuming all humans have disappeared).

All that's left of the Magic Kingdom is Cindarella's Castle and Space Mountain, plus a few odd buildings including a badly modeled version of the hotel that the monorail goes through. The shape is roughly correct, but they seemed to have skinned it with regular brick building facade, which doesn't look right at all.

I was so stunned by this discovery that I completely neglected to take any exterior shots, so all I got were these out the window views.

Having accomplished my mission, I turned back to the northeast and found a heading to take me back to Orlando. I got back quick enough, requested clearance to land, and returned to the same runway that had vexed me in the bad weather.

This time it was a bit easier. I still didn't nail the middle of the runway, but the landing was smooth enough and at least all three wheels touched down on concrete:

The more I use this joystick, the mushier it seems to get. I've tried recalibrating it, but that doesn't seem to help. I'm surprised I don't crash more often (knock on wood), as sloppy as the controls are and with no rudder pedals to help.

Short Hop to Orlando

After several days of not being able to fly (Thanksgiving, long hours at work, other stuff that hand to get done around the house, etc.), I finally got to take to the skies a bit today. I decided that before continuing my journey, I'd take a short hop over to Orlando and fly around over Disney World. I took off from Titusville and headed west.

I actually used the Orlando VOR (112.20 MHz) located at Executive Airport which is just north of Orlando International for navigation, but I could have just as easily followed Highway 50:

It runs pretty much east/west from the coast in to Orlando. We've driven it before, although the toll road to the south is a bit faster.

Once again, I opted for real-world weather which (once again), was a mistake. Even shortly after take-off, I could tell it was a little too cloudy and hazy for sight-seeing, but I figured maybe I could stay under the cloud and see well enough when I got there.

The closer I got to Orlando though, the darker the clouds became. About 10 miles out, it became rather apparent that sight-seeing would be difficult and flying at low altitude might even be dangerous. I decided instead to follow the VOR signal straight in to Executive Airport and land.

After a refreshing break at the airport, I could either wait for nice weather, or just force nice weather since this is a simulation after all and do my sight seeing in a clear blue sky.

I've been playing around a bit with the air traffic control communication in FSX. I've not mastered it yet, but I was able to contact the airport, request clearance to land, and even land on the actual runway they cleared me for.

Clearance was for a direct approach to runway 15, but I decided to circle the airport and fly the usual landing pattern instead so I could get a better view of the lay of the land. As I made my turn to final approach I once again turned too sharply and found myself to the left of my correct line. I adjusted, but the wind was also trying to push me to the left so I never could get lined up perfectly. There was also a lot of turbulence, so my airspeed was jumping up and down, the altimeter needle was twitching up and down instead of descending smoothly and the nose of the plane kept jerking to the left and right.

Nevertheless, I flew her on in for a fairly smooth landing. Here I am crossing the runway threshold just 5-10 feet up in the air, ready to raise the nose and flare for landing:

You might notice that while my shadow seems to be over the runway, it's actually in the afternoon with the sun to my west (left), so this picture makes the landing look a little better than it really was.

Not that it wasn't smooth, but when they tell you to land on the line, I don't think this is what they meant:

Or at least, that's not the line they meant for me to land on. After touch down, I taxied back onto the runway and lined up on the center-line then announced that I was on the ground, switched frequencies to ground-control and got clearance to taxi to the parking area.

If I have time later today, I'll just set it on "fair weather" and try my Disney fly-over. The Magic Kingdom is about 18 miles southwest of this airport, so it shouldn't hard to find with good visibility.

Oh, one more note to self - don't forget to raise the flaps after takeoff when you use them. I flew all the way with 10-degree flaps, which kept my airspeed low and probably didn't do much for my gas mileage.

Saturday, November 28, 2009

Back on the Horse

I couldn't go to bed tonight without attempting one more landing and I'm glad I did. With a freshly undented plane I took back to the skies, circled the airfield and came back in for another landing attempt. This time I got my alignment pretty good at a distance although I had to bank gently to the right on the approach to get it perfected. My glide slope was maybe a bit steep so towards the end I gave it some gas to shallow out. I crossed the end of the runway below 100 feet, probably below 50 feet and flared out nicely just above the runway:
Touchdown was nice and easy and lined up just right. I could have easily throttled up and gone around again but I decided to quit while I'm ahead - for tonight anyway.

First Crash!

Well, it had to happen eventually. I tried some more touch-and-go landing practice in Titusville this morning. The first landing wasn't so great so I throttled up and went around again. The second approach was looking really good. I was aligned with the runway, glide slope looked right, just looking like a good landing all around.
Then the landing lights at the runway started going red like I was getting too low, so I gave it a little throttle to make sure I'd make it to the runway. I throttled back to idle and prepared to land, but my nose had pitched up a bit when I gave it the gas, so my view of the runway was not great. I was still lined up correctly, but I was higher than I thought so I started my flare sooner (higher) than I should have.

The stall alarm went off, but I under-reacted because I thought I was almost on the ground. As you can see though, I'm still pretty high.

Next thing I know, the nose pitches down pretty hard and I head for the runway, nose-wheel first. You can see I'm still lined up good, but it really works better if the rear wheels touch down first.

Bang! Nose into the ground and the plane starts spinning to the side. No control at all at this point, I'm just along for the ride.

My final resting place, as seen from the control tower. Oh, the shame!!

I suppose later on I'll get my propeller unbent and practice landings some more. Lesson learned - treat any stall seriously, even if you think you're just inches off the ground.

Friday, November 27, 2009

Seven More Landings

Plus one abort. I've been in Titusville today, just flying some touch-and-go and otherwise working on my landing technique. My first couple of attempts were pretty poor excuses for landings. They got me on the ground, but that's about it. Third attempt was off so bad I gave up, increased throttle and aborted the landing, opting to fly around for another pass.

By my sixth and seventh landings of the day, I was improving noticeably. I've identified two main problems. First, I have a hard time judging my alignment at a distance from the runway. In a real airplane with real 3-D and peripheral vision it might not be so tough, but on a flat computer screen, it's just tricky to judge. I'm also still flying with real weather, which means I've got a slight cross-wind with which to contend.

The second problem is my joystick. It stinks! The movement in the middle of the stick is just mushy so you end up having to over-steer just to get anything to happen at all. I'm also convinced that rudder pedals would be invaluable for making minor corrections to alignment during the final approach.

Anyway, here's a shot from my last landing:
Not too shaby on this one. I'm a little off to the left from the correct alignment, and the lights say I'm a little low, but that doesn't really seem to be the case.