PPL Lesson #20: Second nav route and stealth MATZ penetration
Well, a proper mixed bag for today’s nav session. Maybe I should have taken the misbehaving oil filler cap I encountered on my pre-flight checks as a portent and just gone home but I didn’t, and, after the engineer switched out the worn o-ring so that it would tighten properly, we set off for Thame.
Before we delve in, here’s the Skydemon track:
Learning from my issue last time where I was off course before I began, and also because we can’t depart straight north from Blackbushe due to noise abatement, I’d planned to overfly a local landmark 8nm away as my first leg before turning to Thame. However, I wasn’t sure if this undermined what my instructor wanted me to do as he’d mentioned needing to adjust height as we go due to the lower 2,500’ LTMA shelf, which my new route completely bypassed. As such, I’d drawn both the 2-leg and the direct route from Blackbushe to Thame on my chart (yes, you can see where this is headed) meaning to scrub the other one off before we set off once I’d agreed the route with my instructor. Well… I didn’t, and ended up looking for landmarks along the wrong route for a bit.
Still, once I was looking at the right track the reference features I was looking for - chiefly RAF Benson and Chalgrove Airfield - on that first leg let me know I was heading in the right direction. The other main issue with that leg was altitude. It was the first time I’ve flown with significant haze, and without a horizon to reference I struggled more than I ever have to get the aircraft trimmed for straight and level. That combined with an overly firm grasp of the yoke meant that every time I shifted in my seat to look for landmarks I would inadvertently dip the nose, deviating from my planned altitude and only noticing when I did my next altimeter scan. We eventually made it to Thame at the right time and only slightly left of track, so after repositioning overhead I then turned towards Didcot. I was not prepared for what came next.
Our heading of 241° was essentially directly into the low winter sun, and it felt like I may as well be flying in IMC for all I could see straight ahead. Certainly my visibility of the ground straight ahead was limited only to whatever was reflecting the sunlight back at me - essentially just the rivers and larger flat-roofed buildings - through all the highlighted scratches and swirls on the cockpit canopy.
Something else odd happened on second this leg, and other than a big shift in the wind I can’t really think what happened for me to end up on the outskirts of Oxford rather than overhead the power station at Didcot. The compass and DI were well aligned (instructor confirmed, and I’d checked both before and after the turn at Thame and at the midway point), I’d consistently flown the intended heading of 241° (again, instructor confirmed), my planned track (234°) was correct and with winds at 260@25 I’d properly accounted for wind drift with the whizz wheel during planning. The track I ended up flying was closer to 250°. Messing around with the whizz wheel after I got home, it would have taken something like a 40° southerly shift in the winds at 25kt for my heading to have ended up with that track. I can only think I twiddled the DI the wrong way, neither of us noticed for the whole leg and as a result I was flying 10° off the intended heading. If anyone can spot or suggest what I did wrong I’d be happy to hear it.
Eventually I corrected and ended up overhead the power station at Didcot, and I could finally turn away from the hateful sun and head back to Blackbushe. Visibility on this leg was probably similar to the outbound leg but it felt crystal clear after staring directly at the sun for the previous 13 minutes, and I flew pretty much directly down my intended track all the way back to Blackbushe picking out my references on the way.
I felt a bit crestfallen when we got back to the clubhouse, but after a debrief with my instructor I’m probably being a bit too harsh on myself. He couldn’t quite fathom what went wrong on that second leg, and reflected that my altitude keeping was only really thrown off by the poor vis and trying to peer through the haze to see my reference points. Apparently it went well enough that we’re adding a diversion to the next lesson (on Monday) so that’ll be fun!
I’d had a couple of practice attempts at planning the route over the past week or so with the weather of the day, so the planning this morning was relatively easy. When I started the planning this morning I was fairly certain we wouldn’t be flying as the weather was utterly miserable, but thankfully I went through the motions anyway: 30 minutes before the lesson when it switched into scattered cloud with blue skies, albeit looking like it could change at any minute. When I got to the airfield I had a chat with the instructor and we concluded that we’d give it a go - if nothing else, getting some marginally adverse weather practice in wouldn’t be the worst thing. I definitely wouldn’t have gone up if it was me, though.
In terms of the plan, the winds were looking fairly stiff - 244/32 at 3000’ - which gave me a positively pedestrian ground speed of 69kt and 63kt for the first two legs and then a much more spritely 113kt for the final leg, and as much as 19° drift. I found it difficult to always find good identifiable features on this route, particularly on the middle leg, to mark as reference points for timing / heading correction purposes, and it’s definitely something I’ll need to work on going forward. Turns out that “crossing the M4” puts you at any one of a million different places across the chart. Who knew?!
Checking the route on Google Earth, I thought it prudent to fly it in MSFS last night (in nil wind) to try to get some contextual experience with the whole visual aspect of navigation. I’m very glad I did, as if I had to identify Wantage based purely what I can pick off the half mill chart between all the intersecting TMA boundary lines I’d have properly struggled. Hats off to all the folk who flew for decades without any of these modern conveniences and somehow managed not to get utterly lost!
My biggest stumbling block on the flying the route - other than trying to juggle 5 new things to do whist flying, obviously - was on the second leg, where changeable winds meant I drifted well right of track and we ended up directly overhead a reference point that I was expecting to see some distance away out of the right window. Thankfully I was able to identify Hungerford out of the left window based on the river, the railway line and the distinctive riverside train station I’d seen on Google Earth the night before and we made it overhead pretty much on time. Fairly certain without the prompt from my instructor I’d have been heading for the coast, though.
My other takeaway from today is that I need a separate stopwatch to stick on my kneeboard. Trying to navigate to the Stopwatch app on my Galaxy Watch whilst flying straight and level in bumpy conditions was less than fun. There’s one built into the transponder, but it’s buried in a few levels of menu so I suspect it may actually be worse. Any recommendations welcome.
Next lesson is Friday lunchtime with more nav. I’ve got another route to plot - EGLK ➤ Thame ➤ Didcot ➤ EGLK - which looks like it’ll involve my first MATZ penetration and some more complicated altitude management.
Edited to add: I’d picked out that we’d be clipping the MATZ stub during the planning, so I’d written Benson Zone’s frequency on my plog. Having discussed it with my instructor before we set off he said that getting a MATZ crossing would likely be too much workload for my first nav session, and that we’d be okay staying on a basic service from Farnborough since we were just clipping the stub. If I were on my own, I’d probably have planned a crossing anyway, just to be safe.