I guess that means you don't know, but still felt the urge to say something.do you have foreflight? WingX? Garmin pilot?
Put your origin and dest airports in - and see what the possible routes might be -
I guess that means you don't know, but still felt the urge to say something.
If you are above 10k you are above Class B airspace - just saying...![]()
do you have foreflight? WingX? Garmin pilot?
Put your origin and dest airports in - and see what the possible routes might be -
If you are above 10k you are above Class B airspace - just saying...![]()
What I learned from one of my instructors:
1) Fly VFR at some high-ish altitude below 10k and ask for direct through the airspace.
2) When they say no, say "OK, we'll just climb to 10.5 and over fly the bravo."
3) Profit ... AKA suddenly find yourself cleared through their airspace so they don't have to deal with someone they can't control just on the edge of their airspace.
Seemed to work for him (this works best if you have a plane that has the performance to pull off the threat).
That's how a guy I know would deal with them too. IFR up to the Chicago bravo then cancel and go to 10.5 or 11.5 depending on direction, overfly, then pick up an IFR clearance again on the other side. Chicago usually wasn't happy about it but there wasn't much they could say.
I usually plan for the KELSI intersection on the SW side, and Gary on the east side. Chicago is pretty strict on their B. They wouldn't even let me cut the corner by the slighest bit on my last time around.
You can be too cute by half doing that. I knew a corporate chief pilot who would cancel in order to avoid Class B vectors. He'd cancel above the top and go VFR direct to his home base. One day he had a close encounter of an airline kind and his CEO received a scathing letter from the airline flight's captain, calling into question the judgment of the chief pilot. The pilot soon lost his job after that incident.What I learned from one of my instructors:
1) Fly VFR at some high-ish altitude below 10k and ask for direct through the airspace.
2) When they say no, say "OK, we'll just climb to 10.5 and over fly the bravo."
3) Profit ... AKA suddenly find yourself cleared through their airspace so they don't have to deal with someone they can't control just on the edge of their airspace.
Seemed to work for him (this works best if you have a plane that has the performance to pull off the threat).
At one time STl was the same way. I've done the same and it worked out fine.What I learned from one of my instructors:
1) Fly VFR at some high-ish altitude below 10k and ask for direct through the airspace.
2) When they say no, say "OK, we'll just climb to 10.5 and over fly the bravo."
3) Profit ... AKA suddenly find yourself cleared through their airspace so they don't have to deal with someone they can't control just on the edge of their airspace.
Seemed to work for him (this works best if you have a plane that has the performance to pull off the threat).
You can be too cute by half doing that. I knew a corporate chief pilot who would cancel in order to avoid Class B vectors. He'd cancel above the top and go VFR direct to his home base. One day he had a close encounter of an airline kind and his CEO received a scathing letter from the airline flight's captain, calling into question the judgment of the chief pilot. The pilot soon lost his job after that incident.
dtuuri
I'm opposed to privatized ATC and this has nothing to do with it. The airline captain was right, it's a stupid thing to do. The CEO concurred. Bye-bye chief pilot.If it was legal VFR and he was operating legally, there's nothing to say and the scathing letter was absolutely inappropriate. If he was outside the B (or C), then it's see-and-avoid under both IFR and VFR. Possible that the controller put the captain up to it, but the captain was wrong.
This is a key reason that many are opposed to privatized ATC.
oh no, @JOhnH, I know. The answer is that IFR you fly what they tell you to fly. You don't have a choice in the matter - so WTF does it matter?I guess that means you don't know, but still felt the urge to say something.
I'm opposed to privatized ATC and this has nothing to do with it. The airline captain was right, it's a stupid thing to do. The CEO concurred. Bye-bye chief pilot.
dtuuri
Ok, let me set the scene. You can be the chief pilot. You talked the CEO into upgrading from a KingAir to a Cessna Citation with one of those brand new two-waypoint RNAVs that let you move a nearby VOR over to the airport so you can track directly to it. The salesman said it would pay for itself in fuel savings, so naturally you need/want to use it as much as possible. So you get in the habit of canceling IFR as you're coming out of the flight levels at the red line at the first sign you aren't going to get direct to the airport because of traffic. You become a pest to ATC which is only trying to keep airplanes from colliding. One day, you pull your little snit-fit and have a "too close for comfort" encounter with an airliner. Maybe you were legal. Maybe there was 500 feet of separation. Maybe there wasn't. Maybe you were descending through an IFR altitude. Maybe the airliner was descending through a VFR altitude. Who cares. It was TOO CLOSE! Can you still defend yourself? If you were CEO would you want to be a passenger of that pilot's?I don't see why it's stupid.
VFR is see and avoid whether the other traffic is IFR or VFR. Traffic advisories may be given. If the airliner gets an RA on the TCAS they have to follow it (as I understand it). In other words it isn't cut and dried as you might like it to be. Did the airliner driver go overboard? Maybe. Is dtuuuurrrrriiii overboard? Sometimes. As always YMWV.I don't see why it's stupid. If you're VFR over 10,000 ft you're required to have a Mode C transponder anyway. The controller knows you're there and can provide separation to IFR aircraft. Better yet, if you're VFR with FF both aircraft will receive a traffic alert.
Chances are, the chief pilot saved a lot of gas $$ and time for that CEO. Sounds like it was a Part 91 operation so it's perfectly legal and there are checks in place to safely allow it.
One day he had a close encounter of an airline kind and his CEO received a scathing letter from the airline flight's captain, calling into question the judgment of the chief pilot. The pilot soon lost his job after that incident.
dtuuri
Ok, let me set the scene. You can be the chief pilot. You talked the CEO into upgrading from a KingAir to a Cessna Citation with one of those brand new two-waypoint RNAVs that let you move a nearby VOR over to the airport so you can track directly to it. The salesman said it would pay for itself in fuel savings, so naturally you need/want to use it as much as possible. So you get in the habit of canceling IFR as you're coming out of the flight levels at the red line at the first sign you aren't going to get direct to the airport because of traffic. You become a pest to ATC which is only trying to keep airplanes from colliding. One day, you pull your little snit-fit and have a "too close for comfort" encounter with an airliner. Maybe you were legal. Maybe there was 500 feet of separation. Maybe there wasn't. Maybe you were descending through an IFR altitude. Maybe the airliner was descending through a VFR altitude. Who cares. It was TOO CLOSE! Can you still defend yourself? If you were CEO would you want to be a passenger of that pilot's?
dtuuri
This is an example of when dtuuuuurrrriii is over the top. Why did he make up a story about upgrading from a king air? Why did he use the words "snit-fit"?Ok, let me set the scene. You can be the chief pilot. You talked the CEO into upgrading from a KingAir to a Cessna Citation with one of those brand new two-waypoint RNAVs that let you move a nearby VOR over to the airport so you can track directly to it. The salesman said it would pay for itself in fuel savings, so naturally you need/want to use it as much as possible. So you get in the habit of canceling IFR as you're coming out of the flight levels at the red line at the first sign you aren't going to get direct to the airport because of traffic. You become a pest to ATC which is only trying to keep airplanes from colliding. One day, you pull your little snit-fit and have a "too close for comfort" encounter with an airliner. Maybe you were legal. Maybe there was 500 feet of separation. Maybe there wasn't. Maybe you were descending through an IFR altitude. Maybe the airliner was descending through a VFR altitude. Who cares. It was TOO CLOSE! Can you still defend yourself? If you were CEO would you want to be a passenger of that pilot's?
dtuuri
It sure does... a high altitude route will be much different than a low altitude route through a bravo.If you are IFR, it doesn't make a lick of a difference what altitude you are at. You are at the hands of the almighty controller
I would certainly have an issue with the lack of separation. But it seems to me that the issue was caused by some failure in the system, not the canceling of IFR.Ok, let me set the scene. You can be the chief pilot. You talked the CEO into upgrading from a KingAir to a Cessna Citation with one of those brand new two-waypoint RNAVs that let you move a nearby VOR over to the airport so you can track directly to it. The salesman said it would pay for itself in fuel savings, so naturally you need/want to use it as much as possible. So you get in the habit of canceling IFR as you're coming out of the flight levels at the red line at the first sign you aren't going to get direct to the airport because of traffic. You become a pest to ATC which is only trying to keep airplanes from colliding. One day, you pull your little snit-fit and have a "too close for comfort" encounter with an airliner. Maybe you were legal. Maybe there was 500 feet of separation. Maybe there wasn't. Maybe you were descending through an IFR altitude. Maybe the airliner was descending through a VFR altitude. Who cares. It was TOO CLOSE! Can you still defend yourself? If you were CEO would you want to be a passenger of that pilot's?
dtuuri
This happened when class B was known as a TCA. I knew the pilot, flew with him as copilot a few times and can vouch for his reasoning. But I don't know the details first hand or saw the letter or ever even discussed it with the person later. The story was told to me by someone else and it's been so long ago I don't remember who told me. If anybody made it up, it wasn't me. But it sure fits. I've seen 500' separation from VFR traffic in Pittsburgh's class B, close up and personal, and still remember it 20 years later. I suspect some of these pundits here never have. The next time they line up and wait I hope they take a gander at the touchdown marker 1000' down the runway and picture a big transport zooming over the windshield half that distance above. Or even a commuter for that matter.I would certainly have an issue with the lack of separation. But it seems to me that the issue was caused by some failure in the system, not the canceling of IFR.
I would certainly have an issue with the lack of separation. But it seems to me that the issue was caused by some failure in the system, not the canceling of IFR.
I'm opposed to privatized ATC and this has nothing to do with it. The airline captain was right, it's a stupid thing to do. The CEO concurred. Bye-bye chief pilot.
dtuuri
Bear in mind that I'm not a pilot but an A&P/IA with a minuscule knowledge of ATC procedures. While trying to avoid thunderstorms and asking Chicago center for a deviation to go around them the pilot I was flying with was denied his request hands down and we were sent on a long diversion to the south of Chicago.. The same thing has occurred with Cleveland Center and I have to make the presumption that other Class Bravo's have the same attitude. Some are helpful, others are not.
The friend I fly with is based at KFRG and is known to New York controllers. Why is there such divergent opinion between centers and approach controllers? I thought they were there to direct traffic, not deny them entry to their fiefdom.
Your first point, without knowing the specifics it's foolish to comment one way or the other imo.Legal VFR both the airliner AND the GA plane had a responsibility. The airline captain was wrong, and quite frankly might well have set up a lawsuit between pilot and company into which he would be dragged. Maybe he could beat a tortuous interference with employment claim or maybe not. If it went to court, the first question a good defense attorney would have asked would have been what the legal separation was, then whether it was met, then who had responsibility. Since the FAA set the rules, it would be considered to be the legal authority. The captain very well would have had some answering to do. I'm surprised that the pilot who lost his job didn't go to the airline. These days, it would be viral.
I was going into ARR one night on the west side of Chicago and the controller was so determined to keep his airspace sterile of the evil GA planes that he stuck one on the west side at an altitude where said GA plane was picking up light to moderate rime. GA plane asked for another route or altitude and controller said "you have to stay there, I have no where else to put you". GA plane declared, and was granted a route at lower altitude into the Class B. All this was at altitudes below 10,000.
If the CEO's defense attorney asked that question, he'd get fired too.If it went to court, the first question a good defense attorney would have asked would have been what the legal separation was, then whether it was met, then who had responsibility.
That's a pretty all inclusive statement. It would be like saying all Cirrus drivers are half a$$ pilots hoping the plane fly themselves. Or saying all people with red vehicles are trying to compensate for something.Chicago is very proud of their bravo and they don't like us little bugsmashers getting anywhere near it if they can avoid it. Unless you have 100+ paying passengers in the back and two jet engines, you're a second class citizen anywhere near Chicago. That POS mayor Daley must have rubbed off on the local controllers.
Night and day compared to the other large Bravo that I also fly into all the time (NYC) where as long as you perform and speak professionally, they're just as happy to work a C152 as a Boeing or Airbus.
That's a pretty all inclusive statement. It would be like saying all Cirrus drivers are half a$$ pilots hoping the plane fly themselves. Or saying all people with red vehicles are trying to compensate for something.
Obviously I say this in jest. I think Cirrus's and their drivers are generally great and I particularly love the look of yours in the display pic.
The Chicago Class B thing is a complex issue and I assure you not all controllers here are anti GA (most if not all would slap Daley and bring Meigs back if we could).
Until recently the configurations at ORD didn't allow for non-participants at the big airport entry. It was the busiest/2nd busiest in the world and looked like the designer of the airport just dropped pixie sticks with runways in all directions. We are now in an east/west flow scenario like ATL. Unlike ATL we don't have RNAV departures that depart on rails that de-conflict with possible Class B corridors over the top. Jets are coming off ORD in all directions with no canned headings or altitudes other than the SID low crossing altitudes.
Without getting into too many complex details, things are changing (including the controller workforce from the old times) that hopefully will help GA feel better about the airspace. I've noticed flying in and around the airspace regularly that it is getting better. Changing a culture takes time. We do now have several active pilots in the ranks. On another forum I'm a part of a 340 guy I didn't know personally responded to a post about the class B VFR clearance I gave him getting above the departures and eventually the arrivals and quickly direct his destination above the bumps.