IFD 5 Series & IFD 4 Series Touch Screen GPS/NAV/COM

Print Page | Close Window

Origin not in Database

Printed From: Avidyne
Category: Avidyne General
Forum Name: IFD 5 Series & IFD 4 Series Touch Screen GPS/NAV/COM
Forum Description: Topics on Avidyne's IFD 5 Series and IFD 4 Series Touch Screen GPS/NAV/COM
URL: http://forums.avidyne.com/forum_posts.asp?TID=1096
Printed Date: 29 Apr 2024 at 11:53am
Software Version: Web Wiz Forums 12.01 - http://www.webwizforums.com

Topic: Origin not in Database

Posted By: PA20Pacer
Subject: Origin not in Database
Date Posted: 01 Jul 2016 at 8:47am

Hello All-

I departed yesterday from an airstrip not in the Jeppesen database. I had created a user waypoint for the airstrip, but my IFD540 would not let me enter that waypoint as the origin by editing the nearby origin airport that the 540 chose.

Does anyone have any thoughts on the proper way to specify an origin not in the Jeppesen database?

Regards,

Bob

-------------
Bob Siegfried, II
Brookeridge Airpark (LL22)
Downers Grove, IL

Replies:

Posted By: Jack Seubert
Date Posted: 01 Jul 2016 at 10:13am

Bob,

Take a look at page 2-39 in the PG. It works great.

Jack

-------------
Jack Seubert

Posted By: 1964-m20e
Date Posted: 01 Jul 2016 at 11:43am

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.

Posted By: PA20Pacer
Date Posted: 01 Jul 2016 at 1:20pm

Hi Jack-

Thanks for the suggestion. When I set up the user waypoint, I did use the appropriate naming convention as indicated on page 2-39. The waypoint displays on the map as shown in the lower figure on page 2-39, and I do not get terrain warnings when landing. However, when I was on the ground at that location, my user waypoint did not come up as the origin, and I was unable to edit the origin field to the name of my user waypoint.

It is not a big deal, as one can always just accept the populated origin and then enter direct to the first waypoint on the route, but it seems that there should be a better way.

Regards,

Bob

-------------
Bob Siegfried, II
Brookeridge Airpark (LL22)
Downers Grove, IL

Posted By: oskrypuch
Date Posted: 01 Jul 2016 at 2:53pm

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

* Orest

Posted By: PA20Pacer
Date Posted: 01 Jul 2016 at 4:31pm

Thanks to John and Orest for pointing out this limitation. It is good to know that I am not missing something simple.

Regards,

Bob

-------------
Bob Siegfried, II
Brookeridge Airpark (LL22)
Downers Grove, IL

Posted By: DH82FLYER
Date Posted: 01 Jul 2016 at 10:58pm

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

Posted By: PA20Pacer
Date Posted: 02 Jul 2016 at 12:06am

Hi Thomas-

I can certainly live with that procedure. Thanks for pointing out Steve's previous response.

Regards,

Bob

-------------
Bob Siegfried, II
Brookeridge Airpark (LL22)
Downers Grove, IL

Posted By: 1964-m20e
Date Posted: 17 Oct 2016 at 3:10pm

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.