A long, tough day, but still a bunch of fun.
I started at 11 with one of my instrument students. We filed IFR and flew up to Princeton for the NDB 15 followed by the GPS 33, then headed back to Crystal for the GPS 14L.
It was 1.9 hours total with all the screwing around, getting clearances, getting the airplane set up, missed approaches, holds, etc... and about 1.0 in actual. It was a weird day, we were just in and out of the clouds the entire time so I was working doubly hard.
Teaching instruments is never easy and it's extra tough in IMC, not because the flying is particularly difficult but because there's so much more going on and since you're on a clearance you can't let a student make too big a mistake.
When I was doing my instrument rating I never, ever thought I'd be comfortable enough to hang out in IMC looking across at the gauges from the right seat but now it's getting to be routine and I love it.
The approaches went reasonably well and I even learned something about the Garmin 430. We were cleared direct to Crystal from Princeton and when we were finally able to make contact with MSP approach they cleared us direct to ONYOP, an intermediate fix on the GPS 14L approach.
I guess my brain wasn't fully functioning, but I had my guy load the approach and select vectors-to-final with the intention of then going in to the FPL page, selecting ONYOP and going directly there.
Well, turns out ONYOP (or any intermediate fix, I'm assuming) only shows up if you select an Initial Approach Fix. If you select vectors the Garmin just draws a line from the final approach fix and doesn't place ONYOP in the flight plan.
Silly me. It took a few seconds while I guesstimated a heading toward ONYOP then re-loaded the approach via an IAF, went into the FPL page and got us headed directly to ONYOP.
Approach sort of piped up and asked if we were actually headed toward ONYOP and, I'm guessing, eventually figured out that we were still trying to figure it out as well and came back with a droll “Well, just report to me when you get established.”
I'm pretty sure after he un-keyed the mike he said “and you all be careful up there now.”
I love ATC.
After that, I had to check out a new club member in our 172s and he was waiting when we landed. So I debriefed the instrument lesson, explained the whole Garmin/ONYOP deal and immediately started the checkout.
We did an hour of ground on club operations, differences between the two 172s and some other procedural stuff then went flying. The guy flew great so after some slow flight, steep turns, a series of stalls and a power-off emergency approach we headed back to the airport, did a couple of landings and he was good to go.
I waved goodbye and walked over to the next hangar where my primary student was preflighting a 172 for his first night lesson.
We did some ground, got the flashlights ready and went flying. It was a beautiful night and my guy was loving it. I gave him time to get used to the perceptual differences at night then we did a bunch of turns, some slow flight with all the cabin lights turned off then headed over to Cambridge for some night landings.
On the ground, I'd briefed my own personal rule to never, ever, land on a runway at night without some sort of glidepath information (VASI, PAPI, ILS, etc...) unless you were totally familiar with the airport and surrounding obstructions. Even then, it's a bad idea.
For some reason, the PAPI for 16 at Cambridge was out so my guy got a first-hand look at how difficult it is to judge an approach at night to a runway without some sort of glidepath information.
On the second approach things were looking ok, then we started getting low and I sat there biting my tongue.
Finally, when the tops of the trees started showing up in our landing light my guy got the picture and started adding power. It was a great illustration of how easy it is to think everything is fine and fly into an obstruction at night.
From there it was over to Princeton for two more takeoffs and landings and we were both much happier to see the PAPI was working just fine.
We bucked a massive headwind back to Crystal and got the dreaded long, straight-in night approach. Personally, I think that's the most difficult visual approach to fly because it's so difficult to judge distances and there are really no good cues about when to start slowing down.
It's easy to think you're a mile to two from the runway when you're really 10 miles out, so slowing to approach speed too soon makes for a looooong final. Anyhow, I showed my guy how to use the GPS to gauge his distance and how to just fly along nice and level until the VASI showed we were on the glidepath.
The landing was a beauty and the flight was a total eye opener for my student. Crystal is a tough airport to find at night. Couple that with the whole tree episode and I think a lot of learning took place.
For the day, it was eight hours of non-stop instruction, 4.7 hours in the air including 1 hour of actual IMC. My back hurts, my brain is mush and all I ate all day was a bowl of granola at 8 a.m. To make matters worse, there's no beer in the fridge and I sure could use one.
Oh, and I ran over a Christmas tree at 65 m.p.h. on I-94 on the way home.
I'm whipped, but it's a good whipped.