used when an additional record is required to supplement the documentation of multiple-entry data fields. Supplemental records may be attached to page 1 to provide additional space to document crew member names, additional flight legs and their associated records, or weapons proficiency. Exception codes (EXC CODE) are used on the NAVFLIR for entries that require processing for other than routine flights. (These codes are contained in OPNAVINST 3710.7.) The following are examples of situations that would require the use of exception codes: Gaining or losing crew members to the squadron database. Correcting, deleting, or revising previously submitted data. Documenting staff member flight time, such as for an individual who is assigned to a type commander (TYCOM) functional wing. Documenting flight training simulator time. Simulator time only refers to approved simulators capable of logging flight time. Documenting cancelled flights. Exception code X is used to document the cancellation of a flight and is used only in the aircraft data section. Documenting flights when the crew member and the aircraft are assigned to different organizations. The documentation for a routine flight consists of information from the following sections of the NAVFLIR: Aircraft Data-RECTYP (record type) 7B Aircrew Data-RECTYP 7C Logistics Data (Depart)-RECTYP 7E Logistics Data (Arrive)-RECTYP 7F. (This section is not completed in the submission of a cancelled flight.) NOTE: Weapons proficiency data, RECTYP 7G, is not mandatory for every flight, but it should be completed, as applicable, to document time spent in restricted air space, miscellaneous data, and so forth. Naval Aircraft Flight Record Documentation Flow Following each flight, or attempt at flight, the pilot or mission commander signs the NAVFLIR to certify that the record is correct. Two copies of the NAVFLIR are then printed. Copy 1 will go to operations for retention in the master files. Copy 2 is retained in the maintenance department for 3 months. Operations personnel screen the document for accuracy and transcribe the information into the aviators’ logbook. If your command is an Enhanced Comprehensive Asset Management System (ECAMS) site, the NAVFLIR should be routed to the ECAMS operator for incorporation into the database. The analyst or system administrator forwards the NAVFLIR data diskette to the supporting DSF for processing. NALCOMIS OMA activities should refer to the NAMP and NALCOMS End User’s Manual for automated NAVFLIR operating procedures. NAVAL FLIGHT RECORD SUBSYSTEM REPORTS The Naval Flight Record Subsystem (NAVFLIRS) serves as a single source of flight data for Aviation Standard Navy Maintenance and Material Management System (AV-3M), the Marine Corps Flight Readiness Evaluation Data System (FREDS), the Individual Flight Activity Reporting System (IFARS), the Navy Logistics Information System (NALIS), and other reporting systems. Submission of a NAVFLIR or a MAF to a DSF provides the basic data to produce the Naval Flight Record Subsystem (NAVFLIRS) reports that display aircraft flight readiness and inventory information. These machine reports are prepared for requesting activities to ensure uniform reporting of basic aircraft inventory and flight data within the Naval Establishment. Daily and monthly NAVFLIRS reports are generated by the DSF. NAVFLIRS Daily Audit Report The NAVFLIRS Daily Audit Report (DAR), shown in figure 4-11, is prepared daily from the data submitted on the NAVFLIR. Each detail line represents a single record type (RECTYP). This report is used to validate the previous day’s flight data form submission. The NAVFLIRS DAR is printed in three parts. Part I contains all data records that are found to be valid. Part II is a cumulative report that contains all flight records that were submitted during the current reporting period that contain errors that have not been corrected. In addition to current reporting period errors, NAVFLIRS DAR, Part II, reports errors that were not corrected 4-24