Create user wpt using rad/dist

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I am trying to create a user waypoint using the Rad/Dist format and the desired navaid is placed at the wrong location.
The IDU DME is at the end of the runway at LSMD. I want to create a user waypoint at 3.1nm on the 105 degree radial from it.

If I enter the DME itself in an FPL, the IFD places it correctly at LSMD. See the first screenshot below.

When I try to create a user waypoint at 3.1nm on radial 105 from the DME, the DME is placed approx 30nm away, to the west. See the second screenshot. This results in the waypoint being at the wrong location, as shown in the last screenshot.

Edited by chflyer - 16 Apr 2025 at 5:50am

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
chflyer Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 24 Jan 2013 Location: LSZK Status: Offline Points: 1054	Post Options Post Reply Quote chflyer Report Post Thanks(0) Quote Reply Topic: Create user wpt using rad/dist Posted: 16 Apr 2025 at 5:47am
	I am trying to create a user waypoint using the Rad/Dist format and the desired navaid is placed at the wrong location. The IDU DME is at the end of the runway at LSMD. I want to create a user waypoint at 3.1nm on the 105 degree radial from it. If I enter the DME itself in an FPL, the IFD places it correctly at LSMD. See the first screenshot below. When I try to create a user waypoint at 3.1nm on radial 105 from the DME, the DME is placed approx 30nm away, to the west. See the second screenshot. This results in the waypoint being at the wrong location, as shown in the last screenshot. Edited by chflyer - 16 Apr 2025 at 5:50am
	Vince

dmtidler Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 12 Feb 2016 Location: USA Status: Offline Points: 630	Post Options Post Reply Quote dmtidler Report Post Thanks(0) Quote Reply Posted: 16 Apr 2025 at 7:30am
	I believe this is the same bug I reported here quite a while ago. Radial distance user waypoints built off of DME only stations always place the user waypoint directly north of the DME station at the correct distance regardless of the radial selected. That appears to be what it looks like occurred in your screenshot three. At that time; the answer was that this was a verified bug and is supposed to be corrected in an upcoming AviOS release; possibly the next one. Edited by dmtidler - 16 Apr 2025 at 8:28am

chflyer Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 24 Jan 2013 Location: LSZK Status: Offline Points: 1054	Post Options Post Reply Quote chflyer Report Post Thanks(0) Quote Reply Posted: 16 Apr 2025 at 8:05am
	Thanks. I missed that bug report. I agree that this looks exactly like what you describe.< ="chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/inpage.js" id="leather-provider"> It's been over two years since an AviOS update of any kind, so one can hope that this is still on the burner. Avidyne no longer had their own stand at AERO in Friederichshafen last week and were integrated into the Adams Aviation stand instead. Saving money is always a good idea, as long as it doesn't reflect bigger problems.
	Vince

AviSteve Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 12 Feb 2018 Location: Melbourne, FL Status: Offline Points: 2319	Post Options Post Reply Quote AviSteve Report Post Thanks(0) Quote Reply Posted: 16 Apr 2025 at 12:03pm
	The waypoint will be created correctly if the navaid has an associated mag var in the nav database. But if it doesn't, you'll get the behavior you observed. That has indeed been fixed in 10.3.2.2.
	Steve Lindsley Avidyne Engineering

dmtidler Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 12 Feb 2016 Location: USA Status: Offline Points: 630	Post Options Post Reply Quote dmtidler Report Post Thanks(0) Quote Reply Posted: 16 Apr 2025 at 12:23pm
	Steve...thanks for the update!