michelvine 0 Posted August 25, 2015 Share Posted August 25, 2015 I have a problem when entering a flight plan in the MCDU. The route that I enter is : CYUL BOBKI MELTI TORNI RAGID2 CYYZ. This route is a real route. The problem is about the order of the waypoints. I enter the route as it is, but when I enter MELTI, the route becomes MELTI BOBKI TORNI RAGID2 !! I checked the geographic position of the two points and they are right. BOBKI is N45 25.12 W74 25.88 and MELTI is N45 20.61 W74 52.41. I don't know why I go MELTI, then back to BOBKI, then TORNI. It makes no sense.Also, is there someone who can explain how to deal when you get a MANUAL waypoint. From CYUL, if I put SID TRUDO2, I always get a MANUAL waypoint. So, I would like to know what to do with this waypoint?Thank youMichel Link to comment Share on other sites More sharing options...
avegeek 0 Posted August 25, 2015 Share Posted August 25, 2015 im having the same issue its a pain in the arse because thers nothing to help u with your route there n then so u dont know the airways etc Link to comment Share on other sites More sharing options...
skelsey 103 Posted September 7, 2015 Share Posted September 7, 2015 Hi Michel,Where are you entering MELTI -- on the F-PLN page or as a LAT REV? The easiest way to do it would be as a LAT REV from BOBKI which should insert it in the correct place.If I recall correctly, a MANUAL waypoint is the equivalent of VECTORS in Boeing FMC jargon.I'm not familiar with YUL, but I'm assuming that the TRUDO2 is a vector departure: in which case, there is no published route, ATC would just vector you and then at some point clear you direct to whatever your first enroute waypoint is. So you would depart in selected heading, follow ATC instructions and eventually resume own navigation in managed mode direct to (for example) BOBKI. Link to comment Share on other sites More sharing options...
Emi 5161 Posted September 9, 2015 Share Posted September 9, 2015 Hi Michel,are you sure you enter this on the correct LSK?The waypoints are not autosequenced, so you have to enter them correctly and recheck their order. They will show (and be flown) the way you enter them, even if you enter them at wrong places. MANUAL waypoints are points where procedures include Legs which have to be flown in HDG mode (so parts where the procedure ends and ATC has to give you vectors). Link to comment Share on other sites More sharing options...
michelvine 0 Posted September 9, 2015 Author Share Posted September 9, 2015 Hi Skelsey. Hi Emanuel.I think I entered it the right way. I am using TRUDO2 SID so it put a MANUAL waypoint followed by a f-discontinuity. Then I click LSK beside MANUAL and enter BOBKI. I do the same for MELTI clicking LSK beside BOBKI, then TORNI and this is where everything goes wrong. Instead of having BOBKI MELTI TORNI, I end up with MELTI BOBKI TORNI !!!So yesterday, I tried to do it different way. I just entred each waypoint (BOBKI MELTI TORNI) one at a time on the scratchpad then I pressed the LSK beside flight Discontinuity for BOBKI and it was entered on the flightplan. I did the same for MELTI and pressed LSK beside BOBKI and MELTI took place after BOBKI and so on. So everything look fine now.Thank you.Michel Link to comment Share on other sites More sharing options...
ubersu 23 Posted September 9, 2015 Share Posted September 9, 2015 I have observed that when the next waypoint is entered via the 'next waypoint' function, it will from time to time become the previous waypoint. I have never figured out quite why or when that will occur, but it is a pain.DJ Link to comment Share on other sites More sharing options...
mrb13676 0 Posted January 6, 2016 Share Posted January 6, 2016 I have the same problem. It's very annoying. Also, not everytime will the TMPY F-PLAN yellow text appear for confirmation... Link to comment Share on other sites More sharing options...
Keith Huxley 0 Posted January 19, 2017 Share Posted January 19, 2017 I am having the same problem. Enter a fix into the next way-point field and it gets entered into the previous position. This has only recently started to happen Link to comment Share on other sites More sharing options...
Rongor 1 Posted February 3, 2017 Share Posted February 3, 2017 I can confirm this happens frequently. It's obviously not related to specific routes, in fact it can occur anytime. I am using the A320/321 package v1.31 with P3D v3 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.