Shane O'Neill 1 Posted June 25, 2019 Share Posted June 25, 2019 Hello. When filing a flight plan in Swift, it requires to put "ft" for feet after the altitude. When I do this, air traffic control has issues with seeing the altitude on their end. For example, when I file 6000 ft on Swift, it comes up on ATC's flight plan as "6000t". Also when I filed 10000 ft once, ATC said there was nothing there at all. Is this a known? Link to post Share on other sites
Andreas Fuchs 239 Posted June 25, 2019 Share Posted June 25, 2019 Hi Shane, thanks for reporting, I will forward it to the group on Discord. Cheers, Andreas Member of VATSIM GermanyMy real flying on InstagramMy Twitch streams of VATSIM flights and ATC Link to post Share on other sites
Andreas Fuchs 239 Posted June 25, 2019 Share Posted June 25, 2019 Hi Shane, I just tested it with an ATCO using Euroscope as radar-client. I filed flightplans with "5000ft", "A050" and also with "10000ft" and the ATCO had it displayed correctly either as 5000ft or as 10000ft. Cheers, Andreas Member of VATSIM GermanyMy real flying on InstagramMy Twitch streams of VATSIM flights and ATC Link to post Share on other sites
Board of Governors Don Desfosse 31 Posted June 25, 2019 Board of Governors Share Posted June 25, 2019 Just wondering out loud... Is it perhaps an issue with the space character? OP reported he filed as "6000 ft" and "10000 ft", yet Andreas reports testing without a space character, e.g. "5000ft" and 10000ft". I wonder what would happen if Andreas tested with "5000 ft" and 10000 ft".... [/wonderingoutloud] Don Desfosse Vice President, Membership Link to post Share on other sites
Andreas Fuchs 239 Posted June 25, 2019 Share Posted June 25, 2019 Good point, Don! Let me tell the team! At the moment the swift-team is considering dropping the unit (characters) altogether. By the way, when you click on the question mark next to field 7. cruising altitude you will open the Altitude dialog. As you can see, I only inserted "5000" in the dialog and it resulted in "5000ft" in the flightplan. Cheers, Andreas Member of VATSIM GermanyMy real flying on InstagramMy Twitch streams of VATSIM flights and ATC Link to post Share on other sites
Magnus Meese 5 Posted June 25, 2019 Share Posted June 25, 2019 Thread hijack: Can we please remove "kts" from TAS, and make three digits default to mean knots as it always has? If someone's flying a A320 filed at 950, we understand from context they've filed km/h. The org/dest will also provide a clue. And also please make TAB switch from Route to the next field, not actually do text editor tab spaces in the text field. Making stuff more keyboard friendly makes my arm hurt less Thanks! Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now