曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
To “clear” the DD the TYPE and NUMBER will be entered
in the DD CLEARED Block together with full details of action
taken and certified accordingly. The SECTOR RECORD LOG PAGE
NUMBER and ITEM NUMBER will be entered on the right hand
side of the Deferred Defect Record page.
When any work i.e. trouble shooting, unit replacement etc, is carried out on a DD, but the defect is not
cleared, all details are to be entered including the same DD TYPE and NUMBER in the DD RAISED block. This
will establish a history for actions accomplished for this particular deferred defect.
Each Deferred Defect, whether raised or cleared, must have its own corresponding entry in the defect
column of the Tech Log sheets. It is not permissible to clear and raise separate Deferred Defects in a single
action column.
Note that all Defects entered on the Sector Record Page(s) must be actioned, that is signed off as
deferred or repaired (or “inspected, cannot fault, report further …”), before the Tech Log Sector Record page
copies are removed for processing.
10. Deferred Defects Record Pages.
All Deferred Defects will be entered on the record pages,
prefixed by the appropriate TYPE CODE and pre-numbered in
sequential order. Note that each all except the last sheet will be
noted “TICK HERE IF NEXT SHEET USED” at the bottom.
When it is necessary to defer a defect, engineering staff will:
• Enter in the action column of the Sector Record Page that
the defect is transferred to the Deferred Defect Record.
• The defect will be copied to the next available unused DD
Record information block. The following fields are mandatory
:
TYPE CODE : As discussed previously (P 11) (P, C*, E*, M, R, L, N)
DATE : Date of departure of the flight (UTC) Dates are entered using the
European (dd/mm/yy) date format.
L/P, ITEM NO : Tech Log (Sector Record) Page Number and ITEM
NO from the Defect Entry on the related Sector Record page.
• The MEL reference if applicable will be quoted.
• After completion of the DD record, enter the DD Code & Number in
the DD raised block on the Sector Record page.
11. Defect Log Consolidation.
The Deferred Defects Record is assessed during “Weekly Checks” to reduce the number of used pages
- all open deferred defects are recorded in ascending numerical order and copied verbatim. Such DD’s will be
re-written on “Consolidation” sheets which are not pre-numbered. The DD clearance section of the transferred
DD’s should be annotated transferred to DD consolidation sheet and Authorisation Number (Stamp) entered in
the cleared box. Any unused blocks on the consolidation sheet will be struck out. The last pre-numbered sheet
containing any entry must be left in the log, even if all the DD’s are cleared, in order to preserve the numerical
sequence. When less than three unused DD sheets remain, they are to be replenished on the next transit of
DXB.
B777 Aircraft Technical Log. Page 13 of 19
Locator : C:\Documents And Settings\Administrator\My Documents\Emirates\777\Notes\Tech Log\B777 Tech Log.Doc As At : 29.11.2001
12. Fault Reporting Manual (FRM)
The Boeing FRM is applicable only to a specific list of aircraft as detailed inside the manual. It lists
possible aircraft defects (faults) with an associated fault reporting number. An engineer can take the number
reported by the crew and refer to the Fault Isolation Manual for any Boeing specified procedures associated
with the reported fault. Thus it is important that all defects in the Tech Log are accompanied where possible by
an FRM code to greatly assist engineering in fault finding and repairing reported defects. FOM Ch 17 Pg 6
25.Aug.2001 refers.
The FRM is divided into four sections, some of which are further divided. Each of the sections is
essentially a comprehensive list of defects. These defects can be either (a) Primary EICAS messages,
(b) Observed by the flight/engineering/loading crew, (c) a Status Message, or (d) Observed by the Cabin Crew.
a) Primary EICAS message list.
This section is essentially an alphabetical listing of all Primary EICAS messages (Warning, Caution,
Advisory, Com and Memo) with an associated FRM code.
b) Observed Faults.
This section lists faults via a short text description of the defect. Note that most faults have multiple
entries in the listing to allow for the variations in describing the fault (ie: “Light, Overhead, Faulty” or
“Overhead Light, Faulty”)
When reporting non-EICAS faults, it is a requirement to enter the text message describing the fault in
the FRM into the Defect Description block of the Tech Log. The observed faults section is divided into :
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料7(24)
