Two Thousand Four Hundred Seventy Three

That's a lot of days.  Over six and a half years.

Like so many pilots who don't fly for work, my own flying took a back seat to the rest of life for far too long.  Without a decent place to rent a plane on short notice and receive some periodic dual time, plus a demanding work schedule taking me outside the U.S. for weeks at a time, flying just couldn't be a priority.  That's not to say I haven't been busy...

Some of the other things that have taken up my time:

• Teaching two kids how to drive
• Continued work in Canada and North Carolina
• Employer closed up shop, so started two businesses, now self-employed
  
• Three high school graduations, sending two kids to college and one into the National Guard
• Several college campus tours, road trips, and camping trips all over the western U.S.
  
• Watching a total solar eclipse
  
• Countless cross country and track meets, soccer games, mountain bike races, music festivals, and school concerts
• Supporting wife and daughter Ragnar marathon run and motorcycle license courses
• Working in Australia again, plus Africa and Peru
• Taking a motorcycle trip and a safari trip in South Africa
• Buying three cars, an RV, and two motorcycles
• Catching two local hot air balloon festivals
• Riding in a motorcycle parade
• RV trip to the Oregon coast
• Visiting and investing in a startup kit aircraft business
• Attending the Red Bull Air Races
• Earning a PMP certification
• Marrying off a daughter, hosting a wedding luncheon
• Sending kids on school or volunteer trips to Costa Rica, Italy, France, Australia, California
• Taking a concealed carry firearms course
• Working in South Carolina and Nevada
  
• Long motorcycle trip along the California and Oregon coasts
• A Caribbean cruise and New Years Eve in Miami
• Backpacking trips in the Beartooth and Uintah mountains
  
• An Eagle Scout Court of Honor
• Seeing two of our favorite comedians, favorite TV show hosts, and favorite bands live
• Attending Maker Faire
• Taking a long RV road trip from California to Oshkosh
• A pesky pandemic
• Several major home improvement projects
  
• Learning Spanish 
• And coming soon...a new grandson

As our lives start to transition into the next chapter, all of a sudden flying is possible again.  But it couldn't be as simple as just calling up the old flight school and scheduling some time, could it?

First, I opted to renew my medical through BasicMed.  This is available if you have had at least a third class medical (and not had it revoked or denied) in the previous ten years.  While I could have still been medically eligible for a full third class, the time and availability of an AME made it such that it was simply easier and faster to go the BasicMed route.  

Then, I would need a flight review.  My original school was technically available, but they no longer rent planes if one is not enrolled in a formal course to obtain a rating.  So, even if I could have done the review there, I would still not have a place to rent and stay current.

Plan B entailed calling up a different school about the same distance away at a smaller airport.  They also work with the local college and therefore get busy when school is in session.  But since we're still in the summer months, a plane and a CFI were easy to schedule.  I was able to schedule two flights in the same day to get back up there and knock off the rust.

While I have several hours in a 172, I would have preferred "going home" to the DA-20 given the amount of time away from flying.  Since this new school only has 172s and 152s (besides several larger and more complex models), I opted for the 172 since that would likely be the model I'd rent in the future.  We flew two different planes on Day 1.  

The morning flight was in a model with basic "glass" instrumentation.  Rather than the large G1000 screens which dominate the panel and contain virtually all of the key information, this older plane was retrofitted with a small Aspen display - whose small size belies the high volume of information contained on the screen.

 Rather than spend much time on the ground, we went straight to flying.  I did the preflight, which is so ingrained and routine, I barely needed the checklist even now.  Then we hopped in and I took a bit to get all situated.  The instructor walked me through a few of the instrument steps, but we really only focused on those that would be relevant for today's short flight - setting the altimeter, working the radios, interpreting the dials, etc.  As I went through all the steps of getting the weather, picking a runway, listening to other traffic, and going through the rest of the pre-takeoff steps, I said out loud almost everything and what I was thinking about.  This helps any instructor know what's going on in your head and why you might be doing something in a particular way.

Then it was time for takeoff!

This is a small airport with no control tower and just a single runway.  So we listened and looked for traffic, then opened the throttle and accelerated down the runway.  Most everything came back from my memory in an instant.  Keep your hand on the throttle, let the plane accelerate to rotation speed, gently pull back on the yoke, continue to accelerate in ground effect and gradually let the nose point at the right angle to climb out at Vy (the best rate of climb airspeed).

The instructor wanted to focus on slow flight and stalls.  This isn't too surprising, since that's where many students (and licensed pilots) have trouble and one of the first things to degrade after not flying for a while.  But in my case, this wasn't too bad.  I struggled a bit to find the right combination of pitch angle and power to achieve the right speed without losing altitude, but after a couple of tries got it good enough (not perfect by any means).  Rather than the instructor just telling me the right combination, he let me sort it out and kind of wallow through the air for a bit to see how I did.  Stalls were actually pretty uneventful.  You don't have to be super-precise with any particular item, other than keeping the wings level and staying on heading.  Both power-off and power-on stalls were pretty decent, but again could use a little polish.

The instructor threw in the not-unexpected practice engine failure, and I immediately went to tunnel vision trying to find a place to land.  The main problem I had here was focusing on a place that was too close and then needing to lose altitude and energy to make a landing.  But I neglected to do the normal "flow" of the emergency checklist to practice checking fuel and engine to attempt a restart.  Also, I kept needing to change my target landing spot.  I should have used slips, turns, or even flaps to start descending.

The afternoon flight was similar to the morning, but in a plane with slightly less power.  That meant that as we climbed out in this warm, high altitude environment, we pretty much stopped at about 7,000 feet altitude.  The instructor mentioned we may have been caught in a downward-flowing mountain wave, and this was completely foreign to me.  While I've read about them, it didn't occur to me that we could be in one, and looking back it would have been good to talk about the exit strategy if I was encountering rising terrain I couldn't outclimb (in this case we had plenty of altitude). 

We made a total of seven landings, three in the morning and four in the afternoon.  None of them are what I would call great, but they were all within acceptable margins of safety, on the centerline, and allowed for a relatively smooth touchdown.  But on one end of the spectrum, I was far too fast on final, mis-remembering the approach speed (which I had been remembering all the landings before...??).  On the other end, I had one picture-perfect approach which came apart about three seconds before touchdown due to a downdraft or windshear and I had to add a bunch of power before floating down the runway again.  

The big takeaways here, for patterns and landings - watch the speeds, and put in flaps at the same point of the pattern each time.  I also need to watch the left crosswinds since I kept overshooting the base to final turn, which was made worse due to flying a high-wing plane and not being able to see the runway creeping up on me.

Day 2 was a non-flying day due to low clouds and rain, so we did the ground portion of the flight review.  This was also uneventful and I only had to look up a couple of technical items.

Now on the schedule is another flight or two next week to keep working on the basics until I can be fully signed off for solo flight again,

One More for the Road

Winter is coming and so will my trips to Canada.  Less time at home and cruddy weather meant I wanted to get one last short flight in today.  Luckily the weather system at hand is a slow-moving front at the center of a low pressure zone.  Lots of overcast and cool temperatures, but for now the winds were light, and a fairly consistent direction.  Good enough day for a quick flight around the neighborhood.

I took a passenger this time and we stayed low, just about 1,000 feet above the ground to stay out of the bumpy winds up higher.  But a great altitude for just putting around and visiting the Billings airport for a couple of touch-and-gos.

The entire country experiencing fair fall
weather except for our Northern Rockies

Like the past few flights, I concentrated on the pattern, approach, and landing.  Fly pattern at 90 knots, then reduce power abeam the touchdown point (not the end of the runway), maintain 80 knots to the base leg, then more flaps and reduce to 70 knots.  Keep 70 all the way down final and save the last notch of flaps for the last 50 feet.  Let airspeed drop to 60 over the threshold and power to idle.  Then a nice, smooth flare to touchdown.  Sounds so simple.

It all clicked again today, and though we kept it short to stay out of the weather, a great flight before what will likely be another dry spell for a while.

The cold - it's coming.

Weekend Triple Play

Based on my last flight’s debrief, I tried to get more time in sooner rather than later.  Last weekend didn’t work out, but I was able to get in this Saturday.  Again based on my last experience, I wasn’t expecting anything too great.  Figuring I needed a lot of work to get back in the groove, I focused on a few key areas knowing I would be back in a 172:

• Being established in the pattern and timing power and trim changes for landing

• Keeping the nose up in the turn

• Recalling the sight picture for landing

So I did my homework.  The plane would be a newer model 172 – in fact one that I had flown before – so I downloaded the POH to study speeds and procedures.  I also found an excellent resource specifically for late-model 172s published by ATP.  Since they are a well-established academy with standardized procedures and a fleet of 172s, they have put together a manual just for that specific plane.  Rather than the more general handbook advice you might find elsewhere, this one has specifics like power and flap settings for the pattern.  Reviewing it changed everything.

The plan of the day was to obtain a rental checkout.  At this school, the requirement is to perform three touch-and-gos with the instructor.  But I wanted more to get me where I wanted to be.  So we set it up to be a similar set of airwork exercises as last time – some slow flight, stalls, and steep turns as well as pattern work.

Happily, the weather was clear and the air was smooth.  I’m sure it helped, but compared to the last flight, this was completely different.  The review of procedures and the short time between flights made for a totally opposite outcome.  Stalls were crisp, steep turns were right on, and I managed airspeed in a way I don’t think I’ve ever been able to do.  Everything came back together.

So now the test – how were my landings?  Let’s put in this way – there were just a couple of points to work on after the first try.  Get the sight picture right and keep the speed up.  Using the ATP manual as a guide sets up a slower approach than the school here likes to have.  It essentially was a short-field approach – completely OK but removing some of the margin of error, and an easy fix.

Now that I had my trim adjustments and power settings more dialed in, adding 10 knots to the approach speed was easy.  On the next circuit, suddenly the sight picture snapped into place as well.  This was turning out great, and the last landing was even better.  I was very happy with the outcome – to the point that I wasn’t ready to stop.

But we did; the instructor had another student.

However, this plane was still available for another few hours.  Enough time to run home, pick up any interested passengers, and take another flight.

An hour’s tour around the area and, though the winds had picked up a bit, another great landing.

And?  The plane was open on Sunday as well.  Would the wife like to take a flight as well?  Yes, she would.

A very nice, cool morning awaited.  A cold front was on its way in, and I knew we didn’t want to be in the winds with a fairly new passenger.  But the morning looked good and we got out and back before it shifted to a gusty crosswind.  

All in all, three flights in two days.  Granted they were short, but the reinforcement of skills was and continues to be very important.  I’m hopeful this is a turning point that allows me to fly a little more often than I’ve managed in the recent past.  If so, there’s no doubt my flying will only get better.

Exploring North Carolina

In case you're looking for a benchmark for how long is too long between flights, I'm going to say one to two months.  The several months that lapse between my own is way too long, and even the latest spell of four is enough to be starting behind the curve.

My travels take me to North Carolina, which holds claim to being the birthplace of powered flight.  So when I find myself staying the weekend and the weather is pretty decent, I take the opportunity to get an instructor and get up in the air.

The day started normally enough.  The flight school has a fleet of Pipers and Cessnas, and I chose the low-wing Archer.  We spent about 30 minutes inside doing the requisite paperwork and running through the POH to check V-speeds, weight and balance, and systems.  Then out to the preflight.

We climbed into the cockpit for a little overview of the instrument layout, and then stepped out and gave the plane a once-over before getting into the preflight details.

"What's this?" I ask, pointing to a broken engine cowl latch.

"We're not flying today," the instructor flatly replies.

He putters around the plane, wondering what's going on.  We find that all four latches are undone, and that there's an extra 0.1 hour on the engine meter from what's in the paperwork.  We suspect someone is in the middle of some maintenance and testing, but it's not on the books, and the school owner is out of town.  Regardless, this plane isn't flying.

I say, "Well, I've got no problem flying a 172.  I'd rather spend the extra time to get the paperwork re-done and fly."  The instructor obliges, and we carry our gear back inside for another go.

The instructor is different than any I've ever flown with.  Mostly, I fly with younger guys (yes, from my first flight to the present, they have all been male) who, while dedicated and professional, don't have much on this older gentleman.

An aeronautical engineer, ex-Navy flight instructor with time in all types from radial-engine Trojans to modern jets and thousands of hours to show for it, he's been instructing in some way since 1968.  And he brings a completely different perspective to my own flying experience.

Right off the bat, I was set up for a difficult day.  Not only have I not flown a 172 since 2012, but we used an 800-foot AGL traffic pattern rather than a more customary (at least by today's standards) 1000-foot pattern.

This might not seem like much, but when you've trained so far for a certain sequence of events at about the same time and place - throttle back, slow down, flaps, turn, check descent rate and airspeed, more flaps... - and then knock 20% off the altitude you have available to do it, things get busy.

So I wasn't too surprised that my first two landings left a bit to be desired.  It was difficult to hold airspeed, the timing of my trim adjustments was all off, and my sight picture of the runway on the base-to-final turn was not helping.  It was difficult to maintain the glidepath and correct for a light crosswind.

But by the third circuit, the instructor called for a go-around.  Not because anything was wrong, but that was part of the practice and my final approach looked good enough to go try some stalls.

Power-off (also called approach to landing) stalls were no problem.  But the instructor had me do something a little different.  Rather than slow flight with full flaps and right on the edge of the stall, he had me stay at 60 knots with no flaps at first.  That's a challenging speed for this plane, as the controls are mushy, but the plane still responds fairly quickly to attitude changes.  It showed that I still need to work on setting throttle and trim at the right times as I pass through different speeds.

Power-on stalls are always a bit more challenging, as they need a lot of right rudder to correct for the high power setting, but otherwise the mechanics are similar.

Steep turns were also on the menu today.  My turns are acceptable, but I tended to let the nose drop, especially to the right.  This is in fact very common across different pilots and airplanes where the pilot sits in the left seat.

Then a mock emergency landing.  Again, I need a better feel for the airspeed and trim.

After all the airwork, we came back to give my landings another shot.  Though they were better, there was still lots of room for improvement.  This was where my instructor's experience gave me some additional insights.

After a few touch-and-gos, we called it a day.  But the instructor was happy to spend some time doing a debrief, one much more extensive than any other I've had.  He kept notes on all my flying and was able to quantify many of the points I've just glossed over here.

It's too bad my instructor is not a doctor.  Then, I'd be able to say that his recommendation to fly again within a few days is a medical necessity.

Oh, and a few bonus photos of my other aviation-related explorations:

What Just Happened?

It was to be a more-or-less routine flight – except that I haven’t flown in about eight months.  If you read accident reports, you know that aircraft owners all too often ignore these dry spells, hop in for a “quick flight” and find out too late that their skills aren’t quite up to the task.  So it’s nice to have the excuse that I need an instructor checkout anyway for the rented plane, but I wouldn’t have thought I would push my luck like that.

Nonetheless, I had enough confidence that I thought I could take my kids up for a ride after the checkout, so invited them along.  I therefore put myself in the position of hundreds of other accident victims who face a flight with too many external pressures – the need to arrive somewhere on time, the expectations of family or friends, or the weather turning bad just at the wrong time.

In these and many other situations, pilots constantly evaluate the “Go / No-Go” decision.  Do I take this flight at all, do I keep going even as conditions change, and when do I need to make the final call that this just isn’t going to work out? 

My typical DA-20 panel

DA-20 with G500 panel - more info in different places

Today was in fact not a bad day for flying.  A little warm perhaps, but the winds were fairly light with only a minor crosswind.  I was flying with a different instructor, and he didn’t realize that I hadn’t flown a DA-20 with the G500 digital display before.  I had actually flown a similar setup in the Tecnam Eaglet, but I’ve grown accustomed to the round dials in the Diamond.  Again, faced with what is technically an unfamiliar aircraft, would most pilots hop in and figure it out later?  Perhaps.  But the NTSB files are filled with pilots going up in planes they have few hours in – leading to poor use of the resources at hand.  

With all this in mind, I took the high road.  As we began the preflight, I let the instructor know that I had never flown this particular model before.  I personally felt very comfortable with him in the right seat and had no problem taking this plane out for the checkout, but wanted to know if he’d be willing to switch it out if I had any doubts about the rest of the day.  That was it – a very good, honest conversation about the conditions and risks.  I valued the opportunity to get some experience with the G500 anyway – if this had been just a checkout flight and no more, it would have warranted not much more than a passing comment.  

But my plan for subsequent passenger flights changed the equation.  I needed to know what my options were and the instructor should be aware of what I’m planning on doing without him – how else could he evaluate whether I would be safe up there?  And, by the way, he was quite willing to leave it up to me.  If I wanted a different plane, being completely open to pulling another out of the hangar for me – that’s quality service right there and reinforces my choice to use this particular flight school.

The flight itself turned out not bad – at first.  We did some stalls and a couple of steep turns, some slow flight and …  Though my maneuvers weren’t as crisp as they once were, they were passable.  As usual, my radio calls impressed the instructor.  So we decided to call it a day and to a few runs through the pattern.

By now, the wind had picked up.

Keep in mind, these wind conditions should not be a factor for someone who flies regularly.  Maybe a few knots of crosswind and no significant gusts.  Flying-wise, a pretty benign day.

But those eight months had led to the expected skill-atrophy.

A crabbed approach to correct for crosswinds

My patterns, headings, turns, descents, and final approach were right on (despite being the more difficult right-traffic).  But the transition from a crabbed approach to flare and landing really weren’t that great.  My timing and sight picture were off.  Granted, the instructor never had to take over, and these weren’t terrible landings by any stretch, but they were just sloppy enough that it was apparent to both of us that I needed more practice – much more to be able to carry passengers in these conditions.

By the fourth trip around the pattern, the instructor said he’d be happy if I could get two smooth landings in.  But I said, “Look.  I’ve already prepared the kids that their ride is not a sure thing.  Even if I get two landings, it would be more luck than anything else.  They’ll be disappointed, but let’s just do one more and we’ll call it a day.”  He offered one more time, but I could tell I just wasn’t as far ahead of the plane as I wanted to be.  Compounding this is that by focusing so much on the flight, this was a more mentally (and physically0 taxing flight than if I had done the same thing with more practice.  Any further flying would be adding more stress and just didn’t serve a particularly urgent purpose.  

So we wrapped it up, and I gave the kids the bad news.  “But we’ve been waiting TWO HOURS!”. 

“I know,” I said.  “But I want to make sure I’m safe to take passengers, plus it’s hot and bumpy up there.  Let’s save it for another day.”

And that’s what we did.  I don’t know when my next flight will be, but it was still a good lesson.  Not just for myself, but for the kids who need to be aware that sometimes flying a light plane just isn’t the same as a regularly scheduled airliner.  Delays happen, trips don’t get done, and weather can always turn an otherwise fine flight into a dangerous situation.  It’s a tough decision, but it was clearly the right one.