Saturday, August 21, 2010

Anchorage Tourists

The next day I check the METAR to determine the temperature, and then dress accordingly to go for a run. Anchorage in June (yeah that's how far behind I am in blogging!) is really comfortable. The whole city is more or less the temperature of an air conditioned gym. As I run through the streets around the hotel, I imagine someone coming here from somewhere down south where air conditioners run year round. It would be an amazing thing to such a person to have the outdoors be a comfortable temperature for physical exercise. Or perhaps they would think it was shivering cold; I'm sure they would be appalled by winter temperatures, even though Anchorage is right on the sea, so the winter lows aren't that bad. I'll bet the airframe icing is horrendous in the spring and fall, though.

The suburbs I'm running through are pretty much the same as suburbs in any other American city. Paved streets, sidewalks, painted crosswalks, wooden fences in good repair, landscaping, houses of various styles, tame dogs in yards, late model cars with windshields and glass windows all the way around, blue mailboxes, a school--I think it even had a sign proclaiming it to be a drug-free zone. Most of you are probably reading that wondering what sort of idiot I am expecting anything else. I wasn't really, but I was prepared for it to be a few steps towards Nunavut on the comfort and civilization continuum, not indistinguishable from Boise, Idaho. Alaska has stereotypes to uphold!

There's a park I could run through, and if I have my geography right it goes towards Hood Lake, but the trail is really rocky and I don't want to turn an ankle while I'm running, so I stay on the sidewalks and turn back to the hotel for breakfast. While I'm in the lobby eating my muffin and Cheerios, a tourist points out a moose in the bushes beside the parking lot. It's just hanging out there eating. I suppose there are moose in Boise, too, but this one is here, fulfilling the Alaska stereotype. Thanks, moose.

The client's head office wasn't prepared for us to be done this mission on a Sunday, so they haven't made all the necessary arrangements, giving us a couple of days opportunity for being tourists. We drive around and start checking out the tourist spots.

Downtown Anchorage is a tourist town, easy to walk around with lots of cafes, restaurants, art galleries and souvenir shops. We visit, for example, the Oomingmak Musk Ox Producers' Co-operative. It's part educational display, part store. Musk oxen live as far north as Cambridge Bay in Canada, but were hunted to extinction in Alaska, so their herds descend from domesticated animals brought from Greenland. I admit that I am baffled as to how such a large ungulate can derive sufficient calories from the sparse winter vegetation in the wild, but they do. They clearly need exceptionally warm wool. I imagine the Inuit, or Eskimos as they are still called here, have used musk ox wool for millennia but these aren't really traditional native crafts. They comb hair out of domestic musk oxen during the spring shedding season and then ship it to Asia to be carded and spun. The resulting yarn is sent out to knitters in the communities who make it into garments which the coop then sells. It's very soft and warm, like cashmere, and with prices to match.

We also go to the Ulu knife factory. It's in an industrial area across the canal and we drive there with me navigating. We have to turn left on Ship Creek, that's Ship Creek. I wonder if it was named that on purpose, for the double entendre. They don't sell paddles, just knives and cutting boards. An ulu knife has a semicircular blade with a handle on the top, and is a modern version of a native all-purpose stone tool. I bought one with a bone handle, after first making sure that it wasn't made from an endangered or protected species. They had some with handles made of petrified whale bone, and I wasn't sure if it would be legal to import into Canada. Whale products can't be imported, but does petrified bone count as being made out of whale or stone? I didn't chance getting arrested having it confiscated to find out. My favourite sculpture from the galleries we saw was made from a long-weathered whale vertebra. The bone demineralizes over time--or maybe the whale died with advanced osteoporosis--leaving a beatiful porous texture. I can't find a picture of the sort of sclupture I admired most, but here is someone else's work showing the texture. The ones I liked had less detail and were abstract, just playing with the existing shape and texture of the vertebrae. They even had petrified mammoth bone as an ulu handle choice, but cool as it is to think of having a part of an extinct arctic elephant, I didn't find it very attractive.

There are a lot of really fine restaurants in Anchorage, and we took advantage of the opportunity not to eat boring chain restaurant food. We had Pacific salmon, Alaska king crab, arctic char, and reindeer (it's illegal to sell caribou meat in Alaska, so they farm reindeer. They're the same species, just a different lineage). My favourite dish, however, wasn't local at all. It was a beef tips in coconut curry with basil at a restaurant named Ginger. It was so good I wanted to stick my face in the bowl to lick it clean.

One of our clients was in a store today buying supplies, and the clerk asked him where he was headed. He answered with the name of our next destination and two unrelated customers within earshot both groaned in sympathy, and the clerk said, "Oh, I'm sorry." It sounds as if Alaska may have places akin to Attiwapiskat, after all. Every time we check the weather there is is IFR or at best marginal VFR with low cloud or mist, and raining.

Also we will have to haul close to a thousand pounds of our clients' gear to the remote site. They usually drive it, but there are no roads that lead where we are going. I call around looking for cargo tiedown anchors to fit our seatrails, but no joy. I swear these things are migratory, and someday I will find where they all go and harvest them. Honestly, has anyone ever broken a cargo tiedown? No. They just wander off.

Friday, August 20, 2010

Delayed Reporting Time

So I slept, or at least held my eyes closed and thought about how I'd better be sleeping, or I was going to be really tired tomorrow, from around six p.m. to 2 a.m., woke up, turned on the computer, got dressed while it unhibernated, and at 2:05 am determined that it had been raining for the last six hours and was forecast to continue doing so for the rest of the thirty-six hour forecast period. I looked outside and yeah, it wasn't raining hard. There were still dry spots under parked cars, but it was raining.

So our meeting was short. I called ATC and the people who were looking after our airplane and told them the flight was cancelled. And then I went back to bed. At that point I noticed that the bedside clock was an hour slow, which made getting up in the middle of the night when it's still light out and then not getting up after all seem all the more surreal. Did it really happen?

I went back to bed and slept until I was done sleeping, which was about six hours. Now, it hasn't been dark yet, and I've slept twice. What day is it? Alaska is confusing, and duty time laws even more so.

We were supposed to report for work at two a.m. but simply woke up and went back to bed fifteen minutes later without leaving the hotel. So what time does our duty day end now?

Part 700.18 of the Canadian Air Regulations says:

Where a flight crew member is notified of a delay in reporting time before leaving a rest facility and the delay is in excess of 3 hours, the flight crew member's flight duty time is considered to have started 3 hours after the original reporting time.

That's the rule that best applies here. For the first six hours of delay, it also gives an advantage--to the person optimising pilot utilization--over the split duty day rule, which allows a duty day extension of one to three hours: one hour of extension for each two hours of rest in the middle of the duty day. For a delay greater than six hours but less than eight hours, the results are identical to applying the split duty day rule. If the delay were a full eight hours, plus time for meals and personal hygiene, then it would be a new day. It's that rather than the calendar or daylight that determine when a pilot's new day dawns.

If our rest period continues without interruption until eleven or so, the duty day has been technically reset, and we could legally be asked to work a fifteen hour day starting any time after then, say five p.m. until eight a.m. tomorrow morning. That would be nasty, but every once in a while the work demands it. There are some other factors that come into play, the trump card being that if we the pilots consider that we are fatigued or likelt to become fatigued as a result of a schedule, we're bound in law to refuse it.

That's the law, here's the application. At nine a.m. not only has it stopped raining, but all forecast of rain is gone from the TAF. I call back ATC and ask when our next window is for the work. Sunday morning is a pretty quiet time at most airports, but PANC isn't most airports. It's the same lady, what kind of duty days do they have? She's a realist though, and I guess she doesn't have vacation comng this week. After some more hmming and making sure I know just how inconvenient this is, she verbally shrugs, "Sooner you start the better." I call everyone to say we're a go, again, and we'll be airborne within the hour.

Out at the airplane, the FBO has reconnected the nosegear scissors after towing. That's rare. but they've screwed up the billing despite my "FUEL ONLY" verbal and post -it-ed designation of the credit card number I gave them. They'll sort it out later. We've decided to fly this two-crew, because of the busy-ness of both the airspace and the radio work. I ask the other pilot if he wants to drive or talk. He says he'd rather leave the talking to me, if I don't mind. He says I'm good at talking to authority figures. He just knows I love to yap. It's the role I would have chosen. The flying isn't different from what we do every day, but the ATC negotiation and traffic will be interesting.

I call clearance delivery right after start up on the ramp and they already know all about us and our unusual mission, so I don't have to do any explaining. They assign me a transponder code and a runway. I ask if they'd like to assign us a temporary operational callsign for the mission, "to avoid all the alphabet soup." This is for me as much as them, because American controllers won't shorten my five letter callsign to the last three the way Canadians will, and they will pronounce the C maybe as Charlie, maybe as Canadian, sometimes include the type and sometimes not, sometimes pronounce the letters in the phonetic alphabet and sometimes just use their names the way they are pronounced in the alphabet song, and just the way you may not hear your name when it is called by someone who pronounces it incorrectly, I may miss a call for me. And I don't want to spend the next five hours reciting my entire callsign in every call. "Sure," says the controller, "what do you want to be?" They want ME to pick? I make something up on the spot, almost as cool as AIRSHARK ONE. They accept it unblinkingly and tell me to call tower for taxi. I acknowledge, laughing as I release the mike button, because I'm an AIRSHARK! I'm hoping that I haven't stolen someone else's handle or done something illegal here. I was expecting ATC to assign me something convenient for them, usually just the type and a number, or a part of my full registration.

We taxi to the threshold of the runway, take off and start work. It's fun. It's awesome. Anchorage is an awesome area, with sea and mountains and a big inlet and airplanes everywhere. At first ATC asks us to call every turn, but they quickly realize that we are going to do exactly what we say we are going to, with clockwork predictability. If I turn the tracklines on on the GPS they make pretty patterns, because even the turns are close to identical. As I'm not flying, I can see the whole ballet unfolding, and keep expecting being asked to turn aside, wait twenty seconds, extend a line or modify a turn.

We play chicken with B747s flown by pilots with minimal English skills, counting on their comprehension, flight plans or habits to have them turn east at four hundred feet. We do what feels like an airshow pass with big-yet-manoeverable metal inbount to Elmendorf air base. "I acknowledged having it in sight without remembering what it was. We report sighting the helicopters, float planes, and even other aircraft the same type as us as they look out for us. An advantage I didn't consider of being AIRSHARK is that we're not advertising the foreign callsign.

Over the course of the flight we were handled by five different controllers, working quite long stints at the mike, considering that they kept up a continuous stream of instructions, advisories and clearances. And after all that time, ATC has not delayed our relentless progress through the grid by as much as one second. They are moving the massive Boeings around us. It's now well into the working day, but they aren't asking us to give them a break, either. Man, they really want to get rid of us.

We told them when we had flown our last line and were cleared in to land, with a Korean Airlines B747 waiting at the hold short line for us. We taxi off triumphant and proud. I call the ground controller and ask him to convey our thanks to everyone involved. Anchorage ATC are awesome. They took full responsibility for a very awkward flight, never asking me to change frequencies nor wasting a second of our time.

I'm on a high after accomplishing this mission. The ultimate in happiness for me is achieving something as part of a team when we weren't sure that it could be done. To get this done the second full day in Alaska is beyond expectations. Except for the pessimist's expectation that the more you want to have an opportunity to explore a place, the quicker you will be yanked out to go somewhere else.

Our supper restaurant has placemats with a map of Alaska on them, and we look at them to see where we're going next. Hmm. The annotation for that region of Alaska says that it is "cool and foggy" in the summer. Just what we don't need. And the food is truly awful.

Thursday, August 19, 2010

You Want To Do What?

The source of charts that was recommended close to the hotel appears to be primarily a doctor's office that does pilot medicals. They used to sells charts, hence the "Pilot Shop" neon sign visible from the parking lot, but no longer do, so the chart purchase will wait until tomorrow.

Alaska is so far west that every time zone gets up earlier. I've been working mornings, so I wake up early and by our eight a.m. planning meeting I have finished my laundry and gone for a run. After the meeting, the two pilots drive over to Merrill Field. It's a municipal airport, but it stuns us. You know what a mall parking lot looks like when it's busy? Well imagine that, except with airplanes instead of SUVs and hatchbacks. There are hundreds of airplanes here, mostly utilitarian single engine personal transport, all parked in rows on numerous aprons. A large enough proportion are tailwheel that it makes the tricycle gear airplanes looks kind of ... unconventional. The only place I've ever seen this many airplanes in one place is at the Oshkosh fly-in (welcome back those of you who went this year, and thanks for the e-mails and pictures), and my colleague has never been to Oshkosh. He has never seen this many airplanes in one place,anywhere. If you're not an aviation aficionado (although I suppose there aren't many in that category reading this blog), you may not have seen this many airplanes, ever, cumulatively. We're definitely not bothered by the fact that addresses at the airport aren't very useful and we just have to drive around looking for the store.

The recommended store isn't open yet this Saturday morning, so we try a flying school. They are open and have some charts, but are out of the "Alaska Supplement." Curiously, in Canada, the book that tells you details about airports is called the Canada Flight Supplement. In the contiguous American states such books are called airport facilities directories, and they're green. But in Alaska that document is called a supplement again. It's the same format as the AF/D, except that it's orange. I spent a while at first trying to buy an A/FD or a "green book" for Alaska, before I discovered the secret. We chat with the flight instructor about flying here, looking for local information.

When the other chart store opens we go there, and wow, they have every chart. I think they have every sectional and WAC for the whole US and they have Canadian charts that we can't get at home. And they're cheap. We start buying everything we could conceivably use in the next month. We know we're going out to west next, so buy sectionals in that direction. The last WAC doesn't have too much of the mainland on it and we open it up, wondering if it's worth getting. It has part of Russia on it. "Cool, we have to get it!"

There's one chart that isn't available there, so we go down the street to a charter company that may have them. The outfit looks like a cartoon about a dodgy Alaska charter company and I can't entirely tell whether this is something they put on for the tourists, or if that's really the way they are. A sign says "Use This Door" on the least likely looking door. It goes into a small hangar in which the shelves are filled with old baby car seats. There's no one there. We try the other door, and it goes to an office with a scheduling whiteboard, where someone sells us charts. I suppose the door to be used is the one through which arriving passengers reach the boarding area, and they don't want all the passengers in the dispatch office. And I guess the baby seats are for babies on the airplanes.

We did a few more errands, like activating US cellphone plans, buying souvenirs and replacing a computer cooling fan, then went back to the hotel where I started negotiations.

I first laid out the local terminal area chart, the contracted flight grid, and an Anchorage street map, in order to determine multiple ways to describe the area we needed to overfly, and to familiarize myself with the airspace we will be disrupting, and with any landmarks that the local controllers might use in discussing the proposed flight. I look in the flight supplement for a starter phone number.

It's a starter phone number because I know that I will reach someone who then has to transfer me to someone else, who will give me another person to call, who will be on vacation for two weeks, and so on. It's part of the job. I call the starter number. Anchorage is actually very well organized in the ATC department. The person who answers listens, appears to understand and transfers me and this happens once more before I am given a new number to call. I tell each successive person who has referred me, until I'm talking to an Anchorage tower cab shift supervisor.

I identify myself and the aircraft, describe what we need and our constraints, emphasizing our flexibility and willingness to work with their schedule anytime throughout the twenty-four hour day. We're hoping to start tomorrow morning. The shift supervisor listens, asks a few questions and says that shouldn't be a problem. I can hardly believe it. I thought there would be tantrums. I'm sort of disappointed. He needs me to send him a map. I e-mail it, and call back to discuss it, but he didn't get the attachment. I try again, cc:ing the e-mail to my other account so I can look at it myself. It looks perfectly fine to me, but he still hasn't received it. Perhaps the FAA firewall has eaten it. He asks me to fax it. The map the client has provided shows red and black lines on a green Google Earth background. There is no way on God's green, black and red Earth that this will fax legibly. I offer to drive over and deliver it in person, but that is more complicated than it might appear. An FAA ATC facility has very tight security, and this one, like most is too understaffed to spare someone to come out of the secure area to receive a hand-delivered map. Instead, I redraw it freehand on the back of an old operational flight plan, showing the control zone boundaries, shoreline, and major roads, then take it to the hotel front desk and have them fax it. The shift supervisor says he is off tomorrow so to call and confirm with the next shift.

At this point I made like a normal person and went for a late lunch downtown with my coworker at an excellent brewpub we found by Googling "Food Anchorage." We only went the once, because when we tried to go back it was always too busy to get a table.

Back at the hotel I call PANC tower again and ask for the shift supervisor. The new one is on duty, she has received the map, and she is not happy about our proposal. Ten years ago I had to brace myself to ask an air traffic controller if I could cut across the ILS approach path at a major airport. Today it's just part of the fun getting one to approve my spending five hours flying a fine grid that covers the entire airport at 1700' agl, with turns in all approach and departure paths, and the airspace of numerous surrounding airports, possibly including one military one. I acknowledge sympathetically that this will be very inconvenient for her. But I don't take her problem away. I present our areas of flexibility: we're prepared to work any time through the twenty-four hour day. We can move off our line or altitude immediately at any point (but we will have to come back to the same point, and that will take more time). We can fly the lines in any order. We can't compromise on altitude.

I wait for her response. We know we're asking for a lot, and we've budgeted time for the work, but the weather is going to be good this weekend, and in Alaska good weather is never a given. We can't fly this mission in the rain.

She doesn't say, "What makes you think you can do this?" but she must be thinking it. She asks what the work is for. I don't know exactly what it's for; I almost never do. But I know whom it's for. I tell her. It's my trump card. She's not stupid. She knows we have to do this, and she realizes that the sooner we get it done, the sooner we'll be out of her hair.

"We don't really have quiet times here." I know. They are a major courier hub and have passengers arriving from all over the world, as well as smaller aircraft from all over Alaska and plenty of local traffic. She offers us two a.m. to four thirty a.m. tomorrow morning. Rapid duty day math tells me that if we go to bed immediately we can reset our duty days and be back at work at two. I tell her that we plan a take-off at two-thirty a.m., that we'll make another phone call before take-off, and thank you.

Then I call the rest of the team to let them know we're a go, and jump into bed. It's hard, but as a pilot you kind of have to have an "off" switch, in order to be properly rested. I'm anticipating a week of choppy sleep and weird duty days as we try to schedule this work.

Wednesday, August 18, 2010

Safety is What You Make It

When you fly, even if you're a jaded, experienced traveller, and know how to hide your notebook computer under your jacket when the flight attendant looks at you, please put it away. Stow your carry on baggage completely and don't hold heavy objects during takeoff and landing. Fasten your seatbelt tightly. Pay rapt attention to the safety briefing and any instructions from the flight attendants. I understand that a certain joking fatalism is a common defense mechanism to avoid thinking about what could happen, but it's better to think and be prepared. There are survivable airplane crashes. Here's a B737 torn apart by impact forces, but the only death associated is suspected to be a heart attack and not the immediate result of injuries sustained. There was no fire, and clearly the nearest emergency exit to many people would be the gaping hole where the fuselage ended, so no one was trapped.

I don't have any information on what happened to cause that crash. It sounds like they might have encountered a sudden downdraft. I'll try to follow up when the investigation reports a result.

Another story, related only in that it takes place in Colombia has a reader of this blog flying as a passenger in Colombia, in what he thought was a small pressurized airplane, about ten to fifteen passengers on board. And it was raining inside the plane. It's not clear if it was raining outside and leaking or if there was condensation leaking out of the headliners, but the folks in the back were getting wet. A passenger yelled up to the cockpit that it was raining inside and we were all going to die. The FO turned around and his enraged response was, "Callate por favor! Tenemos problemas mas grande aqui al frente ... no podemos ver nada, hay montañas en todas partes aca y hemos perdido contacto con... ."

I'll give the Spanish speakers a chance to gasp and or laugh at that while the others can wonder what they'd think about the FO yelling incoherently at them. He was yelling, "Would you please shut up! We've got bigger problems up front ... we can't see anything, there's mountains everywhere, and we've lost contact with ..."

The person who told me that story says he prayed until a safe landing and never again took a "non-reputable" airline in South America. Ironically, the day before he had read a very similar account in a story from 1945. Some things never change.

It's not that people in Colombia cannot fly safely, maintain airplanes safely or do everything else to any arbitrary safety standard. There is no absolute safety, only a level that you choose to maintain. It's just that the normal level of what is generally considered to be 'sufficiently safe' is different from place to place. The roads in different countries aren't built to the same standards; South American buses are a cliché. A lot of it is money: money for parts, inspection, training, maintenance and infrastructure too. It would cost the same amount of money to build and maintain one road to US department of highway standards as it costs Colombia to build and maintain any number of roads. The degree of safety in any organization is balanced between money available, regulatory pressures, regulator oversight, competition on price, customer demands, and inertia of the current practices and procedures. In any organization you get the safety you work and pay for. There are freak accidents, yes, but there are also freak 'almost accidents' that warn alert companies of the possibility of actual ones.

Tuesday, August 17, 2010

Sweet, We're In Alaska!

In Whitehorse we're cleared to taxi and then take-off, with no restrictions on turns or altitude, so we're quickly on course for the United States. (I keep saying that, because it's so weird). The weather is definitely poor to the south, but along the highway it's excellent. We look from the dotted line on the GPS to the ground, trying to spot some evidence of the actual border. There's not a river for it it follow, just an arbitrary straight line, and they probably don't mow a line in the trees up here like they do along the 49th parallel in western Canada. We see a pull off with a large building on the highway and conclude that that is the border control station. Kind of low-key, but I doubt it's a hotbed of smuggling.

We soar over mighty rivers and past majestic mountains. All that stuff. Looks just like the Yukon, so far. Which is nothing to scoff at. Our flight plan calls for us to hang a left at an airport with customs, I think it was called Tok. The GPS tells us where it is and we can see the pass to enter on the left. As we make the turn the PIC asks, "did you actually see the airport?" I didn't. It's a broad flat, kind of swampy area with a road running through it. The airport should have been pretty obvious. We shrug and continue on, deciding that perhaps it was a waterdrome. I looked it up just now, and it's a 1700' dirt strip, so we can be forgiven for missing it. But it shows how reliant we have become on GPS. I can't imagine ten years ago turning into a mountain pass without ensuring all the landmarks required to identify it were there.

We have two GPSes working on the project right now, the Garmin 496 and the 430. The 496 is a much better tool for this job, because the 430 is designed for IFR and if it had a personality it would be reduced to a quivering wreck by the proximity of rocks in a pass like this. We can't set a comfortable zoom level on it and use it to look around corners for rocks, because it zooms in close and sounds an alarm whenever we snuggle up to the right side of the pass. The 496 just puts up an inset covered in Xs that it thinks we're going to hit. We always turn so we don't.

The weather in the pass is surprisingly poor, dumping rain on us and reducing visibility in mist. It's really nice to have two pilots in here to confirm the navigation without having to look away from the window. It's a bit of a twisty pass. It's in the middle of nowhere, but there's an RCO, a remote communications outlet, right in the pass, so I can file a PIREP while we negotiate it. Pretty cool. We go around another corner and the weather is fine again. Here we are hooking up with the road (which took a different route) as the pass dwindles back to swamp.

Yeah, swamp. By my estimate almost all the bits of Alaska that aren't mountains or rivers are swamps. Do they call it muskeg here? I forgot to ask. There are hectares and hectares of swampland. Must be millions of mosquitoes down there. It's honestly a bit of a letdown. Alaska gets so much press and here it is looking exactly like northern Alberta. Or northern Saskatchewan, Manitoba, or Ontario. It doesn't have the sweeping rocky look of the Northwest Territories. It probably looks awesome all covered with snow, though. Great for snow machines.

The bad weather that was to the south is now to the southeast, we've kind of gone around it. There are mountains over there and as we draw closer their spectacular beauty makes up for the swamp. Between the rocks are huge glaciers. I don't think we appreciated how huge. I know that at first I thought the one in the picture was a road coming out of the mountains, you know how a road that has snow on it stays snow-covered well after the surrounding snow has melted, because traffic has compacted the snow? Then I looked at it longer and realized that it was a giant glacier. The roadlike ribbon of ice continues out of the photo to the right. I just couldn't fit it all in. Glaciers aren't very photogenic. You really have to go and look at them.

There was an RV park at the foot of one glacier, close enough that you could probably smell the ice from there. If I were to come to Alaska as a tourist in a motorhome, I would definitely want to stay at that RV park. While the mountains with their glaciers and bad weather are to the left, the hills to the right have a curious sandy quality to them. Maybe it's different rock, or maybe just the way the weather comes through that have given them different erosion or vegetation. I need a geologist to follow me around and tell me what I see.

The sandstone side approaches the rock side more closely and we go to the right of a hill in between the two. That turns out to be a shame, because as we come out the other side of the hill we realize we missed a close flyby of another glacier. Maybe on the way back. If we were doing this for fun we would definitely have headed over closer to check out the glaciers better, but we have a customs ETA into Anchorage soon, and we're not being paid to sightsee.

Also recall that we have been unable to buy proper Alaska charts. We're working off the GPS database and the information I've researched on the net and printed off. It should be pretty good, but you never know. We should be within radio contact of Anchorage around the next corner. We are, and the Anchorage area is a long, broad inlet. We pick up the ATIS approaching Wasilla--yes the Wasilla of which Sarah Palin was mayor. It appears to be a suburb of Anchorage rather than the isolated Alaskan village I had pictured. There are dozens of airports on the delta. I call Anchorage approach with our position, and intentions, and they assign us a squawk code and ask if we're familiar with the something-or-other VFR route. We're not, so they give us a vector. We rejoice. A vector means we can't screw up too horrifically now. We're under ATC control. As long as we do what we're told and we can't blunder into any airspace we didn't know about. Real professional, I know. I promise I'm embarrassed about this.

The vector takes us downwind along the west shore of the inlet, then they give us a new vector, taking us further west. I think at first that I've misheard the instruction, it's away from the airport and we're already 20 miles away, but that's where they want us to go. We hook up with a base leg, and then final. I have the airport diagram out and verify our assigned runway, 7L. It intersects runway 14 a thousand or so feet in.

A couple miles back on final the controller asks us where we are parking. I'm glad I did my research and can answer with the name of the FBO. I call back on short final to add that we're going to customs first. I don't know whether their question was to determine whom to bill for our landing fee, or what taxi instructions to give us, so now they have both pieces of information.

Flaps are down, gear is down, cleared to land--we were cleared to land ages ago--and then just as we flare they ask us to go around. We don't see the reason, but the controller obviously does so we don't question it. The PIC does a textbook go around, transitioning from going down to going up very smoothly and cleaning up the airplane. We then follow further instructions to turn around and fly a close right downwind for another try. We are rolling out of the 180 when the controller changes his mind again, "Can you accept runway 32 from there?" It's a complete chop and drop, with runway 32 right there off our right wing but my coworker nods and we put it on the runway. This actually puts us closer to customs. It's almost straight in front of us as we turn off at the first convenient taxiway.

The controller thanks us for our cooperation and gives us a long taxi clearance which I copy down and read back. Much of PANC is one huge stretch of pavement with taxiways being defined routes over that slab. I don't get to just beeline across the pavement to the customs hall. I always find it a little harder to find my turns in this scenario. I like it when there's grass or dirt between the taxiways. I study the taxiway diagram then realize that the route we've been given does not go to customs. It's to the FBO. I call ground back and reiterate our need to clear customs, so they give us a new taxi clearance. We successfully find customs and shut down. I pull out the aircraft documents, my licence and passport, and the rest of our paperwork, and then open the rear door for the arrival of the customs agent.

He comes out quite quickly and is friendly. After checking the airplane paperwork against the letters painted on the vertical stabilizer, he asks us to bring our paperwork and come inside. We follow him through a secured door into an enormous customs hall, an area that could accommodate a B747 full of people, but aside from a few other customs officers, no one else is there. He takes us over to the desk labelled "crew line," where someone else checks our paperwork and types things into his computer. They also direct us to a phone where we can close our VFR flight plan. Our customs escort is also a pilot; we soon learn that practically everyone in Alaska is. I think we disappoint him by not remembering the names of the passes and glaciers along our route. I feel a little guilty knowing that this casually executed, spontaneous and underplanned jaunt is the trip of a lifetime that I'm sure many pilots spend years plotting. Sorry.

Back in the airplane we start up and taxi to the south side of the airport. Ground switches us to tower in order to taxi across the parallel runways, one of which temporarily doesn't exist, due to construction. A friendly woman with a stop/slow sign waves as we taxi through the construction zone. I'm guessing that airplanes always have right of way through construction, and her job is to stop any trucks that might be approaching as we move through. The FBO is the first one on the other side and we park and shut down under the direction of a marshaller.

We take our bags and head inside. There is great consternation amongst the staff that they didn't know we were coming. One of them has dialed the manager, who isn't in today, and he gives me the phone. Darn. The guy I spoke to didn't make it clear that I needed an explicit reservation. I guess he thought all airports were like that. The manager, however, apologizes profusely for not being prepared for our arrival. I affirm that I did call ahead, but didn't give a definite arrival time or date because I didn't know for sure at the time. Is this going to be a problem? I tell him that I don't need anything special like ice. As I say that, it occurs to me that ice is amusingly far from "something special" in Alaska, so I amend it to caviar sandwiches. The manager, whose name is Louis, says that he could probably get us caviar sandwiches if we wanted them, and that we are welcome to stay there. I guess we pass the screening.

The one thing we do need is charts. Those turn out to be a bit of a problem. We describe the ones we want, but they only have some expired ones for reference. Louis makes some calls and then tells us where we can get them. They aren't available on the field, but there are two sources, one quite near our hotel and another an FBO at a nearby airport.

Meanwhile our customers have arrived via the airlines so they come and pick us up. We check into the hotel, which has small but nice rooms, and the twenty-four hours of daylight mean that I don't really mind that most of the lightbulbs are missing. There is a comfortable windowseat with a view of the mountains. Just before I go to bed I find out what the job here is. Oh boy. This is going to take some diplomacy.



Also, a former senator with the same name as the airport, Ted Stevens, just died in an air crash. I think he may be the airport namesake even though he was still alive when the airport was named. Americans don't always seem to wait until people are dead before naming things after them.

Monday, August 16, 2010

On the Marge

The next day we load the airplane with our personal gear, cursing as usual the paucity of tiedown points in this thing. Once everything is packed and secured, I call the customs broker to tell him we really are going today. He's used to our 'hurry up and wait' schedules, but now the US won't let us postpone arrival permission from day to day, so he can't file the paperwork and let us catch up to it anymore. Everything has to be done the same day. Good thing I called, because a pilot switch means he doesn't have all the current details on my coworker. I grab his passport out of his bag and provide the broker with the relevant details, and with an estimated time and place for our penetration of US airspace en route. I have to call him again from Whitehorse to get a fax sent to the FBO.

It's very weird for me to be going north across the border to the US. I'm used to going north out of the usual infrastructure of Canadian life. And I'm used to going south across the US border. I'm afraid I'm going to forget some basic rule of going to the US, just because I'm going the wrong way. To me the US being "south of the border" is as cliched as Mexico is in the US. I just received an Aeroplan e-mail that starts "Want to take flight south of the border? Treat yourself to a 10% discount with Aeroplan." It's valid for any flight to the U.S. Imagine if Mexico had a part that was right in the middle of Kansas and that's how disorienting this is.

We take off and fly north, or actually mostly west. It's almost due west by the compass, because the magnetic variation is 21 degrees here. The weather is spectacular in BC and the Yukon. I follow on paper maps to identify the mountains and lakes. We're coming up on Whitehorse, but we're almost parallel to the BC-Yukon border, converging very slowly. We'll cross it just shortly before reaching Whitehorse.

I have a memory of there being something irregular about radio procedures in Whitehorse, but I search the CFS and can't find anything odd. I tune the tower a long way out to get situational awareness coming in. A pilot on frequency position reports "coming up on Lake Leberge" and I freak out. No, not because he's at our position and altitude, but because he's on the marge of Lake Lebarge. My innocent crewmate is 'treated' to a sudden Robert Service recitation.

There are strange things done in the Midnight Sun
By the men who moil for gold.
The Arctic trails have their secret tales
That would make your bllod run cold.
The Northern Lights have seen queer sights,
But the queerest they ever did see
Was that night on the marge of Lake LaBarge
I cremated Sam McGee.

I would have gone on, but mercifully I didn't know any more by heart. I resolved to rectify that at my earliest convenience, but I think that's after my other resolutions about running, simming and building a solar-powered hovercraft, so don't ask me about it soon.

Except for poetic outbursts, descent into Whitehorse is routine. The field is easy to spot and we're sequenced number four for landing, behind a Convair, then resequenced number four again after the first guy lands, because a faster aircraft turned up to fill in one of the gaps. Pretty adept work for what I believe is a non-radar tower. As we exit the runway, on a cross runway, tower asks us where we're going on the field. I say something like "Looking for avgas" or "to refuel" and we're given taxi instructions up a hill. Just when you think you're at a modern airport. At the top of the hill is a little charter operation, or maybe a repair shop, but nothing that looks like a fuel pump. We wave off the marshaller, do a very awkward one-eighty and call back ATC for clarification. They confirm that there is no fuel up here. Whatever I said coming off the runway sounded like the name of the company based up that hill. we taxi back down the hill and across the cross runway, and park where we should have gone in the first place.

We go into the FBO and ask about fuel. It will be about forty-five minutes, because the fuel truck, just went up the hill to fuel a charter fleet. We pick a safe estimated time of departure and divvy up duties: I'll take care of customs and fuel while he does weather and files a flight plan. I also get their fax number and permission to receive a fax. He calls 1-866-WX-BRIEF while I call the customs broker and fill out a fuel order form.

The fax is several pages of all the dirt US customs wants to know about us. I page through it to make sure everything has printed properly and there aren't any glaring inaccuracies. They spelled our names right, anyway. The fueller arrives ahead of schedule and I direct him which tanks to fill, then sign his paperwork.

There are a lot of other aircraft around, some military, I didn't notice whose, and a small fleet of firefighting aircraft from Saskatchewan. They've been working in Alaska, helping to fight forest fires. I didn't know we gave international aid to the Americans. I wonder if the Americans chartered the Canadian firefighting capability, or if there's simply an international agreement and we come to each other's aid in the burning forests. Probably the former. I'm such a communist to think of the latter.

The other pilot, he's the PIC on the customs paperwork, comes back with an 'everything old is new again' discovery. He says that when he called Flight Services they said, "Why don't you come on over?" and they gave him a face-to-face briefing. He's exhilarating in the experience of being right there with a briefer who could point at things on weather charts and at how much easier it was to get a complete picture of the weather. He's too young to remember that that was the way things used to be everywhere. They didn't have GFAs back then, and I don't think the satellite imagery was as good, but it is a good feeling to have an in-person weather briefing. Especially when it was that same person that you were talking to on the radio as you taxied out for departure. The weather is low on the south route, so we'll have to follow the Alaska highway and then cut south down the valley to Anchorage. That makes the trip a bit longer, but within our contingency planning. Also the Alaska-Canada border at Beaver Creek doesn't count as ADIZ, so we don't need to worry about being super accurate with the crossing time.

I call US Customs in Anchorage with our recalculated ETA, and to ensure that they received their share of the paperwork. You'd think this could all be more automated or less labour intensive, but when your dealing with international travel nothing is predicable enough not to worry about. In this case the Americans are ready for our arrival.



Also: I'm looking for someone who has easy access to CYPK who could do a fun favour for me in the next few days. Please e-mail me if you think you could.

Sunday, August 15, 2010

Visual Lookout

Depending on how closely you follow NASCAR and/or the EAA Airventure (a.k.a "Oshkosh") you may know that NASCAR owner Jack Roush crashed his Hawker-Beechcraft jet during arrival at the Oshkosh event. The above link is to news coverage after the fact. The NTSB report refers to amateur video of the crash, but I haven't found it posted.

The NTSB report says:

A review of amateur video taken at KOSH showed the accident airplane in a left base turn to final for runway 18R. The airplane appeared to overshoot the runway centerline during this turn and then level its wings momentarily before entering a slight right bank simultaneously as the nose of the airplane pitched up. The airplane then turned left toward the runway centerline and began a descent. During this descent the airplane’s pitch appeared to increase until the airplane entered a right bank and struck the grass area west of the runway in a nose down, right wing low attitude.

The above, eyewitness accounts on the news, and the following description of the situation from Mark Martin (Roush's friend, former driver for Roush's team, and a pilot) suggest that he was distracted by traffic and slowed the airplane too much while manoevering for the field.

Jack got in a situation where he thought, "How am I going to get out of this without hitting somebody?" Because of all the things that were going on, which is exactly what I thought would happen, because, you know, he's in a jet and there are some very small aircraft at different speeds and those kinds of things, and he just got in a situation where he was uncertain about how he was going to make it all work, got slow and tried to get slowed down and got a little too slow and whatever.

"Stall speed," the lowest possible flying speed for an airplane, increases with bank angle, so a wing that is flying straight and level may stall as soon as the airplane banks, without a reduction in speed.

Oshkosh is an incredibly busy piece of airspace during airshow week, and they do crazy things to accommodate the rate of landing aircraft. Oshkosh arrival procedures are set up for aircraft of different speeds. Pilots choose either the 90 knot stream or the 135 knot stream, but are encouraged to fly at 90 kts if they can. The way they are handled and the spacing they are required to maintain means that Roush shouldn't have been forced to tuck in behind someone in a Cessna on final approach at 55 knots. The NTSB video analysis and eyewitnesses don't mention conflicting traffic. The standard VFR arrival is a right base for a combined final to 18L/18R, with the air traffic controllers directing aircraft left and right. On the left base arrival he was supposed to turn left base directly towards the blue dot, partway down the runway. If he was late on that turn he could have put himself into conflict with arriving slower traffic. We do know his final turn was late so he was slightly past the final approach course where he was supposed to be, right of the centreline on runway 18R, further from traffic on 18L, and towards a shaded "do not fly" zone over airshow guests. I wonder if another aircraft was arriving on a right base for a different touchdown spot for 18R and that was an issue. My internet connection here isn't good enough to download the full NOTAM pdf, or to find some stall speed numbers on the airplane he was flying. The runway "18R" on which he was cleared to land is normally just 18, and runway "18L" is a taxiway the rest of the year. Amusingly the media are calling it "runway 1836" perhaps after NOTAMs or airport signs that would call the piece of pavement "runway 18-36" after its two ends.

Another source, which I don't recommend you click because it is making my computer screen flash--I think it's trying to load pop-ups--states that Mr. Roush was initiating a go around right before the crash. I think that may be just because he went to full power in an attempt to recover from the stall. Mr. Roush doesn't mention that in his description, "Basically a landing accident, based on a conflict in airspace with another airplane, after I'd been given clearance to land."

I assume he was flying with the 135 knot contingent, and not the 90 knot aircraft. I wouldn't try to do an arrival at 90 kts in my bird. It's theoretically possible, but not safe.

The article that caught my attention was this one, with a pull quote from Roush claiming that there is no FAA restriction on private pilots with monocular vision, "except maybe airline pilots." I believe one-eyed US pilots do have to demonstrate ability to compensate, but after that, they can become airline pilots.

ICAO medical standards require binocular vision, but "flexibility based on national experience may be applied," so Canada makes an exception for the licensing of monocular vision private pilots, and on a case-by-case basis, sometimes with restrictions for commercial pilots who lose vision in one eye.

This is Roush's second airplane crash. His first was a crash of an experimental homebuilt into a lake, an accident which the NTSB attributed to "the pilot's decision to fly at low altitude and his improper visual lookout resulting in an in-flight collision static with wires."

He had two car crashes as a racing driver, too. I could say he just lives fast and takes risks, but overshooting the runway centreline when he was already slowed to below his normal approach speed suggests that he didn't have exceptional control of the airplane. Considering the quantity of recording equipment and witnesses involved, there's lots to work with to determine what happened. I'll be interested to see the full report when the NTSB completes their investigation.

Saturday, August 14, 2010

Testing Engines and Patience

The head of maintenance drives all night then calls me midmorning. I get along with him well and we get into these silly preaching to the converted routines where we follow our shared philosophy to the extreme. Things like writing a snag like "pilot's left arm gets wet during flight in rain" instead of "cockpit left side window seal leaks," or him playing devils advocate on how he wants me to communicate "soft snags" such as fuel pressure being low but still within limits, or a door latch being slightly loose. I want to communicate any change to maintenance but I don't want to mess up the paperwork. We go out to the airplane and he peers into all the same orifices that I did and doesn't see any more than I did. I run it on the ground and there is nothing, so we taxi out for a short test flight.

I apply full power with the brakes held, and everything is perfect. There is no surging after brake release, through to rotation and then airborne--still nothing. That airplane runs beautifully. They're old engines, approaching the number of hours that requires them to be overhauled in any case, but the props sync up nicely the engines run smoothly and beautifully with every parameter snugly in the green. Nothing I do induces the surging to return. I pretty much called that. The maintenance chief knows this sort of thing happens, and in fact is beaming with pride at his well-tuned engines. At this point I'm very glad that I had someone in the back yesterday verifying my observations. And we weren't eating the same 'jelly beans' either.

We land and taxi in. The maintenance chief suspects my surging was a transient turbocharger issue, and says it will probably come back, but if it does it's okay to continue a flight, no harm will come of it and I don't need to worry about it being a precursor to a complete engine failure. In the meantime he wants to put some duct tape on something he has seen chafing (yes, the one thing about the finalé of Lost that was realistic was when they mended the airplane with duct tape).

There's now a fuel truck parked on the pumps. I walk over and ask the guys how long before avgas is available and they say half an hour. Meanwhile there is a localized duct tape shortage so we get in his truck and go to Canadian Tire for more.

When we get back to the airport, I can see the tail of the Hawkair Dash-8 parked on the ramp. I brace myself. There are also a couple of medevac pilots standing just outside the security gate, smoking, so I ask them if "the mean security lady" is there. They answer in the affirmative. I brief the maintenance chief on the implications of this, then walk through the security gate (which is wide open: the medevac pilots say the latch is broken) and wave to security lady. She gives us leave to cross the ramp to the airplane. He works on the duct tape shielding and I call the customer to let them know we'll be ready to go as soon as I refuel.

When he is done I thank him. He says he'll stay here until I land the flight in case there is any issue. He has brought a new turbocharger just in case. I sit in the airplane with the door open, while he crosses through the danger zone back to the groundside. There's an ambulance parked not far from me on the ramp, a regular ambulance with four wheels, not an air ambulance. Security lady goes over and chews out the ambulance crew for some transgression.

The Hawkair moves off and a medevac airplane lands and shuts down on the other side of the ambulance. I let them know what I was told about when fuel would be available, which is any minute now. As my customer isn't here quite yet, when the fuellers are done and drive off, I let them go first. While they are fuelling, I see my customer arrive. I go up to the cockpit and do my prestart checks. As soon as I see them shut off the pump and rewind the hose I start up, getting ready to taxi up to the pump as soon as they move off. One of the pilots looks towards me and gestures me over, so I start to taxi. Neither of the pilots is in the cockpit though, and there isn't really room for me to park at the pumps and reach the fuel while still giving them room to leave without blasting me. I stop in the middle of the apron and then the ambulance goes by me.

Ah, they weren't beckoning to me but to the ambulance. The ambulance parks there; they talk a while. I shut down. The patient transfer takes a long time. They probably think I am crazy, rude or stupid to have taxied up towards them while their ambulance was coming over. I think they're rude to do their patient transfer at the pumps. They knew I had been waiting half an hour for fuel before they even got there. It wouldn't have been a great hardship for them to taxi off the pumps before doing the transfer. Yeah, it's an extra start cycle on their engines, and I suppose their SOPs tell them to avoid extra starts at all costs, especially when they're mine. I wouldn't have hung out at the pumps doing non-fuelling stuff when someone else was waiting for fuel.

Finally I get my turn at the gas, then we take off. The flight goes well with no recurrence of the problem. Everything just purrs along, even the asymmetrical cylinder head temperature we had before doesn't materialize. We land after less than six hours, making it a "short flight" for us, and I text everyone involved with the good news.

My fellow pilot replies, "Sweet, we're going to Alaska." My boss invokes thanks to his deity that nothing else has gone wrong. The head of maintenance comes up and helps me refuel for the trip north, probably tomorrow morning, while I assure him everything ran well. The quantities the tanks take show that fuel burn was almost perfectly even. I thank him again for driving up for what seems to have been nothing. He gives me the turbocharger parts that I may need if the problem comes back to stay, and some other just-in-case parts for the northern trip. Considering where we are going we're probably bringing coals to Newcastle, but it's good to be prepared. I bid him farewell for his drive back south.

Evening is packing up, getting ready to go. I call the customs broker to verify that everything will be ready when we need it, and plug in my American cellphone to charge overnight.

Friday, August 13, 2010

Having Issues. May Be A Bit.

This is so my new motto. Maybe I'll do one of these every day until I run out of famous images of historical figures having issues.

My coworker goes straight to bed after landing, not that he's especially tired after just waiting around for a while and making a short flight, but after eight hours sleep it's a new day and anything I don't get done, he can do tonight before tomorrow's icky weather arrives. I fuel and get ready for the flight, and then we're off. On the takeoff run I bring up the throttles, leading with the right lever as I have been doing, to compensate for a MP split at high power. But as I watch the power develop I adjust and discover that I don't have to do that, the left falls behind if I do that. Looks like they fixed that. They have been tweaking one thing every time it goes into maintenance, so they must have got it this time. The airplane accelerates to rotation speed and I lift the nosewheel about eight or ten degrees nose up for my initial climb. The mains come off and then there's a change in sound in the left engine and a little bit of yaw. Could be a turbocharger issue. The manufacturer specifically instructs pilots not to reject a takeoff with a failed turbocharger, so I just keep it at blue line and fly the plane. Now the left engine is surging. It's like an unsynched propeller, except that at this altitude the props are still unsynchronized. I wonder if I'm going to lose one here. Regardless, if it's putting out power, I fly a dodgy engine to a safe altitude before trying to diagnose it. The first order of business, even in a full engine failure or a fire is Control the airplane.

It flies. I reduce to climb power. The manifold pressure gauge needle isn't flicking noticeably and the tach isn't fluctuating between lights. At this angle and lighting I can't see clearly if the digital tachometer readout is fluctuating with a particular pattern. There is no gauge indication anywhere that says there is something wrong. The airplane isn't yawing crazily, it just doesn't sound right. I look at both engines out the windows. Who is to say whether the left one is surging down or the right one is surging up. The mission specialist has noticed too, which is good, because without a clear gauge indication it's easy to think you've gone insane.

I level off at cruise power and tweak things for a bit, switching fuel tanks in case I have something blocking a line, or a fuel contamination issue. No perceptible change for that or with alternate air. There's obviously something not right, so we circle back and land.

I run it up on the ground so I can report everything, but it doesn't do it on the ground, of course. I shut down and call my PRM while walking around the airplane and looking inside the cowlings from various angles to check for loose hoses, blocked intakes or any other obvious defects. The PRM asks the basic questions and says he'll get back to me. After ten minutes or so, the head of maintenance calls me. I describe the issue again, answer some more questions, and let him know I'm willing to take it up for a trouble-shooting flight, but he doesn't want me to. I joke, knowing it's not really a joke, that it probably won't do it again. He says the airplane is grounded, and he's driving up tonight to see it. I'm not sure he realizes how far north this is. I promise to get him a hotel room and tell him to call me whenever he is ready to work.

And then I have to tell everyone else that I just broke the airplane.

Back at the hotel I look at the information I have compiled on the Alaska flight. The fact that sunrise and sunset times are given as Never/Never today means that vampires must love it in the winter. Do vampires get cold? You'd think they could do quite well with a winter home in Alaska and a summer home in southern Chile. Or do vampires these days not mind the sunlight? PANC looks like one of those stupid airports. I mean this not as a slur on the airport but as a gesture of admiration for the pigheadedness of the skill and technology and rules required to make it work as an international hub, with ridiculous weather, almost total winter darkness and crazy terrain, not to mention frequent volcanic activity in the vicinity. There are mountains everywhere and no doubt horrible icing in the spring and fall given the temperatures and water all around it. Of course we're going to Alaska in what will probably be the best month of the year, because that's the kind of lucky folks we are.

Yesterday I e-mailed Dave of FL390, but he won;t be there while I am. I know (internet "know," but for many years, since before this blog) a pilot who lives in Anchorage, but when I e-mail him it turns out he'll be in Papua New Guinea until after I leave, so I won't be able to meet up with him. Of course. It is pretty much par for the course that if I finally happen to get to the remote location where someone I know lives, they will be out of town, either somewhere even more remote, or in my own town, for the duration. And if they ever come to my town I'm away. (The one glorious exception that proved that rule was that Phil (yes, he's fine, just not blogging these days) called me up out of the blue to say he was in town on the day I was having a birthday party! Perfect timing, and then after the party I drove him back to his crew hotel and instead of him getting out we steamed up my car windows for hours until security guards banged on the outside. But that's all you need to know about that).

So in this case, early to bed and waiting to see what the verdict is on the engine in the morning.


This B767 had a hard landing that damaged the fuselage but Boeing's horses and men put it back together again. Notice that the FO of the subsequent flight found the damage on the walkaround, while boarding passengers, and the comments are worth reading, describing and praising Boeing repair savvy.

Thursday, August 12, 2010

I Thank You All

You wonderful, wonderful people! I always knew I was blessed with some of the best readers on the internet, so I shouldn't be surprised that you can put your money where your fingers are. I posted my request to fund Cambodian building materials on a Sunday night, knowing that not many people read on the weekend, but that Monday would be a big traffic day, and hoping that perhaps a few people would see fit to contribute to the cause. It looks like more people read on the weekend than I thought. Before midnight we had enough for at least half a house! It literally brings tears to my eyes that so many people are willing to share in this way.

I giggled at the rationalizations you came up with for the various eCards you chose. You're right, it's a somewhat odd selection to go with charity donations, but it was fun clicking on them. I think dandelions and kittens were the leading choices. The pictures didn't matter because your words (and numbers, as that was the point of the exercise) carried the message.

I don't even know what the current total is, because many of you let me know you donated without telling me the amount of your donation. I estimate you have given enough to build at least two houses. In a couple of days I've gone from feeling the responsibility of being the out-of-town team member who isn't there to pull her weight at the pub fundraiser nights, to the completely different responsibility of being the one whom all of you have entrusted to take the materials you have purchased and make them into a real home for someone whose own community has judged them worthy.

It really is that simple. The money has to be all collected eight weeks before the build because the administrators use it to literally purchase lumber and nails and tin and concrete. Local contractors will lay the foundation and frame the houses before we arrive, and then we complete them. I and my team will arrive and presumably see your donations laid out on a tarp. I'll photograph that and then get to work assembling them into the very best homes I can provide.

For me personally this will be a rewarding, exciting experience because I get to travel to a part of the world where I've never been; see cultural and historical sites; attempt communication in some combination of English, French, Russian and Khmer; build something with my own two hands and give people a gift that proportionately will be the biggest most important gift I've ever had the opportunity to give anyone. Giving a home to someone who really needs it is generally the province of a government, corporation, or billionaire.

I think it make a difference as a person grow up what he or she believes the world thinks or expects, and that a child who discovers that the world cares enough to build his family a house will care about the world in return. You've all won yourselves good karma, and if at any time in the future you're feeling that you're not appreciated or not doing anything worthwhile, remember that there's a family in Cambodia whose kids might have died without you.

It's possible I could raise more money with a month-long nagging blog fundraising drive, but the way this worked is the way I like it. I said please; you answered generously; and I'll be saying thank you for the rest of the year. I will drive every nail with care and gratitude. It means a lot to me that you readers see the worth in this project, and agreed to support me.

Wednesday, August 11, 2010

Does Alaska Really Exist?

I think maybe there was giant earthquake in Alaska overnight. Before I went to bed I ran my nav program to determine that in good VFR weather with calm winds Anchorage is five hours and fifty minutes away. I left the application open when I hibernated the computer, but when I turned it on today it immediately told me Alaska is 9,358.5 miles away and my time on route would be 55h 43 minutes, including a one hour stop. For lunch, I assume. I always like to have a lunch stop in the middle of a fifty-six hour trip. I restart the application and start making phone calls.

There is no point trying to buy charts from US suppliers, because they'd never make it through customs in time for the trip. I need a supplier in Western Canada in order to get them shipped here fast enough. VIP has same-day shipping and has a beautiful graphical interface for buying US charts on its website, but only the lower forty-eight. I phone them to ask about Alaska and they say they don't carry them. Aviation World in Vancouver isn't open yet, so I call Aviation World in Toronto to find out if the store carries the charts and can do rush shipping. They say that shouldn't be a problem, and to call the Vancouver store.

It looks as though there may be some weather issues en route. The mountains in Alaska are very high and the temperature and conditions at altitude suggests icing in excess of what the aircraft systems can shed. I plan a second route around further to the north, following the Alaska highway. It's longer, but much more weather-resistant. There's low weather forecast up "the trench" and around the Alaska Highway route. No airports in the trench, and most of the Alaska highway ones are 1500' dirt strips. Alaska is like northern Canada, except with more people. I wonder if the natives in Alaska will be more like Americans or more like Canadian Inuit.

I pull up the US "Aviation Digital Data Service" weather site. I use it all the time but what I've never noticed before is that it's just the lower forty-eight. Alaska isn't on the normal weather site. This invisibility of Alaska is getting annoying.

I get a text from the pilot who is with the airplane. Instead of the expected, "taking off in ten minutes" message, it reads, "Having issues. May be a bit." I'm thinking I should add that message to my cellphone quick text menu. It covers so much, so succinctly. I'm inspired to create now:

A follow up text message explains that he couldn't get into the hangar where the airplane was, then couldn't get a hold of the guy with the aircraft logbook, and finally was thwarted by bad weather. Meanwhile we have great weather here, and I have to explain before eight o' clock why we won't have an airplane at eight o' clock, while hoping that it won't be too much longer.

Back to planning my route to Alaska. We'll go via Whitehorse for sure. It's the last good place to land in Canada, to reconfirm our border crossing time and make sure all the customs paperwork has preceded us to Anchorage. Even if the weather permitted direct Anchorage from Whitehorse, the mountains east of the city are so high I'd still have to come into the area from the north or south. I plan an approach via the ominous-sounding NOEND intersection for now, just to see how the time works out. I assume that Anchorage will be very busy with FedEx and international traffic at all hours, so we'd better be ready.

Yeah about that. Aviation World in Vancouver are super friendly but don't have the Alaska charts or the A/FD for the state. They are out of the old ones, and the shipment of the new ones isn't in yet. Being in Canada, he explains, they are the last priority to get US data. They would ship the stuff to me if they had it, though. I start collecting data from the internet. I have Canadian charts as far as Whitehorse, and FAA charts and information are online available. I gather up what I hope matches my needs and put it on a USB stick for the hotel to print for me.

I also try to line up a place to park at Anchorage. I'm reading between the lines while looking online for FBOs at Anchorage and it looks as if everyone is catering to jets. I need avgas, twenty-four hour access to my aircraft, and a place to park. At an airport like Anchorage I will need that associated with a business. There won't be a piece of pavement that is just spare for transient aircraft to hang out. Someone will have to pay rent on my bit of pavement, and someone will have to take responsibility for admitting me in and out of the FAA airport facility. A pilot lounge would be nice, but we don't need passenger handling services, as everyone on board is legally crew and doesn't need to be security cleared for our aircraft or carried around in a golf cart. I call and ask an FBO that is listed as having avgas if they can accommodate us. "Yes, yes, we can do that. That will be fine," he assures me. "When are you arriving?" I can't say that for sure, because we have to wait to be released from this job, and then there are the vagaries of weather. I give an approximate date and time and warn that nothing is confirmed. He's fine with that, so I write down the name and telephone number for when we need it.

Eventually, the airplane arrives, and I go flying, but that's a story in itself.

Monday, August 09, 2010

Next Destination: Cambodia

No, I didn't get lost on the way to Alaska. This blog entry is out of sequence, for reasons that will become evident when you read it. I will return to the Alaska adventure with the next post.

I recently ate breakfast with a group of pilots, one of whom was preparing for a trip to Cambodia in order to do volunteer work. "Wow!" said I, and trained my shark-mounted laser vision on him to demand details.

Cambodia, as I knew only vaguely, is a country in Asia, between Thailand and Vietnam, which suffered a Communist takeover in the 1970s and then a Vietnamese occupation and a civil war in the 1980s. In an attempt to have only a gullible proletariat to rule, the communists set out to kill the intelligentsia, eliminating everyone with the education to mount an effective opposition. This meant statesmen, teachers, doctors, and masters of the cultural arts. The frenzy came to the point where people with glasses were subject to imprisonment or execution, because everyone knows glasses are a symbol of smartness. Many who weren't executed starved to death in the disruption. Look at the people who are leading first world countries today: the politicians, corporate leaders, senior civil servants. They were probably all educated or mentored in the 1970s and 1980s. Cambodia hasn't got those people. Cambodia also has one of the highest proportion of amputees in the world, due to the legacy of land mines from all the conflicts. This doesn't put their infrastructure or agriculture on a firm footing. There's no reason they can't be a self-sustaining nation again, but they need some help.

What is being done to help?

Canada delivers a lot of foreign aid around the world, including Cambodia. Janne Ritskes, a woman who worked with a Canadian government programme delivering aid became frustrated with the organizational inefficiency. Like so many people frustrated with the management of their organizations she said "I could do a better job." Unlike most people she quit the inefficient job and set up shop to prove it. She runs Tabitha, a non-profit organization entirely operated by Cambodians. The organization is Christian, but not evangelical. I suspect many of the staff are Buddhist. A lot of what they do is just encouraging people to save money in order to make incremental improvements to their lives. That may seem obvious to you, but you probably grew up in a society where people were doing that. There is hardly anyone alive in Cambodia who remembers the 1970s, but I can't see that people today have much in the way of role models for long range planning. It takes savings of $960 to build a house, but for some families who have absolutely nothing, Tabitha will build them a house after they have saved a token amount, just to get them into the programme. This group from Vancouver is going to build homes.

Who is going?

The core of this group are members of the Vancouver Police Department, but I don't have to be affiliated with the police in any way in order to join them.

When are we going?

The latter half of November 2010.

What skills or experience do volunteers I need to have?

None. I know how to hit a nail with a hammer, at least nine times out of ten, but apparently even that is in excess of minimum qualifications.

Is it safe?

You know the pilot is going to ask that. The guy who invited me went on a previous trip and he didn't get mugged or sold into slavery. We will need a tonne of vaccinations and precautions against tropical diseases, and not step anywhere there isn't already a path. If you're going to go to a country where conditions are unknown, going there surrounded by police officers seems like a good bet.

"You want to go, don't you?" he asked me. Well, yeah, I do. It was pretty obvious. I've never been to Asia. I've never been anywhere in the third world, unless you count Nunavut. I've never built a house. But as you probably figured from the first person pronouns above, I'm going. I signed up as soon as I checked with my doctor to make sure that all the vaccinations were okay for me.

Originally the group thought that they would get a grant from the Vancouver Police, as in previous years it had been a team-building effort for the force, but this year they didn't receive the money, so I just found out participants have to fundraise for the materials necessary to do the building. Right now the people in Vancouver are busy organizing pub nights and silent auctions and the like to bring in the cash. But I'm not in Vancouver, and I can't be a freeloader. The more we raise, the more houses we can build. The whole housebuilding project is a crafty way to spread awareness of the organization and to get North Americans with enough money to go on foreign trips to raise some money. How will I do my part?

So far this is the best idea I have:

Would you please donate some money? To make it not something for nothing, I'll send donors a postcard, from Cambodia or from somewhere on my travels for work. I can also offer you a blog entry that's not on the blog, perhaps one of the ones that was too emotional, or gave details of an emergency that could be used to pinpoint my company. If you are a new reader and weren't around in 2006, you should probably request the northern smoke saga. I also have some bloglike accounts from before I started the blog of my own initial flight lessons, and of learning to fly a Twin Otter. Maybe you have a special request for a blog topic. Let me know what you would like in appreciation of your donation. You will receive a Canadian tax receipt; sorry if that's not useful in your country. Everyone, whether you donate or not, will get an account of the trip, via this blog.

How to Donate

This is slightly trickier than one-click ordering, so please read carefully to make sure the money is credited on my behalf, to the right team. I've left out the obvious instructions like "click Donate Now" and "enter your donation amount." I'm figuring that Cockpit Conversation readers are all smart enough to be targeted in an anti-elitist purge. Or at least have your glasses on.

1. Go to the Canada Helps website.
2. Search for "tabitha" and select Tabitha Foundation from the results.
4. Opposite Fund/Designation choose 2 - Housebuilding - "Vancouver House Building Team Nov.2010". [This is a change: it was #17 before].
5. Opposite Dedications and Gift Options choose Yes, as a gift in honour/on behalf of and put "Aviatrix" there.
6. Either choose the e-card option, or just e-mail me to let me know what you've donated, so I can know I'm successfully raising funds and awareness, and figure out how many houses we can assemble. My e-mail address is still cockpitconversation@gmail.com.

Thank you very much for anything you choose to donate. Note that your donation is going directly to Tabitha and is used exclusively for building materials which I and the group will use to build homes for brutally poor Cambodians. My airfare, spending money and living expenses for the trip come out of my pocket.

Saturday, August 07, 2010

Scheduling versus Safety

The airplane is still away. The pilot who is with it tells me that they could have completed the minimum scheduled maintenance work and had it back today, but the weather here isn't appropriate for our clients' work, and is forecast to remain thus for days, so they are keeping the airplane in Edmonton, doing small fixes that will have to be done sooner or later, so might as well be done before the parts actually break and delay an important mission. It seems like a sensible thing to do, and I expect the client to be happy with it. We're being proactive. That's still a good buzzword, isn't it?

Information flows along various different routes in this operation. I'm happy that it almost always goes through the pilots, so we know what is going on, but this time somewhere between my boss, the mechanics who have the plane, the pilot who is with the plane, and the client's head office, a message has not reached the client field staff. The people in the same hotel as me. The project manager is not happy with the proposed situation, and wants to have the airplane back on site by tomorrow morning. They pay for the airplane, they get to choose these things. I make a few calls and then can go back to the project manager. "The airplane can be here by eight a.m." Now he's happy.

When it's not a safety issue, there's no harm in giving the choice to the client. The time can be now or later. There are a lot of fixes that can be done either preemptively or as after the part actually breaks. The cost of unexpected downtime usually outweighs the cost of replacing parts early, but when it's scheduling not safety we won't hold an airplane back unnecessarily. One of ours is down with a grounded engine right now, but demand hasn't been enough to spur replacing the engine.

I go out for a run. It's hillier than it looks from the air, always is. The sidewalks aren't very good, either. I'm not running consistently enough to see any improvement in my speed or fitness, but I guess as long as I'm staying fit and not getting injured it's good. I can't remember my New Year's Resolutions this year, and I'm afraid to look them up, because I know I must have blown my chances on all of them already.

When I get in, I learn two things. One is that thanks to the time difference between here and Edmonton, they're going to do some of the work and have the airplane here for eight, and the other is that we're going to Anchorage, Alaska in three days. Do we have charts? Hell no. We have three sets of Alaska charts from last year, but none in this airplane. It's too late to try and order any tonight, so I just play with routes to Anchorage in my Seattle Avionics navigation program. I add "find charts" to my to do list for tomorrow.

Friday, August 06, 2010

Local Positioning Signal

I was chatting online with some non-pilots who knew I was a pilot and one, whom I have dubbed Rhubarb, asked me, "Why doesn't each airport have a local positioning signal?" They kind of do, so I asked what he meant.

<Aviatrix>   What is a local positioning signal?
<Aviatrix>   A lot of them have a green and white flashing beacon, if that counts.
<Rhubarb>    heh
<Rhubarb>    Well, like GPS, but local.
<Rhubarb>    A collection of transmitters whose signals can be recieved and processed the same way.
<Aviatrix>   A lot of them also have an AM radio broadcast signal in morse code from quite nearby. You can't put it ON the runway because the antenna would be inconvenient.
<Rhubarb>    Sure.
<Aviatrix>   Some have a transmission in the range 108-117.9 MHz with directional information that helps you align with the runway.
<Rhubarb>    What I'm proposing would undoubtedly involve a whole 'nother receiver, and I guess adding more instruments is not an easy proposition. :-P
<Aviatrix>   And some even have information in that signal that tells you how far away the runway is, and/or your deviation from an ideal glideslope to the runway.

Rhubarb kind of answered his own question, by recognizing that every technology needs a receiver, before I got into historical techniques like A-N beacons, painting the name of the airport in big letters, or lighting bonfires leading to the airport. A local positioning signal is a very good idea, and has been implemented in many ways. Maybe when I'm in a researchy mood I'll enumerate the dates and instigators of all the various local positioning signals that have been used over the last hundred years.

If another blogger wants to steal that idea, and backlink it here for the traffic, it's yours for the taking.

Thursday, August 05, 2010

Four Million Dollar Decision

No, not my decision. Although, considering the cost of my airplane, the equipment and other airplanes around me, I technically make four million dollar decisions every time I taxi to parking. But this is about Airworthiness Directives (pronounced Eh Deez).

Anytime there is a failure of some part on a manufactured airplane and it is deemed to be a design flaw, or something that could happen anytime to another airplane, an airworthiness directive may be issued, requiring you to inspect, replace or modify something. The American FAA issues ADs, and usually Transport Canada just copies them. I think they call it promulgation. I imagine Transport Canada issues them too, if they get to the problem first, but the Americans have so much more aviation they tend to lead the way here. If there is an AD for your airplane, you are required to comply with it within the specified time, or your airplane is deemed unairworthy. The specified time may be "before you fly your airplane again," "within N days," "within M flight hours" or the like. There are one-time ADs, which are usually expensive, but you comply with them once and it's done, and there are recurring ADs which usually just require a trained individual to inspect something to see if it's broken, but are annoying because they have to be done every N hours of flight, and there is no leeway. They cannot be postponed a few hours even when other maintenance legally can be.

I think I've explained most of this before, probably many times while waiting for ADs to be completed, but I happened to run across a document today showing part of the logic process that goes into determining whether a problem with an airplane ends up as an AD or just a Service Bulletin. It shows how quickly a bureaucratic decision can multiply.

AD
Costs of Compliance


We estimate that this AD affects 8,000 airplanes in the U.S. registry.

We estimate the following costs to do the inspection and parts replacement:

Labor Cost: 4 work-hours X $80 per hour = $ 320

Parts Cost: $190

Total Cost Per Airplane: $510

Total Cost on U.S. Operators: $4,080,000

It's some inexpensive (two hundred bucks is a cheap airplane part) part buried somewhere that takes two guys most of an hour to take the airplane apart to get at it, a few minutes to replace, and then another hour to reassemble test and certify. And that's a one-time AD.

Speaking of decisions with consequences, some time ago I told my boss about my blog. I was sitting in a hangar typing on my laptop and he ambushed me with some friendly question like "what are you doing?" and, being completely untrained in the art of lying, I told him I was blogging. I figured the word "blog" makes most people think of twilight fan fiction, emo angst and accounts of shopping trips, and that he would be even less inclined to read it than he is to read my status reports. But he asked for the blog URL. He read some of it, laughed and moved on. I figured that would be the end of it. After all What business owner has time to read blogs?

Then, weeks later, I was taking video of a tractor engine that was on the verge of catching fire. A contractor was using the self-destructing tractor as a tug, and I was teasing him that using that vehicle to tow airplanes in for maintenance was like a sign painter advertising his skills with a billboard done in crayon. I mean you can't keep your own tractor in good repair, but we should trust you with an airplane? The boss saw me intently pointing the camera. "For your blog?" he asked. The look on my face was probably something like "Uhh, you remember that?" and I answered, "Yeah, if it works out." (It didn't, too dark to see what was going on). I suppose this blog is more interesting than the paperwork and terse status reports I keep sending him, but the status reports are more up-to-date.

And as I've said from the beginning, if anyone associated with the operations described in this blog wants anything removed, censored or changed, no problem. Plus I can write more verbose status reports, too. Just ask.

Wednesday, August 04, 2010

Loss of Separation

If you're me, when you see news like this Convair 580 crash in British Columbia, you are sad for the pilots and their families, and you hope that your friend wasn't on board. You don't wait for the names to be released, but talk to whom you must to find out enough about the deceased to rule out anyone you know who works for the company. And then you're glad because your friend is alive, and tell him so. And then you are sad for your friend, who has lost beloved colleagues, but still glad because he is alive and well. And then you discover that someone else you know has not been so lucky as to have her friend not be on board that airplane. You feel a little guilty for a moment, until you remind yourself that a burned out cockpit and unreleased crew names is not a Schrödinger's box, with a waveform that will collapse according to who hopes hardest. It's happened. So you are sad for the other friend, and for the pilot you did not know, who was her friend, and for the dead pilots you did not know, and for the other pilots you did know, who did not survive earlier days. And then you shed a few tears without being completely sure whom they are for. And then you check the weather and NOTAMs and go to work. And that's what you do, if you're me.

Everyone fly safe, please.

Tuesday, August 03, 2010

Pork Bellies

This posting is utterly off the regular topic of this blog. It was inspired by the fact that I had bacon from a free range pig for breakfast, and it was extremely delicious.

Pork bellies are an economic commodity traded on the stock market. People essentially gamble on the accuracy of their predictions about the future demand, supply and thus price of pork. The traders never actually take delivery of the pork, because during the time they are trading it like a hot potato, the pigs haven't been slaughtered yet, or maybe even haven't been born yet.

That made me think about enormous pig factory farms. By keeping pigs in extremely confined conditions, they're creating inhumane conditions for the pigs, the human workers, and the people who have to live near the effluent. In some places they may also be doing environmental damage to fisheries and drinking water, but are they also devaluing the currency? Would changing the laws so that "standard industry practice" like no longer provides an exemption from prosecution for animal cruelty laws merely address animal welfare issues, or would it constitute tinkering with the economic system itself? Is this the real reason why we as a society don't demand that animals that are made of delicious, delicious bacon are not treated at least as well as convicted rapists? If you treated a single dog the way factory farmed pigs are treated, the dog would be taken away and you would not be allowed to own another animal.

And then I wondered, can people who are forbidden by religion to eat pork or handle pig leather ethically make money in commodities trading if they hold pork belly futures? Is contact with the animal itself unclean, or does that extend to its effects. Pigs aren't soft and furry, and they're very robust, but they're also intelligent and sociable. If I buy factory-farmed bacon, I'm paying someone to abuse an animal for my breakfast pleasure. I don't think I'll do that anymore.

If you haven't had your daily dose of bleeding heart liberal hopelessness yet, see this blog on the myriad ways the planet is doomed.

Sunday, August 01, 2010

Resolution Update

I made some ridiculously optimistic new year's resolutions this year and with five months left in the year, not only have I neglected them, but I until I looked them up just now, I had forgotten what they were. It's time for some revisions.

The running goal proved to be counterproductive, because while I started off well with a few months of distance and a good base, I then tried to go too fast and kept injuring myself, setting myself back. I've been awesome at keeping to the 5BX programme (wow that reads like something else if you don't know it says FIVE B X, for "five basic exercises"), though, and am almost at the level recommended for a thirty-five year old male, with little doubt that I'll achieve it on schedule. (The women's program was suspiciously wimpy, so I stopped doing it when it diverged enough from the men's that I couldn't just incorporate it. Maybe I'll pick it up again later). It's much better to run healthy and uninjured than to run fast, so I'm going to scrap the speed goals and instead just count how many kilometres I run before the end of the year.

The people idea worked because it did establish a habit, so even after I forgot the goal it snapped my out of being a hermit. My list of unique contacts ends in mid-February. I did pretty well up to then, but I guess I have to cross off the names of people for whom e-mail bounced or postal mail was returned as undeliverable. That's sad. I'll try to track some of those lost people down.

Simming daily was a good idea and a habit I just didn't get established. I need to set it up so it gets done like checking my e-mail and doing my 5BX. I'll keep trying with this one.

I laugh at the home project idea. The only projects I've had at home this year have been unpacking, laundry and repacking. I think I'll revise this one to try to start each work rotation with a clean desk, and that means having actually dealt with the items piled on it, not just dumped them in a cardboard box. (Yes, I actually have a pile of increasingly ancient cardboard boxes under my desk, full of the stuff I have dumped there over the years. Some of it may be address changes of my lost friends, too).

New adventures are always great, and really it's adventures and fun with my friends that have prevented home projects, okay that and watching five seasons of Lost in one frenzied binge this winter.

Saturday, July 31, 2010

Hearing Impaired Airline Pilot

As a commercial pilot I undergo regular medical examinations to ensure that I am fit to fly. I had an audiogram (hearing test) when I was first licensed, but now I'm just tested without really noticing, as the doctor will ask me a question quietly when I'm not looking at him and when I answer normally he checks a box somewhere. I have had exams where the doctor was more obvious about it, but for the last couple I can't even remember being checked for hearing. Perhaps it was during the physical ear exam, where the poor doctor has to shine a light in my ear and put up with me asking if he's checking to make sure there's something in between my ears.

This weird medical document turned up in a Google alert. I don't know enough about the relevant audio panels to know if there has been some kind of special adaptation for the captains, or if they are just showing his volume level settings.


the hearing impaired airline pilot

Kind of freaky that the hearing aid is bolted to his skull. But then I know so many people that are cyborgs now that it's barely worth remarking on anymore.

To merge the subject of not being stopped by a disability with Caturday, we have another cat with an other-than-normal number of extremities. Avert your eyes if you don't like cute kittens.

Sorry if the videos break people's browsers. I know they do sometimes. E-mail me if it's a problem and I'll remove the videos after a couple of days.