read this and look up GDU12:
download/file.php?id=4072
updating Nav database before expiration
Moderators: Rick, Lance Murray
-
CFIDave
- 5 Diamonds Member
- Posts: 2736
- Joined: Wed Nov 07, 2012 3:40 pm
- First Name: Dave
- Aircraft Type: OTHER
- Aircraft Registration: N333GX
- Airports: KJYO Leesburg VA
- Has thanked: 259 times
- Been thanked: 1547 times
Re: updating Nav database before expiration
Epic Aircraft E1000 GX
Former DA40XLS, DA42-VI, and DA62 owner
ATP, CFI, CFI-I, MEI
Former DA40XLS, DA42-VI, and DA62 owner
ATP, CFI, CFI-I, MEI
-
meowmeow
- 2 Diamonds Member
- Posts: 41
- Joined: Sat Jul 21, 2018 7:47 pm
- First Name: Sven
- Aircraft Type: DA42
- Aircraft Registration: N16ES
- Airports: KBFI
- Has thanked: 7 times
- Been thanked: 19 times
Re: updating Nav database before expiration
These are completely unnecessary problems caused by Garmin sometimes not thinking through the most obvious scenarios. The whole database update process is unnecessarily complicated and insufficiently documented - leading to lots of different opinions and ways of doing things that should be simple and straight forward. It's complicated enough for the aircraft owner, and a big recurring headache for flight schools.
The NAV DB fortunately waits until its active day to ask if you want to install it, but flight charts installed a day earlier than valid day leads to "outdated charts". Garmin's DB Manager software is definitely better now than it used to be, but they still leave too many details unclear, and the details are - as we all know - where the devil lives (i.e. DB issues rendering the whole system unusable for IFR - or even all flight scenarios - until resolved).
The NAV DB fortunately waits until its active day to ask if you want to install it, but flight charts installed a day earlier than valid day leads to "outdated charts". Garmin's DB Manager software is definitely better now than it used to be, but they still leave too many details unclear, and the details are - as we all know - where the devil lives (i.e. DB issues rendering the whole system unusable for IFR - or even all flight scenarios - until resolved).