![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]() "Jonathan Goodish" wrote: I agree, except for "looking." When ATC calls traffic, you have three choices in my experience: Negative contact, traffic in sight (not "contact"), or looking. If ATC calls traffic, responding with "negative contact" before I have a chance to look is counterproductive. Counterproductive to what? No response while I look is also counterproductive, because the controller has no idea whether I heard the traffic call or not. Responding with "looking" acknowledges the transmission and tells the controller than I don't have the traffic but I'm not blowing it off. Why would the controller presume you are "blowing it off?" After I've had a chance to actually scan for the traffic, I will respond with either "negative contact" or "traffic in sight." Then "looking" was an extra, unnecessary transmission. -- Dan C172RG at BFM |
#2
|
|||
|
|||
![]()
In article ,
"Dan Luke" wrote: No response while I look is also counterproductive, because the controller has no idea whether I heard the traffic call or not. Responding with "looking" acknowledges the transmission and tells the controller than I don't have the traffic but I'm not blowing it off. Why would the controller presume you are "blowing it off?" What do you propose as a response to a traffic advisory? Nothing? Stating "negative contact" immediately? When the controller advises of traffic, he expects you to look for it. Under VFR he probably doesn't care if you acknowledge his advisory, or whether you look or if you see it, but under IFR he does. No response (or a delayed response) is not a good option because the controller has no idea whether you heard the advisory or not. Immediately stating "negative contact" before you have an opportunity to look accomplishes nothing, and may very well cause the controller to issue you a turn you don't need or waste even more radio time trying to draw your attention to the target (been there, done that in both cases.) After I've had a chance to actually scan for the traffic, I will respond with either "negative contact" or "traffic in sight." Then "looking" was an extra, unnecessary transmission. Where did I lose you? "Looking" was used to acknowledge the advisory and inform the controller that I am looking for the traffic. JKG |
#3
|
|||
|
|||
![]()
Jonathan Goodish wrote:
What do you propose as a response to a traffic advisory? Nothing? Stating "negative contact" immediately? Since when did "negative contact" mean "I looked once when you first told me but didn't see the traffic so now I am going back to reading the newspaper?" -- Peter |
#4
|
|||
|
|||
![]() "Jonathan Goodish" wrote: What do you propose as a response to a traffic advisory? Nothing? Stating "negative contact" immediately? The latter, of course, unless I see the traffic. When the controller advises of traffic, he expects you to look for it. Bingo! Hold that thought! [snip] Where did I lose you? You lose me when you use made-up phraseology where standard phrases already exist. -- Dan C172RG at BFM |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Air Force One Had to Intercept Some Inadvertent Flyers / How? | Rick Umali | Piloting | 29 | February 15th 06 04:40 AM |
terminology questions: turtledeck? cantilever wing? | Ric | Home Built | 2 | September 13th 05 09:39 PM |
Nearly had my life terminated today | Michelle P | Piloting | 11 | September 3rd 05 02:37 AM |
Washington DC airspace closing for good? | tony roberts | Piloting | 153 | August 11th 05 12:56 AM |
USAF = US Amphetamine Fools | RT | Military Aviation | 104 | September 25th 03 03:17 PM |