Routine Task Card
Routine Task Card
T00E45P3
Work Order No: WO - 107206592 Fleet: A320-FAM Effective Code: 351 MSN: 5929 Tail Number: CC-BFU
WP Line Number: 12
Task Description: --This EO was issued in order to control the uploading of the NDB in FMS (Flight Management System) of the
aircraft. --The Databases of Navigation are updated every 28 days, but it can be loaded when data is available,
which normally happens 6 days before its expiration. After due date, these items would become to MEL. --The
accomplishment of this E.O. is a requirement for CAT II/III, RNAV, RNP and RVSM. --This E.O Includes the
Navigation Data Base (NDB) loading procedure using PDL (Portable Data Loader), ADL (Airborne Data Loader) (if
installed), Cross load in other A319/A320/A321 aircrafts due to ADL and/or PDL failure.
ETOPS Significant:
Tools Request
Tools Description Tools PN
Parts On/Off
Description Qty PN Off SN Off Rem. Reason PN On SN On
Signatures
Skill Man Hours Performed By Signature Date
A320AVIC
Remarks:
Caution : The NDB to install must have correlative for the next cycle, taking special care in the year and
cycle changes according to the effective date.
PRECAUCION: El NDB a instalar debe tener el correlativo para el siguiente ciclo, teniendo especial cuidado
en los cambios de año y ciclo de acuerdo a las fecha de efectividad.
Note: The new NDB will be available not earlier than 10 days from the start effective date.
Nota: La nueva NDB estara disponible no antes de 10 dias de la fecha de inicio de efectividad.
07-04-2016
ADS 2015-2018
Document N° Aircraft Reg.
34-A2005
Bar Code
Doc. Rev. Date
ACCOMPLISHMENT INSTRUCTIONS
GENERAL INFORMATION
WARNING: ALWAYS BE SURE TO OBEY ALL THE WARNINGS AND THE CAUTIONS INCLUDED IN THE
ENGINEERING ORDER. WHEN YOU PERFORM MAINTENANCE WORK, REPAIRS OR
MODIFICATIONS, ALWAYS KEEP ELECTRICAL WIRING, COMPONENTS AND THE WORK
AREA FREE OF EXTERNAL ELEMENTS.
NOTE: The general architecture of Flight Management System for A319/A320/A321 fleet has two FM
incorporated in the FMGCs (Flight Management Guidance Computer), associated with this
system are the MCDUs (Multipurpose Control and Display Unit) and the DMCs (Display
Management Computer).
This EO can be accomplished in 5 different ways according to aircraft condition and available tools.
Accomplish the step applicable to selected configuration and mark others as NA (Not applicable)
ALTERNATIVE A: Step 3, Using MDDU
ALTERNATIVE B: Step 4, Cross loading from opposite FMGC
ALTERNATIVE C: Step 5, Software loading using an std PDL
ALTERNATIVE D: Step 6, Removing FMGCs and installing on other aircraft for software load
ALTERNATIVE E: Step 7, Software loading using PMAT 2000
1. Verify NDB is applicable to the aircraft see table, the load to FMGC must be one of the following
procedures (step).
CAUTION: The NAV DB to install must have correlative for the next cycle, following the
attachment ADS 2015‐2018, and taking special care in the year and cycle changes
according to the effective date. IF THE ACTUAL NAV DB INSTALLED IN AIRCRAFT IS THE SAME
P/N OF AVAILABLE, INFORM TO PLANNIFICATION TO REMOVE THIS ENGINEERING ORDER OF
THE WORK PACKAGE.
NOTE 1:Discs with the NDB applicable to the airplane must be requested in the areas assigned for
this purpose. Maintenance Base for Santiago, these must be requested in DCM area. In case of
any problems, request support area of the DSO. For the affiliate, the discs must be required in the
area of engineering or planning or other assigned area.
NOTE 2: The Part Number NAV DB is composed as follow:
DBV‐CCCC‐RRR
Where:
DB: Code DB may be LA(LAN) or JJ(TAM)
V: Version, depends of aircraft equipment (FMC)
CCCC: Cycle of NAV DB, see document ADS 2015‐2018
RRR: Revision of NAV DB, must be the major number available.
Note: The NAV DB must be for the next cycle according to attached document ADS 2015‐2018
PARTIAL SIGN OFF STATUS:
Step: _______________ Completed through: ____________________________ Emp #:_____________ MH___________
Step: _______________ Completed through: ____________________________ Emp #:_____________ MH___________
Document N° Aircraft Reg.
34-A2005
Bar Code
Doc. Rev. Date
2. Select alternative according to aircraft condition and available tools, and mark respective check
box.
SELECT ALTERNATIVE:
ALTERNATIVE A: Step 3, Using MDDU
ALTERNATIVE B: Step 4, Crossloading from opposite FMGC
ALTERNATIVE C: Step 5, Software loading using a std PDL
ALTERNATIVE D: Step 6, Removing FMGCs and installing on other aircraft for software load
ALTERNATIVE E: Step 7, Software loading using PMAT 2000
Accomplished By
ALTERNATIVE A:
3. NDB Load procedure through MDDU (Multipurpose Data Drive Unit). Refer to AMM Task 22‐70‐
00‐XXX‐XXX‐X (Uploading of the FM Data).
NOTE: If MDDU is not operative or disks are not available you can remove the MDDU iaw AMM 31‐38‐22‐
000‐001, connect PMAT using harness PN 31530‐2, PN 80955‐1 and load software according to step
6. After software load, disconnect harneses and install the MDDU to its housing, according to Task
AMM 31‐38‐22‐400‐001
NOTE: For aircraft PR‐MBG connect the PMAT using harness P/N 704‐1823‐001, P/N 80955‐1 and load
software according to step 7.
Accomplished By
ALTERNATIVE B:
4. Cross Load procedure, from one FMGC to another (it is necessary at least one FMGC with the
software previously loaded). Refer to AMM Task 22‐70‐00‐XXX‐XXX‐X (Crossloading of the FM
Data).
Accomplished By
ALTERNATIVE C:
5. NDB Loading procedure on both FMGC, by separated, through PDL. Refer to AMM Task 22‐70‐
XXX‐XXX‐X (Uploading of the FM Data with Portable Data Loader).
Accomplished By
ALTERNATIVE D:
6. Remove both FMGEC and install it in another A319 o A320 o A321 aircraft. Refer to AMM Task
22‐83‐34 PB 401 (Removal/Installation)., then perform the load of NDB with some of the
procedure indicated in step 4, 2 or 3. Return the units to the original aircraft.
CAUTION: BEFORE INSTALLING THE UNITS ON ANOTHER AIRCRAFT MUST BE VERIFY THAT THE P/N
SOFTWARS AND FMGEC UNIT ARE EQUAL BETWEEN AIRCRAFT, ANY DIFFERENCE MIGHT
CAUSE PROBLEMS ON THE AIRCRAFT INVOLVED.
Accomplished By
ALTERNATIVE E:
7. Use PMAT 2000 to load NDB. For this effect refer to indicated in the manual User Guide of PMAT
2000 attached to this JIC (NO PINTABLE).
Accomplished By
8. Record the part number of the Nav Data used in software loading.
P/N______________________________ Accomplished By
9. Register the effectivity date of the NDB.
__________ /___________ /_________ Accomplished By
Day Month Year
10. Verify for general condition, cleanliness and presence of foreign objects in the concern work area.
Close all opened access
Accomplished By