CY. Example: 1-91, 2-91, 3-91, etc. On the first
ETR of each year, report the last CY ETR,
Example: 1-91 LAST CY ETR 154-90 DTG
312200Z DEC 90. The number of reports that can
be submitted in any given CY are limitless.
In addition to the number assigned to the
ETR, each transaction reported (fig. 7-10) must
be serialized. For example, if the first ETR
submitted by a reporting custodian contains four
transactions, the first transaction would be 001,
the second transaction 002, and the third
transaction 003, etc. These ETR report numbers
are reported in data element field 0 on all
transaction reports. Transaction serial numbers
commence with 001 for the first transaction
reported for the CY, and will increase sequentially
for each transaction reported throughout the CY
to a maximum of 999. If an activity exceeds 999
transactions within any given CY, numbering will
begin again with 001.
Each horizontal line (where possible) in a
message-type ETR details one engine transaction.
They are submitted in this format to facilitate the
direct key entry to an on-line data processing
system used by controlling custodians to transmit
engine data to the Naval Air Systems Command
Headquarters. The data in each column should
be aligned with a straight margin on the left. An
ETR should contain only information directly
concerned with engine management. OPNAV
X-RAY reports and ETR reports WILL NOT be
submitted as a combined report.
Reporting custodians may use different
reporting formats, but the data reported under
the various fields is practically identical. If you
understand the use of status codes, STAR codes,
and data elements, you should have little difficulty
preparing ETRs, no matter where you are
Upon determination that an error has been
made in the submission of an ETR, a correction
report should be sent immediately. Correction
reports are normally submitted as a two-line
report for each correction being submitted. These
reports are prepared in the same basic format as
regular reports. Correction reports submitted
independently should refer only to data reported
in the original report and should include the same
action/information addressees as the original.
Correction reports submitted at the direction of
higher authority should include the reference
directing the resubmission.
Correction reports are not assigned the next
sequential ETR number since they are correcting
previously submitted ETRs. The first line of the
message text repeats the information previously
reported in error, with the exception of adding
the word delete at the end of the transaction line.
The second line of the report contains the
corrected information and the word correct at the
end of the transaction line. For example, if a unit
had previously submitted an ETR incorrectly
reporting the Bureau Number (BUNO) of an
aircraft, the text of the correction ETR would be
as shown in figure 7-11. The reporting custodian
identifies the report being corrected by date-time
group, and ETR number/date. The complete
erroneous ETR line will appear on the correction
message, identified by the transaction serial/line
number of the original transaction.
Correction reports should not be considered
as a reflection on the reporting capabilities of an
activity. These reports are submitted for the
singular purpose of correcting the controlling
custodians engine file.
End-of-Quarter (EOQ) Report of Flying
Hours for Installed Engines
Engine reporting custodians submit an EOQ
report of installed engines. This report includes
data up to 2400 on the last day of the quarter.
The type of engine reported determines the
reporting quarters. All type M, O, R, and T
(except T56) engines are reported as of 2400 on
31 January, 30 April, 31 July, and 31 October.
All type T56 turboshaft engines are reported as
of 2400 on 28/29 February, 31 May, 31 August,
and 30 November. All turbojet/turbofan engines,
types F, J, and TF, are reported 31 March, 30
June, 30 September, and 31 December.
This report includes all engines in an installed
status regardless of location. Therefore, engines
in the reporting custodians aircraft that are in
pools, SDLM, and commercial facilities must be
included. It is the responsibility of the reporting
custodian to contact activities having physical
custody of the aircraft engines to determine the
correct number of hours to be reported.
The EOQ report is to be submitted via naval
message not later than 2400 hours on the third
working day following the end of the calendar
month in which the engine is to be reported; this
will allow for data entry into the AEMS data base
by the fifth working day. Reporting custodians
with access to on-line AEMS terminals will enter
reports not later than 5 working days following
the end of the reporting month. An example of