Search the Community

There is a change coming in the next version of the GTN software that is a potential gotcha that could get you violated if you aren't aware. Our GTN650 is several versions behind. Since the next version that comes out (now saying it will be February) allows us to build a holding pattern at any fix, I think I can convince my partners to pay to have the update installed. With that in mind I've been playing with the v6.0 simulator and reading the pilot guide and have discovered a change that could get me violated if I'm not careful. It has been my practice, that if I know what runway is in use, I'll load the approach well in advance but not activate it. I do that because I prefer to do as much in advance when there is nothing going on rather than wait until the last minute when things are getting busy. The new version loads the approach sequence differently. Here is an example of the change. Say I'm flying from my home field of Auburn, WA (S50) to Port Angeles, WA (KCLM) and I file and get cleared for: S50 SEA V4 JAWBN KCLM Enroute I load the RNAV (GPS) RWY 26 approach at KCLM with the JAWBN transition. With the old software the route would look like this: S50 SEA LOFAL DIGGN JAWBN KCLM (approach) JAWBN COBUX FAMUV SEBTY RWY26 then the missed approach. No problem. If they don't clear me for the approach before I get to JAWBN, the GTN wants to take me to KCLM which is my clearance. With v6.x of the software, when I load the approach, the route looks like this: S50 SEA LOFAL DIGGN (approach) JAWBN COBUX FAMUV SEBTY RW26 then the missed approach. If I don't get cleared for the approach before JAWBN, the GTN tries to take me on it anyway. While in this particular case it is not much of a deviation from the flight direct to KCLM, in other cases there could be a significant difference. The potential exists for a violation. What can I do to prevent that? 1. I can wait until I'm cleared for the approach before I load it. In which case I might as well activate it at the same time. 2. Just keep good SA and if I get to JAWBN without a clearance, ask for it or use the D--> key to go direct to KCLM 3. Manually insert the airport in front of the approach. This creates another problem. If I do that, the route looks like this: S50 LOFAL DIGGN KCLM (approach) JAWBN COBUX FAMUV SEBTY RW26 then the missed approach. But my clearance is from JAWBN to KCLM not DIGGN to KCLM. If I try to do this: S50 LOFAL DIGGN JAWBN (approach) JAWBN COBUX FAMUV SEBTY RW26.... It says invalid entry. It will not let me load JAWBN because it already sees JAWBN as part of the approach. However, I can trick it. If I first load the airport so it goes ...DIGGN KCLM (approach) JAWBN... It will then let me load JAWBN between DIGGN and KCLM to get: ... DIGGN JAWBN KCLM (approach) JAWBN... Another change to be aware of concerning loading the approach early. I'm also in the habit of using the Flight Plan to get airport info. For example, if I want to look up the ASOS or Tower freq I will push Home, Flightplan, scroll down to and select the airport, then WPT Info, then Freqs. With the new version, when you load the approach, the airport, in this case KCLM, is not longer in the Flightplan route. I can't use my method of getting waypoint info for my destination. Inserting the airport back in as above puts it back where I can find it. Or, if I'm cleared for the approach, and things are not too busy, I can add KCLM after the last item of the missed approach. I know there are other ways to get the info but what can I say, Old Dogs.... Forewarned is forearmed. Bob