diamondaviators.net

Russ, thanks for looking into this. My major takeaway is:
"But as a practical matter, most SQL-based pilots have full familiarity with the clearance and the additional read backs clog the frequency and thus do not help overall safety."

Next time I depart KSQL runway 30, I'm going to abbreviate as Mark suggests, e.g.
"Cleared to Santa Barbara, Woodside VFR/IFR departure, vectors Woodside..." Climb via the procedure (pretend it's a SID), then maintain 2100, expect..."

Learn something every day (and re-learn something even more frequently).
Thanks all,
Wayne

I've done it enough times that in the end it is simply a right downwind departure with a few restrictions on altitude and how close in to keep it. Crossing the radial to get the higher altitude is basically once at midfield downwind.

I now generally leave there IFR to go back home to KCCR even when VFR conditions because it saves me from worrying about the airspace and I get higher sooner and a nice direct route almost always.

Charles K wrote: ↑Wed Apr 14, 2021 5:16 pm I've done it enough times that in the end it is simply a right downwind departure with a few restrictions on altitude and how close in to keep it. Crossing the radial to get the higher altitude is basically once at midfield downwind.

I now generally leave there IFR to go back home to KCCR even when VFR conditions because it saves me from worrying about the airspace and I get higher sooner and a nice direct route almost always.

Charles, I'm totally with you... I also pretty much always fly IFR into and out of KSQL... better to have ATC to worry about all that airspace.
Thanks for checking in!
Wayne

I had just flown into KSQL VFR, and didn't find it that hard. If you track the RNAV while VFR, it keeps you below the Bravo shelves. On departure, I thought about leaving IFR but your video made me think twice — it seems much easier to depart VFR, fly the Woodside departure (for example), and then pick up in the air if needed.