The email below was received in August last year from Jeppesen as a result of my enquiry, related to the App not accepting routes. I'm disappointed they haven't fixed it yet.
Good afternoon Claret,
*
Your service request has been escalated to my attention. I understand that you’ve been having some problems with various routes not being accepted in the Mobile FliteDeck application. It appears that most of the routes in your example include a VOR entry/exit point that shares the same ID as a nearby NDB (e.g. GV, CS, AS, AYE). This is causing the problem, because the application will sometimes default to the NDB if it is nearer to the direct route. However, since the NDB is not the entry/exit point to the airway, the route fails. This is a known issue that our Development group is aware of and are working to address in a future update to the application. I apologize for any inconvenience this may be causing.
*
Best Regards,
*
Aaron Rocky Smith
Tier 2 Technical Support Specialist - Nav
Technical Support Services
______________________________________
Jeppesen
A Boeing Company
[email protected]
55 Inverness Drive East | Englewood, CO 80112 USA
Jeppesen – Transforming the Way the World Moves
*