MANUAL DATABASE IMPORT: FILE SELECTION AND FAILURE ISOLATION
Manual Import accepts a compatible DFD v2 database, not a route export renamed to resemble one. The supplied file must have compatible contents as well as an accepted extension. The V3 destination is C:\ProgramData\Fenix\NavdataDFD\Import, with the file placed directly in that folder. Keep this task separate from SimBrief integration: one establishes the directory of navigation objects; the other retrieves a flight using those objects. [107, Import a local database; Activate STANDBY database]
1. Check the source file. The documented formats are .zip, .s3db, .3sdb and .db3. The cycle/revision naming convention must agree with the contents; 2610-r001.zip illustrates the naming pattern only. Renaming an incompatible database to that pattern does not make it compatible. Retain a clear relationship between the provider's actual file, its cycle and the candidate you intend to load. [107, Import a local database; Activate STANDBY database]
2. Start the local workflow. Select Manual Import, open A/C STATUS and request IMPORT. When several suitable files are available and TYPE AIRAC CYCLE appears, enter the four-digit YYCC cycle, then request IMPORT again. YYCC identifies year and cycle; do not interpret the cycle digits as a guaranteed calendar-month label. Let the selection/import complete before making another request. [107, Import a local database; Activate STANDBY database]
3. Interpret selection and validation. The support procedure describes selection by cycle revision, with modification-time handling for duplicates. Read the stored candidate rather than assuming the filename you last noticed was the one imported. If import fails, the existing spare database is retained. That retention is useful, but it means an unchanged-looking STANDBY slot can be the old candidate rather than a successful replacement. [107, Import a local database; Activate STANDBY database]
4. Confirm before activation. Compare the candidate dates and identity with the intended file and flight. Then use the normal V3 activation conditions. A successful import remains separate from making that database active, and activation still resets the FMS. Plan the task as a complete maintenance boundary: import, verify, activate when eligible, verify ACTIVE, then program the flight. [107, Import a local database; Activate STANDBY database]
5. Recover at the failed stage. If no candidate is recognised, check folder placement, accepted format and naming/content agreement. If a candidate is stored but cannot be activated, inspect date and aircraft/FMS/job-state conditions. Avoid changing the route or loading unrelated cycles while the fault belongs to file recognition. The completion point is a known active database, not simply an import dialog or a populated folder. [107, Import a local database; Activate STANDBY database]