MANUAL DATABASE IMPORT AND POST-ACTIVATION CHECKS
Manual Import is an alternative way of providing navigation data. It is useful when you already have a compatible DFD v2 database file. It is separate from importing an OFP: the database supplies the directory of possible routes and procedures, while a flight-plan import supplies the particular journey you want to prepare. After confirming the intended ACTIVE database, continue with flight-plan preparation. [52, Import a local database]
For the local-file method, place the supplied file directly in C:\ProgramData\Fenix\NavdataDFD\Import. Fenix accepts the documented .zip, .s3db, .3sdb and .db3 extensions. The filename must use the required cycle/revision format and agree with the contents; 2610-r001.zip is an example of that format. Select Manual Import in EFB Settings, then request IMPORT on A/C STATUS. If TYPE AIRAC CYCLE appears because several accepted files are available, enter the required four-digit cycle and request IMPORT again. [52, Import a local database]
Wait for the import to complete and inspect the second database. The important distinction is still the same: data imported into STANDBY is not yet the ACTIVE database used for navigation. Apply the normal activation conditions before changing it over. Once activation has reset the FMS, return to A/C STATUS and read the active dates again. That is our confirmation of which directory is now in use. [26, PDF p. 101] [26, PDF pp. 113-120]
Next, rebuild or reload the intended flight and check its airports and procedure names against the current OFP and charts. A database change can alter the choices offered on a departure or arrival page. Finding a difference while parked is manageable: there is time to look up the current route and understand the connection. Carrying an unchecked difference into arrival preparation makes a simple discrepancy much harder to think through. [26, PDF p. 101] [26, PDF pp. 113-120]
Keep database work together as one preparation task. Establish the correct file, import it, verify the stored database, activate when permitted, and read back ACTIVE. Then begin the flight programming with a known starting point. A partial sequence can leave you looking at a newly imported cycle while the system is still navigating with the earlier one.
Once that starting point is settled, keep it stable for the sector. Repeated activation repeats the FMS reset and the need to establish the flight again. The practical exercise gives the local-file steps in a compact form; its completion point is a checked active database, ready for INIT A. There is no need to keep revisiting the import folder once the intended data is working.
IN PRACTICE: V3: import a local DFD database
Before you begin: Optional path for a compatible DFD v2 file; do not substitute unrelated navdata.
1. Select the source
Action. Choose Manual Import in EFB Settings.
Check. IMPORT becomes the intended route; Navigraph sign-in is unnecessary. [52, Import a local database]
2. Place the file
Action. Put it directly in C:\ProgramData\Fenix\NavdataDFD\Import.
Check. No subfolder. [52, Import a local database]
3. Check the filename
Action. Use YYCC-rRRR with its supplied .zip, .s3db, .3sdb or .db3 extension.
Check. Filename cycle/revision matches contents. [52, Import a local database]
4. Import
Action. Open DATA > A/C STATUS; select IMPORT.
Check. With TYPE AIRAC CYCLE, enter YYCC and repeat IMPORT. [52, Import a local database]
5. Finish before activation
Action. Wait; check STANDBY dates, then apply the activation conditions above.
Check. Imported does not yet mean ACTIVE. [52, Activate STANDBY database]
Complete when: Check ACTIVE after separately activating the imported database.