Shane O'Neill Posted June 25, 2019 at 06:30 AM Posted June 25, 2019 at 06:30 AM 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 comment Share on other sites More sharing options...
Andreas Fuchs Posted June 25, 2019 at 12:58 PM Posted June 25, 2019 at 12:58 PM 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 comment Share on other sites More sharing options...
Andreas Fuchs Posted June 25, 2019 at 07:06 PM Posted June 25, 2019 at 07:06 PM 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 comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted June 25, 2019 at 09:59 PM Board of Governors Posted June 25, 2019 at 09:59 PM 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, Operations Link to comment Share on other sites More sharing options...
Andreas Fuchs Posted June 25, 2019 at 10:39 PM Posted June 25, 2019 at 10:39 PM 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 comment Share on other sites More sharing options...
Magnus Meese Posted June 25, 2019 at 10:46 PM Posted June 25, 2019 at 10:46 PM 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 comment Share on other sites More sharing options...
Recommended Posts