I’m using the default a320 neo.
The MCDU constantly says that an airway is not in the database, but when I add the next waypoint, it adds the airway between them. Very frustrating as some airways have lots of waypoints and it’s cumbersome to add them all. Happens to 99% of airways in Australia.
Any idea how to fix this?
1 Like
We’ve moved your topic into the #gd-commsupport category.
The Bug Reporting category is for posting suspected or confirmed bugs that other users are able to reproduce. Using the template is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the Community Support category. If the community can replicate your issue, first search the Bug Reporting category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
Can you add the VORs and have it fill in the airways along with its accompanying points?
Also, does this happen everywhere or just in Australia?
I can concur this happens quite a lot with default aircraft or any aircraft using default fmc logic like captain sim planes. Wasn’t sure if this was something I was doing wrong at the time (usually it’s me doing something wrong so I don’t question it).
Also I do most of my flying in the US and had this issue. Next time I come across this I’ll add more specifics with the actual airway and waypoints I’m having issue with.
2 Likes
Had time to look more into this today as im curious if im just doing something wrong or this is a bug. I was able to duplicate this on my end by using a real world flight pulled from flightaware for a flight from KEWR-KSFO for UAL 202. (Keep in mind I am in no way an expert on the A320 or MCDU)
Routing: NEWEL J60 DANNR J60 DJB KC69Q CABIJ KG75I NELIC KP78E LESNR KD81W KD81U IDECA KU75O PARZZ Q138 FIMUV LEGGS BDEGA3
To duplicate, I emptied my community folder started a flight at KEWR at the gate cold and dark using default a320neo. No flight plan pre-loaded. powered up the plane and started programing the MCDU. I did the following steps:
-
On the INIT page entered FROM/TO, FLT#, CI, and ALT.
-
Moved onto the F-PLN page to enter departure and routing. I was able to add a departure from 22L and first direct to NEWEL. From the airways page added J60 to DANNR.
But could not add another airway J60 to DJB. Also could not add NEWEL-J60-DJB.
However, when I went back and did DANNR direct/to DJB it auto inserted the airway between the two point.
Hope this helps in determining if this is a bug. Let me know if I can provide any more detail.
Since the most recent flight sim update, the A320 MCDU does not seem to recognize any airways at all. It will only recognize waypoints and all have to be direct, no airways seem to be on the system. Before the update this was not a problem at all. Has anyone else been experiencing this?
1 Like
Are you using the sim nav data, or using Navigraph?
I’m using Simbrief to generate flight plans then entering all info into MCDU manually.
If you don’t have a Navigraph subscription and install their nav data in the sim, the nav data in the sim will probably not be the same as that used by Simbrief.
That could explain why you are having these issues.
I will look into this more but I never had this issue before the last update.
The 747-8 works fine and recognizes all airways.
I am having the same issue witht he stock A320neo and with the A319 from LatinVFR no airway work and it says “not in database”. However the stock 787,747 and FBW A320 all work
Copy/paste flight plan into topic.
The Asobo stock A320neo has one type of FMC, the original one from MSFS. The LVFR family uses an enhanced version of the stock A320neo. The FBW A320 uses different coding by 3rd party developers for their FMC. Although it looks the same, it works differently. The 787 and 747 FMC were created by Working Title and integrated into MSFS.
When MSFS was first developed years ago, flight plans were supposed to be created using the World Map before the flight. To keep things simple for most users, airways were not included in the World Map. They still are not available in the World Map. Since the A320neo and the World Map have no import capability from SimBrief, Navigraph, or other apps, there was no need to include airways in the A320neo or in the World Map. This isn’t a bug but rather lacking a feature.
The World Map has been partially enhanced to recognize airways in any imported flight plans by “unrolling” them into there corresponding waypoints. The same thing happens with the 787 and 747 FMC. The FMC has two keys, RTE and LEGS. The only place to enter airways is on the RTE menu. The FMC takes the airway and “unrolls” them into their corresponding waypoints on the LEGS menu.
I hope this explains why for some airliners, “NOT IN DATABASE” is displayed when trying to enter airways. The only “workaround” to manually insert an airway is to input the corresponding waypoints for that particular airway segment.
2 Likes
Okay, that makes a lot of sense. Thank you!
1 Like
did you were able to find a solution to this? because my Ini A330 does not show up any SID or STARS and I installed with the Navigraph hub.