Technical documentation for the aircrafts. Creating and updating the manual, maintenance procedures, troubleshooting (AMM, TSM). Greetings of the day dear friends. I am in search of A(CFMA) AMM in PDF documents are normally available in ADOC. Airbus A Tsm. BOOK ID: byku1lDmnQdq [Pdf] Airbus A Tsm DOWNLOAD Book Free. May 9th, – Podle zákona o evidenci.

Author: Dizshura Akinomuro
Country: Trinidad & Tobago
Language: English (Spanish)
Genre: Technology
Published (Last): 23 September 2004
Pages: 472
PDF File Size: 15.22 Mb
ePub File Size: 17.51 Mb
ISBN: 939-9-35223-886-6
Downloads: 16375
Price: Free* [*Free Regsitration Required]
Uploader: Takora

TO Power up to 80 kts PFR, test result, trouble shooting data if available.

The Fault Symptom pages in each section are divided into the following three main columns: Thank you for interesting in our services. Nonetheless, their definitions make it possible to understand why certain menus are simplified. In this case, the test has not been completed.

Specific instructions for the wiring check are given where necessary. The user who wants to use these messages must do so carefully as the rsm involved is non-correlated and non-priority information. In some cases it is possible for the trouble shooting to be covered in a chapter different to that of the ATA reference given by the warning, malfunction or CFDS fault message. The contents of these is as follows: In most of the cases, computers may be recovered after an abnormal behaviour or a detected fault, either by a software reset reset of microprocessor or by interrupting the power supply of its processing parts for a short time.


airbus a TSM – Free Download PDF

Faults detected during ysm will generate maintenance messages in the PFR associated with this flight if class 1 or 2 as defined in Para 4. The general rule is that an even suffix identifies a component on the right hand side and an odd suffix identifies a component on the left hand side. Therefore, each system has in memory an information linked to every message transmitted to the CFDIU which defines its internal or external a3220 so that the CFDIU can give priority to the most accurate one.

Q320 each of these general divisions faults are divided according to the type of system and display: Depending on the fault and its effect, it will be the one generated either by a computer which detects itself faulty self monitoring or by the computer in charge of the BITE of the system.

Test names are related to the tested parts. The microfilm cassettes are filmed with the appropriate pages for the revision inserted. In each ATA chapter page blockthe table lists: The q320 data are recorded in the PFR: Touch down up to 80 kts These are a32 at chapter level by: This system organization in three types essentially remains transparent for the operator as the CFDIU manages any differences.

This is essentially achieved by analysis of all cockpit events which are triggered by the monitoring of the aircraft systems.


• View topic – A AMM and TSM IN PDF FORMAT

Refer to paragraph 4 for a description of the CFDS and z320 to use it. One of these messages may be more accurate than the others. Task idents begin at and raise, in sequence, to maximum within the P. These messages are recorded in each system BITE class 3 report.

airbus a320 TSM

Block The primary fault only is given in the TSM to avoid confusion with too many associated faults. If a fault appears and disappears several times during the same flight leg, the corresponding fault message is transmitted only at the first detection, but the ECAM warning for a Class 1 fault or the Maintenance Status for a Class 2 fault is displayed every time in the cockpit and transmitted every time to the CFDIU.

For these systems, the flight condition is between takeoff and landing. This function enables a quick access to the class 3 messages of a given system. Consequently, normally these tests are not performed during a short stopover.

For the operator, the resulting consequences are minor: Activation of a test will be requested in the TSM by the fault isolation procedure related to a maintenance message. The actions to be taken are displayed in plain language on the MCDU.