That is expected for VFR flights in the US.
US controllers use CRC, and it won’t show VFR flight plans to controllers, which is how it works IRL. You can still file it so it shows up correctly on maps like vatsim-radar.
1 Like
The information you’ve been provided is correct regarding filing VFR in the US.
That said, there are special procedures to follow when flying in the DC Special Flight Rules Area (DC SFRA). Please reference the material from vZDC ARTCC for more information, but special procedures apply within 60nm of the DCA VOR. Specifics of the special rules depend on how close you are to DCA and where you are specifically within that area.
Very possibly outside the scope of this beta, but is there any possibility of including a STS/ field separate from just using remarks?
BETA
First ever issue with BETA version
No matter what I place in Voice Rules it says it isn’t selected……..
I really like how its a bit cleaner than before. The voice rules box is my favorite new feature and one that should have been added way sooner. Can I file with this now and when will it become alpha?
That’s not my point. My point is having a VATSIM-standardised item 18 identifier to indicate such callsign so tools can parse it. At the moment, there is no such way and aircrafts are being called with the wrong callsign as the tools used show a callsign, but the wrong one.
That’s also not my point. My point was that I suggest moving away from using /[VRT]/ in item 18 to using some ICAO-syntax indicators, e.g. RTF/{TEXTONLY|RXONLY}.