use a regular single-line log entry for each part. The priority that appears in the log entry is the overall category assigned to the TD. When a TD is composed of several parts to be accomplished at different times, make separate consecutive log entries for each part, indicating the priority and status of each. Never include a multiple-part TD in a block entry unless all parts of the TD have been incorporated. In instances where a single line has been left for a directive that has not been received and a multiple-part TD is subsequently received, enter part 1 on the applicable TD page. Reference to the remaining parts of the TD should be made in this entry. The remaining parts of the TD should be recorded on the applicable TD revisions page. Occasionally, your activity may need to remove a TD. This is especially true with power plant changes (PPCs). Document the removal of a TD much like the incorporation of a TD. On the TD logbook page, simply draw a single line through the previous Status code, and enter Status code "Q" in the same block, along with the initials of anyone authorized to sign logbooks. Finally, you must make an entry on the Miscellaneous/History record, specifying reason for removal of the TD, location of parts removed, the authorizing reference, and any other pertinent information. For a detailed description of the TDSA system, you should refer to OPNAVINST 4790.2 and The NAVAIR Technical Directives System, NAVAIR 00-25-300. Q17. Q18. Q19. What document contains a listing of technical directives applicable to a specific bureau number and reported as not incorporated? What document contains a listing of technical directives applicable to a specific bureau number and reported as incorporated? A technical directive is being removed from an aircraft. What information should be entered in the Status Code block of the Technical Directive form? MISCELLANEOUS/HISTORY (OPNAV 4790/25A) This section of the logbook (fig. 6-9) is used by operating activities to record significant information that affects the aircraft for which no other space is provided in the logbook. Examples of such information include: Abnormal flight characteristics Peculiar troubles of an undetermined nature Damage to the aircraft Major component changes not logged elsewhere Instance of aircraft or equipment exposure to large quantities of salt water, fire extin- guishing agents, or other corrosive elements Authorizations for service period extension and PED, and operational service months (OPSERMOS) adjustment as a result of an ASPA inspection Verification of flight hours in period and since new on acceptance and transfer The original activity that accepts an aircraft for the Navy should make a Miscellaneous/History logbook entry that shows the date the acceptance check flight was flown. A date, signature, and activity accomplishing the action will accompany all entries in this section. At the time of standard rework, items of historical value are transcribed to a new form and retained as a permanent part of the logbook. When making entries on the Miscellaneous/ History record, you should make sure that you accurately describe the situation that led to the entry. Some situations require specific wording to accurately describe the situation. Specific wording assists maintenance crews in the repair process by accurately describing what happened and at what maintenance level the situation occurred. Such wording also provides uniformity of entries from activity to activity. Some situations that require specific wording include: Changes in the aircraft’s or equipment’s authorized inspection interval. Change in the inspection induction date or hourly sequence of aircraft or equipment. Hydraulic contamination testing reveals Navy standard class V contamination has been exceeded. 6-15