PilotBrent
Well Known Member
Purpose of this post is to point out a serious problem with Skyview/autopilot system when erroneous ADS-B input is entered into Skyview. Just posted this on the Dynon support forum but wanted to alert VAF users.
Earlier today I was flying near Carroll County airport MD (KDMW) and pressed the Baro button to have the nearest Baro setting entered into Skyview via the Dynon 470 unit. For whatever reason, as you can see the local Baro setting was clearly incorrect, but Skyview accepted the odd value and immediately changed/displayed my altitude very incorrectly as a result. As I was flying via autopilot, the aircraft immediately began to dive which was obviously not my intent. Screen shots are from a second attempt to load correct local Baro settings but Skyview kept defaulting to the incorrect inputs from KDMW.
While I don't understand why the electronically communicated ADS-B Baro setting from this airport was so incorrect, it would be ideal if Skyview had limits or filters to avoid such incorrect values from automatically being accepted into the system.
Earlier today I was flying near Carroll County airport MD (KDMW) and pressed the Baro button to have the nearest Baro setting entered into Skyview via the Dynon 470 unit. For whatever reason, as you can see the local Baro setting was clearly incorrect, but Skyview accepted the odd value and immediately changed/displayed my altitude very incorrectly as a result. As I was flying via autopilot, the aircraft immediately began to dive which was obviously not my intent. Screen shots are from a second attempt to load correct local Baro settings but Skyview kept defaulting to the incorrect inputs from KDMW.
While I don't understand why the electronically communicated ADS-B Baro setting from this airport was so incorrect, it would be ideal if Skyview had limits or filters to avoid such incorrect values from automatically being accepted into the system.
Last edited: