Origin not in Database

Hello All-

I have the same problem.  I let Avidyne know about it and they are supposedly looking into this.  I am fortunate I have a Class B airport 3 miles from my home base so I default to that for my origin for now.

That is a current restriction, no other way to do that for user defined airports.

* Orest

Hi All,
This issue has been discussed before and the following is part of Steve Jacobson's reply...

"This is per design. The only advantage you get from entering an origin is that you can enter a departure. You can also enter a runway, but that's only significant if there's a departure. So if you create a user waypoint representing your airfield and then use that as the first leg in your flight plan, the effect is nearly the same. Yes, activating that flight plan will cause a direct to that fix, but all you have to do is activate the second leg (or go direct-to it) and you're all set."

In other words, when building a route from a User Waypoint, you need to nominate it as a "Waypoint" rather than an "Origin" from the dropdown list.

Thomas

Edited by DH82FLYER - 02 Jul 2016 at 2:31am

Well the good news is the latest database update my home airport LS40 is now in the database and can be selected as the origin for the flight plan.  Now I have to edit my flight plants to remove the surrogate origin waypoint.