[December 2021]
Route: KCCR - KBIH - KFLG - L41 - KFLG - KSEZ - L71 - KCCR
[December 2021]
Route: KCCR - KBIH - KFLG - L41 - KFLG - KSEZ - L71 - KCCR
Full route itinerary: KCCR - KLMT - 0S9 - KORS - 0S9 - KOLM - KRBG - KCCR. 13+ hrs on the Hobbs.
With Catherine back East for a week, I decided to embark on a longish trip to the Northwest corner of the lower 48 – an area I’ve long wanted to visit, but with weather that I wouldn’t have ventured before getting my instrument rating last fall. Joined by poker pal JT, I set off for Port Townsend and Olympia, Washington, to visit mutual friends, Bay Area transplants we’ve kept up with over the years. The full track over the 3 days is to the left, over a VFR sectional.
We left around 9:30 on Friday morning in N21348, a C182, enjoying the recently installed G5 and the luxury of not having to reset the DG every 15 minutes. We headed slightly NW from CCR on a route taking us past Mt Shasta, and on to Klamath Falls/Crater Lake for refueling, bathroom break and lunch. If you look closely, you can see some wiggles in the flight track around Redding, where I was giving JT slow flight and stall lessons.
Klamath is a class D with a lot of military training, though none was happening while we were there.
Leaving KLMT we turned back to the NW, passing Crater Lake and skirting the edge of a fire-fighting TFR. We were initially at 10.5K, but popped up to just under 12.5 for a little while to get above a layer of cumulus and mountain turbulence. I had my pulse oximeter going & could see quite a drop going from 10.5 to 12.5, so we didn’t stay there very long. After passing south of the TFR, we turned more northerly, passing Eugene, Corvallis and Portland on the left and getting great views of the Cascade volcanoes to the right.
I had been watching the weather intently during the previous week, hoping to get a clear day for a low altitude flyby over Seattle on the way north to Port Townsend. Trying to figure out how to make sightseeing around the SEA class B work, I benefitted from Cunningham’s law: “the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer”. I posted a proposed route on reddit and asked for feedback, which came quickly: my idea was stupid, it would never work, and here’s what I should do instead. I also discovered that the Boeing Field controllers have a “contact a controller” link on their facebook page & asked for & quickly got details about transitioning through the BFI airspace.
Mt St Helens, I think (might be Mt Adams) |
In the event, on Friday morning the weather in the Seattle area was forecast to be not great, with several cloud layers and low stratus starting around Portland. I filed an IFR plan before we left, starting from a waypoint abeam Mt. St. Helens up to 0S9 (Jefferson County International), planning to activate it only if we had to. When we got close to Portland it was evident that it would be necessary – the area had solid undercast and we could see lots of puffy clouds ahead, so I picked up the clearance from Seattle Center. They routed us up the west side of Puget Sound where I got some rare time in actual IMC. It was mostly quick hits, in & out of cumulus and only a little bumpy. Not too many sights to see on the last leg, at least for me, though JT was enjoying looking at the islands passing down below when we could see them.
Seattle kept us at 8K before handing us off to Whidbey Approach just a few miles short of the field, denying my request for lower. JeffCo has only one approach, the RNAV-A, which is aligned with runway 9 and has a normal descent angle (though it’s labeled “N/A” for some reason), so I assume it’s circling-only because it doesn’t have the right runway markings. (I’m asking for another round of Cunningham’s law here I think.) The controller gave me “direct JAWBN, direct YAYUB, cross JAWBN yadda yadda cleared approach” when we were just a few miles out, leaving me scrambling because JAWBN is not a waypoint on the procedure, though it is shown on the approach plate as a feeder fix off an airway, which we were not on. With some minor missteps, we got aligned with the transition & headed down to the procedure turn at the IAF in plenty of time. (Our friend CK, out at the airport to meet us & watching our flight path on flightradar24 was a bit mystified and thought we were mistakenly heading for Port Angeles, an hour’s drive down the road.) We broke out around 2000 feet, well above the FAF, so despite all the IMC I don’t get to log the approach for currency.
After our Port Townsend friend CK was finished critiquing my landing (“If you’d landed in the touchdown zone you could have made the first taxiway!”) he took us to a very pleasant pub in the old “lower” town by the harbor, where I made quick work of the pint I felt I’d earned. According to CK, the town was the original harbor for the Seattle area but quickly lost out to Seattle/Tacoma when the railway ended there instead of coming all the way out the Olympic peninsula. It has a waterfront area about which you read the same kinds of stories as from SF’s Barbary Coast days (e.g., drunks waking up on a boat to Shanghai) and a “respectable” churchy uptown on the bluffs with some nice old mansions of the local gentry, which now include CK and his wife KK.
The Salish Sea (the name of the whole watery region) has maybe more microclimates than the Bay Area. Saturday dawned with low overcast in Port Townsend, and a very variable forecast for the rest of the day, but mostly clear up towards the San Juan Islands. The three of us (me, JT, CK) decided to try our luck flying up to Orcas Island for lunch. We found the airport lot nearly full – there’s a little restaurant on the field (the Spruce Goose) that’s supposed to have the best pie in the area.
Somewhere in the San Juans |
Mostly a place to keep a record of interesting places to go, good routes and Stuff that Happened.
First post - my new favorite route from Concord to Half Moon Bay. I found this via a youtube video but haven't seen it described anywhere in detail. Yet based on controller familiarity it seems to be well known. [Correction: this is the SW Bay Flyway shown on the SF FLY chart.] From Concord, the route goes through the Oakland Charlie directly over the field, then the San Mateo bridge midspan, through the SQL Delta and then a climb over the peninsula ridge before descending to HAF. It's pretty much the shortest route outside the SFO Bravo. If you're programming it into your navigator, it's KCCR - OAK - VPMID - KSQL - KHAF. The OAK waypoint is not exactly right - the instruction will be to cross the Coliseum then head for the 30 numbers (assuming, as is essentially always the case in nice weather, that OAK is landing to the northwest). I now have those spots set up as VOR/radial/distance waypoints in Foreflight. But you're navigating VFR, so you can adjust as needed without the programming.
Unusually, the first call leaving CCR is to OAK tower (north, the GA one), not NorCal. My habit is to climb to 3K out of CCR [update: 2.5K is sufficient] and listen on the OAK tower frequency as soon as I'm clear of the CCR Delta. You can only hear the pilot side until getting above 2K and within about 15 miles. Once you hear the tower, call them up. They'll descend you to 2K approaching the field. Nearing the coliseum they'll switch you to the south tower which will send you over the 30 #'s, descend you to 1.4K & send you to the midspan. Before reaching the bridge, they'll ship you to SQL for that transition. SQL's D goes right up to the B shelf. My personal custom is to ask for the transition. It's never been denied. I suppose worst case if they refuse entry you could turn south and go through the gap between SQL and PAO airspace.
The B shelf is at 1.5K along that stretch. Very likely you'll cross under SFO arrivals, often two landing in parallel on 28L & R. If they're not too busy, SQL may offer to switch you to NorCal, but by the time you cross over there you're nearly at HAF so I no longer bother. Leaving that B shelf, you can now climb to 2.5 or 3K to cross the ridgeline.
Lots of altitude changes but very scenic. Here is a recent track log.