Not So Great Divide

Rotate, retract gear, climb power set, after take-off checks complete and a right turn back towards the terminal airspace. I've kept the same transponder code and they're fine with that, clearing me back into their airspace for a second job. It's pretty much the same altitude and the same bumpiness, but it should only take about forty-five minutes. It takes less, but company wants us to land five hundred nautical miles away across hostile terrain, where the bumps are coming from. Ah heck, you know where the hostile terrain that breeds turbulence is in my country. We're being sent across the continental divide to Vancouver.

Seatbelts cinched tight and ask for the clearance. We're cleared straight to ten five, and told to fly a vector for traffic at first, then cleared direct. Ironically the vector is direct Vancouver, but the GFAs have told us that heading south to hug the US border will be the way to stay clear of the worst of the turbulence and cumulonimbus clouds. So I turn southward, and then a little more directly south, waiting until the way forward doesn't look quite so dark with building clouds. I zip up the top of my flight bag after the first time a jolt of turbulence hits hard enough to fling contents all the way out and onto the floor. The flight bag--a knapsack--is already seatbelted to the passenger seat. All my charts flew out of the map pocket, too. Tighten seatbelts further.

I don't really want to do this for the next ... well it would still be over two hours direct with these winds --headwinds of course--but with the indirect route it will be three hours. I consider landing in Cranbrook for the night, so I call flight services for PIREPs and SIGMETs. There's no SIGMET for the turbulence along my route and they haven't had any pilot reports. I give them mine. It sounds as though the worst of the bumps may be behind us, so I decide we'll continue. I still set direct Cranbrook as a waypoint, because it's a good route to intercept the southern track I want to follow.

Approaching Cranbrook, it occurs to me that IFR traffic approaching this airport could be descending out of the clouds through my altitude. I'm in uncontrolled airspace but I call up Cranbrook radio and sure enough there's a Saab 340 on the way in. I give a position report and Cranbrook has me on radar. Impressive coverage here. The Saab is in descent and once they are through my altitude and I am past the airfield I switch back to the en route frequency. I do the same thing approaching Castlegar, and this time it's a Jazz, can't remember if it's a CRJ or a Dash 8 departing visually, with a left turn over the dam. They will be too fast for us to catch, even as they climb, so no conflict. Top of the next hour I update my weather again. Penticton is all thunderstorms, and I can soon see that ahead, so I look at US airspace across the border. It's a row of giant military operations areas. I know I can sometimes get clearance into them, but I hold off on asking until I see whether the Penticton area is passable within Canada. It is. I fly between Oliver and Osoyoos clear of the storms.

I eat some snacks to keep my brain and body working, but my innards don't feel too great. Then I realize that having a seatbelt cinched to the maximum for two hours is not doing my intestines any favours. I loosen the lap belt and yay for renewed gastric motility. How do those people who wear super tight pants and belts all day digest their food properly?

I try to go through a valley but it's choked with cloud and I end up climbing through one of them, picking up ice as I turn away from the rocks. This is not how you're supposed to do it and I imagine that ice-filled windscreen is the last sight a lot of pilots have seen around here. It wasn't quite how I planned it, but the shadows of rock and snow and cloud are deceiving around here. The ice all slides off as I descend into a wider and less cloudy valley and follow the river to the farmlands around Vancouver. Vancouver Tower clears us straight in, and to land, about ten miles out.

Turbulent

We're in the sky over a major Canadian city and my dispatcher has had to pull favours and whine to get us here. We sent subcontractors to do this job, because we're very busy, but they were denied entry to the airspace. Apparently we're the A Team, because ATC let us in. Company has given us a list of other work to do for when the controllers have had enough and kick us out of their airspace, but meanwhile the controller has cleared us in and given us a pretty free rein, as long as we remain west of his runway in use. Accordingly, I'm on my best behaviour, staying super alert to what the controller is doing and giving him the information he needs in the clearest most concise words I can find. He has been amazing, routing traffic under over and around me so that I can do my job, and even keeping track of where we were working when he has to divert us.

It's turbulent, continuous chop from both convective heating and mechanical turbulence. I think I'd be feeling sick if I weren't flying the airplane. As a pilot I want to help my co-worker feel better, but all the normal advice and techniques one would use to mitigate airsickness don't apply here. It's his job to have his head down concentrating on computer screens, and it's mine to make frequent quick turns and altitude changes. He does his job and I do mine and we continue that for five hours, finishing the high priority job and then thanking the controller profusely before we switch en route to land at a satellite airport outside their airspace.

I'm usually kind of slow getting out of the cockpit after a flight, but today I jump out and get water for my co-worker and start fuelling the airplane. I'm compensating for not being able to help during the flight.

I get in to taxi to parking, and he gets in too. "Coming for a ride?" Yeah, a long ride. Company has texted him instructions for further work we are assigned to do. He gets right back in the airplane and we taxi out. There's a Cessna in the circuit, and only one taxiway with a backtrack, so we wait for him to land and taxi clear. Someone else has called meanwhile with an intention to cross midfield and join the circuit, so we enter as soon as the Cessna is clear to make the backtrack and take off before the other airplane arrives. And then the arriving pilot almost instantly calls base. That was unexpectedly quick. I guess he changed his mind about crossing midfield. He changes it back when he realizes I'm on the runway, and I'm rolling while he's on final.

More on this flight later, I think.

Not Supposed to Say

I'm flying from point A to point B, and remarkably neither A nor B is named after an animal or a body of water. I'm not on a flight plan just "VFR company note" which means my company is in charge of reporting me missing if I don't turn up, and I have flight following which means I'm monitoring the frequency of a centre controller who occasionally looks at my blip on a radar screen and, time permitting, tells me if any other radar blips threaten mine. Presumably if my radar blip disappeared and I stopped talking to them they'd tell someone or make a note, too. At the very least, if I didn't turn up at destination and company reported me missing, they could examine the records (still called "pulling the tapes" as if they were recorded on tapes sitting on a shelf) and see where my blip was and whom I was talking to when I was last recorded as existing. As I cover ground, the controller whose frequency I am monitoring will eventually say, "Switch to my frequency 133.40," or "Contact such-and-such Centre now on 122.75." The same controller may be monitoring different frequencies and she moves me to the one with the best reception for where I am, or I'm moving out of her area and she is passing me on to the next sector. My information moves with me to the new sector so I just have to say my call sign and verify my altitude. They already know where I am going, but they verify it, because there are multiple airports in the same city. Another airplane checks in on the frequency. The controller gives him the altimeter setting and then it's quiet again. My headset detects silence, so lets the MP3 player sound into the earphones. (Currently playing Convoy, featuring another profession with radio jargon). The new check in comments on this, "Kinda quiet today." The controller agrees. "Getting the crossword done?" asks the pilot. "I'm not supposed to say," replies the controller, which was way more hilarious in the airplane than it seems right now. It was the way he said it, like he was really hiding some big secret. The controller passes me on to the next sector and I say to my coworker, "I should have asked him if he had figured out twenty-one across yet."

Your Route Is Clear

This incident occurred the day I realized that I perhaps I should start blogging some of my adventures again. It was just such an Aviatrix day. Over ten hours logged, and once upon a time I would have had a sheet of paper under my operational flight plan on my lapboard and filled it with cryptic notes that would allow me to recreate the whole day for you, but a girl has to sleep and do her company paperwork sometime, so here's just that slice, complete with its life lesson.

We were assigned to work in military airspace, and I had been given a sheaf of papers including maps, the names, telephone numbers and e-mail addresses of what seemed like half the chain of command and their administrative assistants, plus instructions that we did not need to telephone anyone, just call RADIO CONTROL on such-and-such a VHF frequency ten minutes out. "Radio control" is an odd way to address an ATC entity, so I looked up the military installation in question in the CFS (directory of all Canadian airports) and found that the frequency was that listed for the local tower. Now that made sense. I called them up as instructed, with a proper efficient position report and request, "Basename Tower, this is Aircraft Type Foxtrot Alfa Victor X-Ray, forty miles northwest, nine thousand fife hundred. Request entry to CYR for previously approved air work one zero tousand seven hundred." (Someone is now itching to point out that if I was going to be truly proper I would have said "niner" and maybe I should have, but Canadians usually just say nine. I would have remembered to say niner for an American base, I hope). The numbered CYR is the designated airspace controlled by the military base.

The response is something to the effect of, "Go ahead your PPR number." PPR is a common abbreviation for "prior permission required," but I don't remember seeing such a number in my sheaf of papers. I have a quick re-read and no, there isn't one. My fellow crewmember already has his cellphone out texting company and in barely more time than it took me to indicate to the controller that I would try to get that for him, the number is provided to me. It was "six". Okay it was 2012-0006, but essentially the number between me and the airspace in front of me was six. I provide it in turn to the controller and we breathe a sigh of relief when it acts like an unlocking code to the secret levels of the video game and he says, "Your route is clear."

That sounds like permission, but it's not standard civilian phraseology, and I want to be absolutely sure. I'm organizing words in my head for the clearest, most succinct and professional way to say, "I am a civilian pilot unversed in military ATC differences, please confirm that means we are cleared as requested," when he buries that slightly fuzzy phrase in a question containing a pile of acronyms and numbers so deep that I don't know where to start asking. I think the best I can come up with is, "I'm sorry, I don't know what that means." I've been through military control zones across North America and while there are usually some quirks, I've never been at such a communications impasse before. Eventually I figure out that he is asking about the exact location of the work relative to the trans Canada highway. Yeah, one of the numbers turned out to be the local designation for Highway One and I think the rest were terms relating to the land covered by the restricted airspace. He stopped using them. We go back and forth a bit on this. He says "over" or "out" after every transmission, which is in fact part of the rules in aeronautical radio procedures, but in practice is only used when reception is terrible.

He's asked me to remain east of the highway, which is essentially an east-west highway. We don't seem to share enough common vocabulary or reference points to discuss this. He says "Wait out," which I presume to mean standby. He then comes back and asks me to fly a holding pattern. That's unexpected for a VFR aircraft. Usually a controller would just tell me to hold outside the zone, or give me specific holding instructions, but I can handle this. I'm five minutes from his airspace now, so I just fly a hold right there on the inbound track, working out that I need a one minute thirty-five second outbound leg and a fourteen degree outbound correction in order for a rate one turn to bring me perfectly back onto the inbound track, with six minutes showing to the destination. I call him back to ask for an estimate of how long I might have to do this for, but there's no answer. Eventually he comes back and tells me I'm cleared to work, "do not proceed east of [three digits spoken singly] dot one four." Now sitting where you are reading this, even with my obfuscation of my exact location, it's probably obvious to you that he was giving me a longitude, and I did figure that out after a second or so of staring stupidly out the window. It was just such an unexpected way to designate a meridian of longitude. I read it back as [three digits] degrees, fourteen minutes and told him that our our work straddled [meridian]°14'. We were at an impasse, so we lobbed the whole problem back to company to sort out on the phone and found some other work to do.

They called us back with an approval when we had not quite enough fuel to do the job, so we landed and refuelled and came back up to discover that "dot one four" meant decimal one four degrees, not fourteen minutes, so I had only to remain west of [meridian]°09', which I could do, and we quickly completed the job. It hadn't initially even crossed my mind that I'd be given a longitude in decimal degrees. Who navigates in decimal degrees?

Afterwards I lamented to my coworker the failure to communicate, and he was the one that came up with the realization that we were not talking to a military air traffic controller at all. We were talking to a comm tech down there on the ground with a radio, whose principle job was to keep people from blowing each other up on the range. When he said "out" he may have sometimes meant he was putting down the radio and walking away. And he probably had even less idea of what I was saying than I did of what he was saying. Because as the conversation got difficult I retreated to the most excruciatingly correct formal aviation radio language I could muster, trying to measure up for this terribly important military tower controller who didn't have time for anyone who didn't file flight plans in mach numbers, when really he might have been just as intimidated by my pilot jargon, causing him to try to duplicate it, and coming up with phrases that didn't mean what he thought. He hadn't once called himself "Basename Tower," just "Range Radio."

We had to return to that zone on another day and by changing my perception of the person I was speaking to, I changed my experience completely. I finished the mission by saying, "Thank you for your service," allowing him and others in earshot of the radio to perhaps realize that they had not really provided any air traffic control service to me, and that I was really thanking them for serving our country.

That made me wonder how often I have attributed to someone else too much authority or too much knowledge and, in trying to approach them at the level which I think they are expecting, have intimidated or alienated them. In future I will remember that the person in the metaphorical or physical intimidating tower is possibly not disdaining me at all, but in the same situation of trying to appear informed and in control. Maybe that would even work on the Springbank Tower controllers. And if someone is just being unnecessarily officious, they'll think they're being condescended to, which they deserve.

The Empire Will Be Pleased

The title is what my coworker said through his Darth Vader oxygen mask as we descended from the flight levels in an unpressurized airplane after completing a tricky piece of work. We descended overhead Banff, Alberta. It is so spectacularly beautiful there that I was distracted from the work I was supposed to be doing. I was even raving about the remarkable pointiness and ridginess and beauty of the scenery to the air traffic controller. The air traffic controller was meanwhile excited by the fact that I could still talk to him. We went from the flight levels to dodging in and out of those spectacular stripey peaks and we still had excellent two way radio communications. And then we landed at Springbank. Springbank is the Buttonville of Alberta. Screaming busy with training traffic, and controllers who tell you what you want instead of listening to what you requested. The best was the one who gave me an instruction to turn right, and then chewed me out for deviating from the straight out departure clearance I had been given. Such a startling contrast from the service I got from the very next controller they handed me off to. I cannot turn right and go straight at the same time, although with some of the aerial work I do it almost seems that way. If you have the opportunity, you should go to Banff and fly around at about 11,000' in the spring. I think you should put it on your bucket list. I'm a not a stranger to mountains, Banff just seems to have especially amazing ones.

Always Check NOTAMs -- Even When Running Drugs

Pilots and regular readers know that a NOTAM (NOtice To Air[wo]Men) is a little bulletin describing a change to facilities, airspace or procedures that isn't published on the current charts and publications. They look boring. They can be tedious and repetitive to read. Most of them won't pertain to your operation. If you fly out of some little flat bit of the wilderness airport there's probably a NOTAM about the airport lighting being unserviceable from shortly after the snow melts until whenever it is that gophers go back into hibernation.

You can look them up here for Canada if you know your airport identifier. They look like this.

CYHZ
110478 CYHZ CHURCH LAKE(WATER)
CHL3 AMEND PUB: OPR TEL TO READ 902-644-3604

110792 CYHZ AMHERST(HELI)
CCB3 AMEND PUB: NEW WIND FARM 15 TURBINES 0.7 NM RADIUS 455002N 641504W (APRX 1.8 NM NNW AD) 454 FT AGL 483 FT MSL. LGTD NOT PAINTED

110796 CYHZ STANLEY
CCW4 AMEND PUB: NEW TOWER 445602N 635751W (APRX 10 NM SSW AD) 299 FT AGL 988 MSL. NOT LGTD AND NOT PAINTED

110817 CYHZ NEW GLASGOW(ABERDEEN HOSP)(HELI)
OBST LGT U/S 12 TOWERS AT WINDFARM WITHIN 2.7 NM RADIUS 453359N 625746W (APRX 13 NM WNW AD) 377 FT AGL 1460 MSL
1111301630 TIL 1202291600

110844 CYHZ TRENTON
CYTN RNAV(GNSS) RWY 07, RNAV(GNSS) RWY 25 AND NDB RWY 25 APCH: RESTRICTED OPS SPEC 099 OR 410 REQUIRED AD VISUAL SFC NOT ASSESSED CREWS MUST BE FAMILIAR WITH AD ENVIRONMENT
1112151230 TIL APRX 1203161800

110845 CYHZ DEBERT
CCQ3 RNAV(GNSS) RWY 09 AND RNAV(GNSS) RWY 27 APCH ARE RESTRICTED. OPS SPEC 099 OR 410 REQUIRED. AD VISUAL SFC NOT ASSESSED. CREWS MUST BE FAMILIAR WITH AD ENVIRONMENT
1112151230 TIL APRX 1203161800

That's less than half of the Halifax NOTAMs this afternoon. If you're really operating out of Halifax you need to read them all, plus all the ones for the place you are going, and the ones covering airspace you'll be passing through, and possible diversion airports. The float plane guys don't care about the GNSS approaches. The airlines don't care about the windfarms. No one on wheels cares about the change in the operator's telephone number for the Church Lake waterdrome, but they are filed by the order they were filed in, and no one has realized the safety benefit of somehow filtering or classifying them.

They're a fairly often neglected aspect of flight planning. If you're flying between familiar aerodromes on a regular basis, there's a strong temptation to skip them. The flight briefers don't give them unless you ask. (And I still haven't forgiven the briefer I asked for NOTAMs for a flight from Meadow Lake to Buffalo Narrows, who neglected to tell me that the airspace I was chartered to fly through was in use by the Canadian military and their international guests for fighter jet exercises. It's the only time I've called and asked to speak to the supervisor of someone paid to provide me with flight services.) I have fielded a phone call from an airborne coworker who sighted vehicles working in the vicinity of his destination runway, "Avi, could you please check and see if there's a NOTAM ..." (There was).

So I can see how if you were conducting an operation that wasn't actually legal in the first place, transporting certain agricultural products, for example, that you just might not bother to check them. But these folks would have had a better day had they done so. A US reader will probably clarify the difference, but the Americans do have what I'm going to term a special relative of the NOTAM called the TFR (Temporary Flight Restriction) which highlights what in Canada would be NOTAMs restricting airspace to certain operations. They probably did this because people were missing NOTAMs and ending up on the windshield of Air Force One, but what it probably does is make the problem worse, with people clicking on the fun little map that tells you where they don't want you flying today (hey, is President Obama in Seattle today?) and then figuring that covers the important stuff and not going through to the boring list of nav aid outages.

CAT I Takeoff

I'll tell you about the circular yurt construction shortly, but today I couldn't pass up this story about a cat that escaped from its carrier before take-off on an Air Canada flight. Air Canada allows small pets to be carried in the passenger cabin, provided that they remain in approved pet carriers that fit on the floor under a seat. The door to the carrier was, according to the passenger 'inadvertently opened' while the carrier was being stowed. My initial guess was that the passenger wanted to give Ripples a quick snuggle before shoving it under the seat, but apparently security video shows that the CATSA inspectors who opened the cage for security screening did not secure the latch. In any event Ripples saw an opportunity and fled.

So you have an airplane, which is not a really large place, and a cat, which is not a large animal and the other had to be found inside the one. That took them a while because the cat had done what cats do and found the smallest, warmest most inaccessible compartment in the whole aircraft: an avionics bay. This is the airplane equivalent of getting into the computer rack and curling up on top of the server. Or sleeping on top of an old-fashioned TV inside the entertainment unit. They had to access the avionics through an exterior panel to remove the cat and then to ensure that it wasn't a trained terrorist attack cat that had left a little explosive payload in there--or a non-terrorist cat that had simply chewed on something or left a payload of another variety--they took a further delay to inspect the avionics.

I thought Air Canada didn't carry pets in the winter months, but here's their pet policy. They accept them in the cabin, as checked luggage and as unaccompanied cargo. They do have seasonal restrictions on pets in the baggage compartment to keep pets from being baked or frozen during ground handling.

I stand by my earlier statement that there should be a program in place whereby a passenger wishing to have a cat at their destination registers the one they have, drops it off at the airport and on arrival is given one of a similar size and colour, to enjoy for the duration of their stay.

Solve for X

Today someone in an aviation workplace was either amused or insulted, I'm not sure which, by my excitement that he was genuinely using trigonometry for real things. I'm afraid that he may have thought that my excitement and admiration was over the fact that he knew how use trigonometry at all, but really this is just one cool part of a very cool project he is working on.

What do you think he's up to?

Helicopter Charter

I'm not currently working with helicopters, either as a charter customer or with a company that operates rotary ring aircraft, but I had to love this trojan horse spam.

Your order for our air commuter services has been received and processed. The chopper will be at your disposal from 3.30 p.m. wednesday to 5.45 tuesday. Once again, the rates are as follows:

1 hour in the air: 824$
Takeoff / Landing: 229$
1 hour down time on the ground: 163$
Longest fly-time is 5 hours.
When flying for longer distances, a co-pilot is needed, and the cost accordingly grows by 133$ an hour.


Bill.doc 747kb


With Respect To You
Nellie Nickerson

The purpose of the spam is to get me to click on "Bill.doc," which in the original is a link to an executable. I have to commend these spammers for the completely awesome vehicle they have chosen for what I assume is a trojan horse of some sort. I love the imagination they bring to the rates. I have chartered a helicopter before, and like an airplane the rates applied to the flight time, regardless of the number of takeoffs and landings, and in this case there was no charge for the thirty minutes or so we spent on the ground between flights with the engine shut down. Perhaps somewhere in the world there is a charter rate schedule like this, but I find it hard to believe that in an aircraft where it can be hard to distinguish between takeoffs and landings, that someone would charge over one quarter of the hourly rate per one. I like the fee per extra crew member; in my experience crew usually get about half the amount clients are billed for their services, which implies that a co-pilot could be making $66 a flight hour.

Truth Be Told

The post from a few days ago didn't actually herald my being back. It was actually an indication that I'd neglected the blog for so long that a post I had written long ago and postdated to the far future came due and published itself. I didn't have a good plan for when to schedule it at the time and had been punting it forward through time for years.

See, I'm a person of obsessions. Some last a week. Some last for years. Some dwindle and are then rekindled. I blogged pretty much daily for almost ten years. (Cockpit Conversation was not my first blog). I blogged because I wanted to, and because it was fun to read the feedback. Recently another obsession has risen to the forefront of my life and seized the time and creative spark that used to go into blogging. If it stops being fun I'll see what comes next.

But seeing as you have all been so enthusiastic about that stray post, I'll see if I can blog once in a while, maybe at a frequency like Sam's rather than my former almost daily posts. We'll see how it goes. I haven't completely lost my habit of taking notes about my flights, so maybe in the back of my mind I'm still blogging.

Happy New Year, everyone. I do like you guys. Thanks for all the fun times--and the nasty times--that you've shared with me.

Not the Weather Report

I have a few requests to blog about the weather more, and I mean to, but somehow haven't for a while. I was going to today, with a report on the Weather Channel as a jumping-off point, but then I realized something that sidetracked me on that entry.

There's two sorts of being identified as the blogger. One is when someone who reads the blog meets me, or perhaps already knew me but figures out that I am me. Those ones are great, because if you read the blog you must know I mean well, plus you like the blog: no one goes on reading something they dislike. The kind I find more uncomfortable is when someone who doesn't read the blog and who knows me, but not as a friend, discovers that I have a blog, and who then goes quoting me out of context. You see that sort of thing done by and to politicians all the time. They end up defending stupidly innocent actions like where they shop or what their kids wore to the prom. This hasn't happened to me, but I don't think I'd like it if it did. Sometimes I think I should put my real name on the blog so that no one can "out" me, my already having done it myself. Politicians do that, too, "full disclosure"--telling the public things we don't care, just to pre-empt anyone else claiming they are hiding it.

I don't think I will do that in the near future, but I will present for your amusement ...

The Top Ten Ways to Accidentally Out Yourself On Your Own Blog

(I have caught myself doing all of these).

• 10. Forget to censor your own name when quoting conversations.
• 9. Post a photograph that shows your recognizable reflection in a shiny object.
• 8. Post a story about yourself that also makes the national news.
• 7. Leave yourself logged in to a shared computer.
• 6. Visit your blog from an FBO computer with a giant screen.
• 5. Do a real life meet up with fellow bloggers who like to post pictures.
• 4. Leave your blog in the browser history of someone else's computer.
• 3. Post the callsign of your aircraft.
• 2. Send e-mail to a customer from your alter ego e-mail address, with your blog URL in the signature field.

And the number one way to embarrassingly out yourself on your own blog is to ...

• 1. Post a video taken of an amusingly dire report on the Weather Channel, when said video was taken in the hotel room, and clearly shows your reflection in the TV throughout ... naked.

And that's why this blog entry isn't about the weather.

Projected Absence

I'm really wrapped up in a creative project that is using the same part of my brain and my day as blogging, and for now I'm going to give it priority.

I'll try to catch up later, but here's a tidbit from my day.

While I was preflighting today I saw a Canadian Forces Airbus in military grey, with muted markings and the only colour the red Canadian flag on the tail. The FBO crew parked an airstairs truck at the forward door and a long line of soldiers came out, carrying duffel bags across the apron to the FBO. I don't know where they had come directly from, or whether the range of the airliner would support it, but it was most interesting to imagine that they were returning directly from Afghanistan. I shouted "Welcome home!" across the ramp, but it wouldn't have been audible above the sound of the APU and of other idling aircraft.

Later, after takeoff I heard the Canadian Forces callsign, with a female pilot's voice, check in with departure. She was on the same instrument departure as I was, and given the same instruction after departure. I realized that she was climbing up behind me, then was given another vector that would put her past me on the right. I wonder if they loaded more soldiers to take back to wherever they got the first lot, or if they were ferrying empty.

Dauntless Aviation

I'm using software from Dauntless Aviation to study for the FAA exam. I definitely recommend it. It not only shows you all the questions you could see on the exam, with the correct answers, but highlights excerpts from the regulations that explain them and points out tricky parts of the questions. The merchant site is a little intimidating, but I think it's just that they are a very small company and hooked up with a somewhat aggressive payment processing company that they can't really rein in.
Today's confusion is over alternate requirements in the the US regulations. In Canada you always (with some very specialized op spec exceptions) require one alternate and there are complex but interpretable rules governing the weather conditions required to file a particular airport as your alternate. In the US you need one alternate, two alternates or zero alternates and whether you need them depends on what state you are flying in, the weather and possibly what operation type. I confess that I haven't got it all sorted out yet. I'm going to try and make a table of sorts:

Part	Type	Engine	Location	# alternates	Required fuel	Other
121	flag	turbine	?	0	2 hours

Sector Altitudes?

Question: What action should be taken when a pilot is "cleared for approach" while being radar vectored on an unpublished route?

Answer: Remain at last assigned altitude until established on a published route segment.

In Canada, cleared to the approach I would be able to, and probably would get into an untenable position later on the approach if I didn't, immediately descend to the 100 nm or 25 nm safe altitude published on the plate, as appropriate, in preparation for intersecting a published route segment. I would tell ATC I was "leaving one fife tousand for one zero tousand tree hundred" or whatever the sector altitude was, but I'm not sure I'd be required to do that. Saying it helps me remember it, and allows ATC to know what to expect.

I remember being told by a flight instructor long ago that in the US you were not allowed to descend immediately on being cleared for the approach, and commenters here told me that yes you were, but with this question I may have finally found the case that the original flight instructor was considering. It looks like if I'm on an airway or a published transition to an approach, cleared for the approach clears me to the MEA for that route, but if I'm off airway just being vectored towards the airport, I can't descend to a published safe altitude until directed? I suspect this is more because US airspace have more published transitions and routes and less just hammering around through the clag towards the NDB at the airport.

American Weeks?

What the heck does this mean?

Each dispatcher must be relieved of all duty with the certificate holder for at least 24 consecutive hours during any seven consecutive days or the equivalent thereof within any calendar month.

The dispatcher is supposed to have one day off every week? The dispatcher is supposed to have one week off every month? The dispatcher is supposed to have one day off every seven days, but if Monday is his day off, and it's March and March started on a Monday, and he's had the 1st, 8th, 15th, 22nd and 29th off so there are only three days left in the month he gets another day off because during the calendar month of March the last two days are equivalent to a week?

What does a calendar month have to do with anything? So there are different rules in long months than short ones? If it stopped after "seven consecutive days" it would make perfect sense. But what on earth could be equivalent to seven consecutive days, but wasn't adequately described by "seven consecutive days"?

And can ATPL holders automatically work as dispatchers in the US, or are they supposed to be policing their dispatchers' sleep schedules? Why would such a question be on a pilot's exam?

Also I have to know that if a drunk creates a disturbance on my aircraft I have five days to report it to the Administrator.

Lost Comm Altitude

If you are IFR in IMC and lose contact with ATC, you still have to fly somewhere. There are a set of logical rules that dictate the timing, route and altitude of that flight. I'd expect them to be the same in both countries, and they are almost word for word.

CFR 14, Part 91.185(c)(2) (USA)
Altitude. At the highest of the following altitudes or flight levels for the route segment being flown:
The altitude or flight level assigned in the last ATC clearance received;
The minimum altitude (converted, if appropriate, to minimum flight level as prescribed in § 91.121(c)) for IFR operations; or
The altitude or flight level ATC has advised may be expected in a further clearance.

versus

AIM 6.3.2.2 (b) (Canada)
Altitude: At the highest of the following altitudes or FLs for the route segment being flown: the altitude(s) or FLs assigned in the last ATC clearance received and acknowledged;
the minimum IFR altitude (see RAC 8.6.1); or
the altitude or FL ATC has advised may be expected in a further clearance. (The pilot shall commence climb to this altitude/FL at the time or point specified by ATC to expect further clearance/ altitude change.)

Curiously, while routing defaults to the flight plan, the flight planned altitude isn't mentioned in here, unless the last clearance received was the IFR readback including the flight planned altitude. So that means that if you're departing somewhere and really don't want to fly at the MEA to destination, you'd better get the controller to say "expect flight level 230" and not just "expect higher."

American Birds Follow Airspace Rules

Both countries have a speed limit of 250 knots below 10,000', unless you're flying an airplane so crazy that it would be unsafe to operate it at a lower speed. In Canada the next speed limit restricts you to below 200 knots below 3000' within ten nautical miles of a control zone. In the US, it's below 200 knots below 2500' within 4 nm of the airport inside a class Charlie or Delta control zone. But in a class Bravo control zone, fill your boots at up to 250 kts. I'm writing Charlie out in full for the US version because that's how they say it (we say "cee"). That will maybe help me remember.

According to a document I read recently, the low altitude speed limits were established to reduce the severity of bird strikes, but I'm guessing that was just for the 250 kt ones, because I can't see that the birds would pay really close attention to which airspace they are in. The 200 kt speed limit is probably to help ATC control different speed aircraft.

Although the Americans have most of the same airspace letters as Canada, they don't really line up. They have class Bravo control zones whereas we only have class B airspace over 12,500'. If you pretend US Bravo is Canadian C you'll follow all the right rules, ensuring you have a clearance before entering the airspace. At 200 knots or below.

We Interrupt This Sequence

I'm going to suspend the trip I've been describing right there to describe--and solicit your help with--the process of converting a Canadian ATPL to an FAA one. I have an opportunity for an interesting short term job, and potentially others in the longer term, if I have an FAA licence. Don't worry, Americans, I'm not stealing your jobs, the job is not in the USA and is not for an American company. It's for a company based in country A that is operating an airplane in country B and that airplane just happens to be N-registered, that is, it's registered in the US. The law says that the pilot's licence has to match the airplane registration. (In many cases you have a period of time, typically six months to a year, to make the transition from in internationally respected licence such as a Canadian one to the local licence, but not for the US).

The process involves getting an FAA medical certificate, passing a written exam, and putting them together with a bit of paperwork and a processing fee. I've already had the FAA physical, and am just waiting for their approval. I'm studying for the exam so I can have that written as soon as possible. I haven't yet figured out if I need to make an appointment to write it or can just show up at a testing centre. Er, I guess that's a testing "center."

My first impression as I look at the material to be studied is that there's a disconnect between what I have and what I'm converting to. There's an assumption that someone writing an ATPL level exam has mastered the material of the private pilot level, but I have to figure that out too. The material is totally unrelated to what I'll be doing, so there isn't a lot of point in thoroughly learning and understanding it. In the US all test bank questions are available in advance, so when you're in this situation you can just learn the correct answers with out really know why. I've never taken a test this way before, but when in Rome Washington, D.C. Things like I've learned that "part 91" means general aviation, "part 135" is on-demand air carriers and "part 121" is scheduled air carriers. But the questions mention "domestic carriers" and "flag carriers" and "supplemental air carriers." They must be defined somewhere. My local pilot shop has run out of the FAR/AIM because the new one is on order, so I've ordered one directly from the US.

I have to figure out how aircraft approach categories (A B C D) work in the US. There's something in the questions that implies that it's not just based on approach speed as in Canada. I have to figure out how the NOTAM system works. Apparently you get different sorts of NOTAMs with different letters from different sources.

Up until now I've almost deliberately not learned about US regulations that don't affect Canadian pilots (like needing one flight attendant for the first 10 passengers (in aircraft with a payload capacity of 7500 lbs and up) of for the first 20 passengers when the aircraft payload is under 7500. With 50 to 100 passengers you need two flight attendants, and one more for every fifty passengers or part thereof after that. And it's based on seating capacity, not boarded passengers, implying that you need three flight attendants for a B737-600 with four people in the back. Or something. Maybe I can store this in a part of my brain that's reusable.

What Kind of Airplane?

"Huh. Wow. What kind of airplane?"

As far as I remember, that's more or less the first thing I said ten years ago on learning that an airplane had hit the World Trade Center. Yeah, cringe, but I was trying to distinguish between incidents like this and something that would do more damage. Some context: I had driven to work listening to a CD (or maybe a cassette tape: it was an old car) because the radio reception along my commute was poor, and it wasn't a time of day when I could expect good programming. I had arrived, grabbed the aircraft documents, inspected the airplane, ensured it had been fuelled and come back to the airside office to drop off my preflight paperwork. It was a small shared office, so I had to squeeze between my coworkers and a television set to get to the filing cabinet where I needed to drop my operational flight plan and weight and balance documents. They were staring at the TV, but then it was a media-related company so they were always staring at the TV. On my way back outside to start the airplane, someone said, "An airplane just hit the World Trade Center." The TV wasn't at an angle that I could see it. In answer to my question, he told me it was a Learjet. I didn't even know which world trade centre it was. I assumed it was in the US, but I guessed Chicago, because the old airport was right by downtown. I ran up my airplane engine wondering if the crash was a control problem or pilot incapacitation or what.

I know someone who was woken up by a call from his friend that morning and ordered to turn on the TV. After seeing the burning buildings his response was even more cringeworthy than mine. "I think I've seen this movie."

My non-pilot coworker--yeah, I've always had jobs like this--jumped in the plane and tucked Walkman (look it up, kids) headphones under his aviation ones, as usual. I told you it was a media-heavy company. He was less conversational than usual, but I assumed this had to do with low caffeine intake, not realizing what he was hearing on the radio. Half an hour or so into the flight he said something was on fire.

"Where?" I asked, looking out the window for smoke or the flashing lights of firetrucks.

"The Pentagon is on fire," he repeated.

The pentagon? What pentagon? I sifted though associations with the word, my strongest image being something from witchcraft, imprisoning demons in a chalked pentagram ringed with candles. That made no sense. Then I thought of another possibility. "You mean bombs and missiles Pentagon?" I asked. He shushed me, so I tuned the ADF to a local news station, just in time to hear a synopsis of the morning's terrorism, and that US airspace had been closed.

Before I had a chance to call flight services to find out if this would affect me, the air traffic controller whose frequency I was on instructed me to land. I landed back at our base, not a major airport, and as I was on short final an ultralight took off, the pilot and the controller who cleared him still oblivious to the day's events.

This is probably the third time I've told the story on the blog and I imagine I've told it dozens of time in real life. Every generation has to have its "where were you?" moment. Ask an old American where they were when they heard Kennedy had been shot. (Yeah if you remember Kennedy, you're officially old. You're welcome). I hope the next such "everyone remembers where they were" event is a good one. There have been good ones, like humans landing on the moon. What amazing good thing could happen today that would be tweeted around the world and that would compel people to tell the story of where they were when it happened, even ten years later? What some people might consider good could be controversial, so please don't mock or condemn any commenter for their choice of an earthshaking positive moment. Is there anything? Or are we too jaded and too divided now to all be awed by an event?

Flipping Out Over Flight Planning

You know what's kind of annoying during flight planning? When you are working with both VFR and IFR charts and you have to remember to flip the VFR chart vertically and the IFR chart horizontally. Or is the other way around? If you always work with one or the other, it's no problem, it becomes instinctive. But when your job requires you to go IFR to work somewhere VFR or vice versa, you have to work with both. Flip. Damn. Flip. Flip. Damnit. Flip.

You know what's really annoying during flight planning? When the pilot forgets her copy of the job folder at the home base and doesn't have the paperwork she needs. Stupid. We've forgotten something almost every trip. The key. The GPU. That folder. In it is has a map of the lines and a list of the lines with their altitudes and photo blocks for each job, plus photo flight forms for each area control centre that we work with. I borrow the operator's map sheets, although they don't have the pilot-related mark up information I researched, and then I call Edmonton to fax me another copy of the missing form. They are happy to do so.

I think it's sweet that Edmonton Area Control Centre, which I frequently have cause to praise, has its own logo, and adorable that that logo looks like an old CP Air 737, but if the Nova Hotel is trying to impress me by putting hotel stationary instead of plain paper in their fax machine, it's not working.

Planning complete I taxied out, yold to the King Air, clomb to cruise altitude, shove five minutes of my filed flight time thanks to a tailwind and crew about it after landing. Or I would have, had the past tense of these English verbs not changed over the years. I kind of like yold and clomb, though. They sound better than yielded and climbed. Maybe I'll start a fad to reestablish them.

yield - yold
shave - shove
climb - clomb
crow - crew

The Shadin fuel flow meter always shows more fuel on board than there actually is. Taking notes, I think it may least accurate during high fuel flows. It always overreports fuel flow and underreports fuel remaining. I kind of like it that way, because I always have more fuel than it says. I still need to be careful though. A few years ago I hit a wingtip because a particular building always looked closer than it really was, and one day I took too much advantage of that safety margin. I cracked the plexiglass cover on the nav light and it had to be replaced. Maintenance shrugged and said it was the cost of doing business. The chief pilot said only, "The new one looks much better. Can you break the other one next?" The owner didn't say anything that I recall. I work with nice people.