Recommended Posts

Hi! I have a problem when I planing a flight from LFMN. I create a rout in FMC as usual, get a aktive rout, T/O and press A/P on. Then the aircraft will not follow the aktive rout, she try to returns to the ORIGIN. As you can see at the picture neater time "Z" or distans "NM" are displayed.  The issue only occurs at LFMN. What do I do wrong?

//Oscar Speer

 

 

DUuzvrzn5ynAmEo9260sXoVTPievUA-Gy0bPrXPt

 

 

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Posted (edited)

Hello Oscar.

Can you show me a Picture of your PFD as well ? I want to make sure you have LNAV Armed ( that is what lets AFDS to command the A/P to follow the Required Lateral Navigation Path entered and activated in FMCS ). Do not forget to have Flight Director and LNAV Armed. 

Edit:

Assuming your picture is just a sample not what you are really trying to do, I hope you understand that the Airplane will not move and taxi around with Engines off magically and will not follow the active route without being Airborne and 250ft AGL at least.

Regards.

 

-S.

Edited by Samany69
extra edit.

Share this post


Link to post
Share on other sites
Posted (edited)

Oskar, I don't think you're doing anything wrong here. This looks like the RNAV SID off rwy 04L/R at LFMN with the first "arbitrary" waypoint on hdg 043 deg. when at 420 ft. then turning right to track radial 138 outbound from NIZ VOR till 8 dme, etc. Seeing you are still stationary, no distance or time to this first waypoint can thus be calculated and so none displayed. Have you tried manual flying the SID till the second point and then select A/P? It works for me. It's actually fun to fly the whole departure manually.🙂

 

Edited by Johannvr

Share this post


Link to post
Share on other sites

Hi, Johann and Saman! Yes I have fly the sid with manually input to A/P (HDG, Speed, Altitud). It works:-) The problem occurs at 4000 ft AGL or higher. Yes, LNAV, VNAV and FD are on. I have this issue only at LFMN. 

Share this post


Link to post
Share on other sites

The departure  procedure looks like it is missing something.  This is the BADOD6E (this is not a RNAV procedure Johann).  It is normal for the distance and time to not be display until after you takeoff, first the time is unknown until you start flying and second the distance is unknow because it is a conditional waypoint (043 until 420... how far is that?  You don't know until have a rate of climb to predict the distance).

6 hours ago, Oskar Speer said:

Then the aircraft will not follow the aktive rout, she try to returns to the ORIGIN.

This is what I don't understand.  The aircraft should fly to the ndb and not the airport after passing NIZ d11.  You haven't provided enough information to figure out why this happens.

Share this post


Link to post
Share on other sites

    The picture from my flight LFMN-ESGG. If I engage LNAV the aircraft turns back to ORIGIN. Disconnect LNAV and input data to A/P manually and it works fine again.  In the ND, you can see that "Z" and "NM" data is missing. This issue only occurs when T/O from LFMN. In addition, tonight during the flight, the left CDU just get a Black Out (=the display goes black) when I press "FMC". I guesses that I have done several wrong commands. Dan, I do not know what kind of info you need from me about the flight but maybe you can tell what you need from me. The CDU FMC do not "EAT" way points and airways in the Legs page as it use to do. I can see them all in the display even if I left them behind during my route.

 

zBK9PEaYXpew0rjXgTQ65wITZIFe4JAGwBXPUtT9

Share this post


Link to post
Share on other sites
Posted (edited)
10 hours ago, Oskar Speer said:

Hi! I have a problem when I planing a flight from LFMN. I create a rout in FMC as usual, get a aktive rout, T/O and press A/P on. Then the aircraft will not follow the aktive rout, she try to returns to the ORIGIN. As you can see at the picture neater time "Z" or distans "NM" are displayed.  The issue only occurs at LFMN. What do I do wrong?

//Oscar Speer

The first three entries on your LEGS page (   420); (NIZ-8) and (NIZ-11) are all conditional waypoints.  They are NOT in a fixed geographical position and only indicate when an event will occur.  Because these three conditional waypoints are relatively close in to the airfield it is perhaps hardly surpising you are having problems trying to reconcile your initial LNAV tracking.  Every flight is different on the day, but it can sometimes be easier to look through the Flight Director and fly the aircraft manually using VNAV and LNAV in these situations, possibly until you are cleared direct to NCNB or AMIRO; then you can engage the autopilot.  Incidentally, LFMN is not the only airfield where conditional waypoints are generated automatically when entering a SID or STAR and you will find you cannot enter conditional waypoints manually.

To get rid of the waypoints behind you all you need do is activate a direct intercept to the next waypoint.

Bertie G

Edited by berts
additional info
  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

I've seen problems with the NGX/777 and cascaded conditional waypoints in other cases.  For example, selecting the OCK transition for an EGLL ILS will lock up the PMDG FMS.  This was fixed in the 747 QOTSII.  I think the NGX should fly these three cascaded conditionals but it seems not to want to... and in other cases I've seen the ND rendering a wrong direction turn only to have the FMS/AP follow through on the correct course.  Having said all that (it should but has a bug) in RW were I piloting the departure I'd either be selecting one of the many RNAV based procedures or handflying this one until I was direct AMIRO and hand it off to otto at that time.

By the way, glad you posted this. I used to visit Nimes for a couple of days every year when stationed in Germany and taking my summer vacation in Spain. Nimes was a great place to stop overnight. Such a beautiful and historic city.  I feel in love with it and used to dream I'd retire to the South of France.. haha. Well, South of Texas will have to do and my visits to Nimes will be a simulator.

EDIT:  I've been looking at your picture and I cannot make out the LEGS page on the CDU.  Is the FMS advancing through each of the conditional waypoints as you pass them?  You should be getting a time an distance to waypoint once you are enroute to that waypoint.  Also, climbing through FL290 on the departure looks very odd..not sure what you got going on there.

Edited by downscc

Share this post


Link to post
Share on other sites

I will try the departure for myself. Whilst I do, can you provide me with:

zero fuel weight, fuel load, the flight planned route you are following, cruise altitude, cost index.

Share this post


Link to post
Share on other sites
Posted (edited)

My attempt at it. At 12 mins is the takeoff roll. Please don’t rate my crap performance. It was an experiment flight (definitely has nothing to do with my crap piloting skills lol). This was second shot at the SID. First attempt had same fmc/lnav behaviour.

At 12 minutes mark is start takeoff roll (no atc, no traffic, nadp1). As you can see, not sure if normal or not, fmc/lnav path rendering a bit off... not sure what to expect from real world fmc or what manuals say. Dan seems to know a fair bit. Anyone else care to chime in? Lnav tried somewhere in the climb, but as expected, would not track properly as op originally reports.

For all I know, this could be normal behaviour....... I don’t know.

 

 

Edited by Copper.

Share this post


Link to post
Share on other sites
On 5/20/2018 at 11:08 PM, berts said:

The first three entries on your LEGS page (   420); (NIZ-8) and (NIZ-11) are all conditional waypoints.  They are NOT in a fixed geographical position and only indicate when an event will occur.  Because these three conditional waypoints are relatively close in to the airfield it is perhaps hardly surpising you are having problems trying to reconcile your initial LNAV tracking.  Every flight is different on the day, but it can sometimes be easier to look through the Flight Director and fly the aircraft manually using VNAV and LNAV in these situations, possibly until you are cleared direct to NCNB or AMIRO; then you can engage the autopilot.  Incidentally, LFMN is not the only airfield where conditional waypoints are generated automatically when entering a SID or STAR and you will find you cannot enter conditional waypoints manually.

To get rid of the waypoints behind you all you need do is activate a direct intercept to the next waypoint.

Bertie G

Yes, you are right. I going to create a flight from LFMN to morrow when I get time for the simulator and activate a direct intercept to the next waypoint. I believe that the PMDG B744 is not a very advance simulator but still, I do not know how to "activate a direct" in this case. 

Share this post


Link to post
Share on other sites
On 5/20/2018 at 11:27 PM, downscc said:

I've seen problems with the NGX/777 and cascaded conditional waypoints in other cases.  For example, selecting the OCK transition for an EGLL ILS will lock up the PMDG FMS.  This was fixed in the 747 QOTSII.  I think the NGX should fly these three cascaded conditionals but it seems not to want to... and in other cases I've seen the ND rendering a wrong direction turn only to have the FMS/AP follow through on the correct course.  Having said all that (it should but has a bug) in RW were I piloting the departure I'd either be selecting one of the many RNAV based procedures or handflying this one until I was direct AMIRO and hand it off to otto at that time.

By the way, glad you posted this. I used to visit Nimes for a couple of days every year when stationed in Germany and taking my summer vacation in Spain. Nimes was a great place to stop overnight. Such a beautiful and historic city.  I feel in love with it and used to dream I'd retire to the South of France.. haha. Well, South of Texas will have to do and my visits to Nimes will be a simulator.

EDIT:  I've been looking at your picture and I cannot make out the LEGS page on the CDU.  Is the FMS advancing through each of the conditional waypoints as you pass them?  You should be getting a time an distance to waypoint once you are enroute to that waypoint.  Also, climbing through FL290 on the departure looks very odd..not sure what you got going on there.

Strange thing happens. When I climb out from NIZ. The T/C in ND is marked much to early all ready at FL100 can I see the marker. In this case was T/C=350 (odd or not odd).

Share this post


Link to post
Share on other sites
15 hours ago, Copper. said:

My attempt at it. At 12 mins is the takeoff roll. Please don’t rate my crap performance. It was an experiment flight (definitely has nothing to do with my crap piloting skills lol). This was second shot at the SID. First attempt had same fmc/lnav behaviour.

At 12 minutes mark is start takeoff roll (no atc, no traffic, nadp1). As you can see, not sure if normal or not, fmc/lnav path rendering a bit off... not sure what to expect from real world fmc or what manuals say. Dan seems to know a fair bit. Anyone else care to chime in? Lnav tried somewhere in the climb, but as expected, would not track properly as op originally reports.

For all I know, this could be normal behaviour....... I don’t know.

 

 

?

Share this post


Link to post
Share on other sites
16 hours ago, Oskar Speer said:

?

clearly the lnav path is not drawn properly. I inserted a few fix range rings and radial lines from which a mental picture of the early stage of the SID can be imagined and flown. fmc lnav path and charted sid do not reconcile.

 Additionally, the 2nd cond wpt in the sequence becomes active but never transitions to the 3rd cond wpt or to the nice ndb wpt, which is why when you engage a/p with lnav active, the plane turns back to the 2nd cond wpt spatially located near the 04r der.

In this example, I modify the fmc programmes sid and replace the 2nd and 3rd cond wpt's. The lnav path is drawn mostly correct. The intent was to test if it would work, and it did.

There is a problem with the sid nav data coding, or fmc, or both. I think the nav data cannot be coded properly because the fmc is not capable.

For those playing at home, the sid in concern is LFMN, BADOD6E - an ndb sid and below is the navigraph  nav data code string for the departure.

SID BADO6E RNW 04R RNW 04L TRK 043 UNTIL 420 TRK 138 UNTIL 8.0 FROM FIX NIZ TRK 158 UNTIL 11.0 FROM FIX NIZ TURN RIGHT DIRECT FIX NCNB AT OR ABOVE 6000 FIX AMIRO FIX BADOD 

 

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/22/2018 at 9:58 PM, Oskar Speer said:

Yes, you are right. I going to create a flight from LFMN to morrow when I get time for the simulator and activate a direct intercept to the next waypoint. I believe that the PMDG B744 is not a very advance simulator but still, I do not know how to "activate a direct" in this case. 

As I said earlier, the first three entries on your LEGS page (   420); (NIZ-8) and (NIZ-11) are all conditional waypoints.  They are NOT in a fixed geographical position and only indicate when an event will occur, so they are not fixed in space and neither is the LNAV track to them. The QOTS v3 is actually one of the most advanced simulator addons you can buy, especially if you have the 64bit verson of P3D (which is why most of us can't wait for the latest PMDG 744-8 to be released).  There are a few well documented issues to do with LNAV tracking which might date back to the original version, but they are relatively minor and certainly do not spoil the sense of realism when you engage the autopilot and 'fly' using LNAV and VNAV.

The main problem as I see it is in the way these videos show the aircraft being operated. For example in one takeoff LNAV and VNAV are armed and then shortly after getting airborne HDG is selected (why?); shortly followed by speed intervene (why?); and then deleting the manually tuned NAV radios (why?).  Try leaving the aircraft in LNAV and VNAV the next time and sit on your hands more.  Let the aircraft autotune the NAV radios for you on the departure too (because that is what it is meant to do) and see what happens.  Oh - and start the elapsed timer and not the stopwatch at the start of the takeoff roll (the stopwatch is used if you have an engine failure and need to time the discharge interval for the fire bottles).  The chances are you will then be able to sit back, relax a bit and even look out of the virtual cockpit for other AI traffic! 

Bertie

          

Edited by berts
addition

Share this post


Link to post
Share on other sites
Posted (edited)
6 hours ago, berts said:

The main problem as I see it is in the way these videos show the aircraft being operated. For example in one takeoff LNAV and VNAV are armed and then shortly after getting airborne HDG is selected (why?); shortly followed by speed intervene (why?); and then deleting the manually tuned NAV radios (why?).  Try leaving the aircraft in LNAV and VNAV the next time and sit on your hands more.  Let the aircraft autotune the NAV radios for you on the departure too (because that is what it is meant to do) and see what happens.  Oh - and start the elapsed timer and not the stopwatch at the start of the takeoff roll (the stopwatch is used if you have an engine failure and need to time the discharge interval for the fire bottles).  The chances are you will then be able to sit back, relax a bit and even look out of the virtual cockpit for other AI traffic!

          

The intent of videos is to test lnav badod6e depiction as mentioned; not to fly procedurally.

Even with modification to the SID, the aircraft didn’t want to track 138deg hdg to intercept NIZ 158 radial at 8nm (knew it wouldn’t), hence hdg select as a matter of experimentation, remembering the intent here is not not to fly procedurally correct, but to experiment. I would’ve thought the flight number set during the quick preflt would’ve given that away

Nav tuning - with this NDB procedure (not RNAV) depending on nav by what I’d describe as raw data, why wouldn’t you manually tune in NIZ and NC? Additionally, why wouldn’t you delete them when they’re no longer needed?

My reasoning to manually tune is to ENSURE NIZ wasn’t lost due to auto tune. With a manual entry, it’ll remain as long as I leave it tuned. I delete the entry when I no longer depend on it. Same goes for NC, except unlikely to need to nav by ndb again so I left the entry.

as for the vertical mode selections in both videos... experimenting! I don’t leave VNAV during normal procedures often. It’s good to let loose and do weird stuff during these sessions to revise behaviour. How boring a life if all you ever do is LNAV/VNAV autopilot x to command...... takes the fun right out of things keeping in mind we are in a desktop sim and I DONT FLY WITH TRAFFIC as previously stated.

back to the problem. I refute that the 2nd and 3rd cond wpt’s are not fixed.... they are! Or at least they should be. They are defined by the chart as being on the 158 radial from niz at 8nm and 11nm. Those points are fixed, laterally. After passing 420’ we’re meant to turn trk 138 to intercept that radial at that defined point.

so then why is fmc drawing the lnav path lower to those 2 DEFINED and FIXED points in space? You can see the difference in the first video.

I surmise it’s because either nav data or the fmc, or both... and am happy to keep believing it, just as happy to admit I’m wrong if that’s not the case.

 

Snippet of sid proc https://ibb.co/hFV8MT

nd lnav track compared to fix page radial line and range rings https://ibb.co/i5EUT8

as you can see, lnav niz8 and niz11 SHOULD be laterally placed where the 8nm and 11nm rings intersect with the niz 158 radial line..... they do not.

Edited by Copper.

Share this post


Link to post
Share on other sites

Brian, as Bertie suggested in his first reply, if you select a non-RNAV procedure with conditional waypoints very close to the departing rwy, like this BADOD6E departure at LFMN, the chances are you might miss some and LNAV mode wants to turn back to the active waypoint that was "missed", probably the first or second conditional one. Your first video clearly shows it. On the ND you can see flying Hdg mode to "correct" the procedure by intercepting 8dme R158 NIZ. (The official procedure states when at 400ft, RT on hdg 138 till 8dme NIZ, then intercept NIZ R158 till 11dme then RT dct NCNB) and in the process missed the second conditional wpt. The FMC Legs page shows this wpt as still active and it's confirmed on the ND by being magenta. Selecting LNAV will bring you back to this active wpt, You have to clear this by selecting the next wpt and making active in the FMC, which will then show up on the ND as magenta and not white.

I too have noticed the ND does not display the conditional wpts correctly at first, but I agree with Bertie here. It's a minor issue, just clear the missed wpts and get the next wpt active and LNAV will function correctly. I have flown this departure a couple time and noticed sometimes the first conditional wpt "shifts" as you progess and sometimes not and then gets missed by going wide past it. I just correct this by selecting the next wpt and activate it in the FMC. No problem, I am happy and even ATC (if online).

Share this post


Link to post
Share on other sites

That’s the point. Lnav path is drawn incorrectly. The result is, if the procedure is flown as charted, that wpt niz8 & niz11 are missed and are not sequenced. That is not normal. The “why” is what needs evaluating. 

Yes, the current fmc sid wpt’s are too near, and at an acute angle to rwy04 l/r der. Sound airmanship dictates the solution you and berts proffer but does nothing to evaluate the cause of the situation Oskar reported, which is what I’m trying to do as critically and objectively as I can. My aircraft handling aside I believe there is an issue with nav data or fmc, or both, and in previous posts I’ve provided the reasons why.

Others suggest this is due to to the conditional nature of the wpt’s. Ok, let’s explore that. My questions is - why is niz8 and niz11 conditional, when they are charted as defined points in space? If you can answer that critically, without reference to my aircraft handling which shouldn’t impact on niz8 and niz11 placement (due to them being defined points in space) I’d be appreciative.

note that I’m trying to do the evaluating because *IF* there is something amiss, then we would all benefit if it gets fixed *IF* there is something wrong which I believe there is. The root cause of this problem could impact on other procedures.

 

 

Share this post


Link to post
Share on other sites
Posted (edited)

Having tried and confirmed in another product, and having reviewed a video of another independent product I believe it is the nav data as lateral path depiction appears the same confirmed on 2 of the 3 separate (different companies) products. The 3rd I can't confidently say but looks like it.

NOTHING TO DO WITH FMC

 Here endeth the lesson :) Off to navigraph I go.

Edited by Copper.

Share this post


Link to post
Share on other sites
Posted (edited)

Brian, I will try and answer your question. It seems the AIRAC data is the issue. If you look at the Navigraph data you quoted, the section of concern in bold:

SID BADO6E RNW 04R RNW 04L TRK 043 UNTIL 420 TRK 138 UNTIL 8.0 FROM FIX NIZ TRK 158 UNTIL 11.0 FROM FIX NIZ TURN RIGHT DIRECT FIX NCNB AT OR ABOVE 6000 FIX AMIRO FIX BADOD 

NIZ8, as you call it, is not chartered as a defined point in space or a fix, but "arbitrary", hence conditional on a hdg of 138 from the previous condition till 8dme NIZ, not fixed. NIZ11 is fixed (named MN044 on the RNAV SID BADOD6A) as it is 11dme on NIZ radial 158. According to the highlighted section above an incorrect wpt will be calculated on 158 deg from the previous "arbitrary" wpt instead of on NIZ radial 158. This is clearly what we see on the ND with the third wpt incorrectly positioned.

I tested this today with A/P and LNAV selected just passing 400ft. The aircraft could not reach the second wpt which was "held fixed" by the incorrect third fixed wpt. On my second attempt I selected BADOD6A with the third wpt now a fix MN044, the 2nd wpt "moves" on the niz8 arc and could be reached with the aircraft following track through MN044 without any issue.

I hope this explains it good enough.

 

(you just beat me to it, yes Navigraph will have to fix it)

 

Edited by Johannvr

Share this post


Link to post
Share on other sites

Johann. That is a perfect explanation. Thank you for looking at this problem critically and objectively with me! You’ve expressed the anomaly with the nav data better than I ever could, particularly your comparison between the conditional (NIZ-11) and fixed (MN044) waypoints and their interaction with the preceding waypoints and the impact on visual representation of the lateral path.

The problem is with Navigraph. The question is whether BADOD6E and other procedures like it are impacted in the same way, and if the nav data can be written better to reconcile with charted requirements.

Further discussion is not required on PMDG forum as it does not relate to them in any way shape or form and I do not wish to further implicate them more than I might already have.

🙂 thank you all for playing

 

Share this post


Link to post
Share on other sites
23 hours ago, Johannvr said:

TRK 158 UNTIL 11.0 FROM FIX NIZ

 

10 hours ago, Copper. said:

The problem is with Navigraph.

I've done a lot of terminal procedure encoding, and while not the expert that Terry Yingling was I do have a basic knowlege.  The procedure encoding is using the correct syntax and one has to stare at the chart awhile to see the problem.  When posting to the Navigraph bug report forum, recommend to them that they use the NIZr158 as published for then the procedure becomes:

SID BADO6E RNW 04R RNW 04L TRK 043 UNTIL 420 TRK 138 INTERCEPT RADIAL 158 FROM FIX NIZ TRACK 158 UNTIL 11.0 FROM FIX NIZ TURN RIGHT DIRECT FIX NCNB AT OR ABOVE 6000 FIX AMIRO FIX BADOD 

The tricky part about this procedure is that it is poorly laid out and relies on the minimum climb gradient to reach 420 and the turn to 138 such that the NIZr158 is reached before NIZd11, and ideally about NIZd8.  However, flying in the cockpit in IMC conditions there is no practical way to ensure you intercept radial 158 exactly at NIZd8.  A better way for the authority to design this would be to say something like:  TRK 043 UNTIL 420 TURN RIGHT DIRECT FIX NIZ158/008 TRACK 158 UNTIL 11 FROM FIX NIZ.....; but that's not how it's drawn.

  • Like 1

Share this post


Link to post
Share on other sites

That is a good suggestion to Navigraph, Dan. It seems the idea of rwy04L/R procedures are to turn to hdg138 when at 420ft and then till NIZ 8d to avoid the buildup hill to the east. Only then continue to intercept NIZ R158 or the fixes applicable to the different SID's

LFMN is a NICE airport to do those non-RNAV rwy04L/R departing procedures and the approaches to rwy22L/R

 

Share this post


Link to post
Share on other sites

Maybe we can all agree then that the PMDG B744 FMC isn't the problem here after all, because for all practical purposes it models Conditional Waypoints very well, doesn't it? 

As I said earlier, as far as the FMC is concerned these Conditional Waypoints are NOT in a fixed geographical position and only indicate when an event will occur.  Therefore the conditions for crossing each one will inevitably be met in a different geographical position on every departure and will depend on all sorts of variables, including the effects of wind, aircraft weight etc.pilot handling, speed and bank angle in the turn etc., etc. 

In the case of the "TRK 158 UNTIL 11.0 FROM FIX NIZ" where you end up geographically will be somewhere on the 11.0 DME Arc from NIZ and that will depend on the position where you started tracking 158 degrees.

The Aeronautical charts can normally only be drawn to depict one fixed position for each Conditional Waypoint, so they have to be interpreted by the pilot in a practical sense and flown as accurately as possible.  If the aircraft isn't capable of complying with a particualr SID or STAR for performance reasons then there will normally be a note to that effect in the aircraft's performance manual.

Bertie G 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now