Douglas' Blog

Use of 126.7

I’m not sure where, but I seem to recall reading an article or blog about improper use of the aviation frequency 126.7. Maybe it was TC’s Aviation Safety Letter or COPA’s Flight. I actually thought it was one of Michael Oxner’s entries on his Controller’s Corner blog but I couldn’t find anything there or on any of the archives of my regularly read blogs either.

Not that it matters. The gist of the article was about improper use of the 126.7 frequency, which is commonly known as the enroute frequency, and is used to both contact FSS and to blindly broadcast position reports as you cruise towards your destination. My policy is to broadcast as often as possible and when nearby another airport of some sorts, to broadcast on that frequency also. And, at the same time, unless flying IFR or under flight following, I will listen to both frequencies at all times for fear of missing someone’s transmission while on the other frequency. And if only every had a similar policy, it may be that accidents such as the one near Brandon may not have happened.

The interesting thing for me about the article I mentioned at the start is that the article talked about how the frequency shouldn’t be used for idle chit-chat or anything other than position reports. I found it rather odd that such an article would exist. I had never in all my cross country flying time heard anything on 126.7 other than position reports or updates from FSS. And due to my military background, where we never spent more than a few seconds talking on the radio if at all, I would never think of having a ‘conversation’ using the radio on a frequency that is clearly to be used otherwise.

But that changed on my recent trip from Springbank (CYBW) to Prince George (CYXS). On the return flight just south east of Grande Prairie, I switched from monitoring the mandatory frequency (MF) to monitoring 126.7. Actually, I switched the talk frequency to 126.7 while maintaining a listening watch still on the Grande Prairie MF just in case. I quickly broadcast a position report and waited for any replies. There was nothing on the frequency until I was approaching Smokey River. I didn’t actually notice the river but there was a position report given for the Grande Prairie area as ”over the Smokey river” so I grabbed my VFR map off the dash and scanned for the river. As it happens, V301 crosses over that river on it’s way to Whitecourt and since I wasn’t clear as to where the reporting traffic was, I figured I’d give an updated report of my own and hopefully figure out where the other traffic was.

That plan, however, was short lived as someone immediately came over the radio with ”Is that you, John? What are you up to today?” or words to that effect. It was bizarre to hear two people talking as if they were in a neighbourhood pub about how thing were going. But what was unnerving was the fact that as they blabbered on, leaving me unable to get my position report in, I was rapidly approaching the Smokey River area. And as by the time these two jokers were done their conversation, I was past the Smokey River and hadn’t been able to pick either of the two aircraft. While the sky is big and open, the chance of mid-air collisions does exist and I think in this case, my choice of following a Victor airway at a proper eastern altitude of 7500 feet (5000 feet above the ground) probably avoided any potential conflicts. For me, it was just another reason to ensure that (a) I fly high enough to avoid the laisez-faire pilots; (b) I get flight following; or (c) I fly under IFR (which I soon hope to have).

Another intersting side note; I had always thought that everyone was familiar with Victor airways. Last year when I flew to Dauphin, MB, I followed airways most of the trip and at one point actually flew 1000 under another VFR aircraft flying the same airway in the opposite direction. But on this trip to Prince George, I actually had someone ask me over the radio what ’Victor 301’ was as he wasn’t familiar with this landmark. Perhaps the pilot was a rotory pilot and they aren’t taught the same things? I dunno. But regardless, between that and the clowns chit-chats, I was appreciative the good training given to me a decade ago when I was doing my private licence and my good sense to follow most of it.

Fanaticism As A Lifestyle

When I started using Linux back in the mid-1990s, Macintosh computers were crap. The machines were expensive, the OS was unstable and there weren’t much in the way of applications outside of some stuff for publishers and artists. Windows wasn’t much better but at least the hardware was cheaper and people were building applications like they were going out of style.

I chose Linux because for me, it was the best tool for the job at the time. And as a programmer it was exciting to be a part of this growing, viral movement called open source. And it was even more exciting to help out, whether it was actual coding or tracking down bugs or in the case of the more complex stuff, simply reporting bugs and feeding other developers more information. Sure, at times it was a struggle but the world needs people willing to dig in an help out. The problem with today’s world, no matter what the realm? Everyone wants to take the easy route.

Linux is the near-perfect operating system for me. Everything I need works. Yes, there have been hiccups, issues, and various other struggles. And if I hadn’t been using this particular laptop, Linux would be THE perfect operating system. But I like the portability of a laptop and it’s nice to be able to work on various projects no matter where you are, rather than working on business stuff on a business computer and personal stuff on a home computer. But since I was using a laptop for it’s portability not for it’s suspend/resume, the fact that ACPI-driven sleep modes didn’t work really didn’t matter; it was simply a ’nice to have’. So did I mind? No. Was I able to build a 10 employee business on top of Linux and then sell it? Yes. Was I able to build a handful of personal and side projects on top of Linux? Yes. Do I regret my choice of Linux? Not for a second.

And why would I switch to OSX now? Because some stuff works? I’m sure some of it does, but not everything, as I wrote last year. Every product, whether it’s a car, an aeroplane, a MP3 player or an operating system has it’s good side and it’s bad side. The grass is always greener somewhere else and in the case of Macintosh, that grass looks like every neighbourhood dog has done it’s business on it. No that’s okay, I’ll stick with what’s best for me, not what some Jehovah’s Witness like evangelist tells me I should switch to.

Now, ten years later after starting out with Linux, what’s changed? Well, Macintosh machines are still more expensive. The operating system is more stable, though that’s only because Apple built their OSX ontop of BSD. And although some people are quick to critisize open source software, Linux and BSD are basically fancy kernels with open source software built around them. In fact, Safari is built using KDE’s KHTML code. And the biggest change of all is that under Apple’s executives “great” leadership, Apple has seen it’s Macintosh market share eroded down to a handful of people who buy machines because they’re pretty looking and because Apple makes them. Instead of buying something that suits their needs, they buy something because the product name starts with a styled, italic letter ’i’.

But I won’t tell you to switch to a different OS. What you decide to use should be a personal choice and/or an informed decision based on various factors. And how presumptuous of me to know what you, the reader, might want? That said however, personally, I can’t wait to see all those suckers lay down their money for iCrap.

Three Year Struggle Over

Since owning this Dell Latitude C840, I’ve been in a constant struggle with various aspects of it’s use. I’ve had nvidia driver issues, wireless issues, modem issues, fan issues, docking station issues and external monitor issues. But no issue has driven me crazy more than the fact that I couldn’t suspend the laptop. At one point when I first got the laptop and was running Red Hat Linux I think it would suspend using APM but that’s so long ago I no longer remember if that is truth or fantasy.

But recently this year I started mucking around with suspend again. It was the first time I’d really tried since I last wrote about my troubles. The problem with trouble shooting suspend problems is that it’s very disruptive to doing actual work; if things go bad (which they inevitably did) you end up rebooting and trying again. I spent a few hours trying in early July while on holiday at North Buck Lake without success and given the age of the laptop decided that it was simply time to give up. The machine would suspend and resume just fine now, but on resume the LCD backlight would fail to come back on. And without that backlight, reading the LCD is next to impossible.

But I absolutely hate unsolved problems; it’s a curse for me. If something doesn’t work, I think about it until it gets solved. So this morning, I tried again. I did a bunch of research with Google and discovered that various people had been successful, using xset or vbetool or combination thereof. So I wrote a shell script to run on suspend, which was a mish-mash of various things people had tried, but again no backlight.

That is until, I tried using those tools to first turn off the backlight (via dpms) before the suspend. And, that did the trick. As such, my three year struggle with suspend/resume on my Dell Latitude C840 is over.

Here’s the script I use to suspend the laptop:

#!/bin/sh

#------------------------------------------------------------
# ACPI - suspend script
#  - enhanced by Douglas Robertson
#
# To Do:
#  - track what networks were brought down and bring back up
#  - track what modules were loaded and reload on resume
#  - ???
#------------------------------------------------------------

if which fgconsole > /dev/null 2>&1 ; then
    XHACKS_ORIGINAL_VT=`fgconsole`
else
    XHACKS_ORIGINAL_VT=1
fi

chvt 1
VBEMODE=`vbetool vbemode get`
vbetool dpms suspend


# down with the network!
ifconfig eth0 down
ifconfig eth1 down
ifconfig eth2 down
ifconfig wlan0 down

# remove usb modules
rmmod uhci_hcd
rmmod ehci_hcd

# remove any other modules that are known to wreak havoc
rmmod tg3
rmmod ide-cd
# ???

sync

echo mem > /sys/power/state

sleep 1

modprobe uhci_hcd
modprobe ehci_hcd
modprobe tg3
modprobe ide-cd
modprobe ndiswrapper

chvt $XHACKS_ORIGINAL_VT

vbetool dpms on
vbetool vbemode set $VBEMODE
xset dpms force on

# up with the network!
ifconfig wlan0 up
#ifconfig eth2 up
ifconfig eth1 up
ifconfig eth0 up

It works for me; hopefully it helps those who have also struggled in the quest to suspend/resume with a working backlight. If you have issues you can try contacting me, but I’ll warn you that I’m no expert. Not at all. Though after thre years you think I would be.

Got Time For A Comment?

I was going to include this as part of my entry about my third IFR country flight, but it’s not really related to my IFR training per so I think it deserves it’s own post.

I filed the plan for today’s IFR flight from Springbank to Red Deer to Calgary and back to Springbank. It was the first flight plan I’d filed and I was very precise when explaining the route and the hold/approach requests to the FSS so as to ensure I was able to get as much out of the flight as possible. After being passed from Calgary Terminal over to Edmonton Centre, the Edmonton Centre controller gave us our hold clearance for over the Red Deer beacon. I copied the clearance down as fast as the controller spoke it and managed to read back the clearance word for word (which was a first).

Then a garbled transmission came over the air that started with ”X-ray Hotel Oscar”. Normally I am able to catch most, if not all of, any garbled transmissions based on the context of the flight. But I looked at instructor Jason only to find that his faced showed that he hadn’t recognized the transmission either.

”Say again for X-ray Hotel Oscar.”
”X-ray Hotel Oscar, do you have time for a comment?”

For whatever reason (no it wasn’t anyone clobbering the first), the second time the transmission came through just fine.

”Go ahead for X-ray Hotel Oscar.”
”X-ray Hotel Oscar, Edmonton Centre. I just wanted to say that as you know in this area [Red Deer] we get a lot of training type requests and that’s our specialty. And I just wanted to let you know that your flight plan is very clear as to what you want to do and that’s much appreciated.”

Of course my instructor Jason took the reply and said that it was no problem, which I heckled him about since it was I who had filed the plan. I really wanted to let the controller know that it was me, the student, who had filed that plan, but I let it go. I know, as does anyone who’s now read this entry, that it was me. And for that, I gloated the remainder of the flight. That said, thanks must be extended to the flight service specialist who obviously copied my request verbatim into the NavCanada system.

I’m not sure who the Edmonton Centre controller was, and I’m not sure I’d recognize his voice again, but if he reads this entry, he’ll know I’m talking about him. And if you do read this Mr. Edmonton Centre Controller, your comment about my flight plan was as much appreciated as my actual flight plan was to you.

IFR Lesson #27

The club’s Cessna 182 is still missing a working ADF. As such, NDB approaches are out if we use that aircraft, so today’s lesson will be in the IFR Warrior, C-GXHO, again. Although that means everything will happen at a slower speed, the worst part of doing IFR flights in XHO is that XHO only has a single VOR as the second one is slaved to the GPS, though that slaving seems to be broken anyway. The 182 was my preferred aircraft to do the IFR flight test in; it has an HSI slaved to an external compass, a second VOR and, when it works, an ADF. Two VORs make testing easy, makes it possible to triangulate your position and makes it easy to follow Victor airways which aren’t straight. And two VORs also makes it easier to anticipate the interception of a specific radial. So, two VORs is good, one is much less good. The IFR Warrior has a moving map GPS instead of a second VOR, though the GPS is not approved for IFR use. So it’s basically useless in this case.

So I have decided that as a result, I will most probably do my flight test in the Warrior. All told, that may work out for the best anyway. I have tewn times as much time in the Warrior as I do in the Cessna 182 so that will mean that I will likely be far more at ease in the Warrior than in the 182. Though, since I want to fly the 182 more in the future, I will plan on taking future tests in the 182 (if I haven’t convinced myself to buy my own plane by that point). And the Warrior isn’t all that bad; it’s just a different aircraft for IFR than the 182.

After preflighting XHO, I gave my flight plan to instructor Jason who looked it over briefly and then told me to go file it. For the first two flights, Jason had filed the plan with FSS so this would be my first time filing an IFR flight plan. The results were good, as I’ve noted in this separate entry.

The flight path was pretty much the same as the previous IFR flight, with a hold over the Red Deer NDB followed by an approach. At the MDA, I took off the hood and saw runway 34 at CYQF and as per Jason’s instructions did a touch and go, which resulted in a rather steep short final given our height relative to the distance to the threshold. I then climbed out and followed the missed approach instructions, and calling up Edmonton Centre on the way back to the beacon. The plan was to then head to the Calgary VOR, where we wanted to do another approach.

Edmonton Centre cleared us to the Calgary VOR, at which point I told the controller that we’d like to do an approach at Calgary International after which we would cancel IFR and proceed to back to Springbank VFR. That seemed good enough for Centre and luckily Calgary Terminal was feeling nice (it seemed to be a good karma evening all around) and upon reaching Calgary Terminal space, we were vectored west and then cleared to intercept the localizer for ILS 16.

Once again, I kept our approach speed on the high end (around 95 kts) to help Terminal manager the other around us, which I think they appreciated. At one point, when we were number one for landing but still perhaps eight miles or so from touchdown, there were two commercial flights behind us, who were given their sequence numbers of two and three right after each other. I think the number two jet had noticed that they had flown through the localizer already and knew we were a training flight because he asked the terminal controller in a snide tone, ”Any idea when you are going to turn us?” The controller, without missing a beat, replied in a friendly, yet somewhat cheeky manner ”In just a few more miles… it’s for traffic.”. Jason and I looked at each other and snickered.

The rest of the ILS 16 approach was good except that we got a late clearance for the actual approach and I had to drop quite rapidly to keep the glideslope from going full down deflection. But everything worked out and when I looked up at the decision height runway 16 was right in front of me.

For those who are curious, you can see my flight on FlightAware.

Flight time: 2.5 hrs
Instrument time: 1.9 hrs (hood)
Approaches: 2

Why We Fly - Reason #127

If you’re looking for the other 126 reasons we fly, they haven’t been written yet. They exist, but I haven’t written them down. And of course the reasons will be different for everyone. And there’s most likely more than 127 reasons too. But I didn’t want to start at number one and since I’ve always liked the number (*warning* geek talk) 2^7-1 I decided to start there at number one hundred and twenty-seven.

Once again I was catching up on my RSS feeds (for those not in the know, I’ll likely never catch up), and read Yet Another Aerobatic Video and from there I ended up watching a video posted by Frank which, at this point, is probably the best home made aviation video I’ve seen to date. You can watch the video, titled Climb through the clouds into the sunrise! on YouTube. The video has terrific footage, a great soundtrack and includes some radio communications. You can also check out Frank’s other videos on YouTube or over at his website www.160knots.com. Frank owns a Bellanca Super Viking (tail number N4201B) and has lots of great info and links relating to the Super Viking and flying in Southern California.

In any case, I highly recommend that you check out his climb through the clouds at 5:45am because that is reason #127 why I fly. Now, if only I can find the time to finish up my instrument rating I too can experience such beauty.

IFR Lesson #26

The ADF in the club’s Cessna 182 is confirmed now as completely non-functional, so today’s cross country flight was done in the IFR-certified Warrior, C-GXHO. As per normal, I preflighted the aircraft on my way from the CFC parking lot, ensuring that all IFR-required instruments functioned along with all lights and the pitot heat. Then I headed inside to give instructor Jason my flight plan so he could file the IFR flight plan. Today’s flight would be CYBW direct QF (Red Deer NDB) direct YYC (Calgary VOR) direct CYBW, with a hold over QF and approaches at Red Deer and Calgary International. But our entire plan depended on us getting into the air as soon as possible as Jason needed to be back in 2.5 hours to teach ground school.

After receiving our clearance and doing the run-up, I experienced multi-pilot cooperation for the first time. Normally, Jason acts as a typical instructor/mentor; I do everything and he watches over everything and makes sure to point out my good/bad points. But today, due to our need to ensure a speedy takeoff, Jason took control after the run up, doing the talking and taxiing to position at runway 16 while I completed the last of of the pre-takeoff checks and worked all the avionics. I am able to do a little of this when flying with Ali, as she is confident enough now to hear something on the radio and change frequencies, transponder codes or altimeter settings. But because I am still the only trained pilot per se, and thus PIC, I always end up double checking all her actions. But in today’s flight, cooperation between Jason and I was fluid and instead of a potential five minute delay we were able to sneak a expedited takeoff before another aircraft turning short final.

Since we didn’t need to cross Calgary Terminal’s airspace to get to our destination (unlike my last flight), getting airborne and getting pointed in the right direction was much faster and easier since we could skirt the western edge of Terminal’s space. Then it was direct to the Red Deer NDB for a ten minute hold, which went okay. Then I shuttled down from 8,000 to start an approach, which was less than stellar but on a good note I learned how truly important it is to be stablized on an NDB approach before reaching the FAF. In my case, due to winds, I was well off the published inbound track such that a 30 degree or so turn was required at the FAF in order to line up with the runway. Add to that the fact that I was still struggling to get down to the proper height, the approach was a great example of how not to execute a proper NDB approach.

After going missed on the approach we tried to get an approach in at Calgary International, but Edmonton Centre informed us that Calgary was too busy to bother with us so we cut the flight short, cancelled IFR and headed direct Springbank. And Jason made it to his class with minutes to spare.

Flight time: 2.1 hrs
Instrument time: 1.8 hrs (1.5 hrs hood; 0.3 hrs actual)
Approaches: 1

IFR Lesson #25

Today’s lesson was my first cross country IFR flight. It has always been my plan to do my flight test in the club’s Cessna 182; partially because it has better instruments (an HSI), partially because it flies faster and mostly because I plan to spend more time renting the 182. It’s faster, has a better useful load and is a great airplane. So, as such, today’s flight was in the 182.

I preflighted the plane as per normal, though I did a quick check of all the instruments we were going to need, tuning in the VOR and ADF to ensure their functionality. I didn’t see any reason to discover a problem with them after starting up and taxiing to the run-up area. Then I headed inside to give my plan to instructor Jason, since he would be the one filing the flight plan. Our planned route today was CYBW direct YC (Calgary NDB) direct 5V (Drumheller NDB) direct YYC (Calgary VOR) direct CYBW. We would be doing a hold over 5V and approaches at Drumheller and Calgary International.

The flight started out with a 10 minute delay as Springbank Tower waited for Calgary Terminal to slot us into their plan. ”Welcome to the world of IFR,” commented Jason. After takeoff however, our time in Calgary’s airspace was uneventful, with us being vectored around, which was no big deal as that is pretty standard when doing any flying around the Calgary area. The only difference was that this time I had the hood [of shame] on to keep me from peeking out the window. We were cleared direct to the Calgary NDB, which we did and after giving a position report (which although wasn’t required since we were RADAR IDENTIFIED was done for practice), we were cleared direct Drumheller [NDB]. And that’s when things went wrong.

I tuned, identified and tested the ADF for Drumheller and took up a heading that the ADF pointed to. Except that the heading seemed about 20 degrees too much to the north. And when the Calgary Terminal controller cleared us again to go “…direct Drumheller now” I was pretty sure that the ADF was steering us off course. A quick check of the VFR-only GPS confirmed what we suspected; the ADF was not functioning properly. At all. But since we weren’t sure if it was just a distance thing or what, we decided to continue on to Drumheller to see if we could still get in a hold and an approach.

Unfortunately, the ADF continued to act up and upon our arrival at Drumheller, we simply turned around and requested a clearance back to the Calgary VOR. In hindsight, Jason should have asked the Centre controller for a DME hold using the Calgary VOR. That said, I did get some instrument practice and I was able to fly through some cloud, all be it for perhaps 15 seconds, for which I was able to remove the hood. It was very cool to look out of the aircraft and see nothing but white. Very cool indeed.

Upon our return to the Calgary Terminal area, we were cleared to intercept the localizer for runway 16 and cleared for the ILS 16 approach. I intercepted the localizer perfectly, and kept the speed up until the FAF, but overall the approach was erratic in terms of speed and course. But at the decision height when I pulled off the hood, the runway was within limits for a safe landing. So, overall, I would say that it was a good first effort, especially since I can only get better with practice. We then went missed on the approach, cancelled IFR and flew back to Springbank. Overall, a great first IFR flight.

Flight time: 2.0 hrs
Instrument time: 1.3 hrs (hood)
Approaches: 1

Oilers PIREP

I tried calling the Calgary Flying Club this evening and there was no answer. Twice. Usually this means that either the club is really busy or it’s reasonably close to closing time and the weather is so crappy that they’ve sent everyone home. So I went to the Nav Canada flight planning site to check the Calgary/Springbank weather. Not great. But I was delighted to see that several of the PIREPs coming out of Edmonton FSS were cheering the Oilers on as such:

UACN10 CYEG 142106
EG UA /OV CYEG 090010 /TM 2106 /FL032 /TP C172 /RM SHWRS VCNTY BEAUMONT AND EZ3. ***GO OILERS GO***

Of course, I’m a Flames fan myself but since Edmonton is our neighbour to the north and because we have friends up there, I’m cheering for the Oilers also. Go Oilers!