kolos 0 Posted July 24, 2017 Share Posted July 24, 2017 Hy All, When preflight, any flight plan is loaded, the first waypoint always turns as a fly over waypoint, regardless of SID flyby or over format. Any other simmer experience some similar? This is frustrating when SID contains a strict flyby waypoint. If I input a conditional waypoint before it (for example waypoint/-3), that solves the problem. But I'm a little bit fed up with inputing such conditinal waypoints always before all flights. Are there any more wise solution for this? thanks Kolos Link to comment Share on other sites More sharing options...
datguytho 38 Posted July 25, 2017 Share Posted July 25, 2017 Sorry if I may missunderstood your question. Is the first waypoint really a overfly waypoint and is displayed as such in the FMS? Or is it just flown like an overfly waypoint without the triangle? Link to comment Share on other sites More sharing options...
kolos 0 Posted July 25, 2017 Author Share Posted July 25, 2017 When loading the flight plan, still everything fine. After performance data input, the first waypoint switches to flyover and shown on ND as flyover. If takeoff and engage A/P, waypoint will flown as flyover, however that should be fly by... Link to comment Share on other sites More sharing options...
kolos 0 Posted July 25, 2017 Author Share Posted July 25, 2017 No triangle Link to comment Share on other sites More sharing options...
datguytho 38 Posted July 25, 2017 Share Posted July 25, 2017 Screenshots of the ND and MCDU Flight Plan page before and after the performance input would be helpful. Link to comment Share on other sites More sharing options...
kolos 0 Posted July 27, 2017 Author Share Posted July 27, 2017 Actually just learned that, changover point happens not when inputing performance data, but airborne. Before airborne: Please login to display this image. Please login to display this image. When Airborne: Please login to display this image. Please login to display this image. Link to comment Share on other sites More sharing options...
kolos 0 Posted July 27, 2017 Author Share Posted July 27, 2017 Tokyo Haneda departure from rwy 16R YANAG1. In the navdatabase waypoint format and sequencing are all correct. But happens the same with all SID and STARs as well all around in Japanese airports. Regardless of prior altitude overfly conditinal waypoint exist or not. Link to comment Share on other sites More sharing options...
datguytho 38 Posted July 27, 2017 Share Posted July 27, 2017 Which AIRAC cycle is used here? It seems to be kind of outdated. Link to comment Share on other sites More sharing options...
datguytho 38 Posted July 27, 2017 Share Posted July 27, 2017 Oh and btw, the turns before or at a waypoint are calculated as soon as this fix is the next waypoint in the flight plan. So this has nothing to do with performance data or the plane being airborne. Also, what happens when you manually add a fly-over and remove it? Link to comment Share on other sites More sharing options...
kolos 0 Posted July 28, 2017 Author Share Posted July 28, 2017 - AIRAC: yes, that's is outdated. Actually I have never updated since I purchased Aerosoft a321 in 2015. - yes, I know, turn radius and condition are calculated just when waypoint becomes active inbound. But fly by/over condition is calculated wrongly. And it happens with all airports's all SIDs. - I will try manual fly over input. However I have a bit similar solution. Inputing "minus distance" conditional waypoint. But rather I would like to find reason why airbus identifies the first waypoint always as fly over then tweaking it. Can you experience the same with your Bus? Or for you it works well as fly by? Link to comment Share on other sites More sharing options...
datguytho 38 Posted July 28, 2017 Share Posted July 28, 2017 I have never experienced such an issue with SIDs. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.