v1.025 FMS Navigation Database Issue
Thanks for the update of Q400.
After update, it's nice to be able to select transitions from the CDU, but it doesn't seem to have fixed the wrong route.
It may be a Navigraph issue, but regarding RJOO TIGER2 Departure, there seems to be a problem with the route to TIGER when flying from Runway 32L/R.
Could you please investigate this as I am attaching the documentation regarding CDU and Chart?
Runway 32L/R Procudure:
Climb RWY HDG to 500FT or above, turn left within 4NM from RWY end/ITE 2.1DME, via ITE R201 until crossing YOE R301 turn right to intercept and proceed via YOE R291 to TIGER.
Cross TIGER at or above 6000FT.
RJOO Runway 32L/R to TIGER route.
TIGER to SOUJA route.
FMS Route Selection
Please refer to images, but TIGER has been removed and changed to go almost directly to SUMAR.
Is this a bug or a Navigraph issue?
Is it normal?
I'd be happy to get more details.
Comments
Thanks for the report of this issue. We will do some additional testing on this issue.
Is this issue fixable without a Q400 Update?
Who is coding the program that converts Navigraph data for the Q400?
I've checked the access data(nd.mdb), and it seems certain that it's the Navigation Database issue.
I'd love to know what your plans are, even though there's been a bug about navigation for several years that hasn't been fixed.
@kroswynd
Is there any plan of the fix?
Q400 has been in a state of broken FMS for several years now. Since ver 1.025, the VNAV problem and the bug where SID Transition cannot be selected have been fixed, but the details of SID are still wrong.
If this is a problem on Navigraph's side, I would like your company to discuss with Navigraph about a fix.
@Struggle_Crow
Any fixes moving forward will be driven by the new platform implementation if feasible.
If I recall there will have to be some correction from the navigraph side of things, but it is still a part of our to do list.
Cheers