Squawk1200

Today was to be an interesting day.  The plan was for me to make my first solo cross-country flight, to RMG where I went with Scott last weekend.  So I spent some time this morning working up a flight plan from LZU to RMG in my old friend 546DC.  I’d previously spoken with Scott, who’d mentioned wanting to have me do some power-off landings, so I planned on a bit of dual time prior to my solo.

The first monkey wrench in the day’s plans came after I’d finished up my flight plan- I’d neglected to even check the weather at RMG.  I suppose I was subconsciously assuming it was the same as the clear blue skies here in Atlanta-a bad assumption.  The RMG METAR showed an overcast layer at 2300′- technically low enough for me to fly under and land, but I was uncomfortable with it.  I checked the satellite, and determined that the cloud cover might b burning off, so I decided to hope that the clouds cleared up in the couple of hours between then and the start of my flight.

Over at LZU, Scott was finishing up with his previous student, so I took the opportunity to recheck the RMG weather and the satellite.  Things hadn’t improved at all- in fact, the overcast layer had come down to 2100′.  Once Scott was done, I mentioned the weather situation, including my discomfort with flying in those conditions.  That turned out to be a moot point anyway- my solo endorsement specifies, among other conditions, a 300′ minimum ceiling, so RMG was right out.  After reviewing the area weather, we decided on Thomson-McDuffie (HQU) instead.  I worked up a quick route, then put off finishing the plan until after we’d made our dual flight.

LZU was pretty busy, so instead of working in the pattern there, we headed a few miles east to Winder.  I’d watched Scott execute a power-off landing out last time out, so I had an idea what things should look like.  I also knew that this would be a real exercise in energy management; the DA-20 is perfectly capable of gliding the distance required to make it from downwind to the runway; in fact, there’s energy to spare.  The game becomes judging when to drop flaps and start bleeding off excess energy in order to come down in the selected touchdown zone.

It was easier than I thought, really.  I entered the downwind leg, and pulled the throttle to idle abeam my touchdown point.  Having seen how Scott kept the pattern in close, I started my base turn early.  I already felt I was plenty high, and Scott confirmed by advising me to drop the first notch of flaps.  I continued to come around, ending up on a short final.  Just before completing my lineup, I dropped the last notch of flaps and came in for a nice gentle touchdown; a bit long perhaps, but otherwise lovely.  I repeated this exercise twice more, with good results- on the second, I went out a bit further than necessary on my base turn, and had to delay dropping final flaps, but I still made it back with energy to spare.

After an uneventful trip back to LZU, we checked the weather again.  HQU was showing a 3200′ ceiling; enough room to fly under for an arrival.  After some thinking, I decided the trip was good to go, and set about finalizing my flight plan.  Scott saw that I was getting everything together, then signed my logbook and departed the area for home.  As I was getting my weather briefing, he called me with a thought… since HQU was 75+ miles away, if I stopped at another airport during my trip, this could count as my long solo cross-country. (150+ miles total distance, one leg +50 miles, three stops)  Sounded like a plan to me.

Before beginning my taxi, I set up the plane for my trip; rather than flying direct to HQU, I was going to make a slight north dogleg over Athens ans take advantage of the VOR there as a waypoint.  I dutifully tuned to the proper frequency and selected the appropriate radial, or so I thought. (more on this later)  Out and airborne, I got my first blow to my plan- it was clear I wasn’t going to be cruising at my planned altitude of 5500′.  The clouds over LZU had closed up a bit, and as I approached 3500′, I felt I was getting in the neighborhood of my minimum clearance.  There were holes that I could possibly have climbed through, but that was risky for both practical and legal reasons.  As such, I elected to cruise at 3500′ instead.

I settled about navigating to Athens.  The air was a bit bumpy, and the lower-than-expected clouds made me a bit nervous, so when I kept drifting off the radial to Athens, I figured those were responsible.  But as time went on, I couldn’t seem to intercept the radial- the needle would move left, I’d make a left turn… no change… repeat… so on.  (Astute readers, probably including at least one CFI, already know what’s going on)  I was wondering about all this oddness when I saw an unexpected sight on the GPS- Lake Lanier.  Now, Lanier is almost directly north of LZU, whereas Athens is almost directly east.  Alarm bells went off, and suddenly I knew exactly what I’d done.  I’d selected the reciprocal radial from the one I was supposed to be flying, with the consequence that if I’d wanted to correct my course without adjusting the VOR, I’d need to correct opposite to the needle deflections.  Argh.

So I spun the OBS to point the way to Athens, made a nearly 180-degree turn, and continued on my way.  The good news was that I was now flying the radial that I was going to take to HQU anyway; I’d just gone about 15 miles out of my way.  The rest of the trip to Athens was uneventful, save for the continuous sense that the clouds were continuing to lower.  By the time I’d gotten south of Athens, I was down to 3000′ to make sure I had sufficient cloud clearance.  At this point, I was really starting to get concerned that the clouds would continue to come down as I approached HQU.  About halfway between Athens and HQU, my path took me near Washington-Wilkes County (IIY), which I’d planned as a possible divert location if the weather at HQU degraded.  As I got near to IIY, I dialed up the HQU AWOS to see what the weather looked like.  I was a bit far out, and the transmission was a bit garbled, but I distinctly thought I heard a reported 1000′ ceiling.  Thus, with HQU weather sounding untenable, combined with my bit of nervousness about the clouds I was flying under, I elected to divert to IIY.

The place was dead.  If not for cars on the surrounding roads, it could have been a set for an apocalyptic movie.  I heard nothing but empty air as I sent my intentions over CTAF… approaching, entering the pattern, base, final, clear of the active.  I parked in front of a locked-up FBO building and hopped out to assess the situation.  First order of business, as learned from my last flight, was to call and cancel my flight plan.  No more ominous voicemails for me, thanks very much.  I attempted to use the flight briefer app on my phone to check the HQU weather, to no avail.  I had about the weakest signal possible, and data transmission just wasn’t happening.  Without any apparent way to get weather info for HQU, and seeing as how I had no particular need to try to press on, I decided to plan my flight back to LZU.  The flight to IIY and back would still count as a cross-country.

Alas, but here my phone betrayed me again.  I picked a direct track back to LZU, picked out a few visual waypoints, worked out the flight plan, then attempted to file the plan and get a weather brief.  Neither the briefer or I could understand the other.  I wandered all over the ramp looking for some kind of sweet spot, to no avail.  Well, I knew the winds aloft forecast from earlier was still good, and so I could use those numbers to work out the headings I needed to fly.  One more try for the briefer, no joy… well, no flight plan for the return trip then.  I took off from the still-dead airport and pointed the nose to the west.

For the return trip, I decided to take advantage of the GPS.  So far, for my cross-country flights, I’d intentionally avoided referring to the GPS in favor of learning to navigate by pilotage or radio aids, but given the number of kinks in the flight so far, it seemed wise to use all available resources.  Of course, first I had to remember how to enter a direct track in the thing.  A few minutes of fumbling and I had a nice purple line pointing the way to LZU.

The flight back was uneventful; the air seemed to have smoothed out, and holes were appearing in the clouds.  The sporadic shafts of sunlight peeking through made for a great view, and I found that as great as they looked on the ground, flying through them was even better.  I picked up all my waypoints and held the direct course with no fanfare.  Back at LZU, I shot a few touch & goes before making my full stop just ahead of the school’s other DA-20, wrapping the day up with 2.3 hours of solo cross-country time.  I also checked the AWOS history for HQU, and discovered that I’d apparently misheard the weather- at no time during my flight was the ceiling reported below 3200′.  Well, better safe than sorry, I suppose.

As I look back at the flight, I could have done some things differently.  Flight Watch is available for checking weather while in the air- instead of diverting to IIY based on a garbled radio transmission, I probably would have been better served calling them up and asking about the weather.  I should also really get myself an AFD;if I’d had one on hand, I might have been able to check the HQU weather from the ground at IIY via phone and determined that I could have pressed on.

All told, the flight went off OK, I learned some lessons, got to see some new scenery, and had a real-world experience diversion experience.  Since I didn’t get my long distance cross-country, I’ll keep with my original plan to make my long solo cross-country next weekend, weather permitting.  My parents are going to be in Chattanooga, and it’s my dad’s birthday, so it seems like a good opportunity to make it up north and take him out to dinner Sunday afternoon.  Hopefully Scott and I can get in some night flying this week as well.

Wow, only five days since my last flight… maybe the sporadic January days are truly behind me now.  Overall, I’m starting to get the feeling that I’m on the home stretch here… I’ve gone and soloed both in and out of the pattern, and after today, I’m all set to go do  a solo cross-country and work on getting that requirement knocked out. (”That requirement” being five hours of solo cross-country time)

For today’s flight, Scott instructed me to plan a flight to an airport of my choosing, at least 50 miles from PDK.  In a sense, this was a pleasant change; earlier portions of training were necessarily regimented to a certain degree; fly here, do pattern work, fly home, go to the practice area, perform three steep turns, etc.  Suddenly it was all up to me.  I decided that one additional self-imposed requirement would be that my destination be an uncontrolled field.  We’d performed a fair amount of pattern work earlier at small fields, but that was mostly before I got over my radio stage fright.  Since then, nearly all of my pattern work had been done at towered fields, and as a result, I felt it best that I go somewhere where I’d have to learn to talk in the blind.

I settled on KRMG in Rome, GA, slightly over 50 miles from PDK.  My flight path up there was made a bit more interesting thanks to Dobbins ARB in Marietta- flying straight from PDK to RMG would have run me through their airspace, and while that’s not a problem if one gains permission, I elected to challenge myself a bit by throwing in a dogleg around the airspace.  I’d previously flown to Chattanooga, but that was a simple direct-follow-the-VOR-needle flight.  This time, I was going to fly to RMG without the benefit of any fancy stuff- no VOR, no GPS.  I selected several checkpoints to check my progress, and even scouted the area on Google Earth to get an idea of what I’d be looking at.

Over at PDK, Scott and I reviewed my flight plan and the route I’d chosen, a conversation liberally sprinkled with questions about airspace rules, information found on the sectional, and other little tidbits that I’ll need to know.  My planning passed muster, and then I had my first experience filing a flight plan and getting a weather briefing. (that guy talked fast, even after I told him I was an idiot student)  Today’s weather could hardly have been better- clear skies all around, light winds, great visibility.

After an uneventful taxi (save for me trying to get taxi instructions on the tower freq), we were airborne and headed northwest.  By the time I reached my planned altitude of 6500′, I was already nearing my first checkpoint, a small private strip north of town.  I was unable to get it in sight- probably hiding under the nose- but I knew that I could expect to pass overhead when RYY was off my left wing, and my proximity and heading to Lake Alatoona confirmed this, so I made my turn towards RMG.  The rest of the flight was uneventful; I hit my checkpoints as expected, though a little late, as my cruising airspeed was lower than I’d planned.  Given the fact that I was navigating only by ground references, I was a bit surprised when RMG materialized almost directly off my nose- I was far more accurate than I’d expected.

The plan at RMG was to fly around in the pattern a bit and practice short- and soft-field landings, but first I had to get past an inexplicable return of radio stage fright.  Come on, just key the mike and talk already… eventually, I did get to the point where I made calls maybe about half as often as I should have… I need to do this more and get it ingrained.  Meanwhile, my first time around was ugly.  I got in too tight on downwind, and the resulting tight pattern had me end up way high turning final.  Despite pulling the power out, as I approached the runway it was clear that this one wasn’t going to work… time to go around.  This time I flew a bit further out, and though I again came in high, I was able to save it for a touch & go.  Next time around was high again, and as I powered up to go around, I realized that I hadn’t ever put in full flaps… ok, get it together.  Next time around was far better; I was on slope as I turned final, got a little low on short final, but ended up with a nice touchdown.  In a valiant attempt to pretend I was doing a soft-field, I flew down the runway with the nose in the air a bit before climbing out again.

Thereafter, things were much better.  I still wasn’t talking on the radio as much as I should have, but I quit coming in ridiculously high and was looking like I had some idea what I was doing again.  After a few more circuits, I headed for home.  I’d only gone a few miles before Scott sprung the (expected) surprise.. ye gods, PDK was closed and I needed to divert to Cherokee County!  I got a pretty good position cut from the Rome VOR, and from that I got a rough heading to 47A.  I did some quick mental calculations for estimated time and fuel to 47A, then set about fine-tuning my location and flight path using the sectional.  It was easier than I thought; I was able to identify landmarks every few minutes to monitor my progress, and I only faltered as I got close to 47A.  I got a little too sure of my heading and was carefully scouring the area ahead at the expense of either side.  As I continued squinting over the nose, Scott made a few nudging remarks until I noted that the airport was at about my 1:00 position.  There’s a good chance I would have flown past it had I been alone.

Satisfied with my ability to find my way around, Scott let me turn south for PDK.  As we approached the airport, he raised the idea of me going out for a few solo circuits at PDK; this sounded good to me, but given my subpar performance earlier, I decided to try a few times around with Scott before taking that leap.  Landing #1 was great, and things were looking good… but then, at about 600′ on the climbout, the engine seemed to cough a bit… uhh, yeah, let’s go for a full-stop on this one.  This time, Scott took over on the downwind so he could demonstrate a simulated engine-out landing.  It was really just as well… by the time I would have finished a few touch & gos, it would have been getting dark anyway.

Back in the office, Scott added a few endorsements for me to fly solo at PDK and FTY, and we discussed getting me on a solo cross-country maybe next weekend.  I may do my long cross-country the following weekend, most likely to Chattanooga and back.  I still feel I need to spend some more time at untowered fields to get in the groove of making my calls.  In the meantime, there’s the question of what ramifications that engine stumble might have… 546 will be getting checked out this week, and I hope she’s OK, because 393’s schedule is invariably crowded, especially on the weekends.  And I’ve got lots of work to do!

Oh, one final bit of information… as I was about to head home, I observed that I had a voicemail.  Upon listening to said voicemail, I heard the voice of a man with FSS, informing me that we were overdue and S&R procedures were about to be started.  We had indeed forgotten to close our flight plan, at least initially; Scott remembered as were were in the pattern at RMG and called up to cancel it, but presumably we were already overdue at that point.  I went ahead and called up just to make sure everything was kosher… I don’t want to get any fuel bills from the CAP in my mailbox.  So I guess that was my first experience with forgetting to close a flight plan.  Live and learn…

So ends another flightless period, and with a bang to boot. (more on that later)  Despite my expressed desire last time around to try to get back to flying more often, events continued to conspire against me.  It started with the repairs to 546 being more extensive than expected; originally, the left side rudder pedal assembly was scheduled to be replaced, but it turned out that the rudder cable had to be swapped as well.  This pretty much requires stripping the airplane behind the seats, so the maintenance downtime increased quite a bit.

Meanwhile, with 391 having been sold a few weeks ago, there was but one remaining DA-20, and as you might imagine, it was in high demand.  Between the plane being booked solid and a miniature rainy season striking metro Atlanta, today was the first time I got to fly again.  I had previously tried for last Friday morning- a rainy day- and yesterday- which featured low clouds from Sunday’s heavy rains and gusty conditions to boot.

But this morning dawned clear, if a bit cold.  I cocooned myself, mounted the bike, and headed out to scenic Lawrenceville to meet Scott.  We had already discussed the plan of the day, which was for me to fly solo out of LZU, head to the practice area, and pretty much do as I pleased.  Concerns for the day, on the other hand, were that the winds were forecast to pick up starting at about 9 AM or so- so my window of flight wasn’t that big.  Scott inquired if I wanted to go around the pattern a few times with him, but I felt confident working in the pattern at LZU, so this ended up being my first “all me” flight.

In many ways, it was a sort of emotional rehash of my first solo.  You just get used to doing things with someone else; preflighting the airplane, climbing in… just all the little things seem vastly different when you’re alone.  The plane took a few tries to start thanks to the temperature, but soon enough I was idling on the ramp, willing the heat to start working and the oil temp to come up.  Then I switched to willing myself to push the talk button and call ground.  As I taxied down to the runup area, it seemed as if someone had taken sandpaper to my senses.  Evey noise the plane made was amplified in my ears.  Every bump felt like an earthquake.  On the roll, I was again reminded of the vast difference in performance caused by a missing passenger.  Up, up, and away, turn to the north, got the lake in sight, keep an eye out for the tall tower to the east, boy, did 3500′ ever come up fast.

There I was, over the lake.  What to do now?  Well, I could just poke holes in the sky, but it *has* been a bit since I practiced my maneuvers, and I *am* in the practice area.  So I tooled about over water, doing steep turns, discovering that slow flight looks different with less load, throwing in a few power-off stalls for good measure.  OK, what now?  I did a few more steep turns, focusing on trying to better coordinate rudder with aileron on the roll-in and roll-out.  Still need to practice that some more.  I still wasn’t quite ready to head back to Gwinnett, and ATIS hadn’t been updated with the latest wind info, so I just flew around the perimeter of the lake a bit, taking in the sights on the ground.

Then it really was time to head back.  ATIS had now been updated, and winds were reported out of 250 at 15.  Stiff, but straight down the runway; should be OK.  I decided to stick with my Plan A and squeeze in a few touch & gos before parking the plane.  Got instructions from the tower to enter right base for 25.  I made a slight miscalculation here and started my descent too late, and ended up having to work to get down to pattern altitude, but I gt it done.  Meanwhile, I could feel that the winds were picking up, moving the plane around a bit.  I made a mental note to keep some extra speed on final to compensate.  Once I got on final, I realized I was in deeper waters than I had expected; the wind made it challenging to maintain a good glide slope.  Still, I managed to stay more or less on slope and in line, but in the flare, things got ugly.  Seemed as if I caught a gust just after leveling off, as the plane suddenly decided to climb up about five feet or so.  As I corrected for that, the wind dropped again and I ended up taking a really hard bounce.  There was no saving this at all, so I came up with the power and got back in the air.

Clearly, this was not a time for solo pattern work.  I requested a full-stop the next time around.  I was really rattled by the abortive touch & go, and it showed in a really ugly traffic pattern.  My confidence in my abilities had taken a big hit, and I was really concerned about getting the airplane safely on the ground.  But I was flying solo- nothing to do but quit worrying, concentrate that much harder, and get the plane down.  The wind continued to give me trouble- at one point on my base leg, I went from an 80-knot descent to hearing the stall horn blaring in an instant.  Stick the power, keep the plane flying, get it on the ground.  Final was the same story as the last time: varying winds keeping my descent rate changing.  I tried to keep extra speed, but the twitching airspeed needle made it difficult.  Then it was time to flare, and as if my magic, the wind seemed to stabilize, and I settled down for a rather gentle landing.

Taxiing back to the ramp was tough.  Apparently the adrenaline dump was affecting me; my legs were shaking and didn’t want to stop.  With the airplane parked and the engine killed, I breathed a sigh of relief.  On the one hand, I’d gotten rattled like never before in the air… but on the other hand, I’d worked through that, flown the plane, and come back safely.  All told, it was a bit of a sobering realization- soloing is great, but with the great feeling comes the undeniable fact that there’s no longer a security blanket riding along.  The buck really and truly stops with me, no dancing around it any more.

Back in the hangar with Scott, we debriefed my experience and then headed over to look at the many pieces of 546.  Since I’m a sucker for seeing how things worked, this was fascinating for me, following the cables from the pedals back towards the tails, seeing the pushrods from the stick, picking out all the familiar parts under the cowling… great educational finish to the day.

I know I already said this one time, but hopefully now I can get back to flying more frequently and get back on track.  Next scheduled flight is this Sunday afternoon.

Ah, quite a week and another dry spell… Last weekend was a sort of perfect storm of aircraft issues, with 546 down with a rudder cable issue and 393 down with a nicked prop.  After hearing of the issues on Sunday, I waited to hear about the status of the aircraft through the week, until Scott asked if I was up for a Friday afternoon flight.  Well, I’m pretty much up for flying any time, so I agreed.  Prior to this particular flight, I’d amassed nearly 19 hours of time.  Time-wise, I still need 40 hours minimum overall time.  Additional requirements to be met are 10 hours of solo (I have .6 so far), of which 5 have to be cross-country, 3 hours of simulated instrument (I have a meager .3), and 3 hours of night.  As far as airmanship goes, one major point is soft- and short-field operations.  So the general idea in the short-term is to get soloed at PDK so I can go out and work on my solo time, and also work on those soft/short-field ops.

Friday afternoon, the weather was lovely.  Light wind, clear sky, just a haze layer to deal with.  It would have been a great day to solo, but unfortunately the airplane wasn’t up for it.  We were flying 546, which still was awaiting replacement of the pilot’s rudder pedal assembly.  The rudders were still functional, though they couldn’t be adjusted fore and aft. (Luckily for me, they were stuck in the Green Giant position)  The mechanic had OK’d the plane to fly for the time being, but recommended against soling from the left seat, just in case there was a failure.  So that pretty much put the kibosh on soling, but there was still the opportunity to do some short/soft-field work, as well as for me to redeem myself after last week’s spotty pattern work.

Since PDK was getting a bit busy, we elected to head over to FTY for the pattern work. We had previously briefed short/soft-field work, so we reviewed soft-field takeoff techniques as we taxied and ran the plane up.  Even better for me, AOPA’s Flight Training magazine had a nice article this month on soft-field ops, so I was feeling ready to give it a whirl.  The basic idea with soft-field ops is to limit drag on the airplane from the soft surface.  As such, general principles to follow on the ground are to keep the stick full back to reduce weight on the nosewheel, and not to stop unnecessarily.  For the takeoff, one taxis onto the runway without stopping and begins the takeoff roll with the stick still full back.  On a normal takeoff, one waits for 45 knots to begin rotating the airplane and then proceeds into the desired climb attitude.  But since we want to reduce drag on the soft-field takeoff, the objective is to get in the air as quickly as possible- so the stick is kept back through the roll until the nose comes up and the airplane starts flying.  All well and good, but we’re going too slow to climb out of ground effect, so the next step is to push the stick forward, level out a few feet above the runway, and accelerate to a good climb speed.  This is actually pretty fun- if I were less focused, I might have imagined I was a Blue Angel performing a low transition.  Heh.

So the soft-field takeoff went well, and the short stint over to FTY was over in no time.  The aforementioned haze made it difficult to pick out the airport, but we got there and got in the pattern.  Landing #1 was to be my first soft-field landing.  The objective here is to land as gently as possible- digging the gear into a soft surface would be uncomfortable at best.  So the approach goes fairly normally until just before touchdown, when a smidge of power is added and the stick kept back to keep the nosewheel up as long as possible.  I found this to be a fairly straightforward operation, though I don’t quite have the feel yet for holding the nose up- but that’s what more practice is for.

After a few soft-field landings, we moved on to short-field work.  Here, the idea is to clear an obstacle on final, touch down at a predetermined point, and get stopped quickly and safely.  Carrying too much speed into the flare and floating down the runway is, shall we say, undesirable when there’s not much runway to work with.  We need that space to get stopped.  I found short-field landings more challenging- correct practice calls for starting the approach higher than normal and then steepening after clearing the imaginary obstacle.  I found myself overdoing the “higher than normal” part, to the point where it was difficult to get rid of all that energy and still hit my touchdown point on-speed.  This would have been a good time for a forward slip, but it’s been some time since I practiced those, and I’m reluctant to refresh myself whilst on short final.  And while I never quite conquered that too-high tendency, I got to the point of doing pretty well at hitting my touchdown point, but some more practice is definitely in order.

After several more landings, the afternoon was still young.  Scott inquired as to whether I wanted to go back to PDK or maybe do some maneuvering.  Since it had been some time since I practiced any maneuvers, I took the second option.  We exited the pattern and proceeded northwest, initially skirting the nearby Dobbins ARB  airspace.  After a bit, Scott called up Dobbins and asked if we could transit their airspace.  We got permission, and I got the interesting experience of flying right over the base.  Got to see some C-130s, C-5s, and UH-60s on the ramp… was hoping to spot a freshly minted Raptor from the Lockheed plant, but no such luck there.

Clear of the airspace, I performed slow flight, power-off stalls, and steep turns at Scott’s request.  Power-off stalls were a bit subpar- I was pitching over too far on the recovery.  In retrospect, I think this is because I never retrimmed the airplane from a 110-knot cruise down to 40-knot stalls, so there was a lot of nose-down tendency.  I’m used to needing some forward pressure on the stick in the recovery, but in this case, a simple reduction of backpressure was sufficient.  Steep turns went well, though I threw in a bit of a climb at the beginning of my first one and wasn’t quite getting banked enough.  These are the kind of things I can get out and practice solo once we get that knocked out.

The flight back to and landing at PDK were uneventful.  Back at the ramp, I was beginning to pack up my stuff when Scott made a proposal: he had to take 546 back to LZU anyway for the repair, so why didn’t I tag along and get some more time plus a bit of a night introduction, and he’d drop me off at PDK afterwards?  I was agreeable, provided I could make a pit stop first, so that’s what we did.  So I was opened to a whole new world of flying… it might seem obvious to say that things look very different at night, but… well… they do!  We were on course to LZU, and Scott kept asking if I had the airport, while I kept looking in the direction it should be, trying to pick up the beacon… all I succeeded in doing was catching some departing traffic.  We were instructed to follow another aircraft on downwind, and I was stunned when I finally picked up the airport… almost off my right wing.  Jeez, that snuck up on me.  Pattern and approach went well… on short final, Scott reminded me to be aware of night illusions making it difficult to judge my height off the runway.  This was verified when I touched down about five seconds sooner than I expected- it was a genuine surprise to me when we hit the tarmac.  Taxiing proved to be challenging as well… that little taxi light on the left wing doesn’t do a whole lot.  In fact, I may never complain about the dim headlight on my motorcycle again.

So ended a good, productive day of flying.  I didn’t get my PDK solo in, but I did get lots of practice for techniques I’ll need for the exam, plus a night intro to boot.  We definitely did more than just make holes in the sky.  546 should be fixed early this week, so hopefully I can get in my solo either one afternoon this week or next weekend, and then head out to the practice area sometime to do some solo maneuvering and navigation.  Won’t be too long before I’m doing solo cross-country… for that matter, won’t be too long before I’m sweating inches away from an FAA examiner.  The pace has been a  bit slow the last few weeks due to the holidays and maintenance issues, but I’m hoping we can get back into a good groove now and get this thing knocked out.

The big hope for today’s flight was to get in a solo at PDK, but alas, that didn’t happen.  Conditions weren’t all that great to begin with- winds had been gusty in the morning, and were originally forecast to calm down in the afternoon.  But come 4:00 and my arrival at PDK, they were still gusting decently.  Still, thanks to PDK’s runway 34, it was still possible to fly in this and at least give it a college try.

Before heading out into the brisk January chill, Scott and I discussed generally the state of my training, things we had to cover, so forth and so on.  High on the list are short/soft-field takeoffs and landings; I’ve become fairly proficient at the standard variety, so it’s time to be thinking about and practicing the variations.  We moved to the whiteboard and briefly discussed the reasons and procedures for short/soft-field operations.   Most of this I was at least passingly familiar with, so it was in a way a review for me.  I just need to go put in into practice.

Out on the ramp, I ran my preflight, hopped in, and 546 fired up surprisingly easily considering the temperature.  After a brief battle between my headset cable and the seatbelt, plus some additional time to get the oil temp up, we were taxiing over to 34.  First order of the day: perform a short-field takeoff.  No problem- get lined up, come to a full stop, go up with the throttle while holding the brakes, brakes off, rotate about 10 knots later, and immediately get stuck on Vx.  Scott had already gotten me in the habit of climbing at Vx initially, so this was in my comfort zone.

Unfortunately, immediately after this, things got squirrelly and stayed that way.  On the climbout, I was twitching the plane all over the place; too much right rudder, let it off, unintentional left turn, level the wings, not enough right rudder… so on through the climb.  Continuing the theme, I cut my crosswind leg short and then drifted a bit towards the runway on downwind.  My pattern didn’t really have a base leg- just one continuous turn to final.  Then my speed control was iffy on final, and as I recall, I took a big bounce on landing.  Whatever it was, it was not pretty.  On the climb back up, I silently cursed my regression.  I’d essentially spent the entire pattern way behind the airplane.  Not good.

Things did get better from there, but never really great.  I had a few more bouncers, plenty more trouble with speed control in the pattern, and I topped it off by mostly clamming up on the radio- a really essential part to flying at PDK, given the frequent special instructions in the pattern.  While I don’t think I really crossed the boundary into unsafe territory, nobody needed to tell me that this wasn’t a pre-solo performance by any means.  In the end, it was just an hour or so of pattern work… which, in fairness, I could have used.  I hadn’t done any since mid-December, several weeks ago.

Once the plane was tied down, I had time to evaluate myself.  The primary problem, really, was a mental one.  From the moment I started overcontrolling the airplane in that first climbout, I was behind the airplane either a little or a lot.  That’s a tough hole to dig out of in the air, especially when you start on a low note.  I simply wasn’t mentally prepared before going in the air.  I can’t point to any particular source of distraction, but there was definitely something.  Perhaps I had visions of coming out, sticking three landings, tossing Scott out, sticking three more, returning to the ramp amid cheering onlookers, scoring a date with the supermodel who’d just happened to be watching from the observation park… you know, the usual perks that student pilots enjoy. 

In any case, it gives me something personally to work on in the future- mental preparation.  I actually used to do this before going to work on busy weekend nights- spend a few minutes clearing my mind and getting things lined up- and I found then that it made a marked difference in my performance.  Seems like this is a habit I ought to get into again.

In the meantime, I’m focused on surviving the blizzard conditions forecast for tomorrow night, and then getting back in the swing of things with a good flight this weekend.

I’ll give you all a moment to hum some Aerosmith and get that out of the way.

Yesterday I broke a horrendous 2+week no-flying streak.  Was out of town for Christmas, and then my first scheduled flight last Wednesday got canceled because the city of Atlanta decided to enforce the area I’d been parking for work for, oh, eight months.  Since they towed my vehicle, that made it a bit difficult to get out to PDK to fly.  But I had already scheduled a larger block for Saturday afternoon, a time to do my first cross-country flight.  This flight would also have a second purpose; to go up to Chattanooga, TN and deliver some Christmas presents for my niece, since my brother wasn’t home for Christmas.

First things first, it was COLD Saturday.  Below freezing all day long, and here I am with just my motorcycle to get around on.  Arrived at PDK a bit late, with some preliminary flight planning in hand.  I had planned a direct route to CHA, which was made easy since PDK has a VOR on-site and CHA has one nearby.  Simple matter of planning to fly a radial from Point A to Point B.  My plan still needed some tuneup- most notably, I’d neglected to account for magnetic variation.  Still, after 45 minutes or so, we had a presentable plan.  Scott then called while I listened in to file the flight plan and get a weather briefing.

Out on the ramp, I preflighted the airplane and then called my brother to let him know what time to expect us in CHA.  In the cockpit, 546 let it be known that she wasn’t a fan of the cold weather, but after a few tries, she fired up.  A quick taxi out, runup complete… well, oil temp is still low.  So we sat for a few minutes until the engine had warmed up sufficiently.  On takeoff, the stiff headwind made for an impressive climb rate, but a less-than-impressive groundspeed.  At my planned cruise altitude of 4500′, the air was substantially bumpy.  I fought it for some time, but eventually surrendered to Scott’s recommendation to climb to 6500′.  Up there, the air was far smoother, and the airplane much less work to fly.

Along the way, I also got an introduction to en route radar service.  Once we’d got clear of the PDK class D, we dialed up the Atlanta center frequency and requested flight following.  This is an elementary level of radar service- we still fly under VFR and navigate on our own, but the controller gives us traffic advisories.

The next new challenge for this flight was working in the class C airspace around Chattanooga.  Rules for entering are similar to class D- two-way radio comms are sufficient.  However, the size of the airspace is larger, and there’s an additional step between you and the tower- the Approach controller.  If we hadn’t been utilizing flight following, it would have been our responsibility to dial up Approach inside the outer area.  However, in this case, the Center controller simply gave us instructions to change to the Approach frequency at the proper time.

Approaching CHA, I was set up well to fly a nearly straight-in approach, and since there wasn’t any other traffic around, that was what I got.  It’s a bit challenging to know where to drop flaps for the straight-in; in a normal pattern, I start my descent abeam my touchdown point, but that reference is of course lost if I don’t fly a downwind leg.  But I flew the pattern fairly well, and made a nice landing.

My brother was waiting in the parking lot, so I let him in, introduced him to Scott, and we walked out to the plane to retrieve the gifts.  Back inside, after a short discussion, we elected to visit the nearby Rib & Loin for a small lunch.  This was good for me, as I’ve not yet found a decent BBQ place in Atlanta. (though I have some recommendations to check out)  Back at CHA, I paid for the top-off and ramp fee, we did a quick weather brief and some planning, and hopped back in the plane.

Here was another crash course- when I contacted ground, the instructions I got back were phrased differently from what I’d heard at PDK or LZU, and the controller admonished me for not reading them back correctly.  Scott informed me that this was because CHA did modified IFR clearances for departure, and thus the readback requirements were more stringent.  I then proceeded to get on the wrong taxiway, but we made it to the runway OK, and before long, we were headed home.

This time, the stiff headwind that slowed us down became a lovely tailwind, and once we were at altitude, we worked up to nearly 150 knots groundspeed.  As such, the trip home went quickly.  Along the way, Scott had me get out a sectional and attempt to figure out our location based on landmarks.  It took me a few minutes, but I got it narrowed down to a general area.  We proceeded on course to PDK- again, made easy thanks to the on-location VOR- and before long I was in the pattern for 34.  Here the wind got me, and I ended up way below slope at the end of my base turn, and I actually had to level out for a bit on final, but once I got back on slope, I came down for another decent landing.

Back in the (WARM) office, we debriefed the flight.  I still have to solo at PDK… maybe later this week will be the right time for this.  We’ll just have to see!

So today, it was time to set aside the solo afterglow and return to the dreary world of dual time.  Well, not that dreary, but sometimes I do surrender to the needs of poetic license around here.  Today was really the first decent day since I soloed Saturday morning- the last three days were filled with joys such as heavy rains and fog.  Today, however, was nice and sunny, though a bit breezy.  I excused myself from the office at 3 and made my way over to PDK.  Earlier, I’d gotten a text from Scott that 546 was sporting a shiny new battery and was back in service.  Good to know.

In the office, we busted out the ASA syllabus to figure out what to do today.  I still need to solo at PDK, but as I mentioned before, today was a bit breezy, and on top of that I need to step up my radio game a bit to handle the traffic.  Instead, Scott decided on some simulated instrument time, unusual attitude recovery, and general maneuvering practice.

Out on the ramp, after preflighting and firing the plane up, I handled the comms and got us out to the runup area at 2L.  Here was a rather impressive traffic jam; the Cessna exiting the runup area was #5 holding short, and after my runup, no one had yet left.  I had to exit the runup area back towards the ramp to swing around behind that Cessna.  Truth be told, with the long parallel runway closed, I’m surprised I haven’t seen a backup like this before.  Anyhoo, after some sitting, we were finally #1, and then cleared to takeoff.  In the air, I did a big no-no; winds were generally from the west, tending to push me off the centerline to my right… that is, towards the parallel.  Since it’s closed, this isn’t an immediate safety issue today, but other times, drifting over there after takeoff could have serious consequences.  Point taken; get a ground reference to maintain that course on takeoff.

I was climbing through about 2000′ when Scott brought out a wonderful gift: Foggles.  For those not in the know, the point of Foggles, as well as other “view-limiting devices,” is to make it difficult to see outside the airplane, thus forcing the hapless wearer to fly on instruments.  Flying off the instruments is quite a bit harder than one might think- for a left-brained guy like myself, I tend to think of it just in terms of data processing; if A, then B.  Which it really is, but there are multiple instruments to monitor, each one working the same way; look for deviation, maneuver to correct, scan other instruments, come back, detect deviation again, repeat, over and over.  It was surprising the tendency I had to put the plane into a turn.  Just completing the climbout and leveling at altitude was a challenge.

The Foggles stayed on long enough to do some basic maneuvers and to introduce standard-rate and timed turns.  By performing a standard rate turn, the airplane will complete a full circle in two minutes.  Standard rate turns are particularly useful in the case of a direction gyro failure; the magnetic compass is only really accurate in straight, unaccelerated flight, so attempting to turn to a heading based on the compass can be difficult.  Instead, one can use a timer and a standard rate turn to make a predefined heading change, and then refine with the compass as needed.

Eventually, the contraption came off my head, and I was perceptibly disoriented to have my visual reference back.  It was strange to see Lake Lanier off the nose, when the last time I saw the ground was just a few miles out of PDK.  Next we discussed “unusual attitudes,” which is a rather benign term for a serious issue.  Say I were to look down for a few seconds, checking a sectional or some such, and look up to find myself in an unintentional climb or descent.  It’s important to be able to recognize the state and recover assertively.  The way this is practiced is for the student (me) to close his eyes and think about bunnies or some such while the instructor takes the plane, yanks and banks a bit to disorient eh student as to what’s going on, and then have the student open his eyes and recover.

It was actually kind of fun.  Close my eyes, hum a show tune, open them… nothing but sky, cut power push the nose over, level the wings.  Not too bad. (though later I’ll have to do this under the hood)  The last one was a bit disturbing, though- I opened my eyes and saw nothing but earth under me.  Descending right turn, maneuver to correct, and I hope I never actually see that in flight. (unintentionally, at least)

I wrapped up with a power-off stall and a few steep turns, and then we headed back to PDK.  On the way, the Foggles came out again, while Scott vectored me into PDK.  I had no idea how far this was going to go, but they stayed on until I had entered the pattern and turned final.  Remember the disorientation when I took them off the first time?  It’s even better when you’re on approach.  Between the instrument-visual transition and the wind, I did a pretty ugly touch & go.  We stayed in the pattern for a few more, and then did the full-stop and went back to the ramp.

Sadly, with the holiday coming up, it’ll probably be almost two weeks before I can fly again.  I’m heading home for Christmas Saturday and staying through the next weekend, so I’ll have to work to retain everything when I come back.  Maybe then I can take care of the PDK solo and be ready to go out to the practice area on my own in January.  Cross-country solos will probably be here before I know it…

I mulled over a witty title for this post before deciding on the minimalist approach.  Bottom line: As I type this, it’s been just under two hours since I was in the plane, and I still break into a giant grin about every five minutes or so.  I can’t help it.  That sentence keeps hitting me like bolt of lightning… driving down the road, ho-hum… wait, I flew solo today.  *cackle*

It’s been an interesting week since last Monday’s breakthrough performance.  Given the choice, I would have gone out the next day, but the weather’s been iffy this week.  Thursday looked like the best chance, so I booked 546DC that afternoon.  But in the wake of heavy rains Tuesday, winds were brisk both Wednesday and into Thursday.  15 knots gusting to 25 isn’t great for anybody, much less a student with no help.  So we rescheduled for Friday afternoon.  I spent the workday Friday watching the clock like a hawk, until I got a call from Scott.  546DC was broken- apparently no juice from the battery at all.  Still, I decided to head out from work early and over to PDK to review my pre-solo written exam with Scott.  In the meantime, I was checking the schedule for the DA20 at Gwinnett.  It was free Sunday afternoon, but Sunday’s forecast called for lots and lots of rain.  However, she was free Saturday morning before 11:30.  Rain was expected to roll in Saturday afternoon, but I figured it was worth a shot, so I scheduled a 9 AM flight.  The pre-solo exam review went well; Scott was skeptical about the weather for Saturday, but agreed to give it a whirl.

I spent Friday evening watching the weather like a hawk, all the while chanting to myself, “The rain will hold off.  The rain will hold off.”  Got up this morning, and things were looking good.  Rain was looking to be arriving around noon; in the meantime, the clouds were high enough to fly under.  Winds were a bit stiff, but at least well-aligned with the runway at Gwinnett.  At 8:15 I headed east, willing the truck to hurry up and get warm before I developed frostbite.

I arrived at LZU a couple minutes ahead of Scott.  Up in the office, Bruce informed us he had put the charger on the plane to make sure it had juice to get the plane started, despite the near-freezing temps.  Right there in the office, Scott signed my logbook and medical certificate.  Now I just had to prove I was up to it in the air.

Actually, first we had to bring the plane to life, which proved to be no easy task.  We gave it a few tries, coming close a few times, but never getting it to catch.  We sought help from Bruce, who joined me in the plane and tried some more.  Same thing- every couple of tries, the engine would fire a few times, but never really catch.  Things were starting to look bleak, and I confronted the possibility of a third postponement, especially after the last start attempt, when the prop stopped.  The battery was nearly dead.  One more try- and then, like magic, she caught.  Bruce and I sat for about ten minutes to get the engine warm, and then he swapped with Scott.  This time, the engine fired right up, and it was go time.

In the runup area, things were iffy again.  On testing the mags, the engine ran noticeably bad on right only.  And again, I thought we might be a bust after all, but Scott told me about how excessive idling with the mixture full-rich could foul the plugs.  We ran the engine for a bit with the mixture leaned out, and it cleaned up satisfactorily.

In the air, my task was deceptively simple: show Scott three good full-stops in a row.  Working against me was the wind- it was well-aligned with the runway, so there was a minimal crosswind component, but still stiff at about 10 knots.  The first effect of the wind was a serious boost in climb performance.  Normally, at the 500′ AGL mark, I bring the flaps up and turn crosswind; I did this today, and Scott reminded me not to turn crosswind before reaching the end of the runway.  That’s the first time I’ve ever had to worry about that…

Things got off to a shaky start with the first landing.  Pattern was good, but I got way fast on short final; up near 80 knots instead of the proper 65.  Flare was ugly, and I took a hefty bounce…up with the power, we’re going around.  Not the performance I wanted today at all.  Doubt crept back in again… was I going back to the days of high flares and trampoline touchdowns?  I resolved to do better next time around… and I did.  Then I did it two more times.  As I rolled out on #3, Scott called the tower, and reality started to set in.

“Tower, 1JA, I’m going to solo my student, can I come up to the tower and watch from there”

“Sure thing.”

So I taxied down to the base of the tower.  Before getting out, Scott made sure I was OK.

“Ready for this?  Have any questions or concerns for me?”

“Oh, I’ve got plenty of concerns, but I think I’ll be OK.” (I probably would have failed a lie detector test on that one)

Just like that, I was lone.  In the airplane.  In the left seat.  With the engine running.  To my right, there was a cavernous space.  It seemed so… wrong.  I uttered a few things that would probably best not be repeated in mixed company, but there was no one to hear them but me.  There were a few moments of hesitation.  I had to do it; it was time, and I knew I was ready, even if my emotions strongly disagreed.  Finally, I got up the courage to call ground and get taxi instructions.  That broke the freeze; my right hand obeyed me and moved the throttle, and I was moving.  Alone.  Down at the runway, I keyed the mike.

“Tower, 1JA is holding short 7.”

“1JA, you’re still on the ground frequency.”

*slap*  OK, take 2.

“Tower, 1JA is holding short 7.”  No response.  That doubting part of my brain became convinced that the radio had just broken.  I think I was expecting some random problem to crop up and stop this madness.  After about 30 seconds, I repeated my call.

“1JA, hold short.”

I waited.  Then I waited some more.  Finally, tower called and informed me Scott was on his way up, so he was holding me for him.  I was OK with this, perhaps out of some malformed sense of procrastination.  After about five minutes, I thought back to the plug fouling issue earlier… I didn’t want that to happen again, so I made use of Scott’s info and leaned the plane while bringing the throttle up.  I waited like that a few more minutes before getting the takeoff clearance.

“1JA, fly left closed traffic, cleared for takeoff runway 7.”  A remarkably calm voice issued from my mouth and repeated the clearance.

And then I was sprinting down the runway, feeding in right rudder to maintain centerline.  45 knots came up fast, and I was flying.  Actually, I was FLYING.  Look, I’ve been a flying groupie for a while.  I’ve read plenty of first solo stories, all of which contained some reference to amazement at the improved performance with just one person on board.  Even though I understood this and expected it, I was unprepared for the magnitude of the change.  Between the light load and the headwind, I felt like I was climbing in an F-15.  If I had maintained Vx or even Vy, I would certainly have been at pattern altitude before even getting to the end of the runway.  As it was, I climbed at about 75-80 knots and still found myself pulling power on the crosswind turn to level at 2000′.

Landing #1 was one of my best yet.  I leveled out just right, flared nicely, and touched down gently.  This hits on another little nugget from the doubting part of my mind- I’d made good landings before, but that part of my brain suspected I was getting help from the right seat.  Obviously, this wasn’t true, or I never would have soloed- but still this was the first landing where there was no denying that I did the whole thing.

Back around for #2.  I still was stunned by the climb performance, and actually overshot pattern altitude by about 100′.  Abeam the touchdown point, power comes out, flaps to takeoff, start the descent.  This time, I got distracted by something- perhaps that still-bizarre sight of the empty right seat- and didn’t pay attention to my descent rate.  As I turned base, I glanced down and was alarmed to see I was still at pattern altitude!  OK, I can deal with this… drop the last notch of flaps early, get slow, pull power.  I was still a bit high turning final, but I got back on slope and things were looking good until the last second- I leveled a bit early, and then as I was flaring, the left wing dropped and the plane drifted left of centerline.  The idea of going around entered my head at the same time the left wheel touched down and the plane bounced a bit.  Going around was still on my mind, but I got the plane level, and put it down smoothly the second time.

One more to go.  This time, I kept a better eye on my descent rate, and maintained speed much better on final.  I leveled out high again, but recovered nicely for a decent landing.  A little rougher than I’d like, but not unsafe by any means.  Couple minutes later, I was picking Scott up for the trip back down to Advanced.  I didn’t really let myself grin until I saw him walking toward the plane.  It was like it was some kind of affirmation that I really had soloed.  I was in the plane, and he was on the ground.

As we taxied back to Advanced, we talked about… something.  I think I was making intelligent conversation, but I wouldn’t swear to it.  Up in the office, I made use of the heretofore-ignored “Pilot in Command” column of my logbook.  .6 hours solo, 3 landings.  Scott and I then headed over to the on-airport restaurant, the Flying Machine, where I enjoyed a post-solo cheesesteak and fries, which Scott generously paid for.  That random grinning thing was really taking hold here… eat a french fry, chew a bite of cheesesteak… wait, I just soloed.  *cackle*

So now it’s time to move beyond basic maneuvers and pattern work… there’s plenty to learn still.  For now, I still need Scott’s OK before any solo flights, and a logical next step is soloing out at PDK and then getting permission to do more than just tool around in the pattern.  It probably won’t be long before I’ll be doing solo cross-country work.  For that matter, it won’t be long before I’ll be going for the checkride.

*whew*

For the record, it was Scott who first suggested that magic pills may have been involved in today’s flight.  And before I go further: If anyone from the FAA happens to be reading this, the pills in question are strictly figurative.  Honestly.  Now about this whole flying thing… after a series of iffy landings Sunday, today’s flight was pretty much a total turnaround.  Neurons that had been previously groping aimlessly about in my head gathered to form useful bundles of knowledge and coordination.

Actually, to rewind a bit, the flight looked iffy for most of the day.  I arrived at work early to offset leaving at 3 for PDK, and as I kept an eye on the METAR throughout the day, things were questionable.  Most of the morning saw solid or broken clouds at about 1200 feet- too low to fly under safely.  But as 3 approached, I saw the reported clouds breaking up south of the city.  I stuck my head outside just before three, saw blue sky and sun off to the west, and decided to go for it.  I was rewarded with continued breaks in the clouds on the drive over to PDK.

Up in the Advanced office, Scott presented me with a take-home pre-solo exam.  I also have to do a shorter written exam in front of him before I’m good to solo, but that’ll be another day.  I tucked the exam in my bag and we trotted out to the plane.  Battery was a bit low, but it fired up and away we went.

Today’s practice was to be nothing but pattern work.  Instead of heading to our old haunt in Monroe, we took the short hop over to Fulton County. (KFTY)  It’s much closer than Monroe, and the only thing to watch out for is the Dobbins ARB airspace bordering FTY to the north.  Luckily, there’s a prominent smokestack of some kind that makes for a nice marker- stay south of it, and you’re A-OK.

Up in the air, the apparently clear skies belied the presence of a substantial haze starting around 2000′.  We briefly went up to 2500 before descending back down to pattern altitude at FTY.  Well, actually, I ended up at about pattern altitude +200; I hadn’t checked the field elevation and made the incorrect assumption it was nearly the same as PDK.  Perhaps as a result, as I made my turns to base and final, I found myself pretty high.  I was starting to think it was all going to begin again, but an odd thing happened: I got on slope, came over the numbers nicely, if a bit high, and the sun presented me with a nice visual aid- my own shadow to my left.  It made for a nice reinforcement of my height above the runway, and I leveled out, bled off some speed, and touched down nicely, maybe a bit hard, but no bounce.  Power up and go around for the next time.

The amazing part was that it wasn’t a fluke.  Next time around, I got pattern altitude right, and despite a looooong extended downwind from the tower, I came in nicely for another smooth one.  Probably my two best landings so far, back to back.  “How did that feel?”, Scott asked.  Well, pretty nice indeed.  #3 wasn’t quite so nice; I took a little bounce on it, but settled down nicely after that.  The next two were good ones, too.  I wasn’t sure what had happened to me.  24 hours saw me go from a big bounce and go-around to five passable landings in a row.

After #5, we pointed back east towards PDK.  I called up the tower and asked for one more touch & go followed by a full stop.  I got a 2-mile straight-in for 2L, but after a series of extended downwinds at FTY, I felt good about making it work… and I did.  then I wrapped up the day with my best yet- leveled out a few feet up, easing back on the stick, watching the airspeed drop out of the corner of my eye.  The stall horn started to buzz, I eased the back pressure a bit, and we were down, no drama at all.  Uncanny.

It was hard to stifle a grin afterward.  The last few flights had been frustrating; I wouldn’t go so far as saying I didn’t enjoy myself, but it was a near thing.  Those days, I’d come back to PDK feeling beat down, worn out… today, I would have happily stayed up for another hour if not for that pesky sunset issue.  It all came together and suddenly, it was tons of fun again.

There are other areas where I see myself improving, too.  It’s becoming less of a chore to hold left rudder in the climbout to stay coordinated.  Seemed like before, I was always glancing down, seeing the ball to the left… ok, more rudder…  Today, for the first time, I looked down and saw that I was putting too much left rudder.  I’m still far from perfect, but it’s starting to come to me.  I also stayed (mostly) on top of comms.  In the pattern at FTY, I dealt with long downwinds, waiting for the tower to call my base turns, getting a left 360 to let a jet land in front of me, etc.  I even kept the plane pretty much on centerline on the rollout at PDK.  Lesson learned; easy on the brakes.  They love to send the plane hither and yon if you let them.

So it looks like, conditions permitting, next time out could well be solo time.  I’m shooting for Thursday afternoon; I feel like I’m on a high and I don’t want to sit around for six days to go again. (Sunday is the next day where the weather looks tolerable)

Short version: 12.5 hours and no solo as of yet.  In the grand scheme of things, it’s not as if I’m way behind the curve or anything; but I suppose I had some odd (and highly unrealistic) fantasy that I would take to the stick and throttle like Art Scholl or something.  Heh.  Ok, I’m over myself now, let’s talk about the real world some more.

As the title alludes, the thing preventing me from soloing is that evil slice of time at the end of short final.  I’m getting better, but I’m still far from consistent- so today’s flight essentially consisted of going out to do some touch & gos and pattern work.  PDK being, well, PDK, this essentially requires going elsewhere; our chosen target was Monroe, GA. (D73)

My first concern going into today was the state of the airplane; I was actually supposed to fly this past Friday morning, but the battery was too low to get the engine started; then once we brought out the jumper cables (yes, they do exist for aircraft), the ignition switch proceeded to fail.  My concerns were not allayed when I arrived at PDK and noticed old 546DC with the canopy cover on- there had been reservation before me, and they would have left the cover off after their trip.  Up in the office, Scott confirmed that the previous folks hadn’t gone- the switch was replaced, but the battery was low again.  Out came the cables again; with the help of the other instructor on duty, we got the airplane started and the day was saved.

Taxi and takeoff were uneventful, save for a dude in a Baron who put a lot of effort into getting in front of us for the taxi and then proceeded to sit at the hold-short line for at least five minutes waiting on an IFR clearance.  Oh, and since the long parallel runway was closed for resurfacing, I had the somewhat odd experience of taking the runway with construction guys in hard hats about 75 feet away.  But before long, we were pointed east.

Since one thing offered today was a decent wind, I got to work on using trial-and-error to work out a wind correction angle.  Not following?  Well, unless you’re flying directly into or away from the wind, you’re not going to track a course identical to the aircraft’s heading; the wind pushes you off-course.  So in order to maintain a desired course, it’s necessary to point the nose into the wind slightly, and in order to evaluate the wind correction angle, some kind of reference is needed.  In this case, Scott set up the VOR receiver to track the course to D73, and I also had the course line on the GPS for extra guidance.  In fact, the line on the GPS gives a nice visual of the crab angle; I could look over and see the little airplane pointing to the right of the course line, yet tracking straight.  All in all, an enjoyable exercise.

Arriving at Monroe, we overflew the field, got a look at the windsock, and picked runway 3 for the day’s fun.  Alas, but the wind was abut 45 degrees of runway heading, so it was going to be a day of learning to deal with the crosswind.  Has to be done… I established my downwind, and flew a decent pattern.  I’ve got a pretty good handle on maintaining a good rectangular course and keeping my speed right in the pattern.  All was well until I turned final… whoa, that wind does a lot more than I expected.  I felt as if I was fighting it all the way down, but in the end I was over the numbers at a decent height.  It all went to crap from there… ugly flare, long float, and then a bounce that might have been impressive under conditions.  Scott reinforced my thoughts; that a go-around was in order.  Up with the throttle and flaps, and we’ll try again.  Second time around was better; good pattern, good final, pretty good flare, smooth touchdown, and we’re going again.  I was more prepared to deal with the wind this time, and wasn’t so far behind the airplane.

At this point, we took a quick break; a glider had been staging on the ground during our first two times around the pattern, and they asked to go after our second one.  No problem… we headed west and found a water tower so I could try turns around a point with some real wind.  Having just come from D73, and with the field still in sight, I had a good sensation of where the wind was coming from, and stayed on the tower fairly well, though I still have a tendency to gradually spiral in towards my point.  Scott also showed be a little cheat for the ground reference maneuvers- glancing at the ground speed readout on the GPS.  Since I’m (hopefully) not playing with the throttle in the turn, my airspeed should stay more or less constant; so checking the ground speed tells me whether I’m in head- or tailwind territory.  It was actually pretty impressive to watch; as I turned away from the wind, I watched the ground speed jump 10 knots in about 15 seconds.  Good tip.

Well, the glider and tow plane were clear of the field, so back to the pattern we went.  Since we were roughly parallel to the runway, we just flew a really wide downwind instead of angling in for a close pattern.  This required me to adjust my cues a bit, since we’d have a base leg about twice as long as normal.  This landing wasn’t bad, except that I floated way down the runway; as a precaution, Scott decreed a full-stop.  No problem, except there I go zigzagging across centerline on the rollout.  I really must stop trying to steer with the brakes on rollout.  There’s plenty or airspeed to use the rudder, and the brakes are sensitive enough that steering that way tends to become a losing battle and makes things get hairy in a hurry.  Nobody likes that, least of all me. (Scott may disagree on that point, though)

After taxiing back, we shot a couple more touch & gos, none of which were stellar, but then again there weren’t any go-arounds either.  After #2, the glider wanted to go up again, so we headed on back to PDK- my time block was starting to run out anyway.  On the cruise back, I was feeling frustrated.  It seems like the touch & go sessions always tax me near my limit, and just five or six times around the pattern can be pretty draining, especially with a crosswind like we had today.  I suppose what gets me about this is that it’s really the only thing that I feel isn’t coming to me easily at all.  Climbs, descents, turns, stalls, slow flight, ground reference- not bad at all.  If I bugger one of those up, I correct and go on.  Perhaps part of the thing with landing is that it’s not a constant thing I can correct and work with like flying straight and level.  Instead, it’s about 15 rapid seconds followed by five minutes to think about it.

Anyhoo, the cruise back was, in a way, a welcome relief, a respite from the concentration of pattern work, a time to get myself back under control and in control.  Scott asked if I wanted to do a touch & go or two back at PDK.  Actually, yes.  I always feel like that last landing of the day is a chance to redeem myself for my earlier transgressions, and I had felt like I left Monroe on a sour note.  PDK was a bit busy, but the tower controller was amenable to giving us a touch & go.  This one went much better, as did the following full-stop, though I did a bit of zigging again and even locked up a brake a couple times on the rollout.

Back at the ramp, as  I took off my headset, I had a revelation.  This was my first flight where I’d not once thought about how the headset was hurting my ears.  The reason was that I had my newly acquired Lightspeed set in hand, or maybe on head is a better term.  I’m not convinced the ANR on these does a lot, but then again, it is the bottom-tier model.  I’ll have to try switching the ANR on and off in flight to see how noticeable it is.  Regardless, the new set is worth it in sheer terms of comfort.

In the office, we debriefed, discussing flaring some more.  For my part, despite my issues, I felt a lot better at Monroe today with maintaining my glide slope by visual reference.  It was probably a questionable thing that I came into this knowing how to read a VASI or PAPI (glide slope indicators placed beside the runway), and I’d come to rely on them too much.  Since Monroe lacks these things, I’m forced to do without.  Last time out there, I actually felt lost on the slope a bit, but today I had a much better feel for the slope.

Sounds like next time, we might go west to Fulton County instead of Monroe.  The main benefit is that it’s far closer to PDK than Monroe, so there’s more time for pattern work and less time boring a hole in the sky.  And Lord knows I need more practice flying in the pattern than cruising.  The downside is that the FTY airspace borders the airspace around Dobbins ARB- better keep that pattern good and close! (Who knows, maybe I’ll see a Raptor fresh off the assembly line)

Next flight: Monday afternoon.