50 series—Acquisitions 60 series—Transfers and receipts 70 series—Removals 80 series—Strikes 90 series—Miscellaneous A detailed explanation of Status and STAR code combinations are listed in NAVAIRINST 13700.15. Q3. What type of code is used to describe the condition of an engine, purpose for which the engine is used, or stage or progress the engine has reached in the maintenance cycle? Q4. What series Status code is used to describe an installed operating engine? Q5. What type of code describes or gives the reason for (1) strikes, (2) transfers, (3) acquisitions, or (4) removals? Q6. A STAR code must always be used with what type of code? Q7. What type of code amplifies an aircraft engine Status code? ENGINE TRANSACTION REPORT (ETR) LEARNING OBJECTIVES: Identify the purpose of Engine Transaction Reports (ETRs). Identify the deadline for submission of ETRs. Recognize situations that require submission of ETRs. ETRs advise the controlling custodian of actions that concern the use, status, or custody changes of assigned engines. The report covers all transactions that occurred since the previous report. A report must be submitted not later than 2400 hours of the first working day following the date the action occurred. Should it become necessary to submit a late report, use the actual Julian date of action and indicate in the Remarks section that the report is late. Some situations that require submission of ETRs are listed below: of parts The receipt or transfer of an uninstalled engine The removal or installation of an engine The cannibalization or strike of an engine The delay of an engine repair due to a shortage The receipt or transfer of an aircraft with an installed engine There are many other situations that require an ETR, however, those listed above are used most often. ETR PREPARATION The preparation of an ETR is a relatively simple (but important) task. NAVAIRINST 13700.15 contains guidelines and examples that cover almost any engine transaction. Figure 9-1 is an example of a message-type ETR prepared for transmission that reports four transactions. Transaction 019 reports an engine removed; transaction 020 reports the engine transfer. Transactions 021 and 022 show receipt and subsequent installation of the replacement engine. Notice that fleet activities prepare ETRs in a horizontal line format. Most shore activities, however, submit ETRs electronically through the AEMS on-line computer terminal. These terminals are connected by telephone lines to a central computer that contains a master list of engines and other propulsion systems. ETRs can be directly entered into the AEMS database. Activities with access to AEMS computer terminals should use on-line reporting. Complete procedures for on-line reporting are outlined in NAVAIRINST 13700.15. Q8. Q9. By what means is a controlling custodian advised of the status, use, or custody change of an assigned aircraft engine? What is the deadline for submission of ETRs? Q10.  A total of how many transactions are required on an ETR that reports the removal and transfer of an engine and the subsequent receipt and installation of a replacement engine? Q11.  What is the preferred method of submitting ETRs for shore-based activities? ETR NUMBERING LEARNING OBJECTIVES: Describe how ETRs are numbered. Identify data elements and fields used on ETRs. Define retention requirement for ETRs. ETRs submitted by reporting custodians are numbered sequentially throughout the calendar year (CY) beginning with report number 1 for the first report submitted on or after 1 January of the CY. Each successive report increases by one number until 31 December, after which ETR numbering restarts with report number 1 for the CY. Example: 1-96, 2-96, 3-96, etc. On the first ETR of each year, report the last CY 9-3