There might be an airport about to introduce SSR in the near future (yes this is the 21st century) that operates ATSOCAS.
Questions come to mind that I am sure you all have answers for ,if not THE answers.
If you have only been allocated 8 discreet squawks by spectrum thingy at DAP it is therefore almost impossible to allocate every FIS crosser, or local a discreet squawk as others do. So the plan is to have 2 conspicuity codes one for locals, arrivals and departures and another for transits.
As we all know conspicuity must be treated as unvalidated and unverified and as it is not discreet cannot be deemed identified.
The 2 conspicuities are of course however “known traffic” when you can assure yourself that you really do know the intentions.
Without going round the houses on RAS and participating traffic again as that is covered in a local instruction;-
Q1 Can the conspicuity be asked to squawk ident if no inference of radar service is implied to assist in discharging our responsibilities with the PAX, Jet, RAS traffic that this FIS is going to be in conflict with? and an
agreed level cap be applied.
Q2 Is it practical, safe, legal, a good idea to change the potential FIS confliction to a discreet code( if you have any left), ensure that no service is implied and then when it is no longer a confliction change it back to the conspicuity.
Q3 How does the LCE team help the troops to ensure that the new data on the displays does not tempt them into taking FRISING to the next level of using modes A and C to expedite the Jet RAS traffic by keeping the pesky FIS’s out the way??? and reducing the willingness to not seek to achieve 5 nm etc.
