Waypoint as Origin on Flight Plan

The nav database does contain some private airports.  Generally, if one does not exist, I can get it added within a cycle or two.  I just checked the latest database and it does not contain FL59.  I'll send a request to Jeppesen and maybe it will even be in there before you get your airplane back.  Cross your fingers.

DH82FLYER wrote: However you can add a User Waypoint-Airport as an ‘origin’ by nominating it as a “Waypoint”, rather than an “Origin” from the dropdown menu when constructing a Flight Plan...see 540 Pilot Guide pg 2-4.

Yes, in the airplane, but not in the sim.  As Steve points out, the sim uses Origin to re-position the aircraft geographically from the default KMLB to the users desired location, hence the need to use KRSW to at least get close until FL59 gets added to the database.

There was a problem adding the departure airport as the first waypoint on a flight plan. On few occasions, after takeoff and activating the autopilot, it kept trying to go back  to the departure airport instead of navigating to the next waypoint. That was fixed by removing the departure airport from the saved flight plan.

Yes, that happened with the saved flight plans, having the departure airport as first waypoint.

Ibraham wrote: There was a problem adding the departure airport as the first waypoint on a flight plan. On few occasions, after takeoff and activating the autopilot, it kept trying to go back  to the departure airport instead of navigating to the next waypoint. That was fixed by removing the departure airport from the saved flight plan.

Ibraham wrote: I had created some flight plans/routes with our home airport as the origin/first waypoint. after takeoff and heading east of the airport towards the 2nd waypoint on the saved flight plan, activating the autopilot caused the airplane to start turning back towards the departure airport. That only happened with the saved flight plans with the departure airport as the first waypoint. When I realized the cause of that behavior, I deleted the departure airport from the saved flight plans and it corrected the issue.

For your home airport in the saved flight plan, which was it, origin or first waypoint?  I think the distinction is important.  I fly out of areas that aren't in the database and believe I've seen this behavior.  I have to set the departure as the first waypoint rather than the origin.  I don't think it unreasonable for the IFD to consider that first waypoint (no origin) as a "TO" waypoint.  We just need to understand how the IFD540 architecture is structured.  It is then simple to just activate the first leg before departure (no need to delete the departure).  Not a bad idea anyway to check before departure where the GPS is first going to send us.  This is all supposition on my part as I've not tested it, but will next chance I get.  Perhaps Steve can clarify if this is the behavior Avidyne intended and expects.

Edited by Bob H - 29 Jan 2019 at 3:36pm

AviSteve wrote: Being "the first waypoint in the flight plan" is different from being "the origin".  An origin is a specific kind of leg.  You can insert it manually by choosing "Origin" in a dropdown.  Only one is allowed per flight plan, so if there's one already there, you won't see that choice in a dropdown.  If you choose "Waypoint" from the dropdown, the thing that gets entered is just that - a waypoint - not an Origin.  The origin can never be active.  If you try to go direct-to the origin, the FMS will create a leg with the same identifier and then make that the active leg. An origin is more of a placeholder with the main purposes being to provide an anchor for the first leg and to provide a means to enter a departure (as applicable).

Thanks Steve.  So, based on your response, if the departure point is entered as the first waypoint, not origin, it will be treated as a "TO" waypoint.  Then engaging the autopilot will turn the aircraft back toward the departure point.  This makes perfect sense to me.

Circling back to the start of this thread...  I just got confirmation that FL59 will be added to cycle 1903 nav data.

Hello Steve: I have the same situation with my home airport: GA18 not in Avidyne database making it impossible to properly originate a flight plan from home. 

Steve, I'm finding that many of the airports on the sectional (89NY, NC99 are two that I use) etc. are not in the database, and haven't been since the beginning of testing.  They ARE in foreflight, so the data is available.  It may be a difference between Jeppesen and the FAA database, but the data is available.

oskrypuch wrote: Zeddy wrote: Hi Steve, Please add the following private airports to the data base:  OH66 OA12. Thanks. You'll need to contact Jepp. They will be happy to do so. * Orest

Avidyne could solve this issue for home bases (but not enroute airfields) by allowing a user waypoint to be definable as an airfield and allowed to be selected as Origin (i.e. first waypoint in a FPL).

Edited by chflyer - 16 Apr 2021 at 10:52am