G3X vs. GNC 355 (or any navigator) in backcountry flying

[Neal]

Most of the airports I go to are private fields such as 20VA, VA19, etc. The problem is they are not in the Garmin navigators such as I have a GNC 355 which is beyond annoying and I don't know why they don't share the airport database that the G3X has. Today was a case in point where a flight plan I uploaded from ForeFlight to the GNC 355 somehow got reversed which is moot so it required me to enter the airport and use Direct To for navigation. I typically (always) use ForeFlight and the GNC 355 (external navigator) for my flying. I know when the GNC 355 doesn't have the airport the alternative option is to use ForeFlight and send it to the panel. It's a pain, today I gave up and switched to the internal navigator and used the G3X directly. We all know the G3X is perfect on its own, I'm just trying to make use of the fancy schmancy I paid good money for. I think I'm sticking with the G3X as the primary navigator going forward. It's just easier for backcountry airports as they are available and I don't have to fight my avionics.

I'm curious what others are using for their navigation?

 

[Cactus Charlie]

I use the GPS 175 if the airport is in its database. Some of my user defined "airports" are in either GPS-175 or GDU or both. It is so easy to switch between internal and external navigators that I don't get too excited about it.

The places I like to go are not in any published database but sometimes I have to go where there is 100LL.

I keep the GDU 465 database current but I have not purchased a GPS 175 database update since I installed it several years ago. I will buy an update for GPS 175 if I plan an XC flight outside Arizona.

 

[ve6yeq]

My current workflow is always to plan on ForeFlight and then send it to the GNC 355. Then depending upon how I feel, I can either use AP Nav mode or just hand fly although I have been recently using AP heading mode as I fly along coast lines so I can get my hands free for photos when the air is not smooth enough for just the old trim and rudders “AP”.

The only downside to the ForeFlight workflow is the naming of the automatic waypoints in the Garmin world…

The G3X Touch databases are a pain to manage as Garmin requires different databases for Canada and the US so I have to reload from SD card when I cross the border. In Canada, the Garmin airport database is really poor so you need to talk the Garmin support into giving you a copy of the international AC-U-KWIK database not the default AOPA one.

Legally, as a Canadian pilot, I need to have on board 2 sources of charts and airport directories so I have been paying for the Garmin Database subscription in addition to ForeFlight so I can forget paper charts and the CFS.