Querer 74 Posted January 9, 2019 Share Posted January 9, 2019 Hi all, I have another question that might be rather silly: I do my flightplanning with ProATC/X to have a nice alignment of this ATC tool with my Airbus flightplan. However, I still do not entirely get how to properly transfer the ProATC/X flightplan to the bus. What I do currently and what usually fails is: I copy paste the route of ProATC/X into the Company Route Editor and name it for example LSZHLEMD01. Then I load this flightplan into the MCDU of the Airbus. While it always correctly tansfers each waypoint and departure and arrival airport, it does not work regarding airways. Is this intended? Example of the flight LSZH to LEMD: ProATC/X provided me the route LSZH DCT WIL MEBOX J70 MILPA UZ65 RBT03 DCT MURRO DCT MEN DCT DITEV UN871 LARDA DCT EDIVA DCT BAN LEMD. If I copy this into the Company Route Editor, it works without any error message. However, the bus then only loads the waypoints and completely ignores the airways. Resulting in a direct-to from DITEV to LARDA, which is obviously not what ProATC/X intended. I then tried to add the airway manually and failed. I was able to select UN871 as airway at DITEV, but LARDA as exit point was not possible. Why? Thanks for any help. Link to comment Share on other sites More sharing options...
Deputy Sheriffs Secondator 643 Posted January 9, 2019 Deputy Sheriffs Share Posted January 9, 2019 First thing that comes to my mind is that your Navdata AIRAC is different on ProATC and on the Airbus. Can you confirm that you are using same Navdata provider and cycle on both? Link to comment Share on other sites More sharing options...
Querer 74 Posted January 10, 2019 Author Share Posted January 10, 2019 Yep, I can confirm this. I use the NavDataPro AIRAC from Aerosoft and the GUI to update the Airbus, CRJ and ProATC/X. They have all three the same database regarding AIRAC. Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted January 10, 2019 Deputy Sheriffs Share Posted January 10, 2019 I think the problem is that ProATC produces utter nonsense: there is no airway J70 from MEBOX to MILPA, according to actual charts J70 is only a oneway from MEBOX to WIL. Please login to display this image. And this messes up the route string during conversion and results in simply DTOs. And TBH meanwhile we had several cases, where this tool is anything else then reliable. So if you want to have a tool producing reliable routes, choose something like simbrief. Link to comment Share on other sites More sharing options...
Querer 74 Posted January 10, 2019 Author Share Posted January 10, 2019 Ok, that is something I suspected already for other strange flightplans by ProATC/X, that it does not take into consideration the direction of the airway (could also be my fault, that ProATC/X actually meant J70 between MEBOX and WIL but ignored the one-way thing). Could this also be the issue with UN871? I will try simbrief or something else, those routes can be easily imported into ProATC/X, maybe the more useful approach... Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted January 10, 2019 Deputy Sheriffs Share Posted January 10, 2019 Yes, ProATC also flies UN871 in the wrong direction. Maybe you should ask Pointsoft, whether they will solve this problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.