Showing posts with label uncontrolled airports. Show all posts
Showing posts with label uncontrolled airports. Show all posts

Wednesday, January 14, 2015

Your Clearance Cancelled Time is Cancelled

I overheard this post title on switching to a frequency. No one has ever said that to me and I'm not certain which of two possible but contradictory meanings it might have. If I received it, I would ask a clarifying question, but the pilot who received it did not.

Before departing on an IFR flight, a pilot first files a flight plan, specifying for the air traffic control system exactly which route she intends to follow, with what timing. The flight plan may be filed online, by phone, or sometimes by radio. I usually file mine by phone, because I can do that while using my eyes and the non-phone-holding hand for other things, and can say what I'm doing in words rather than having to code it for the online form. I would only file by radio if I discovered while airborne a need to convert to an IFR flight, and I was out of cell tower range so I couldn't use my awesome Bluetooth headset-iPhone combo. (I didn't want Bluetooth at the time I bought the headset, but I needed a new headset RIGHT AWAY and that was all they had in stock. If you ever have reasons to talk to someone on the phone with your engine(s) running, get the Bluetooth. The days of holding the phone against your ear and yelling, "I can't hear you: I'm in the plane" are over).

The IFR flight plan is supposed to be filed minimum thirty minutes before departure, but the controllers are generally so awesome that the plan is coded and available in the system in minutes. When my company says, "Can we go to Fort Dead Royalty now?" and the flight requires an IFR clearance, I say "sure," file the flight plan for thirty minutes hence, and then board, start, run up and call for clearance. My actual take off time will usually be fifteen to twenty minutes after filing, and I'm calling for clearance as few as five minutes after filing, but it's almost always ready as soon as I need it.

The clearance I get may be identical to the one I filed, or it may be altered to comply with local procedures I didn't know about, specific runways that are active, or I may be cleared not to my destination airport but to an intermediate point, requireing me to get a new clearance before I leave that point. (Yes, I would have to stop and hold, flying in a little oval, if I hadn't received the clearance by then, but it's almost always given to me before I need it). If the airport I will be departing is a controlled airport, then when I am ready to take off, the tower controller will talk on the phone to the IFR departure/en route controllers and get an IFR release, allowing them to clear me for take off. But if the airport is uncontrolled: unstaffed or staffed only by a Flight Service Specialist, the initial IFR clearance will include a clearance cancelled time. The controller giving me the clearance is going to ensure there is a space in the system for me, but if I'm not airborne by the clearance cancelled time, I'm not allowed to go, because my space will have passed by. My departure clearance will have been cancelled. Sometimes there is also a clearance valid time, meaning that I can depart any time between the clearance valid and clearance cancelled time.

So if I were given a clearance cancelled time, and then my clearance cancelled time were cancelled, my first guess is that that means the traffic that was going to be a problem after the clearance cancelled time is no longer considered to be interfering with me--perhaps it has changed course or altitude--and that I can delay as long as I like before take off. My second guess is that "your clearance cancelled time is cancelled" is synonymous with "your clearance is cancelled." I'm ninety-five per cent sure that the first meaning is correct, but because there is a chance that I'm wrong, I'd ask. Beats getting run over by a Boeing 737.

Monday, September 16, 2013

Not Stranded at Animal Waterbody

Those of you who haven't followed this blog for years may not know that almost every town in Canada is named after an animal, a body of water or both. If you think it isn't, chances are that it is, just in another language. Also members of the Royal Family and European explorers count as animals. Place names in this blog are often not named after the same animals and bodies of water as they are in real life. Our story begins in

I preflighted an airplane that was parked at Antelope airport this morning. It was clean and had all the right parts attached the right way around, but had mysterious scratches on the inside of the pilot's side window. I think there may have been a seat removal incident. (Getting seats in an out of an airplane is sometimes a topological challenge). The side windows I use more for finding the runway than finding traffic, so the scratches aren't a tragic impediment.

I confirmed the fuel load and then filed two IFR flight plans: one from Beaver Bridge to Civet Creet and one from Civet Creek to Duck Ditch. Then I loaded the airplane and flew it on a VFR itinerary (meaning with no flight plan at all, just my company keeping track of where I am) from Antelope to Beaver. I then departed Beaver on the filed IFR flight plan, but before I reached Civet, asked Centre to pull up my subsequent flight plan from Civet to Duck and asked to now intercept that pla, without actually landing at Civet. They were okay with that, so we did it. About three hours after that, we were discussing the relative merits of landing at Elk, Fox and Gopher. The fuel at Elk was by callout only, and this was a holiday weekend. I've never been to Fox, but the CFS makes it seem like a reasonable place, and with no hours given on the fuel service, it must be self-serve. Fuel is self-serve at Gopher, too, but the airport is really remote and kind of an awkward set up. If we go there and something is wrong we won't have the fuel to go anywhere else, and we'll be stuck there until the long weekend is over.

You'll notice that Elk, Fox, and Gopher weren't on the menu this morning. I definitely didn't check NOTAMs for Gopher. I don't like Gopher much. They have dingy hotels and restaurants. But the airport is fine, if you aren't in a hurry for your fuel. I try to call Flight Services. I'm in the flight levels, something like 20,000' and I can't reach Flight Services on any of the surrounding frequencies, in two different FIRs. Usually the flight follower also acts as ground support, but it's a long weekend, and someone is out on compassionate leave, so the flight follower today is the company president, holding a cell phone that we can send satellite texts to, but don't want to disturb just to ask for a NOTAM.

Finally I ask the Centre controller if he can see if there are any NOTAMs for Gopher, for me. He says doesn't have access, and I understand. But a few minutes later he comes back and tells me no NOTAMs for Gopher. I thank him, explaining that we're considering landing there and I really didn't want to spend the rest of the weekend there if there wasn't fuel. He says, "No kidding!" in such a heartfelt way that I suspect he had personal experience with the place. I advise the controller that in five minutes are going to start a descent out of high level airspace, cancel IFR and land at Gopher. Could we please get an appropriate altimeter setting? The field has none, but he finds one not too far away and there is a huge ridge of high pressure, so they should be about the same. He asks me to report through 18,000'.

Through 18,000' I call, but there's no reply. I try again on the back up frequency he gave me--it's common in remote areas for controllers to give you a "if I lose you on this frequency, try me on ___," instruction. I hear another aircraft make a call on this frequency, but when I call to ask for a relay they don't respond. I'm not going back up to make a call that I was told to make below. I suspected this might happen. That's why I told him what I was going to do before starting my descent. I continue down, trusting the controller will figure it out. The CFS says that there is an abandoned aerodrome a mile east from my destination, so I look carefully, trying to spot the old one so I know I've correctly identified the new one. I can only see one, and the one I see doesn't appear to have any pavement markings. I'm about to circle west, but then I see two airplanes and a functional windsock at this one. The pavement markings are very faded, but present.

Once I land I make a quick phone call to let the IFR controllers know I'm down and that I tried to call when they told me to. They seem unconcerned. The fuel pump works, and we use it. Our next leg is VFR and we just advise the flight follower, no flight plan.

Saturday, May 26, 2012

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.