By the way, the AIM is badly in need of a re-write in many areas.
That ought to take up your free time for the next weekend, or two...
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
By the way, the AIM is badly in need of a re-write in many areas.
I see your point. My biggest gripe is when pilots, after receiving a traffic call looks in that direction until the traffic is in sight. Now that ATC pointed out traffic we know that the traffic is there somewhere. What we should do is look in all other places and try to locate unknown traffic.
Is that you Doug McCain.... trying to avoid the issue....???
Seriously.... the only two replies are....
1. Negative contact
or
2. Traffic Insight
These are not accpetable
- lookin'
- got 'em on the fishfinder/TCAS
- Tally Ho
- switchin' to guns
- are you going to eat that?
I see your point. My biggest gripe is when pilots, after receiving a traffic call looks in that direction until the traffic is in sight. Now that ATC pointed out traffic we know that the traffic is there somewhere. What we should do is look in all other places and try to locate unknown traffic.
When a controller pints out traffic during cruise at the flight levels, he/she is only doing it simply so you won't be startled seeing another aircraft coming at you. After acknowledging the call, it is NOT necessary nor required to make another call to center to report the traffic "in sight". The controller really doesn't care too much.
Yesterday there were two blocked transmissions because pilots unecessarily called back to report "traffic in sight". An AA flight bugged INDY center TWICE to let the controller know the traffic was in sight....the second time with great irritation in his voice because he wasn't responded to on the first transmission when it was quite clear the controller was doing some coordination.
If a conflict was clearly there, rest asured I would have more than a "thank you" response to the controller as would these pilots I think.
That's your biggest gripe, eh? Pretty lucky to have had such a placid career.
And there's this new thing called TCAS. All the kids at the malt shop are talking about it. Bichin!
Huh?
Use a little CRM will ya. One set of eyes can look for the ATC traffic and the other can look for the unknowns you suggest. ATC is telling you about that traffic for a reason. How bout getting a visual on the guy so that you can determine IF he will be a problem at some point.
say again,
It's not "unnecessary chat" if there's about to be a midair collision. DON'T YA THINK?
When a controller pints out traffic during cruise at the flight levels, he/she is only doing it simply so you won't be startled seeing another aircraft coming at you. After acknowledging the call, it is NOT necessary nor required to make another call to center to report the traffic "in sight". The controller really doesn't care too much.
Yesterday there were two blocked transmissions because pilots unecessarily called back to report "traffic in sight". An AA flight bugged INDY center TWICE to let the controller know the traffic was in sight....the second time with great irritation in his voice because he wasn't responded to on the first transmission when it was quite clear the controller was doing some coordination.
After acknowledging the call, it is NOT necessary nor required to make another call to center to report the traffic "in sight".
It is also NOT necessary for you to come here and lay your radio philosophy on us.
Loser.
I never used to say "with you." I have since started hoping that you'd be listening and get your panties twisted.
Make sure not to use any of your precious radio time to tell us we are doing it wrong. That would make you quite the hypocrite.