I am not sure how this approach would integrate with the common use of navigating between known/mapped IFR navigation waypoints:<a href="https://www.google.com/search?client=firefox-b-d&q=IFR+navigation+waypoints" rel="nofollow">https://www.google.com/search?client=firefox-b-d&q=IFR+navig...<a href="https://skybrary.aero/articles/waypoint" rel="nofollow">https://skybrary.aero/articles/waypoint<a href="https://www.flyingmag.com/how-ifr-fixes-get-their-names/" rel="nofollow">https://www.flyingmag.com/how-ifr-fixes-get-their-names/
walrus01 · · focus · HN ↗
<a href="https://www.google.com/search?client=firefox-b-d&q=IFR+navigation+waypoints" rel="nofollow">https://www.google.com/search?client=firefox-b-d&q=IFR+navig...
<a href="https://skybrary.aero/articles/waypoint" rel="nofollow">https://skybrary.aero/articles/waypoint
<a href="https://www.flyingmag.com/how-ifr-fixes-get-their-names/" rel="nofollow">https://www.flyingmag.com/how-ifr-fixes-get-their-names/