designated to use the ASR. The ASR (fig. 8-10) is used in the AESR to provide data tracking on assemblies and subassemblies that have rework or overhaul life limits and are designated to be removed at organizational-, intermediate-, or depot-level maintenance activities and 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. Equipment History Record (EHR) Card (OPNAV 4790/113) The EHR card (fig. 8-11) provides a method for monitoring specific maintenance data on designated 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. The EHR card is maintained in the AESR in the same way as the card is maintained in the aircraft logbook. Scheduled Removal Component (SRC) Card (OPNAV 4790/28A) Maintenance history, installation, and usage data is recorded on the SRC card, (fig. 8-12). The SRC card is maintained as part of the AESR as long as the component is installed. When the component is removed from the equipment, the card accompanies the component. It is very important that maintenance history continuity be maintained. The same procedures used to maintain or adjust the SRC card in the aircraft logbook should be used to maintain or adjust the SRC card in the AESR. Module Service Record (MSR) (OPNAV 4790/135) Modular engine design allows I-level maintenance activities to remove and replace interchangeable 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 record system to keep track of modules, the life limits of the assemblies and components within modules, and other maintenance data associated with modules. The MSR (fig. 8-13) provides this capability for all modular engines; for example, T56, T400, T700, and F404. The activity that accepts a module forwards a copy of the MSR to the Navy Aviation Maintenance Office (NAMO) 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 modules are delivered to the Navy at the contractor’s plant, the cognizant Navy representative is considered to be the original accepting activity. The MSR accompanies the module at all times. When the module is installed as a part of a propulsion system, the MSR is maintained concurrently with, and becomes a part of, the propulsion system AESR. When equipment that has a MSR is not installed, a two-prong fastener should be used to bind the MSR together. Staples should NOT be used. Upon completion of repair or rework, a copy of the MSR that reflects the current status of the module is forwarded to the central repository. The MSR must be inserted in the appropriate propulsion system AESR or be securely attached to the module when the module is returned to the supply system. When an MSR becomes damaged or mutilated, the activity that has current custody initiates a new record. All information is transcribed to the new record except for entries in the replacement blocks, which are made in pencil. Entries in the record are typed or plainly printed in black ink. When a record contains no space for additional entries, a new record is prepared, and both records accompany the module until the records are consolidated at repair or rework. Only I- or D-level maintenance activities are authorized to consolidate MSRs. In the top left comer of the first page of each MSR, the type of MSR is indicated; for example, fan, turbine, or afterburner. In the Replacement block (top right comer of the first page of the MSR), the noun name of the component or assembly within the module that has a life cycle limit is entered. Since the component or assembly within the module has a life cycle limit, the entire module must be removed from the propulsion system when the limit is reached. The Due block is computed by adding the component or assembly interval time to the module time and subtracting any hours or counts on the component or assembly at installation. These entries are made in pencil since these hours or counts are subject to change. 8-15