Crossloading of the Flight Management (FM) Data
TASK 22-70-00-610-009-A
Crossloading of the Flight Management (FM) Data
To crossload the FM data of one Flight Management and Guidance Computer (FMGC) to the other.
2. Job Set-up Information
A. Work Zones and Access Panels
B. Referenced Information
3. Job Set-up
Subtask 22-70-00-860-157-C
Subtask 22-70-00-970-071-B ** ON A/C NOT FOR ALL
Subtask 22-70-00-860-116-C ** ON A/C NOT FOR ALL
[Rev.10 from 2021]
2026.03.31 23:10:52 UTC
Crossloading of the Flight Management (FM) Data
WARNING:
MAKE SURE THAT ALL THE CIRCUITS IN MAINTENANCE ARE ISOLATED BEFORE YOU SUPPLY ELECTRICAL POWER TO THE AIRCRAFT. UNWANTED ELECTRICAL POWER CAN BE DANGEROUS.
1. Reason for the JobTo crossload the FM data of one Flight Management and Guidance Computer (FMGC) to the other.
2. Job Set-up Information
A. Work Zones and Access Panels
| ZONE/ACCESS | ZONE DESCRIPTION |
|---|---|
| 210 | CKPT,FWD COMPT BHD TO FLT COMPT BULKHEAD |
| REFERENCE | DESIGNATION |
|---|---|
| TASK 24-41-00-861-002-A | Energize the Aircraft Electrical Circuits from the External Power |
| TASK 24-41-00-861-002-A-01 | Energize the Aircraft Electrical Circuits from the APU |
| TASK 24-41-00-861-002-A-02 | Energize the Aircraft Electrical Circuits from Engine 1(2) |
| TASK 24-41-00-862-002-A | De-energize the Aircraft Electrical Circuits Supplied from the External Power |
| TASK 24-41-00-862-002-A-01 | De-energize the Aircraft Electrical Circuits Supplied from the APU |
| TASK 24-41-00-862-002-A-02 | De-energize the Aircraft Electrical Circuits Supplied from the Engine 1(2) |
Subtask 22-70-00-860-157-C
A. Aircraft Maintenance Configuration
(1) Energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-861-002).
(2) Make sure that the aircraft is in the ground configuration.
(3) On MCDU1(2), push the BRT key for the MCDU to come on.
Subtask 22-70-00-280-083-C ** ON A/C NOT FOR ALL (1) Energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-861-002).
(2) Make sure that the aircraft is in the ground configuration.
(3) On MCDU1(2), push the BRT key for the MCDU to come on.
B. Check of the Part Number(s) (P/N) of the Software Component(s) (Pre-loaded to the Related FMGC) on the Applicable "P/N STATUS" Page(s) on the Multipurpose Control & Display Unit (MCDU)
Subtask 22-70-00-280-083-D ** ON A/C NOT FOR ALL NOTE: The software components that you can crossload (FM1 to FM2 on MCDU1 or FM2 to FM1 on MCDU2) on the related "P/N STATUS" page are as follows:
(1) Do a check of the P/N(s) of the software component(s):- The Flight Management System (FMS) operational software-component
(page 2: FMS SOFTWARE) - The navigation database
(page 3: NAV DATA BASE) - The airline modifiable-information file
(page 4: FM AIRLINE CONFIG (AMI)) - The operational program configuration-file
(page 5: FM OPTIONS CONFIG (OPC)) - The performance database
(page 6: PERF DATA BASE) - The magnetic variation database (if available)
(page 7: MAG VAR DATA BASE).
| ACTION | RESULT |
|---|---|
1.On the "MCDU MENU" page:
| On the MCDU:
|
2.On the "A/C STATUS" page:
| |
3.On the "A/C STATUS" page:
|
|
4.On the "P/N STATUS" page:
|
|
B. Check of the Part Number(s) (P/N) of the Software Component(s) (Pre-loaded to the Related FMGC) on the Applicable "P/N STATUS" Page(s) on the Multipurpose Control & Display Unit (MCDU)
4. ProcedureNOTE: The software components that you can crossload (FM1 to FM2 on MCDU1 or FM2 to FM1 on MCDU2) on the related "P/N STATUS" page are as follows:
(1) Do a check of the P/N(s) of the software component(s):- The Flight Management System (FMS) operational software-component
(page 2: FMS SOFTWARE) - The navigation database
(page 3: NAV DATA BASE) - The airline modifiable-information file
(page 4: FM AIRLINE CONFIG (AMI)) - The operational program configuration-file
(page 5: FM OPTIONS CONFIG (OPC)) - The performance database
(page 6: PERF DATA BASE) - The magnetic variation database (if available)
(page 7: MAG VAR DATA BASE).
| ACTION | RESULT |
|---|---|
1.On the "MCDU MENU" page:
| On the MCDU:
|
2.On the "A/C STATUS" page:
| |
3.On the "A/C STATUS" page:
|
|
4.On the "P/N STATUS" page:
| |
Subtask 22-70-00-970-071-B ** ON A/C NOT FOR ALL
A. Crossloading of the FMGC Database
Subtask 22-70-00-970-071-C ** ON A/C NOT FOR ALL | ACTION | RESULT |
|---|---|
| 1.On MCDU1(2): | On MCDU1(2): |
|
|
| On MCDU1(2):
|
|
|
|
|
|
|
| 2.Use the MCDU related to the side from which you want to upload the database. | |
| 3.On this MCDU: | On this MCDU: |
|
|
| On the two MCDUs:
|
| | When the crossloading is completed:
|
4.When the uploading is completed for the two FMGCs:
| |
| 5.Close circuit breakers 10CA1 and 10CA2. | |
| 6.On MCDU1(2): | On MCDU1(2): |
|
|
| |
|
|
A. Crossloading of the FMGC Database
When you do the crossloading procedure of:
Subtask 22-70-00-280-073-C ** ON A/C NOT FOR ALL When you do the crossloading procedure of:
- One software component that you can upload (for example, navigation database), use the related "P/N STATUS" page (for example, page 3 for the crossloading of the navigation database) on MCDU1 to upload FM2, or on MCDU2 to upload FM1.
- All the software components that you can upload, use the "P/N XLOAD" page on MCDU1 to upload FM2 (the "FMS2 UPDATE" indication), or on MCDU2 to upload FM1 (the "FM1 UPDATE" indication). Only the different software components are crossloaded.
NOTE: If the "XLOAD NOT SUPPORTED" indication comes into view on the two MCDUs, it is necessary to do the crossloading after a cold start (two FMGCs are off for a minimum of 10 minutes).
NOTE: On MCDU1(2), the "INDEPENDENT OPERATION" indication comes into view in the scratchpad.
| ACTION | RESULT |
|---|---|
| 1.Use the MCDU related to the side from which you will do the crossloading. | |
| 2.On this MCDU: | On this MCDU: |
| |
|
|
| On the MCDU:
|
3.When the uploading is completed for the two FMGCs:
| |
5.When the safety test of this FMGC is completed on MCDU1(2), make sure that:
| |
B. Do a check of the P/N(s) of the software component(s) crossloaded to the FMGC on the MCDU.
(1) Make sure that the "P/N XLOAD" page is shown on the MCDU.
(2) If the P/N of the navigation database is erased after the reset of the FMGC software component (that was crossloaded), do the crossloading again.
Subtask 22-70-00-280-073-D ** ON A/C NOT FOR ALL (1) Make sure that the "P/N XLOAD" page is shown on the MCDU.
(2) If the P/N of the navigation database is erased after the reset of the FMGC software component (that was crossloaded), do the crossloading again.
| ACTION | RESULT |
|---|---|
1.On the "MCDU MENU" page:
| On the MCDU:
|
2.On the "A/C STATUS" page:
|
|
3.On the "P/N STATUS" page:
|
|
| 4.On the "A/C STATUS" page: A.Make sure that the "IDLE/PERF" value is the same as the value you recorded before the crossloading procedure. B.If the "IDLE/PERF" value is not the same as the value you recorded before the crossloading procedure: 5.Enter "ARM" in the "CHG CODE" field adjacent to line select key 5L. NOTE: "ARM" is the initial code. You can change it when you enter three other characters in the airline modifiable-information file. 6.Record the "IDLE/PERF" value in the scratchpad.7.Enter this value adjacent to line select key 6L. | |
B. Do a check of the P/N(s) of the software component(s) crossloaded to the FMGC on the MCDU.
(1) Make sure that the "P/N XLOAD" page is shown on the MCDU.
(2) If the P/N of the navigation database is erased after the reset of the FMGC software component (that was crossloaded), do the crossloading again.
5. Close-up(1) Make sure that the "P/N XLOAD" page is shown on the MCDU.
(2) If the P/N of the navigation database is erased after the reset of the FMGC software component (that was crossloaded), do the crossloading again.
| ACTION | RESULT |
|---|---|
1.On the "MCDU MENU" page:
| On the MCDU:
|
2.On the "A/C STATUS" page:
|
|
3.On the "P/N STATUS" page:
| |
| 4.On the "A/C STATUS" page: A.Make sure that the "IDLE/PERF" value is the same as the value you recorded before the crossloading procedure. B.If the "IDLE/PERF" value is not the same as the value you recorded before the crossloading procedure: 5.Enter "ARM" in the "CHG CODE" field adjacent to line select key 5L. NOTE: "ARM" is the initial code. You can change it when you enter three other characters in the airline modifiable-information file. 6.Record the "IDLE/PERF" value in the scratchpad.7.Enter this value adjacent to line select key 6L. | |
Subtask 22-70-00-860-116-C ** ON A/C NOT FOR ALL
A. Put the aircraft back to its initial configuration.
(1) On the MCDU, push the MCDU MENU mode key to get access to the "MCDU MENU" page.
(2) Put the media back into the storage box in the cockpit.
(3) On MCDU1(2), push the DIM key for the MCDU to go off.
(4) De-energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-862-002).
Subtask 22-70-00-860-116-D ** ON A/C NOT FOR ALL (1) On the MCDU, push the MCDU MENU mode key to get access to the "MCDU MENU" page.
(2) Put the media back into the storage box in the cockpit.
(3) On MCDU1(2), push the DIM key for the MCDU to go off.
(4) De-energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-862-002).
A. Put the aircraft back to its initial configuration.
(1) On the MCDU, push the MCDU MENU mode key to get access to the "MCDU MENU" page.
(2) On MCDU1(2), push the DIM key for the MCDU to go off.
(3) De-energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-862-002).
(1) On the MCDU, push the MCDU MENU mode key to get access to the "MCDU MENU" page.
(2) On MCDU1(2), push the DIM key for the MCDU to go off.
(3) De-energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-862-002).