What do you guys use?

cmhumphr said:
I learned that saying "We got em' on TCAS or the fish finder" does absolutely nothing for them. They need to know you have the traffic in sight and will maintain visual separation. Since you fly down low a lot and especially on clear blue days when the GA traffic is dense, We get a lot of TCAS climbs and descents and we just say,"Traffic in sight, maintaining visual separation".
Click to expand...
How have you learned this, obviously not by reading the AIM.
 
I remember this from the controller forum, and AIM backs it up: there is no standard response 'Looking'! They want either 'in sight' or 'negative traffic', everything else is mostly annoying controllers.
 
TIS sucks. We have it in the Duke, and it doesn't work in two different areas on the route between Norfolk and Dulles. Really comforting when ATC calls traffic, and you hear "traffic not available" shortly thereafter.
 
I usually say roger, looking. I seldom call traffic in sight at altitude even if I see them. I had a near midair many moons ago where we called the traffic in sight and the controller issued a climb to the traffic. The plane we thought was the traffic wasn't the one and Do-328 almost took the nose off our aircraft.

I know feel they can wait or we can take a vector for their climb so the controller can maintain what he/she has to maintain on radar.
 
Bandit_Driver said:
I usually say roger, looking. I seldom call traffic in sight at altitude even if I see them. I had a near midair many moons ago where we called the traffic in sight and the controller issued a climb to the traffic. The plane we thought was the traffic wasn't the one and Do-328 almost took the nose off our aircraft.

I know feel they can wait or we can take a vector for their climb so the controller can maintain what he/she has to maintain on radar.
Click to expand...

I thought they weren't allowed to use visual seperation above FL180?
 
TUCKnTRUCK said:
Honestly, unless I "need" to have them it's... Looking, even if I see them I don't want the same level of services. Anyways for us 121 guy, most traffic calls are informational/ convenience only. Even with them in sight most controllers keep IFR separation requirements.
Click to expand...

You're 121, so GA traffic should get out of your way anyway.

Unless they're current on their user fees payments.

:D
 
Looking for traffic, or traffic in sight. Sometimes... negative contact if it sounds like it's important as opposed to your typical 1,000 feet below advisories in the flight levels.
 
Bandit_Driver said:
I usually say roger, looking. I seldom call traffic in sight at altitude even if I see them. I had a near midair many moons ago where we called the traffic in sight and the controller issued a climb to the traffic. The plane we thought was the traffic wasn't the one and Do-328 almost took the nose off our aircraft.

I know feel they can wait or we can take a vector for their climb so the controller can maintain what he/she has to maintain on radar.
Click to expand...

I agree for the most part, though when I'm low on gas and I can accept a visual interval vs continued vectors out into east jesus for "spacing", I will call it. But then I will also lock them up on the radar (if I haven't already) which helps for my own warm and fuzzy
 
You must log in or register to reply here.
Back
Top