You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm VATSIM Scandinavia's Events Assistant for Iceland and the facility engineer for BIRD FIR/OCA. I recently became aware of the fact that the new "RCL RECEIVED" message is being changed slightly by mutual agreement of the OCAs. See the following screenshot from BIRD AIP SUP 10/2024:
I have discussed this matter with other VATSIM OCA staff (Gary from Gander/Shanwick and Bernardo from Santa Maria; NY is not affected), and we have agreed that we would like the RCL RECEIVED language on Nattrak amended as following: Instead of:
RCL RECEIVED. FLY CURRENT FLIGHT PLAN OR AS AMENDED BY ATC. CONTINUE TO MONITOR NATTRACK PAGE UNTIL ENTERING OCA
Nattrak's "RCL received" message (when implemented) should read:
RCL RECEIVED. CONTINUE TO MONITOR NATTRAK UNTIL ENTERING OCA
Thanks very much in advance for your assistance on this!
The text was updated successfully, but these errors were encountered:
FIY these changes have been pushed back and are currently not live on natTrak (#129). I'm still waiting on having a proper specification to look at for what the changes should be, as discussed in the vatsim tech discord.
Hi, I'm VATSIM Scandinavia's Events Assistant for Iceland and the facility engineer for BIRD FIR/OCA. I recently became aware of the fact that the new "RCL RECEIVED" message is being changed slightly by mutual agreement of the OCAs. See the following screenshot from BIRD AIP SUP 10/2024:
I have discussed this matter with other VATSIM OCA staff (Gary from Gander/Shanwick and Bernardo from Santa Maria; NY is not affected), and we have agreed that we would like the RCL RECEIVED language on Nattrak amended as following:
Instead of:
Nattrak's "RCL received" message (when implemented) should read:
Thanks very much in advance for your assistance on this!
The text was updated successfully, but these errors were encountered: