EGLLRJBB_PDF_1775183761.3e8e4656.pdf (551.6 KB)
I’m contacting you in an official capacity from TFDi / MD-11 support. I provide module support and have been fielding tickets related to invalid flight plan import issues into our product.
I’ve put together a solution article that has deflected - https://support.tfdidesign.com/support/solutions/articles/62000237255-md-11-navigation-data-troubleshooting
We occasionally (couple times per month) get reports of customers who receive an error when attempting to use our automatic flight plan import feature via our EFB. While this is occasionally a by-product of a mismatch between SimBrief and navigational databases, one that has repeatedly appeared is a routing between the EU and Japan. Specifically going west to east (EU → JP) on the north side of the ZLHW airspace.
Here is the scenario:
EGLL → RJBB (.pdf from Simbrief is attached) and most specifically this sector GOVSA W66 DKO
GOVSA is at the intersection of W188, W66, and W271. The W22 airway, according to Navigraph charts is a one-way airway (Westbound) that Simbrief is selecting as a preferred route to DKO. When the routing should be LIKMI W270 DKO or GOVSA W271 BOTKI W270 DKO following an eastbound jetway. For whatever the reason that GOVSA W66 DKO appears to be a critical routing, most of my EU to JP routes that I’ve built via SimBrief use it.
A quick test shows that the iniBuilds A350 & PMDG 777 import the route successfully (GOVSA W66 DKO).
What I don’t know is if Vatsim/IVAO controllers would give you a re-routing for this.
Thoughts here? Is there some background logic in SimBrief that verifies the appropriate direction of flight for an airway? Or does it just verify that an airway exists?
Our module is configured to respect the navigation data routing and I think we can both agree that having type all that routing into the EFB isn’t going to be an ideal solution for 95% of our customers.
Thanks,
Jason Fearing
TFDi Technical Support