Airport Codes: BRC

High density altitude with heavy ship.

During our ferry flight from Seattle, WA to Page, AZ, we decided to make a fuel/lunch stop at Bryce Canyon airport (BCE). Although I think we could have made it to Page with the fuel we had on board — about 1/3 tanks or 18 gallons to go 60 miles — we’d barely make our legal requirement of 20 minutes of reserve fuel for the flight. We’d also be flying direct over relatively hostile yet strikingly beautiful desert terrain. Not the kind of place you want to make an emergency landing prompted by a low-fuel light.

Bryce Canyon Airport is at 7590 feet MSL. We listened to the AWOS as we approached and learned that the temperatures were in the 80s (can’t remember exactly) and the density altitude was 9400 feet. (Whoa.) There was a 4-6 knot wind coming from the north.

Density Altitude ChartLouis, a sea-level pilot, was at the controls. I figured we weighed about 2300 lbs. I knew we could hover at 6300 feet/104°F at max gross weight. Although I could have pulled out the manual to double-check the performance charts for our exact combination of weight, altitude, and temperature, I didn’t think it was necessary. After all, the 6300 feet/104°F combination equaled almost 11,000 feet density altitude (consult the chart; you can click it to see a larger view on Wikipedia). 9400 feet was well within that.

And Louis did well on approach. Although he came in a little fast at the beginning, he had a good approach speed and angle — at least by my standards — as we flew into the wind for landing direct to the ramp. He even got it into a hover where we’d park. But then the low rotor RPM horn went off. The helicopter wasn’t generating enough power to keep the blades spinning at the required RPM.

We were about three feet off the ground when this happened, so it wasn’t a big deal. I told Louis to just put it down. He was either fixated on the RPM gauge or trying hard to put it down gently, because he didn’t set it right down. He drifted backwards a few feet as we descended with the horn blaring. Finally, he put it on the ground. The rotor RPM shot up, but didn’t overspeed into redline.

I should make a few things clear here, especially for non-pilots, non-helicopter pilots, and non-Robinson pilots.

  • Rotor RPM is life. If your rotors slow beyond what’s necessary for lift, the helicopter will indeed drop like a brick. That’s a very bad thing.
  • The emergency procedure for low rotor rpm is to lower the collective and increase the throttle. We’re trained to do this so much that it becomes automatic. But lowering the collective isn’t always practical. The pilot needs to evaluate the entire situation — primarily height from the ground or obstacles (how close are you?) and rotor RPM (how low is it?) — before taking action. You don’t, for example, want to simply lower the collective if you’re at 95% RPM 3 feet off the ground in rough terrain at 2,000 feet density altitude. (Of course, you’re not likely to get a low rotor horn in that situation anyway.)
  • Most modern helicopters have electronic governors that work with the throttle to make sure the engine delivers enough power to keep the blades spinning within an acceptable range of rotor speeds. My helicopter has such a feature. It works very well — except in high density altitude situations when the collective is raised quickly. Then it doesn’t always keep up rotor demand. In those situations, it doesn’t fail — it just doesn’t always spin the blades at the ideal 102% speed.
  • On a Robinson helicopter, the low rotor RPM warning system, which consists of a loud horn and a light, kicks in at 97% RPM. That’s really high and it gives the pilot plenty of time to fix the problem before it becomes very serious.
  • A Robinson helicopter can fly at 80% RPM + 1% per 1000 feet of density altitude. That means we could fly, in this situation, with 89.4% RPM. It isn’t recommended, but with a good pilot at the controls, it is theoretically possible.

The horn at landing had me concerned. After all, I was at the airport to have lunch and add fuel — both of which would add weight to the aircraft. (Okay, so lunch wouldn’t add that much weight.) If I couldn’t get it flying with what we had on board, adding fuel would only make matters worse. It was midday, after all, and we’d have to wait hours before the temperature started to drop. There was a chance we could get stuck there for a while. In that case, I wanted to know before I went to lunch so we could do something interesting in the park rather than sit around the airport terminal.

At BryceSo I took the controls, bought everything back up to 102% RPM, and started raising the collective. I’ve done a lot of flying in high density altitude situations, so I know from experience that it takes a certain “touch” to avoid low rotor situations. I pulled the collective up slowly, felt the helicopter get light on its skids, and kept pulling. We were off the ground at 22 inches of manifold pressure, in a nice, steady hover. The engine sounded good, the low rotor RPM horn kept quiet. Keeping in mind that it takes more power to hover than to fly, I was satisfied that I’d be able to take off at our current weight and density altitude situation. I set it back down and we shut down.

But when I placed my fuel order, I asked for only 5 gallons. That’s 30 lbs of 100LL.

The line guy at the airport told us about how he liked watching the R22s take off from the airport. He said they only come in the late fall and early spring. They almost always do running takeoffs. I kind of wondered why they’d come at all. That helicopter, with two people on board, simply does not perform well at high density altitude.

We went to Ruby’s Inn on the free shuttle they offer from the airport. Three other folks who’d come in from Scottsdale in a small plane joined us for the ride. We had lunch in the restaurant there, ordering from the menu rather than waiting on line for the buffet. I had salad. I’m trying to lose weight and this seemed like a good time to stay on my diet.

After wandering around the huge “General Store” there, we hitched a ride back to the airport on the shuttle. I paid for my fuel, stopped in the restroom, and headed outside.

I admit that I was a little nervous about our departure from Bryce. One of the reasons for this was a recent R44 accident in Washington State that involved Louis’s old flight instructor. She’d been flying a Raven I in the Snowqualmie Pass area with three passengers on board when she’d crashed on takeoff. The NTSB report is still preliminary as I write this, but most folks are pretty certain that density altitude played a part in this fatal crash.

BCE diagramI’d wanted to depart into the wind, using the 6 to 8 mph breeze to help me get through effective translational lift (ETL), which occurs around 24 knot airspeed in an R44. The trouble was, the wind was blowing across the ramp area and a small jet was parked at the edge of the ramp, making a low-level obstruction there. If I hover-taxied over to the taxiway, I could takeoff downhill, but with a quartering tailwind that would not help the situation. Of course, a running takeoff — that’s where you get the helicopter light on its skids and run on the skid shoes until you’re through ETL — would be possible on the taxiway, which was smooth. In the end, I decided to pick it up into a hover and take off with a quartering headwind toward the runway and big empty space beyond its approach end. I’d have pavement under me for at least 200 feet, so I could always slide along it or abort the takeoff with a running landing if I couldn’t get enough lift to clear the fence and the road beyond it. You can see all this in the diagram; we were the red X.

I started up and we listened to the AWOS. Density altitude was now 9900 feet. (I guess it had warmed up a bit because there hadn’t been earth-shifting earthquakes while we ate.) Mike and Louis were quiet as I pulled pitch and brought the helicopter into a hover. I’m not sure if they were as surprised as I was that we didn’t get a low rotor horn. I pointed the helicopter in the direction I wanted to go, pushed the cyclic forward gently, and started my takeoff run. We varied from 3 to 8 feet off the ground before I felt the familiar vibrations of ETL. Then we were climbing nicely, well clear of the fence and the road. No horn.

I turned to the southeast toward Page and flew for a while before handing the controls back to Louis.

Real Scud-Running

Scud-running, defined.

In a recent post titled “Almost Scud-Running,” I recounted a flight through Snowqualmie Pass in Washington with low clouds and limited visibility. I said that was “almost” scud-running. But what we did on departure from Seattle’s Boeing Field (BFI) on Saturday was definitely scud-running.

So I guess a definition is in order here. This is my definition — other pilots might define it differently.

To me, scud-running is flying in weather that is so questionable that you’re required to alter your course to get around it. I’m not talking about an alteration planned before takeoff — we did that, too. I’m talking about multiple in-flight course changes to find your way around weather you can’t fly through. And that’s what we did on Saturday morning.

The original flight plan had us going through the pass again and, from Ellensburg on the other side, to Walla Walla and down into Oregon. But there were low clouds over Seattle that morning and a check with Duats and the Seattle FSS confirmed that Stampede Pass had just 1/4 mile visibility. Stampede Pass is one pass over from Snowqualmie and roughly the same altitude, so if it were fogged in, Snowqualmie probably was, too. (Stampede has an ASOS; Snowqualmie does not.) We could wait for the weather to lift – which might not happen that day at all — or take another route. Since I was suffering from severe back pain due to a possibly herniated disk, I wasn’t interested in waiting around. I wanted the flight over with. So we planned to go due south and find a path around the west side of Mt. Rainier and Mt. St. Helens.

Louis was flying and would do 95% of the flying for the entire ferry flight from Seattle to Page, AZ (Lake Powell). He’s familiar with BFI and handled the radio communications with the tower there before guiding us through the narrow corridor between Renton and Seatle airspace. Then we were heading south with the clouds just above us. We had perfect visibility ahead of us, but the mountains were obscured to the east.

How I Run the Scud

I have a technique I use for scud-running in mountainous terrain. This is a technique that’s easy in a helicopter — which has the ability to slow down, stop, descend almost vertically, and make very tight turns. I do not recommend using this technique in an airplane. Actually, I don’t recommend doing any kind of scud-running in an airplane.

In my technique, I fly as close to the desired course as possible as long as I can see the next upcoming ridge or mountain top. When I get near that ridge, I peek over the top of it. If I can see the top of the next ridge, I cross over and continue. If I can’t see the top of the next ridge, I fly parallel to the ridge in the direction of clearer skies, which is normally opposite the direction I really want to go. As soon as I can see the next ridge, I hop over the one beside me and head to it.

Of course, if the skies aren’t clearer in any direction, I just look for a landing zone, preferably an airport where there’s a lounge, restrooms, and vending machines or a restaurant. I do not want to get boxed in by the clouds with no options except down in mountainous terrain. And I’m not stupid enough to fly my helicopter in clouds, even if I wanted to punch out through the top.

I’ve used this technique safely in an attempt to get across the pass at Tehatchapi at the southern end of California’s Central Valley. That attempt was not successful — the pass was completely fogged in — but it did allow me to get close enough to make an informed decision without putting myself in any danger. I subsequently crossed out of the valley at Grapevine after landing at an airport and talking to the local FSS.

On Saturday

That Saturday, I guided Louis on a scud run using the technique discussed above. I had a sectional chart with me and always knew exactly where we were. There were lots of valleys that looked promising, but in quite a few cases, the chart clearly showed that these valleys would simply climb up toward either Mt. Rainier or Mt. St. Helens, both of which were hidden in the clouds. Sucker valleys. It was a good thing that there were two of us up front. If I’d been alone and unable to really study the charts as I flew, I would have tried more than a few of them and wasted a lot of time.

Scud RunningMike took this photo from the back seat when we were nearly out of it. It was pretty bright at this point and easy to see that the cloud tops weren’t far above us. It was tempting to punch out through a hole to the top. But I don’t like flying when I can’t see the ground. If the engine quits I want to see my spot right after entering an autorotation — not seconds before we hit the ground.

The result of all of this was that we wound up going nearly due south to avoid the weather. Here’s the track from my SPOT Messenger; ignore the numbers and just follow the track from Seattle south and then east:

Scud Running in Washington

Bonneville DamAll this groping around added an hour to our flight for the day and shifted our flight path to the south. The weather was still iffy with low clouds in the Columbia River Gorge between the Cascade Locks and Hood River. You can get an idea of the situation in this photo of the Bonneville Dam that Mike took when we flew by.

But by the time we got to The Dalles, it was clear and sunny — another beautiful day on the east side of the Cascade Mountains. We left the Columbia River behind and headed toward our first fuel stop at Pendleton, OR.

Almost Scud-Running

Flying through a mountain pass in marginal conditions.

Louis and I flew from Wenatchee (EAT) to Seattle’s Boeing Field (BFI) yesterday afternoon. The flight required us to cross the Cascade Mountains. There are two passes to choose from: Snoqualmie, which I-90 goes through and Stevens, which State Route 2 goes through. I’d wanted to take Stevens — I’d already traveled Snoqualmie once and wanted a change — but the decision would not be mine.

It was a weather issue, of course. After weeks of picture-perfect weather here on the east side of the Cascades, a cold front had moved in. Rain clouds were coming over the Cascades. It even drizzled in Quincy.

As I flew out of Quincy Airport for the last time this season, I took a good look at the ridge between Ellensburg and the Columbia River, where all those windmills are lined up. The sky was dark out that way, with thick gray clouds. Although the windmills were clearly visible, I could also see the vertical streaks of falling rain. It looked as if a flight up I-90 was out of the question.

But the picture was worse when I reached the Wenatchee area and could see out toward Stevens pass. The sharp, rocky mountains are closer there and the clouds clung to them like cotton balls rubbed across coarse sandpaper: lots of wisps in an 8 to 10 knot breeze. The clouds were definitely lower; the pass was definitely higher.

It looked as if scud-running would be in my near future.

If you’re not a pilot, or you’re a very new pilot, you might not know the term scud-running as it pertains to aviation (or anything else, for that matter). I define scud-running as flying in variable visibility conditions, when you have steer around low clouds or fog enroute to get to your destination. Scud-running is never a good idea. In fact, it’s usually a bad idea. More than a few pilot have met their end hitting a “granite cloud” while attempting to run the scud.

Helicopters, however, are uniquely suited for scud-running. We normally fly low, so the clouds have to be really low to affect our flight. We can travel at a wide range of speeds, from 0 to (in my case) 115 knots, so we can take our time and really look at what’s around us before committing to a path. And if that path turns bad, we can make a 180° turn to get out of it in a very narrow space. Best of all, if things get really out of hand, we can always land in a field or parking lot and wait out the problem.

Don’t get me wrong: I’m not recommending scud running to any pilot. It’s dangerous. I’m just saying that if you’re flying a helicopter and the clouds start to close in, you’re more likely to live to tell about it — if you handle it right — than someone flying a plane.

In Wenatchee, I checked the weather. I used Duats to get conditions in Stampede Pass, which is just south of Snowqualmie pass, and every other place along the way on both routes. There was no information handy for Stevens Pass, but my eyes had told me enough. Stampede pass had ceilings of 6000 feet. That was more than enough for me. Then I checked the radar in motion to see which way the rain I’d spotted near the windmills was going. It was driving northeast. We were north of the rain; it would pass to the south of us if we flew direct to Ellensburg or Cle Elum. It was cloudy and raining on the other side of the cascades, with 4,000 foot ceilings. Wind was light everywhere, so turbulence wouldn’t be an issue.

I decided to take Snowqualmie Pass.

We started up and I took off on a steep, 1,000 foot per minute climb from Wenatchee Airport. We had to cross the river and then cross the high ridge on the other side. To our left, the rainclouds were moving east. To our right, the low clouds were stuck on mountain peaks. The ridge was clear; the clouds were at least 1,000 feet above it. I aimed slightly to the south of the GPS’s direct-to Ellensburg, pointing the helicopter at the friendliest piece of sky.

I gave Louis the controls when we reached the ridge. He continued the climb, but adjusted our route to intercept with Ellensburg. We climbed closer to the clouds. I thought for a while about how I use a GPS for en route navigation — as a sort of general guide. Louis was putting us on the GPS track. Whatever.

We topped the ridge and the land dropped down toward Ellensburg on the other side. We stayed pretty high. Didn’t seem any reason to descend to a 500-foot cruise altitude when we’d just have to climb again. I set Cle Elum as the next go to waypoint in the GPS. Louis adjusted course to head west.

Ahead of us, the mountains closed in. I-90 threaded its way through them in one narrow valley after another. Although we still had at least 2,000 feet of cloudless sky right above us, the clouds dropped up ahead. The entrance to the mountainous area looked shrouded in a white haze. It didn’t look good.

I dialed in the Stampede Pass ASOS. It assured us that the ceilings were 1700 feet. Plenty of space for us. But we weren’t going through Stampede Pass. We were going through Snowqualmie Pass. They were very close, but would they have the same conditions?

We continued on. I paid close attention to the high-tension power lines that ran along the side of the road. If we had to descend and turn, I wanted to make sure I knew exactly where those wires were.

The road climbed into the mountains. We stayed at pretty much the same altitude until we were about 500 feet above the road. Then we climbed with it. We slipped into the white haze, which turned out to be a light mist. Tiny raindrops covered the helicopter’s cockpit bubble. Visibility was still okay, but there wasn’t enough moisture to bead up and run off the window, so we had to look through all those little droplets. Still, so far, so good.

We passed the two little airports at Cle Elum and I punched the next airport into the GPS: Easton State. If I have to make a precautionary landing, I like to do it at an airport, so I like to keep an airport dialed into the GPS. Sure, we could land in a big parking lot or field, but that’s a good way to get unwanted attention in these little towns.

Meanwhile, the clouds continued to come down. My internal alarm systems came to life when we started flying between low-hanging wisps of clouds. The last time I’d done that, I’d flown into one I hadn’t seen. That produced about 2 seconds of terror before I made a descending 180° turn to get out. I didn’t want to be there again. I told Louis, who was still flying, about my experience.

We passed Easton State. The next airport was Bandera, on the other side of the pass. I punched it in. We were now flying in a deep canyon, about 400 feet over a lake and I-90. The wires were not an issue anymore. At the west end of the lake, the highway made a sharp turn to the left into what looked like a cloud bank.

Crossing the Mountains

I listened to the Stampede Pass ASOS again. Now the ceilings were 1400 feet — still not bad. We weren’t far from there. We continued to the end of the lake, where we could see into the next canyon. Visibility was still okay, so we went in. This was the narrowest part of the canyon with very little room to maneuver. The clouds stayed high enough. The misty rainfall continued. We were okay, but I knew it could turn bad at any time.

Then we were through the pass and the road started to descend. The clouds went down with it. So did we. We’d made it through the pass but I still wasn’t sure whether we’d have a clear enough shot out of the mountains. We could never see more than a few miles ahead of us because of the mist and the twisty turns of the canyon.

But by the time we passed Bandera, it was obvious that we wouldn’t have to turn back or land. As the road continued to descend, the clouds stayed put. I tuned in the ATIS for Boeing Field and heard 10 miles visibility with 4000 foot ceilings. We landed there about 20 minutes later.

Here’s our entire route, laid out on a sectional chart;

EAT to BFI via Snowqualmie Pass

I wouldn’t call this experience scud running, but it was about as close as you could get. I don’t think too many airplanes would have made this flight successfully without getting into the clouds — granite or otherwise. Although something small and slow like a Piper Cub could have handled the altitude and airspeed, the uncertainty of what lay ahead, coupled with the extremely narrow spaces that would make it impossible for an airplane to turn around, would make this a very dangerous flight for any plane.

I’ve been in worse weather situations than this one, but I don’t think I entered into this one lightly. The entire time we were in the mountains with low clouds, I kept thinking about escape routes, landing zones, obstacles to turning, and what could happen if we let it. In Arizona, I don’t get much practice flying weather. While I think that what we experienced yesterday was marginal VFR at best, other pilots more accustomed to weather flying might think I was taking the whole thing too seriously.

But it’s when you let your guard down that Mother Nature sometimes steps forward to slap you in the face.

Airport Codes: SBP

Landing at San Luis Obispo.

For my first Airport Codes meme entry, I thought I’d cover one that’s relatively fresh in my mind: San Luis Obispo (SBP).

SBP was a fuel and lunch stop on a flight from Wickenburg, AZ (E25) to Boeing Field (BFI) in Seattle, WA in May 2008. I was flying with Louis, a CFI who wanted to build time in an R44. Or maybe I should say Louis was flying with me, since he was acting as PIC.

Our arrangement was for Louis to fly and me to handle radio communications. We’d come in from the east, passing over Grapevine and climbing up trough the wide valley west of there. About 30 miles out, we broke away from the road and made a beeline to the airport.

Chart to SBP

I tuned in the radio, listened to the ATIS recording, and waited until we were closer to make my call. The female controller was issuing instructions to other aircraft. The airport wasn’t very busy for a late Saturday morning, but the radio was full of sound. The controller was chatty, which is extremely unusual for a controller of either gender. Either she liked to give instructions or she assumed the pilots were dumb enough to need as much information as she could provide. When I made the call about seven miles out, I made myself a target for her communications.

Oddly enough, I happen to have video for this flight. I had the POV.1 camera on the nose of the helicopter and although I didn’t realize it, it had been turned on since just past Grapevine. So you can see and hear the landing — including the chatty controller — for yourself.

In reviewing this video, I really think the controller had a bit too much to say. When a controller talks too much, he or she makes it difficult for pilots to make contact with the tower. Imagine, for a moment, that you were inbound to SBP and needed to establish communication with this Class Delta tower. There aren’t too many opportunities to talk during the 6 or so minutes from the time I first called in to the time we landed. This makes it tough, especially for new pilots who may already struggle with communications.

Anyway, we landed in the No Parking zone as instructed, cooled down, and shut down. Then we went up to the terminal area where there was a restaurant. After being completely ignored for about 10 minutes, we finally got an apologetic waiter. Lunch was good.

While we sat there, four airliners came or went. Let’s see if I can remember…American, US Air, United, and Delta? All of them were turboprops except United, which came in with a small jet.

After lunch, we went down to the ramp. Our choices for fuel were full serve, right where we were parked (A on the diagram below), or self-serve, on the other side of the airport (B on the diagram below). Self serve was 50¢/gallon cheaper. I made the wrong decision: I decided to air taxi to the other side of the airport and fill up at self serve.

Taxi Diagram for SBP

In a perfect world, this would not have been a bad decision. In a perfect world, we would have started up, got immediate clearance to cross the runway, landed in front of the pump, shut down, fueled, started back up, and got immediate clearance to depart to the northwest.

But there was no perfect world at SBP that day. As we prepared to reposition, a flight of three or four Howards called in on approach. The controller, now a man, was having trouble keeping track of them, probably because they called in individually and they were all Howards. (Eventually, he just told half of them to stay clear of Class Delta.) With the other traffic part of the equation, the controller was overwhelmed. He wouldn’t clear us to cross the runway. So we sat there, spinning and sweating, waiting for the clearance. When we finally got it, I scooted us across. I was hot and cranky. I fueled up quickly and we climbed back aboard. I started up and we waited again. I called the tower three times and was ignored on the first two. On the third, the controller said, “Helicopter Zero-Mike-Lima, I hear you. Stand by.” Nasty.

By the time we left, I’d burned enough fuel to eat up any savings in fuel price. Lesson learned at SBP.

Read other posts in this series:

The End is Near

The end of my cherry drying contracts, that is.

I came to Washington State in the beginning of June to start a pair of cherry drying contracts. I was fortunate enough to get a third contract wedged in between the first two, giving me almost seven solid weeks of work.

Well, “work” is not quite an accurate term. I was on standby for all three contracts, but only flew 5.2 hours on two days during one contract.

Thank heaven I was getting standby pay. Without it, I would have taken a heavy loss this summer. But with it, and thanks to the availability of a pilot willing to share ferry costs on both 10+ hour flights between Washington and Arizona, I’ll stay in the black.

My third contract officially ends on Monday, July 28 at nightfall. Unless the weather looks threatening, they’ll likely cut me loose a few hours earlier. It doesn’t matter. I’m not leaving until Tuesday.

But in the meantime, I figured it might be a good idea to drive my orchards, just to see if there was still fruit on the trees. I was in Wenatchee today, so I drove past the one near Wenatchee Airport. There are two cherry orchards across the street from each other. I’m not sure which one is mine. (Heck, it’s hard to tell from the ground when all the photos I have are from the air!) One of them still had plenty of cherries, the other had none. I continued on to Quincy and visited two of my three orchards there. Both were heavy with cherries. One of them is likely to be picked soon — fruit boxes had been laid out neatly in the rows between the trees.

As long as there’s fruit on the trees, there’s a slight chance they’ll ask me to stay on. Although I don’t mind staying an extra day or two, I really don’t want to stay longer than that. I feel done with this place, if you know what I mean.

My trip home will be completed in multiple steps:

  • Tuesday: Fly the helicopter from Quincy to Seattle. Then take Horizon back to Wenatchee and drive back to Quincy. I hope to get all that done on Tuesday, but might have to take an early morning flight on Wednesday to get back to Quincy.
  • Wednesday: Drive the trailer to Walla Walla. That Washington town consistently comes up as a top choice when I go through the quiz on the Find Your Spot Web site. I was there in 2006 during my Midlife Crisis Road Trip and I liked what I saw. But I was only there long enough to do my laundry and visit a downtown independent bookstore. This time, I’ll stay two nights and check it out.
  • Friday: Drive the trailer from Walla Walla to Salt Lake City. I’ll be staying with the family of one of my editors, Megg. She’s going to take me hiking on Saturday.
  • Saturday: Drive the trailer from Salt Lake City to Page, AZ. If I get a late start from SLC, I’ll spend the night on the road and get in sometime on Sunday.
  • Monday: Fly in Mike’s plane from Page, AZ to Wickenburg. I need to get Alex the Bird home.
  • Friday: Fly with Mike on US Air from Phoenix to Seattle.
  • Saturday-Sunday: Fly with Mike and another pilot from Seattle to Page, AZ. I’m hoping to spend the night in the Reading area, where a buddy of mine is on a fire contract. I think we’d all get a lot out of seeing how a fire operation works.

I still have four chapters of a book revision to finish. I goofed off in Wenatchee most of today, but I expect to finish up over the weekend. There’s another book right after it, but I’ll get that started when I get back to Wickenburg and finish it when I settle down in Page.