aeronautical components and equipment that do not qualify as SRC. An individual card for each EHR-serialized item is maintained as part of the AESR while the component is installed. When the component is removed from the equipment, the EHR card is attached to and accompanies the component to its final disposition. This record is maintained in the AESR in the same way as it is maintained in the aircraft logbook (chapter 6, figs. 6-16 and 6-17).

Assembly Service Record (ASR) (OPNAV 4790/106A)

The latest edition of NAVAIRINST 4790.3 establishes the policy and responsibilities for the planned removal/replacement of selective assemblies designated to use the ASR. The ASR is used in the AESR to provide data tracking on assemblies if the assembly has a rework/overhaul life limit, and its subassemblies are either D-level removal only; or, if removed by O- and I-levels, its subassemblies are discarded, The same procedures used to maintain or adjust the ASR in the aircraft logbook should be used to maintain or adjust the ASR in the AESR. (See chapter 6, figs. 6-18 and 6-19).

Module Service Record (MSR) (OPNAV 4790/135)

Modular engine design allows I-level mainte- nance activities to remove and replace inter- changeable modules with ready-for-issue (RFI) spares. The removed modules are either repaired at an IMA or forwarded to depot maintenance for overhaul. This capability requires a system by which these modules, the life limits of the assemblies and components within them, and other maintenance data may be recorded and maintained. The MSR (figs. 7-3, 7-4, 7-5, and 7-6) provides this capability, and it is used for all modular engines; for example, T56, T76, T400, T700, and F404.

The activity that accepts a module forwards a copy of the MSR to the NAVAVNMAINTOFF central repository. MSR initiation for modules installed on aeronautical engines as part of a DOD contract is the responsibility of the activity that accepts the engines for the Navy. When these

Figure 7-4. - Module Service Record (page 2).