Taking my complex time to ~4.5 hours

Today I earned another 0.9 hours of complex time in the Arrow. It has been a while since I've been able to fly; the weather has been poor for a week or so. The decent weather today brought the fellow pilots out of the woodwork to work off their pent up need to soar.

We had gone through most of the procedures before today, so this flight was to knock out the last two: power-on stalls and simulated engine outs. The stalls were nothing surprising - fairly docile if you keep on top of the rudder input. The engine outs were another story. We practiced a few at West Point airport and when you pull that sucker back to idle you are landing REAL soon. For instance, we pulled it to idle when I was a little past abeam the numbers (coming from too-wide a downwind leg) and we weren't going to make the runway - we would have had to settle for a field in front of the runway if this had been for real.

When we were about to add a little power in order to make the runway on that first "engine out" we looked up to see skydivers all around us. They had been annouced on unicom so we were ready for them. We did a go-around (called off the landing and started climbing again) and made a right turn to go away from the open chutes. Making a wide circle around the airport let the jumpers land and the jump plane - going for the pattern in a dive-bomber descent - get back on the ground before we re-entered the pattern.

We did two more simulated engine outs which I managed to put on the runway and then headed back to Williamsburg. My instructor had turned on the interior lights (when I wasn't looking) on the way to JGG. This meant that when I went to lower the gear just before entering the pattern the three green "gear down" lights didn't come on (they were too dim to see b/c the interior lights were on and dim).

I calmly said "Hmm, not getting 3 green" (I figured my instructor had done something, since we just practiced this emergency before going to West Point). As he was saying "Well, what should we do?" I checked the master switch - it was on - I looked at the circuit breaker - not popped - so that left the interior lights. As I went for them he called out "YOU SAW ME TURN THOSE ON!" - I laughed and said I didn't but I don't think he believes me. What I really should have done in this situation was exit the pattern, get some altitude, and run the full checklist. Since I knew he was tripping me up though, I figured I would go through the steps that were in my head first.

I made the pattern into JGG a little too tight, causing me to overshoot final and come in pretty high. Not a good approach at all. I managed to salvage it, though I probably should have gone around and tried again. The "swamp monster" gave us a nice little balloon-up-then-dump-you-down as I was high in the flare. Thankfully we had some extra airspeed that let me pitch up more to fight it.

Things to work on:

  • Call out "3 green" at the various points in the pattern, don't just do it mentally
  • Avoid any side loads on the gear when landing/taking off - today's serious gusts were causing me to overcorrect with rudder

Comments

Post a Comment

Popular posts from this blog

Updating data on the Garmin Perspective system

Image
After changing from the Avidyne system to the Cirrus Perspective (G1000) system, I had to relearn an important part of owning an airplane: how to update all the data the systems use. There's even more data in the Perspective, including AOPA directory data and more charts. In this walkthrough, I make use of the Jeppesen app for Apple OS X: JDM .  It has worked well for me, though I did need to call Jeppesen when I first set this up to get my subscriptions fixed up.  They gave great customer support when I did. The process starts (optionally) by hooking up a ground power unit (GPU).  In the case of the Cirrus, you can certainly do this without it, but I tend to hook it up just to be sure.  The systems draw about 8-10amps while updating, but you won't generally have the power on for long.  One tip I've read: power up the GPU before plugging it into the plane, at least for the one I bought.  That saves the plane from seeing any power spikes that might have occurred when t
Read more

G1000 transistion training - emergencies - final flight

Image
For the final flight in my G1000 transition course we focused on failure scenarios. Not the "engine goes POOF" kind but the avionics kind. Normal situation This picture shows what the 2 Garmin screens show in a normal (non failure) situation. You can see we have 2 screens - the left PFD focusing on flight performance (airspeed, heading, attitude, altitude) and the right screen (MFD) focusing on engine data, mapping, checklists, and everything else. Failed PFD screen In this scenario the screen that is right in front of you (the PFD) has failed. This basically means the screen has gone dark. We simulate that by dimming the screen down to 0% brightness. After darkening the PFD we shot a GPS approach into Rock Hill. When this failure has occured you shift the G1000 into Reversionary mode. That means the info that is normally split across 2 screens is now merged into 1. It actually duplicates the same data on both screens, but since the PFD screen is no longer functioning
Read more

A-10C Standby Compass - Sun Shade

Image
 One of the final items to add to this instrument build (besides the text covers for the lower LEDs) was the sun shade for the AR LED box.  I made this out of thin aluminum sheets , cutting it from a template using some metal sheers .    My template was created by tracing some of the actual artwork from the DCS sim, and then scaling it to the proper size. It turned out ok, not perfect but pretty good.  Primed and painted it and then installed it using 2 of the 4 holes that were already on the LED box 3D print.  I used some heat inserts in those holes to give the screws something to bite, but the holes are really too big for my inserts so had to use some glue to help out.  
Read more