A Lesson in Communication. Flying San Carlos (SQL) - Auburn (AUN) in a Bonanza

My flight on October 9th, 2024 was a great reminder of the importance of communication between the cockpit and the air traffic controllers!
While flying from San Carlos, California (SQL) just south of San Francisco, to Auburn, California (AUN), I was climbing underneath the San Francisco Class Bravo airspace. During the climb, we were issued restrictive clearances (maintain at or below), to which I complied. Each of these clearances coincided with the bottom altitude of the Class Bravo airspace I was flying under. As we cleared the arrival corridor to the east, we were issued a restrictive clearance to an altitude above the shelf we were flying under, importantly, we were NOT issued a clearance to climb through the Bravo. I began to climb, but recognized we were not cleared into the airspace (we were still well below it). This prompted me to ask a clarifying statement, to which the controller replied in the negative. Had we continued climbing, it would have resulted in entering the airspace without a clearance.
In aviation, we are continually reminded of the importance of situational awareness, communication, workload management, etc.
In the future, I would have phrased my question to the controller in another way. I would instead request a clearance to fly through the Bravo, not request to confirm that his intentions were to clear us into the Bravo. Great lesson learned.

[@mr__nobody]

Great review of the clearance expectations misunderstanding. would it be prudent it get it the habit of flying through SUDGE to avoid this in the future? or is that a waste of time and fuel?

[@sailingfromswitzerland]

It's strange to have been given a clearance up to an altitude that would cause you to violate airspace you weren't cleared to enter (i.e., "at or below 3,000, at or below 4,000, etc.). Why not say "below 3,000" and "below 4,000" and perhaps include "remain clear of Bravo" for extra measure? Kudos for getting confirmation.

[@davidsine4390]

When operating VFR, you must hear the words...You are cleared to enter the Cass B Airspace... This is completely different than the requirement to establish 2 two way communication in other types of airspace like class C and D. Since, in this case the controller did not say those words, I knew what the controller was going to say before he said it as to whether clearance to enter was issued. In this case I would have requested a clearance to enter the class.B airspace on your present heading when the controller issued the 7,500 VFR climb clearance. Reguardless, it was excellent that you asked for clarification before proceeding. Great job.

[@DialAPilot]

Couldn’t agree with you more, David! Thanks for the insightful comment. Agree the right way to handle that would have been to request the clearance, instead of requesting to clarify that one was given when both of us knew that it had not been.

[@davidsine4390]

@@DialAPilot The only thing I was wondering, and too lazy to research, is what about when you are operating VFR into and out of the primary airport within Class B airspace. I know when departing VFR, in this case SFO, the local controller doesn't specifically say, "cleared to enter Class B Airspace" on takeoff, although technically you're already in Class B Airspace while taxiing, although you do have to have a class B clearance prior to departure of course. I could be wrong, but when landing at SFO VFR, I don't beleive the controllers specifically say, " Cleared to enter" either. 99.9% of the time I operated IFR into and out of SFO, so in that case I'm covered obviously. So the question of whether they say say cleared to enter, reguarding arrivals rarely came up so I don'tremember. Operating VFR in Class B Airspace is kind of a mix mash of regulations because you're operating VFR, but ATC treats you almost as if you're IFR as far as positive control. Normally mandatory heading and altitude assignments. They were even doing it to you somewhat operating VFR below Class B Airspace.

[@onetime5640]

Great video, thank you !

[@DialAPilot]

Thank you!

[@curtc4918]

That controller is a tool.

[@slates010]

Anything for content 😅