Refer to slide 10-13 of for more information Some of them can be considered via computing an own pseudo fix point in the future. There are some path terminators (CA, CI, CR, VA, VD, VI, VM, VR) being ignored, since they provide no lat/lon information (needed in. But I guess it is not needed to have that with the resolution of waypoints/ route at the moment. The computed routes do not include any interception information. This applies for routes having been exported via the A350 itself and the routes being generated by this script. The LOAD SID and the RTE SEL functions of the A350 FMS seem to ignore speed constraints. I am not sure, if all works correctly, therefore please send reports of wrongly computed routes. I coded some Python workaround because I wanted to be able to load SID / STAR routes via the according buttons in the FMS of the FF A350.
0 kommentar(er)
