RJ100 does not following the route (waypoints) properly....
-
I have had problems following the waypoints since the release of the RJ100 Pro series.
On autopilot (LNAV) it simply does not follow its route correctly.
It seems that the waypoints of Navigraph in the AIRAC via the hub installed for the RJ100 Pro, differ from the map in the Navigraph Charts...
I use the Navigraph maps on my PC with a 2nd monitor.
With other aircraft I have no problems...I have tried various start-up procedures such as "Ready for Take-Off"
But the difference continues to irritate me....See the attached photo?
I am inbound VANAS in the EICA but on the left of the photo in the Navigraph map I fly completely differently.....
This flight was started with "Ready for Take-Off".
-
Would you be able to share the route for this flight so we can try and replicate this, please?
Looking at the screenshot of the cockpit, the aircraft is flying the route that is entered into the FMS (as displayed on the ND) so that all looks correct. A discrepancy like this could be caused if a different SID has been entered into the FMS compared to the SID in the flight plan, so it may be worth double-checking that the SID that is entered into the FMS is the same as the one listed on the flight plan.
Mark - Just Flight
-
Hi Mark,
This was the route i was flying: LSGG/22 MEDA1A MEDAM DCT NITAM M730 TESTO TEST1N LIMJ/28
At the moment the foto was taken i was directing towards VARNAS in the FMC...
I brought VARNAS to the first line in the FMC.
But the plane was not going in that direction.....Hopefully I have informed you sufficiently
Hans
-
Hi Mark,
I experience the same issue with a flight I just tried out from London City Airport to Dresden. It seems, the waypoints in the FMC are totally off from the waypoints in MSFS.
Here is the flight plan:
EGLC/27 ODUKU1A ODUKU M84 TOVGU M604 GASBA M197 REDFA L620 SUVOX Z718 OSN L980 SAS L986 BOLBO M748 OSKAN OSKAN4A EDDC/22The flight is prepared and imported via Simbrief Dispatch in MSFS. After loading into the aircraft, the flight plan is imported into the FMC via the LOAD ATC RTE function.
You can already see the discrepancies of waypoints in th FMC's plan view for the first couple of waypoints.This is how the flight plan is displayed (and flown):
This is how the SID looks like:
The waypoint LCN02 is displayed 20 nm west of EGLC and then there are some weird twists and turns further along the route...
I have the current navdata installed for MSFS and RJ via Navigraph Hub.
Removing the current navdata for MSFS, the RJ and 146 via Navigraph Hub doesn't seem to make any difference. But then again I don't know if Navigraph Hub actually removes them properly...
By the way, I tested the same flight plan with the BAe 146 and it's UNS-1 and the same issue with the totally off waypoints seems to exist, but sadly the UNS-1 has no map.
I have some screenshots showing the issue but can't upload them right now (unspecified error message)...Other aircraft (for example the FlyByWire A320) display and fly the same route without issue.
-
@telephono Thank you for the detailed explanation. We have been able to replicate this by creating a flight plan in the MSFS main menu and then using the LOAD ATC RTE function to import that flight plan into the FMS.
I suspect the LOAD ATC RTE is a function that should not be available in this build, as the FMS does not currently support the .PLN flight plan files that are generated by the MSFS main menu. It is something we have investigated in the past so it's possible that this feature either wasn't disabled or was inadvertently reenabled at some point. We have logged this with the GNLU development team to investigate further.
In the meantime, the currently supported methods of flight plan entry into the GNLU-910A FMS are:
- Manually entry using the RTE and DEP/ARR pages.
- CO ROUTE integration: Requires an .RTE flight plan file to be saved locally in the correct file directory on your PC
- STORED FLIGHT PLANS integration: Requires an .RTE flight plan file to be saved locally in the correct file directory on your PC
For further info, the manual flight plan entry is covered on pages 23-29 of the GNLU-910A FMS Operations Manual, and the latter two import methods are covered on pages 38-40.
Hope that helps and apologies for the confusion.
Mark - Just Flight
-
Perfect!
Entering the flight plan by hand indeed resolves the issue.
Let's hope @Milonas did use the same shortcut and used LOAD ATC RTE to input the flight plan into the FMC...As I also used LOAD ATC RTE in the BAe 146 UNS-1, I assume the issue is the same and will input my future flight plans by hand, too.
-
Indeed! The route was retrieved in the FMC with the function "Load ATC Route".....
From now on I will enter a route manually.....
I will point my Simbrief Downloader to the correct folder and let the route appear there....Thanks everyone for the quick response!
Hans
-
Any route inputted into the RTE page can be saved locally on your PC by selecting the SAVE FPL option on the INIT/REF INDEX page. Once saved, that flight plan can be recalled on future flights either by using the CO ROUTE field via the FLIGHT PLANS option on the INIT/REF INDEX page.
Mark - Just Flight
