Autopilot and Userwaypoints

Turbo-Dynamic

I love flying!
Joined
May 5, 2014
Messages
4
Hi Dynonteam,

I created a lot of user waypoints in my Skyview. I allways include an altitude information. Is it possible to navigate via autopilot and vnav to this user waypoints?
Example; Current altitude is 5000ft...user waypoint has altitude information of 3000ft. The goal should be to fly inbound this user waypoint including vnav with the autopilot - that means the altitude over the waypoint should be like it is saved in the user waypoint at 3000ft.

Is this possible?
 

preid

Member
Joined
Jan 22, 2010
Messages
754
Location
SoCal
At his point, when using the Skyview and doing a RNAV approach I manually turn the ALT dial the the desired altitude at each point. I could see a real benefit to your question.
 
W

William_Ince

Guest
Just discussed this with Dynon sales a few days ago. Rep was an active pilot.
Rep indicated that SkyView VNAV does not fly a path automatically, using published or user inserted, GPS waypoints with altitude constraints, like Airbus and Boeing systems can. In other words, SkyView will not honor latitude constraints within the flight plan, including GPS RNAV approaches.  Pilots must initiated all decents (and climbs) manually.

If properly equipped though, it will "capture" and fly an ILS glideslope.

SkyView is not quite there yet, when it comes to real vertical navigation.
That capability would be another leap.  It sure would be fun though.
 

dynonsupport

Dynon Technical Support
Staff member
Joined
Mar 23, 2005
Messages
13,226
SkyView WILL follow a GP (Glidepath) from a precision GPS approach, just like an ILS.

However, General Aviation GPS units like the Garmin 430 or 650 don't output altitude constraints for RNAV approaches, so there's nothing for us to follow. It's not really SkyView that is lacking, it's the GPS units.

To answer the base question, we do not follow altitude constraints in user created waypoints. Flight planning with altitude constraints is a large step (probably why GA IFR navigators don't do it either!), given you need to define before, after, at, vertical speeds, etc for each point.

Someday, maybe.
 
Top