Originally Posted by
Lissart
Yes but...... 4444 says: "The information presented on a situation display MAY be used to provide IDENTIFIED a/c with......etc." (My bold.) So before you can do anything really useful the a/c needs to be talking to you or, at best, someone else who has identified, validated and verified it. Right? Otherwise there is limited value in seeing that something is out there on your screen....
I don't get your point; controllers in France (so I'm told)
routinely identify aircraft who call them requesting Flight Information Service; once identified the height readout MUST be verified and thereafter, traffic information and (when necessary) advisory avoiding action is passed.
In the UK, controllers MUST identify and verify altitude readout for traffic requesting TS or DS unless the identity is transferred from another radar unit who will have already done this. Traffic requesting Basic service ie what used to be called Flight Information Service MAY be identified and if so, any altitude readout associated with their SSR
must be verified. Thereafter even this traffic may be passed
generic information on possible conflicting traffic especially when 'duty of care' requires it ie if you see a 'dead ringer' for your traffic you should tell the pilot about it rather than sit there and do nothing.
In the case quoted at Bournemouth, even though the Falcon was only on Traffic Service in the Initial Approach phase, NOT the Final Approach stage, he
was identified so the controller
could have offered advisory avoiding action (traffic is in your ......, if not sighted suggest left/right heading...) or if the confliction looked serious, upgraded the Falcon to De-confliction service and passed avoiding action prior to passing the traffic information.