Originally Posted by
Emb170man
Out of LGA, westbound past ELIOT...why do we get stuck at 17,000ft for 50+ miles before we can get the climb? Wastes a lot of gas. The other problem is with VFR aircraft. I have had 3 RA's that I have had to climb or descend for at 17,000 feet out of LGA. Departure will call out a King Air at 16,500 or 17,500...its always head on and I end up having to deviate on my altitude due to an RA. The best part is that the same controller is normally talking to the King Air guy and never asks either of us to turn 10 left for traffic. I realize that you are not required to seperate VFR from IFR traffic, but if they are only 500 feet sperated, I'm going to get the RA and have to cause you more work (plus I have to fill out paperwork that night when I get to the hotel...boo!).
If you are 500' above or below a VFR King Air, you *are* separated - we only need 500' between a VFR and IFR, even in class B (heavies and 757s are the exception). If a controller issues that traffic, you can ask for a vector around or away from him and the controller is supposed to make an effort to do that. You're right, in class E, we don't *have* to even do that, but I don't know any controllers who would let you run right at another target, same altitude, and not try to get you away from it.
It sounds like TCAS and the FAA's minimums don't agree. My personal feeling is that if I called the traffic, and they're both level at least 500' apart, I do nothing unless a pilot asks for a turn away from them. The reason is that early in my career, I was asked by a pilot why I was turning his airplane when the other guy was level 500' above him.
So, if someone wants a turn away, I will give it to them. If they say nothing, I let them run because it's safe and legal for me to do so.