DATA: AIRCRAFT IDENTITY AND V3 DATABASE MANAGEMENT
Before building a route, open DATA and A/C STATUS. This is where we check the aircraft and engine information and the navigation-database dates. The navigation database is the system's directory of airports, runways, waypoints, airways and procedures. A route entry can only use the information available to the loaded system, so this early check saves us searching for a procedure in the wrong directory later. [26, PDF p. 101]
Read the actual identity as well as the dates. Our exercise calls for the A320 CFM configuration; the calculations and flight-planning profile must agree with it. Then establish which database the aircraft is using. A familiar-looking route on another screen does not establish the MCDU's database state. We will inspect the state directly before entering the flight. [26, PDF p. 101]
Fenix V3 has two database slots. ACTIVE supplies the navigation data currently used by the flight-management system. STANDBY holds another database, which the MCDU labels SECOND NAV DATA BASE. New data first goes into that second slot. It is useful to picture a checked replacement waiting beside the working directory. Downloading the replacement and making it the working directory are separate events. [52, Choose a navdata mode]
The EFB's mode determines how those events happen. Disabled leaves manual CHECK available; Hot Standby updates the spare database for separate activation. Automatic can update and activate when the required conditions permit. Manual Import uses a compatible local database file. The names describe the update workflow. The FMS continues navigating with ACTIVE, whichever method supplied the new data. [52, Choose a navdata mode]
For a Navigraph update, connect the account in EFB Settings with an active subscription, then use CHECK on A/C STATUS and wait for download and validation. Read the second database's dates afterwards. A future cycle may be stored in advance, but its effective date still matters. A larger cycle number alone is not permission to activate it early. [52, Update through Navigraph] [52, Activate STANDBY database]
Activation swaps the database slots and resets the FMS. Plan that reset before programming the flight, on the ground in the permitted preflight or completed-flight state, with no check, download or validation running and the effective date reached. After activation, read ACTIVE again and then build or reload the intended flight. Activation and database maintenance follow the V3 workflow described here. [52, Update through Navigraph] [52, Activate STANDBY database]
IN PRACTICE: V3: download, validate, then activate
Before you begin: Parked, stable electrical supply; perform database work before programming the flight.
1. Authorise
Action. Connect Navigraph in EFB Settings > Connections, with an active subscription.
Check. Connection confirmed. [52, Update through Navigraph]
2. Control the update
Action. Choose Disabled for this manual CHECK exercise.
Check. Automatic updating is off; manual CHECK remains available. [52, Choose a navdata mode]
3. Download
Action. Open DATA > A/C STATUS and select CHECK.
Check. STANDBY downloads and validates. [52, Update through Navigraph]
4. Read the dates
Action. Wait for completion; inspect SECOND NAV DATA BASE dates.
Check. The intended cycle is available, not merely downloading. [52, Update through Navigraph]
5. Activate deliberately
Action. Select SECOND NAV DATA BASE only on ground, preflight/flight complete, with no update running and effective date reached.
Check. FMS resets; previous ACTIVE becomes STANDBY. [52, Activate STANDBY database]
Complete when: Read back ACTIVE after the reset, then programme or reload the flight.