Alphabet Challenge Leg 22 KVNY - KWJF
Posted: Thu Feb 05, 2015 7:26 pm
Pilots,
Another uneventful and enjoyable hop over the mountains. Not so much. I so so wanted to label this Alphabet Challenge Leg 22 KVNY-KWTF, but I am bigger than that. Really, I am...
Context: Lookout! There are mountains up north. Really really close mountains. KVNY is about 800MSL. KWJF is behind some 5-6000 footers. KVNY has a ODP that the IFR rated pilots in the pilots lounge were talking about and that I may have looked at even though, I'm not rated and this was a VFR/VMC flight. It says you better get high quick. So I planned on getting high quick. Heading NW to TWINS intersection with a cruising altitude of 7500 (NE cruise direction). Before heading direct to KWJF using its retro cool ADF beacon. All of which I did in fact do.
http://peaware.pilotedge.net/flight.cfm?id=87437
Ok, so where to start? In short, there is a regulatory dispute/disagreement between PE ATC and me. Sounds pretty ominous, and we know what happens when you fight city hall. Let me preface this by saying I make tons and tons of mistakes on PE. But I am adamant that this isn't one of them...I don't even think it's a Grey area, but it is of course a Peter Grey area.
So what the heck am I talking about?
Situation:
Shortly after departing VFR from KVNY I was told to by KVNY tower to "have a safe flight" and contact SOCAL.
At this moment, the replay shows I was at 4800MSL/130KIAS climbing ~1800 FPM and abeam the numbers of 16R 1.5 miles west
I contacted SOCAL reporting "5500 for 7500."
I was informed, "It is important that I inform you that you have violated the ENTIRETY of the Class C airspace....you did not establish two way communications with the controlling authority flight following does not constitute two way communications..."
After a bit of back and forth which you can listen to if so inclined, I issued a "Roger, we'll talk about this on the ground. Cancel flight following" and motored on to an uneventful landing at KWJF.
Let's Review:
- AGREED: Class Charlie requires two way communication be established with the controlling authority prior to entry.
SOCAL's Point of View:
- SOCAL Asserts that my Assigned Squawk Code and concomitant Flight Following approval do NOT constitute "two way communications with the controlling authority"
- SOCAL maintains there is a difference between a flight following squawk code assigned to you from the principal airport inside a a Class C and a satellite airport under the shelf of the Charlie.
- SOCAL maintains that flight following squawk and uninterrupted comms with Tower through handoff to SOCAL does not constitute "permission" to enter the C.
N3298S Point of View:
No violation occurred. Two way comms were established and maintained. KVNY tower and SOCAL failed to coordinate flight following.
I maintain that, certainly on the ground, ATC is ATC:
If ATC assigns me flight following and a squawk that constitutes 2 way comms for the purposes of entering the C upon departure. I don't differentiate the flight following I get assigned prior to departure at KBUR vs KVNY. That squawk and FF are KEY here.
IF I didn't have flight following (and tower handoff to boot), then I wouldn't have had prior two way comms for the Charlie. I get that Tower only owns the D up to 2999.9999.
But TOWER Gave me a squawk ACTING as SOCAL's agent on the ground. Otherwise, every pilot departing KVNY better call up SOCAL on the ground to request Flight Following DIRECTLY. (Insane)
I had (1) ATC Assigned Squawk Code given to me on the ground by ATC, (2) ATC Assigned Flight Following and an (3) ATC approved(acknowledged/coordinated?) Departure Altitude (7500) provided me by CLEARANCE DELIVERY and (4) ATC Assigned Departure Procedure assigned by Tower -- Left Downwind Departure to the NW (5) Tower kept me on Frequency from 0AGL to 4800MSL abeam the numbers on 16R. Only abeam the numbers to 16R at 4800MSL was I told to contact SOCAL.
If you assert that an ATC Squawk/Flight Following assignment + seamless comms with TOWER is NOT two way communication with ATC then you have to simultaneously assert that that the flight following I was assigned is valid for the "Entirety of the Class D" airspace only. Not particularly valuable no? And, to be consistent, that I would have to request ANOTHER squawk before entering the Charlie above it, no?
AND
You have to assert that Tower handing me off directly to SOCAL somehow constitutes a loss of two way communication - already established. It's a seamless handoff.
FURTHER
Lets take another example to illustrate the point: Let's say I had wanted to go to DARTS, informed Clr Delivery, gotten assigned a squawk, and cleared for a Left Turnout approved.By SOCALs logic my Squawk code doesn't constitute two ways comms "with the controlling agency." So what exactly am I supposed to do as I climb out above the sepulveda flood control basin 1 NM west of the SFC/4800 shell of the C? Tell tower I'm going to orbit the field below 3000 for a bit so I can call SOCAL? Insanity.
In SUM:
ATC Failed to Coordinate between tower and SOCAL. A pilot in my circumstances has EVERY reasonable expectation that ATC will coordinate when they give you a squawk and tell you to switch to SOCAL.
- Even failing this coordination, Tower could have done other things on the departure they assigned me -- restricted my altitude below 300 - remain clear of the Charlie, Contact SOCAL prior to the Charlie, if I wasn't "in 2 way communication". I had zero expectation that anything was amiss but it would have been easy to stay below 3000. Point is I should not have had to.
Finally to get some perspective - Let's look at the timeline. I hit 3000 MSL within 90 seconds minute of liftoff. I was turning upwind at 3000. I was at 4800 abeam the numbers 60 seconds later. The "entirety of my alleged Class Charlie violation" lasted 60 seconds and 1NM.
Lessons Learned:
To be determined.
Another uneventful and enjoyable hop over the mountains. Not so much. I so so wanted to label this Alphabet Challenge Leg 22 KVNY-KWTF, but I am bigger than that. Really, I am...
Context: Lookout! There are mountains up north. Really really close mountains. KVNY is about 800MSL. KWJF is behind some 5-6000 footers. KVNY has a ODP that the IFR rated pilots in the pilots lounge were talking about and that I may have looked at even though, I'm not rated and this was a VFR/VMC flight. It says you better get high quick. So I planned on getting high quick. Heading NW to TWINS intersection with a cruising altitude of 7500 (NE cruise direction). Before heading direct to KWJF using its retro cool ADF beacon. All of which I did in fact do.
http://peaware.pilotedge.net/flight.cfm?id=87437
Ok, so where to start? In short, there is a regulatory dispute/disagreement between PE ATC and me. Sounds pretty ominous, and we know what happens when you fight city hall. Let me preface this by saying I make tons and tons of mistakes on PE. But I am adamant that this isn't one of them...I don't even think it's a Grey area, but it is of course a Peter Grey area.
So what the heck am I talking about?
Situation:
Shortly after departing VFR from KVNY I was told to by KVNY tower to "have a safe flight" and contact SOCAL.
At this moment, the replay shows I was at 4800MSL/130KIAS climbing ~1800 FPM and abeam the numbers of 16R 1.5 miles west
I contacted SOCAL reporting "5500 for 7500."
I was informed, "It is important that I inform you that you have violated the ENTIRETY of the Class C airspace....you did not establish two way communications with the controlling authority flight following does not constitute two way communications..."
After a bit of back and forth which you can listen to if so inclined, I issued a "Roger, we'll talk about this on the ground. Cancel flight following" and motored on to an uneventful landing at KWJF.
Let's Review:
- AGREED: Class Charlie requires two way communication be established with the controlling authority prior to entry.
SOCAL's Point of View:
- SOCAL Asserts that my Assigned Squawk Code and concomitant Flight Following approval do NOT constitute "two way communications with the controlling authority"
- SOCAL maintains there is a difference between a flight following squawk code assigned to you from the principal airport inside a a Class C and a satellite airport under the shelf of the Charlie.
- SOCAL maintains that flight following squawk and uninterrupted comms with Tower through handoff to SOCAL does not constitute "permission" to enter the C.
N3298S Point of View:
No violation occurred. Two way comms were established and maintained. KVNY tower and SOCAL failed to coordinate flight following.
I maintain that, certainly on the ground, ATC is ATC:
If ATC assigns me flight following and a squawk that constitutes 2 way comms for the purposes of entering the C upon departure. I don't differentiate the flight following I get assigned prior to departure at KBUR vs KVNY. That squawk and FF are KEY here.
IF I didn't have flight following (and tower handoff to boot), then I wouldn't have had prior two way comms for the Charlie. I get that Tower only owns the D up to 2999.9999.
But TOWER Gave me a squawk ACTING as SOCAL's agent on the ground. Otherwise, every pilot departing KVNY better call up SOCAL on the ground to request Flight Following DIRECTLY. (Insane)
I had (1) ATC Assigned Squawk Code given to me on the ground by ATC, (2) ATC Assigned Flight Following and an (3) ATC approved(acknowledged/coordinated?) Departure Altitude (7500) provided me by CLEARANCE DELIVERY and (4) ATC Assigned Departure Procedure assigned by Tower -- Left Downwind Departure to the NW (5) Tower kept me on Frequency from 0AGL to 4800MSL abeam the numbers on 16R. Only abeam the numbers to 16R at 4800MSL was I told to contact SOCAL.
If you assert that an ATC Squawk/Flight Following assignment + seamless comms with TOWER is NOT two way communication with ATC then you have to simultaneously assert that that the flight following I was assigned is valid for the "Entirety of the Class D" airspace only. Not particularly valuable no? And, to be consistent, that I would have to request ANOTHER squawk before entering the Charlie above it, no?
AND
You have to assert that Tower handing me off directly to SOCAL somehow constitutes a loss of two way communication - already established. It's a seamless handoff.
FURTHER
Lets take another example to illustrate the point: Let's say I had wanted to go to DARTS, informed Clr Delivery, gotten assigned a squawk, and cleared for a Left Turnout approved.By SOCALs logic my Squawk code doesn't constitute two ways comms "with the controlling agency." So what exactly am I supposed to do as I climb out above the sepulveda flood control basin 1 NM west of the SFC/4800 shell of the C? Tell tower I'm going to orbit the field below 3000 for a bit so I can call SOCAL? Insanity.
In SUM:
ATC Failed to Coordinate between tower and SOCAL. A pilot in my circumstances has EVERY reasonable expectation that ATC will coordinate when they give you a squawk and tell you to switch to SOCAL.
- Even failing this coordination, Tower could have done other things on the departure they assigned me -- restricted my altitude below 300 - remain clear of the Charlie, Contact SOCAL prior to the Charlie, if I wasn't "in 2 way communication". I had zero expectation that anything was amiss but it would have been easy to stay below 3000. Point is I should not have had to.
Finally to get some perspective - Let's look at the timeline. I hit 3000 MSL within 90 seconds minute of liftoff. I was turning upwind at 3000. I was at 4800 abeam the numbers 60 seconds later. The "entirety of my alleged Class Charlie violation" lasted 60 seconds and 1NM.
Lessons Learned:
To be determined.