| EVENT_ID | EVENT ID | This is the unique identifier that links all of the tables for the event. NOTE: Format is eight-character numeric. |
| EVENT_ID | EVENT ID | System Generated identifer enforcing uniqueness of records |
| RPRT_NBR | REPORT NUMBER | The FAA assigned unique identifier for the incident. NOTE: The format was changed in 1992; both the old and new formats are provided below. |
| FISCAL_YEAR | FISCAL YEAR | Fiscal Year of the Event |
| EVENT_LCL_DATE | EVENT DATE | Event date is based on local time. ATQA may show an incident based on UTC but for tracking purposes use local times only to identify the actual day of the event. Rationale: If an event occurred on Jun 30 and the UTC date used is Jul 1st the runway incursion number is entered in the month of Jun, actual date of occurrence. Month/Day/Year format: MM/DD/YYYY. Where MM equals the month number (Jan = 01, Feb = 02, etc.); DD equals the day of the month; and YYYY equals the year. |
| EVENT_UTC_DATE | EVENT UTC DATE | The date the event occurred based on Coordinated Universal Time (UTC), also known as Greenwich Mean Time (GMT) or Zulu Time (Z). |
| RPRT_NBR | REPORT NUMBER | Enter the report number that is filed on the OE/D, PD, and VPD form. The reports are in the Administrators Daily Alert Bulletin (ADAB) and also entered in ATQA by the facility or Service Center. Column "BJ" indicates when there is more than one type report filed for the same event. For example an OE is filed plus a PD. |
| EVENT_UTC_TIME | EVENT UTC TIME | The time the incident occurred based on Coordinated Universal Time (UTC), also known as Greenwich Mean Time (GMT) or Zulu Time (Z). NOTE: Format is 24-hour clock. |
| EVENT_LCL_TIME | EVENT LOCAL TIME | LThe local time the incident occurred. NOTE: Format is 24-hour clock. |
| INCDNT_TYPE_FAA_CODE | FAA INCIDENT TYPE CODE | Enter the appropriate two or three letter identifier in this column. OE = Operational Error. OD = Operational Deviation. PD = Pilot Deviation. V/PD = Vehicle/Pedestrian Deviation. Other = OTH. OTH is used when an event does not meet the OE/OD, PD, or VPD criteria. |
| LOC_CITY_NAME | LOCATION CITY NAME | The name of the nearest city/town to the location of the incident. |
| RPRT_RCVD_DATE | REPORT RECEIVED DATE | Actual date the report is received by AJS-4 from ADAB or other source such as from a regional POC. Month/Day/Year format: MM/DD/YYYY. Where MM equals the month number (Jan = 01, Feb = 02, etc.); DD equals the day of the month; and YYYY equals the year. |
| RPRT_CLSFD_DATE | REPORT CLOSED DATE | Date the event is classified as a surface event or runway incursion by AJS-4. Month/Day/Year format: MM/DD/YYYY. Where MM equals the month number (Jan = 01, Feb = 02, etc.); DD equals the day of the month; and YYYY equals the year. |
| LOC_CITY_NAME_STD | ASIAS STANDARD LOCATION CITY NAME | The standardized name of the nearest city/town to the location of the incident. |
| LOC_STATE_CODE | LOCATION STATE CODE | The code for the state, territory, or foreign location where the event occurred. See Business Rules below for the U.S. code standards and Foreign codes and descriptions. |
| RWY_SFTY_RI_FLG | RUNWAY INCURSION FLAG | Enter the appropriate letter. "Y" if the incident meets the definition of a Runway Incursion. "N" if the incident does not meet the definition of a Runway Incursion. "U" if the event is undetermined and awaiting additional information, column "E" "date incdt clsfd RI-SI" is left blank until a determination is made. The statement "meets the definition of a Runway Incursion refers to the RI definition in force at the time of the incident. On 1 October 2007 the FAA implemented the ICAO definition of a runway incursion. |
| LOC_STATE_CODE_STD | ASIAS STANDARD STATE CODE | The ASIAS standardized code for the state, territory, or foreign location where the event occurred. See Business Rules below for the U.S. code standards and Foreign codes and descriptions. |
| RWY_SFTY_RI_CAT_RNK_CODE | RI CATEGORY RANKING | Enter the appropriate letter determined by the assessment panel. "A" (refers to the severity definition in force at the time of the incident). "B" (refers to the severity definition in force at the time of the incident). "C" (refers to the severity definition in force at the time of the incident). "D" (refers to the severity definition in force at the time of the incident). "E" (this event is an RI, but there is not enough information to assess. "P" (pending severity assessment). "S" (not an RI, but a surface incident for which severity is not assessed). |
| LOC_ARPT_CODE | LOCATION AIRPORT CODE | The code for the airport where the event occurred (if applicable). NOTE: Format is three or four alpha or alpha-numeric characters. |
| EVENT_ARPT_ID | EVENT AIRPORT ID | Three letter airport identifier. When the three letter ID is shaded grey (excel file format only) it depicts a conflict less than a mile and an airport diagram (PDF) is required for the assessment process. |
| LOC_ARPT_NAME_STD | ASIAS STANDARD LOCATION AIRPORT NAME | The ASIAS standardized airport name where the incident occurred (if applicable). |
| EVENT_LOC_DESC | EVENT AIRPORT NAME | Name of airport |
| LOC_NAV_FAC_CODE | LOCATION NAVIGATION FACILITY CODE | The VOR, TACAN, or NDB Identifier used as a reference point to help describe the incident location. NOTE: Format is three alpha or alpha-numeric characters. |
| EVENT_FAA_REGION | FAA REGION | FAA Region |
| LOC_INTXN_ID_CODE | LOCATION INTERSECTION ID CODE | The airway intersection identifier used as a reference point to help describe the incident location. NOTE: Format is five alpha characters. |
| ACFT_1_ID_DESC | AIRCRAFT 1 IDENTIFER | Aircraft call sign. N/R = call sign not reported. N/A = no aircraft involved. In the case of PD, AC1 is the aircraft causing the incident. In the case of V/PD, AC1 is the aircraft affected. In the case of an OE/OD, AC1 and AC2 is reported as it was entered on the OE/OD report forms. |
| LOC_OCEANIC_FLAG | LOCATION OCEANIC FLAG | The code indicating whether the event occurred in oceanic airspace. |
| ACFT_1_RWY_SFTY_TYPE | AIRCRAFT 1 TYPE | Types as defined in FAAH 7110.65 Appendix 1-2-3 |
| RPRT_STATUS_CODE | REPORT STATUS FLAG | The status of the report (Final or Preliminary). |
| ACFT_1_RWY_SFTY_CAT | AIRCRAFT 1 CATEGORY | Aircraft category as defined in FAAH 7110.65 Appendix 1-2-3. |
| EVENT_EVAL_CODE | EVENT EVALUATON CODE | The hazard evalutation code for the incident. See Business Rules below for codes, descriptions, and definitions. |
| ACFT_2_ID_DESC | AIRCRAFT 2 IDENTIFIER | Aircraft call sign. N/R = call sign not reported. N/A = no aircraft involved. In the case of PD, AC1 is the aircraft causing the incident. In the case of V/PD, AC1 is the aircraft affected. In the case of an OE/OD, AC1 and AC2 is reported as it was entered on the OE/OD report forms. |
| EVENT_EVAL_DESC | EVENT EVALUATION DESCRIPTION | The hazard evalutation for the incident. See Business Rules below for valid field values and definitions. |
| ACFT_2_RWY_SFTY_TYPE | AIRCRAFT 2 TYPE | Types as defined in FAAH 7110.65 Appendix 1-2-3 |
| SEPN_SLANT_FT_QTY | SEPERATION SLANT FEET QUANTITY | The diagonal separation between the aircraft (in feet). |
| ACFT_2_RWY_SFTY_CAT | AIRCRAFT 2 CATEGORY | Aircraft category as defined in FAAH 7110.65 Appendix 1-2-3. |
| ACFT_1_FLTCNDT_CODE | AIRCRAFT 1 FLIGHT CONDUCT CODE | Tracking of PD events to determine under what FAR the pilot causing the error was operating under. (1) UNK = Unknown. (2) 121 = aircraft operated under 14 CFR part 121. (3) 129 = aircraft operated under pt 129. (4) 135 = aircraft operated under pt 135. (5) 91 = aircraft operated under pt 91. (6) 125 = aircraft operated under pt 125. (7) MIL = military aircraft. |
| SEPN_VER_FT_QTY | SEPERATION VERTICAL FEET QUANTITY | The vertical separation between the aircraft (in feet). |
| ACFT_2_FLTCNDT_CODE | AIRCRAFT 2 FLIGHT CONDUCT CODE | Tracking of PD events to determine under what FAR the pilot causing the error was operating under. (1) UNK = Unknown. (2) 121 = aircraft operated under 14 CFR part 121. (3) 129 = aircraft operated under pt 129. (4) 135 = aircraft operated under pt 135. (5) 91 = aircraft operated under pt 91. (6) 125 = aircraft operated under pt 125. (7) MIL = military aircraft. |
| SEPN_LONG_MIN_QTY | SEPERATION LONGITUDINAL MINUTES QUANTITY | The number of longitudinal minutes of separation between the aircraft. |
| RWY_SFTY_NARRATIVE | SAFETY OFFICE NARRATIVE | The preliminary summary of an event that is redacted of call signs and personal information from the original narrative. When the report is final and there is additional information that is pertinent, then those comments will be added to the narrative. |
| SEPN_HRZNTL_FT_QTY | SEPERATION HORIZONTAL FEET QUANTITY | The horizontal separation between the aircraft (in feet). |
| RPRT_STATUS_DESC | REPORT STATUS | Tracking of when reports are preliminary and final. This is key to finalizing the data and the runway incursion numbers by mid December of each year for the prior FY. |
| FAC_RPRT_LOC_ID_CODE | FACILITY REPORTING LOCATION ID CODE | The identifier for the facility reporting the event. NOTE: Format is three alpha or alpha-numeric characters per FAA Handbook 7350.6, Location Identifiers. |
| LOC_LONG_DEG_QTY | LOCATION LONGITUDE DEGREES QUANTITY | The location of the NMAC in longitudinal degrees. NOTE: This field is only used if the LOC OCEANIC FLAG field is Y (Yes), otherwise this field is left blank. |
| EVENT_STATE_CODE | EVENT STATE CODE | Use two letter postal code |
| LOC_DRCTN_DEGM_QTY | LOCATION DIRECTION DEGREES MINUTES QUANTITY | The bearing (in degrees) from the NMAC to the fix or facility (found under one of the following fields: LOC NAV FAC CODE, LOC APRT CODE, or LOC INTXN ID CODE). NOTE: The fields LOC DSTC NM QTY and LOC DRCTN DEGM QTY together will make polar coordinate |
| WX_VMC_FLG | VMC FLAG | Identifies if weather was VMC at time of the event. Y (VMC), N = No |
| WX_COND_DESC | WEATHER CONDITION | Reported weather at time of the event using a format of: visibility, cloud layers, wind direction and speed and any obstructions to weather. (10 SM FEW030 BKN045 20010G12KT) |
| FAC_RPRT_RGN_CODE | FACILITY REPORTING REGION CODE | The code for the FAA region where the event occurred. |
| EVENT_DAY_FLG | DAYTIME FLAG | Did event occur during daylight hrs? Y = Yes (Day), N = No, UNK= Unknown |
| FAC_RPRT_RGN_DESC | FACILITY REPORTING REGION DESCRIPTION | The FAA region where the event occurred. |
| EVENT_LCL_TIME | EVENT TIME | The local time when the event occurred. |
| LOC_AIR_SFC_DESC1 | LOCATION AIR SURFACE DESCRIPTION 1 | Indicates whether the first aircraft involved in the event was in the air or on/near the surface (i.e., landing, takeoff, or ground). NOTE: This field value is extracted from the narrative by the data e |
| VEH_ARPT_EMP_FLG | AIRPORT VEHICLE FLAG | Tracking events when an airport vehicle/personnel caused or was involved. Y = Yes, airport personnel or vehicle certified to be operated on the airfield. N = No. Default answer is No. |
| LOC_AIR_SFC_DESC2 | LOCATION AIR SURFACE DESCRIPTION 2 | Indicates whether the second aircraft involved in the event was in the air or on/near the surface (i.e., landing, takeoff, or ground). NOTE: This field value is extracted from the narrative by the data |
| VEH_PRVT_CITZ_FLG | PRIVATE CITIZEN FLAG | Tracking events when a private citizen/POV not authorized on the airfield caused or was involved. Y = Yes. N = No. Default answer is No. |
| OPRTR_NAME1 | OPERATOR NAME 1 | The name of the operator of the first aircraft. NOTE: The operator is the individual, firm, or airline that causes the aircraft to be scheduled, moved, or dispatched. |
| LAW_ENFRCMNT_INVLD_FLG | LAW ENFORCEMENT INVLD FLAG | Tracking events when law enforcement vehicle/personnel caused or were involved. Y = Yes. N = No. Default answer is No. |
| OPRTR_NAME2 | OPERATOR NAME 2 | The name of the operator of the second aircraft. NOTE: The operator is the individual, firm, or airline that causes the aircraft to be scheduled, moved, or dispatched. |
| ACFT_MAINT_TAXI_INVLD_FLG | AIRCRAFT MAINT TAXI INVLD FLAG | Tracking events by aircraft mechanics licensed to taxi aircraft that caused or were involved. Y = Yes. N = No. Default answer is No. |
| OPRTR_NSDC_NAME_STD1 | ASIAS STANDARD OPERATOR NAME 1 | The ASIAS standard for the name of the operator of the first aircraft. |
| FAA_AF_EMP_INVLD_FLG | FAA AF EMP INVLD FLAG | Tracking events when an AF (TECH OPS) employee caused or was involved in an event. Y = Yes. N = No. Default answer is No. |
| OPRTR_NSDC_NAME_STD2 | ASIAS STANDARD AIRCRAFT OPERATOR NAME | The ASIAS standard for the name of the operator of the second aircraft. |
| OPRTR_CO_DESIG_CODE1 | OPERATOR CODE DESIGNATOR CODE 1 | The code for the operator of the first aircraft. NOTE: This field is not standardized. Format is usually 3-4 apha or alpha-numeric characters. |
| ACFT_NSDC_MAKE_STD1 | ASIAS STANDARD AIRCRAFT MAKE 1 | ASIAS's standardized name for the make (manufacturer) of the first aircraft involved in the event. . |
| CNSTRCT_PRSNL_INVLD_FLG | CNSTRCT PRSNL INVLD | Tracking events when construction personnel/equipment caused or were involved. Y = Yes. N = No. Default answer is No. |
| TUG_PRSNL_INVLD_FLG | TUG PRSNL INVLD | Tracking events when a tug driver caused or was involved. Y = Yes. N = No. Default answer is No. |
| ACFT_NSDC_MODEL_STD1 | ASIAS STANDARD AIRCRAFT MODEL 1 | ASIAS's standardized model description of the first aircraft involved in the event. |
| VEH_SNOW_RMVL_FLG | SNOW RMVL VEH INVLD FLAG | Tracking events when snow removal vehicles/personnel caused or were involved. Y = Yes. N = No. Default answer is No. |
| ACFT_NSDC_SERIES_STD1 | ASIAS STANDARD AIRCRAFT SERIES 1 | ASIAS's standardized series description of the first aircraft involved in the event. |
| STDNT_PLT_INVLVD_FLG | STDNT PLT INVLD FLAG | Tracking events when a student pilot caused or was involved. Y = Yes. N = No. Default answer is No. |
| ACFT_MKMD_MAKE_DESC1 | ASIAS STANDARD AIRCRAFT MODEL NAME | The make (manufacturer) name of the first aircraft involved in the event. NOTE: This is not a standardized field. |
| FRGN_ACFT_PLT_INVLD_FLG | FRGN PLT INVLD FLAG | Tracking events when foreign aircraft or pilot caused or was involved. Y = Yes. N = No. Default answer is No. |
| ACFT_MKMD_MODEL_DESC1 | AIRCRAFT MAKE MODEL DESCRIPTION | The model description of the first aircraft involved in the event. NOTE: This is not a standardized field. |
| CNSTRCTN_INVLD_FLG | CNSTRCTN INVLD FLAG | Tracking events when construction on or near a runway or taxiway caused or was involved. Y = Yes. N = No. Default answer is No. |
| OPRTR_TYPE_CODE1 | OPERATOR TYPE CODE 1 | The code for the business nature and/or purpose of the flight and the corresponding Federal Aviation Regulations (FAR) that apply to the first aircraft. |
| OPRTR_TYPE_DESC1 | OPERATOR TYPE DESCRIPTION 1 | The business nature and/or purpose of the flight and the corresponding Federal Aviation Regulations (FAR) that apply to the first aircraft. |
| CTLR_TRNG_INVLD_FLG | CTLR TRNG INVLD FLAG | Tracking events when training was in progress on the specific position that caused or was involved. Y = Yes. N = No. Default answer is No. |
| ACFT_TYPE_CODE1 | AIRCRAFT TYPE CODE 1 | The code for the aircraft type of the first aircraft involved in the NMAC. |
| OES_CMBND_PSTNS | OES COMB POSITIONS | Tracking events when ATCT control positions were combined which could of caused or been a factor. Y = Yes. N = No. UNK = If it is not unknown if positions were combined. |
| ACFT_TYPE_DESC1 | AIRCRAFT TYPE DESCRIPTION 1 | The aircraft type of the first aircraft involved in the NMAC. |
| HLD_SHRT_INTRCTN_FLG | HLD SHRT INTRCTN FLAG | Tracking events when ATCT issues the pilot/vehicle operator/pedestrian instructions to hold short of a specific taxiway or runway. |
| HLD_SHRT_RDBK_FLG | HLD SHRT RDBCK FLAG | Tracking events when pilot/vehicle operator/pedestrian read back specific hold short instructions. Y = Yes. N = No. |
| ACFT_RGSTRTN_NBR1 | AIRCRAFT REGISTRATION NUMBER 1 | The registration number (tail number or 'N' number) of the first aircraft involved in the event. NOTE: U.S. registry starts with "N". For other countries, see FAA Handbook 7340-1, Chapters 1 and 4. |
| HLD_SHRT_CRSD_DESC | HLD SHRT CRSD DESC | Tracking events of where, specific taxiway or point in the runway safety area (RSA) when reported, the aircraft/vehicle/pedestrian crossed a hold line only and did not enter the runway. If unknown use = UNK |
| ACFT_ALT_FT_QTY1 | AIRCRAFT ALTITUDE FEET QUANTITY 1 | Altitude of the first aircraft when the NMAC occurred (in feet above mean sea level (MSL)). |
| RWY_ENTERED_DESC | RWY ENTERED DESC | Tracking events of what specific runway, when reported, the aircraft/vehicle/pedestrian entered. If unknown use = UNK |
| ACFT_SIGHTD_SEC_QTY1 | AIRCRAFT SIGHTED SECONDS QUANTITY 1 | The time (in seconds) that the opposing aircraft was in sight before the closest separation, which gives an idea of how much time the pilot of the first aircraft had to attempt to avoid the NMAC. |
| RWY_TWY_CRSD_DESC | RWY TWY CRSD DESC | Tracking events of what runway or taxiway an aircraft/vehicle/pedestrian crossed. |
| ACFT_RULE_FLT_CODE1 | AIRCRAFT FLIGHT RULE CODE 1 | The code for the type of flight rules that applied to the first aircraft's flight planning and conduct of flight. |
| TIPH_DESC | TIPH DESC | On 30 Sept 2010 phraseology changed to "line up and wait" (LUAW). This column is only populated when that specific instruction was issued. Y = Yes. Left blank otherwise. |
| ACFT_RULE_FLT_DESC1 | AIRCRAFT FLIGHT RULE DESCRIPTION 1 | The type of flight rules that applied to the first aircraft's flight planning and conduct of flight. |
| TIPH_TWOC_FLG | TIPH TWOC FLAG | This column is only populated when that specific LUAW instruction was issued and aircraft departed without clearance. Y = Yes. Left blank otherwise. |
| PHASE_OF_FLIGHT1 | PHASE OF FLIGHT 1 | Indicates the phase of flight the first aircraft was in at the time of the NMAC. NOTE: The format for this field is free-form text. |
| FLT_PHASE_DESC | FLIGHT PHASE DESC | Phase of flight: (1) if two aircraft involved, then the phase of flight for both aircraft, where the order of the aircraft is same order as Column Q (and Columns K and N). Possible answers are T/O = takeoff, LNDG = landing, = TX = Taxi. If there was only one aircraft involved, then only one phase of flight is reported. (2) NA = no aircraft involved. (3) NR = no phase of flight reported or phase of flight unknown. |
| OPRTR_CO_DESIG_CODE2 | OPERATOR CODE DESIGNATOR CODE 2 | The code for the operator of the second aircraft. See Business Rules for examples. NOTE: This field is not standardized. Format is usually 3-4 apha or alpha-numeric characters. |
| EVENT_TKOF_LNDG_DESC | EVENT TKOF LNDG DESC | (1) Landing or Departure Runway number event though an aircraft may inadvertently land or depart from a taxiway. (2) UNK = applies to cases where the runway was unknown. N/A to cases where runway is not applicable such as in a case of a helicopter departing from a ramp or helipad. |
| ACFT_NSDC_MAKE_STD2 | ASIAS STANDARD AIRCRAFT MAKE 2 | ASIAS's standardized name for the make (manufacturer) of the second aircraft involved in the event. . |
| LAHSO_FLG | LAHSO FLAG | Did the event occur during Land and hold short operations (LAHSO)? Y = Yes. N = No or not applicable. Default answer is "N" |
| ACFT_NSDC_MODEL_STD2 | ASIAS STANDARD AIRCRAFT MODEL 2 | ASIAS's standardized model description of the second aircraft involved in the event. |
| ARPT_AMASS_FLG | ARPT AMASS FLAG | (1) AMASS. (2) ASDE. (3) NONE |
| ACFT_NSDC_SERIES_STD2 | ASIAS STANDARD AIRCRAFT SERIES 2 | ASIAS's standardized series description of the second aircraft involved in the event. |
| ACFT_MKMD_MAKE_DESC2 | AIRCRAFT MAKE MODEL DESCRIPTION 2 | The make (manufacturer) name of the second aircraft involved in the event. NOTE: This is not a standardized field. |
| WO_CLRNC_FLG | WO CLRNC FLAG | (1) Y = Yes. (2) N = No or not applicable. Default answer is "N" |
| ARPT_CLSD_RWY_TWY_FLG | CLSD RWY TWY FLAG | (1) Y = Yes. (2) N = No or not applicable. Default answer is "N" |
| ACFT_MKMD_MODEL_DESC2 | AIRCRAFT MAKE MODEL DESCRIPTION 2 | The model description of the second aircraft involved in the event. NOTE: This is not a standardized field. |
| OPRTR_TYPE_CODE2 | OPERATOR TYPE CODE 2 | The code for the business nature and/or purpose of the flight and the corresponding Federal Aviation Regulations (FAR) that apply to the second aircraft. |
| EVENT_FAR_CODE | EVENT FAR CODE | Tracking of PD events to determine under what FAR the pilot causing the error was operating under. (1) UNK = Unknown. (2) 121 = aircraft operated under 14 CFR part 121. (3) 129 = aircraft operated under pt 129. (4) 135 = aircraft operated under pt 135. (5) 91 = aircraft operated under pt 91. (6) 125 = aircraft operated under pt 125. (7) MIL = military aircraft. |
| FAA_SRVC_AREA_DESC | FAA SRVC AREA DESC | Tracking events by the three service areas. (1) EAST = Eastern Service Area. (2) CENTRAL = Central Service Area. (3) WEST = Western Service Area. |
| OPRTR_TYPE_DESC2 | OPERATOR TYPE DESCRIPTION 2 | The business nature and/or purpose of the flight and the corresponding Federal Aviation Regulations (FAR) that apply to the second aircraft. |
| RWSL_EQUIP | RWSL EQUIP | Tracking events at airports equip with Runway Status Lights (RWSL). 1. Yes 2. No 3. Pending = P |
| ACFT_TYPE_CODE2 | AIRCRAFT TYPE CODE 2 | The code for the aircraft type of the second aircraft involved in the NMAC. |
| COLLISION | COLLISON | Tracking of collision events on a runway, runway safety area (RSA), or movement area. 1. Yes. 2. No |
| ACFT_TYPE_DESC2 | AIRCRAFT TYPE DESCRIPTION 2 | The aircraft type of the second aircraft involved in the NMAC. |
| EVENT_HRZ_DSTNC_DESC | EVENT HRZ DSTNC DESC | The distance reported as closest proximity between aircraft, aircraft and a vehicle/pedestrian. (1) Reported in feet when both are on a runway or RSA. (2) Reported in statute miles (with SM notation) when aircraft are issued go around or are airborne when the go around occurs. |
| ACFT_RGSTRTN_NBR2 | AIRCRAFT REGISTRATION NUMBER 2 | The registration number (tail number or 'N' number) of the second aircraft involved in the event. NOTE: U.S. registry starts with "N". For other countries, see FAA Handbook 7340-1, Chapters 1 and 4. |
| EVENT_VRT_DSTNC_DESC | EVENT VRT DSTNC DESC | Distance reported on a flyover or an altitude as the aircraft passes the position of the other aircraft, vehicle, or pedestrian. N/A = does not apply. UNK = Unknown. |
| ACFT_ALT_FT_QTY2 | AIRCRAFT ALTITUDE FEET QUANTITY 2 | The altitude (in feet above mean sea level (MSL)) of the second aircraft when the NMAC occurred. |
| ARPT_VPDS_ATHRTY_FLG | ARPT VPDS ATHRTY FLAG | Was vehicle or personnel authorized to be on the airport movement area. 1. Yes = Y. 2. No = N. |
| ACFT_SIGHTD_SEC_QTY2 | AIRCRAFT SIGHTED SECONDS 2 | The time (in seconds) that the opposing aircraft was in sight before the closest separation, which gives an idea of how much time the pilot of the second aircraft had to attempt to avoid the NMAC. |
| TAXI_IN_FLG | TAXI IN FLAG | Tracking events during the landing phase. This includes aircraft landing without a clearance. 1. Yes = Y. 2. No = N. |
| ACFT_RULE_FLT_CODE2 | AIRCRAFT FLIGHT RULE CODE 2 | The code for the type of flight rules that applied to the second aircraft's flight planning and conduct of flight. |
| TAXI_OUT_FLG | TAXI OUT FLAG | Tracking events during the taxiing out for departure phase. This includes aircraft that taxi out and depart without clearance. 1. Yes = Y. 2. No = N. |
| ACFT_RULE_FLT_DESC2 | AIRCRAFT FLIGHT RULE DESCRIPTION 2 | The type of flight rules that applied to the first aircraft's flight planning and conduct of flight. |
| PHASE_OF_FLIGHT2 | PHASE OF FLIGHT 2 | Indicates the phase of flight the second aircraft was in at the time of the NMAC. See Business Rules for examples. NOTE: The format for this field is free-form text. |
| INTRSCT_RWY_DPTR_ARVL_FLG | INTRSCT RWY DPTR ARVL FLAG | Tracking events that occurred on intersecting runways regardless of it being an arrival or departure at the time. 1. Yes = Y. 2. No = N. |
| RWY_SFTY_ASMNT_RMK | RRUNWAY SAFETY ASSESSMNET | Comments by RI Assessment Panel members, RISC model issues, and reviewed by HQ RSP staff on determination/concur/non-concur of reclassified surface events. |
| ACFT_INVLVD_QTY | AIRCRAFT INVOLVED QUANTITY | The number of aircraft involved in the NMAC. |
| DUP_RPRT_RFRNC | DUP REPORT RFRNC | Enter the report number on surface events that have more than one report filed. The RI is attributed to the report number and type event in column B and C. Otherwise the filed is blank. |
| RMK_TYPE_CODE | REMARK TYPE CODE | Indicates the origin of the narrative or comments/remarks found in the RMK TEXT field. |
| ARPT_139_FLG | PART 139 AIRPORT | Tracking of PART 139 STATUS - PT 139 if the airport is a 139 airport. No = the airport is not part 139. This status is available at faa.gov under airports in excel file format. |
| ARPT_FAA_FCT_TWR_CODE | FAA FCT TOWER FLAG | FAA = if an FAA Tower, FCT = if an Federal Contract Tower |
| ERR_TYPE_CODE | ERROR TYPE CODE | These codes are used for internal analysis of type errors that occur and are not causal factors. A separate spreadsheet is maintained for this purpose. |
| EVENT_DOW_CODE | DAY OF WEEK CODE | Used for internal analysis and to facilitate day of the week queries. Sun. Mon. Tue. Wed. Thu. Fri. Sat |
| EVENT_MONTH_CODE | MONTH CODE | Used for internal analysis and to facilitate monthly queries. Jan. Feb. Mar. Apr. May. Jun. Jul. Aug. Sep. Oct. Nov. Dec. |
| WX_MET_COND_CODE | WEATHER MET CONDITION CODE | The code for the weather condition at the time of the NMAC. NOTE: Based on the pilot(s) report(s) of conditions as well as official weather observations when available. |
| ARPT_OEP_35_FLG | CORE 30 (OEP 35) AIRPORTS | Tracking of events at FAA identified Core 30 airports that came info effect in 2011. The Core 30 were part of the OEP 35 and for historical purposes the OEP airports will be maintained. |
| WX_MET_COND_DESC | WEATHER MET CONDITIONS DESCRIPTION | The weather condition at the time of the NMAC. NOTE: Based on the pilot(s) report(s) of conditions as well as official weather observations when available. |
| RWY_SFTY_PDF_ASSMNT_FLG | ARPT DIAGRAM ASSMT REQ | Y = Yes. When an airport diagram is required to evaluate and assess a runway incursion (RI). Normally required for potential A-C rankings. Otherwise left blank. |
| RWY_SFTY_TRFC_MIX_CODE | TRFC MIX CODE | This columns was added on 1 October 2005. Internal use to show who is involved in an event that simplifies queries using the traffic mix column. |
| HOT_SPOT_EVENT | HOT SPOT EVENT FLAG | Starting in FY11, tracking of events that occurred at a specific hot spot identified on an airport diagram. The parameter is that the aircraft, vehicle, or pedestrian entered the hot spot area without authorization. "Y" - yes, "N" - no, "NOT AVL" - indicates that this information was not tracked prior to 1 Oct 2010. The airport diagrams changed numerous times during a specified year with hot spots being added/deleted thus the event could not be verified as to whether there was a hot spot violation or not. |
| ADSB_EQUIP | ADSB EQUIP | Place holder for the future on tracking events with ADSB in placed and used for runway safety purposes. |
| RWY_SFTY_RISK_SCNRIO_CODE | RISC SCENERIO NBR | Scenario code used in RISC model - This model was first tested in October 2005 but originally the scenario code was not available. |
| WX_VIS_CODE | WEATHER VISIBILTIY CODE | The code for the visibility at flight altitude during the NMAC. |
| RWY_SFTY_RISK_RNK_CODE | RISK ASSMNT RANKING | This model was first tested in October 2005 and the category ranking is not available prior to this date. Ranking determined by the RISC model based on the facts entered to include the scenario number in previous column. (1) A (refers to the severity definition in force at the time of the incident). (2) B (refers to the severity definition in force at the time of the incident). (3) C (refers to the severity definition in force at the time of the incident). (4) D (refers to the severity definition in force at the time of the incident). (5) E (this event is an RI, but there is not enough information to assess. (6) P (pending severity assessment). (7) S (not an RI, but a surface incident for which severity is not assessed). |
| IN_ATQA | IN ATQA FLAG | Y = Yes. N = No. Administrative tracking of surface reports in ATQA. Used to validate the events in runway safety database and what is in ATQA. |
| WX_VIS_DESC | WEATHER VISIBILITY DESCRIPTION | The visibility at flight altitude during the NMAC. |
| ARPT_ID | AIRPORT ID | Duplicate of column H and tied to column BX for Original Narrative. |
| FLIGHT_CONDITIONS | FLIGHT CONDITIONS | Indicates the type of flight condition at the time of the NMAC. NOTE: This field is free-form text. |
| ORIGINAL_NARRATIVE | ORIGNAL NARRATIVE | Original event narrative from the ATO Daily Event Report that includes call signs. |
| WX_SKY_CODE | WEATHER SKY CODE | The code for the sky cover at flight altitude during the NMAC. |
| WX_SKY_DESC | WEATHER SKY DESCRIPTION | The code for the sky cover at flight altitude during the NMAC. |
| ICAO_STDS_RI_FLG | MEETS ICAO RI STNDS FLAG | FAA transitioned to the ICAO RI standard on 1 Oct 2007 and established specific criteria of what met a runway incursion at all FAA/FCT towered airports. FAA RI's prior to that date are official runway incursions per the previous FAA criteria of an aircraft/vehicle/pedestrian unauthorized on a runway or in the runway safety area (RSA) as identified for each specific airport. This include any violation of a hold line that protected a runway surface. One or more of the violaters had to be on the runway surface, across the hold short line or in the RSA to be considered a surface event to include loss of separation on a runway. In addition the previous FAA RI criteria specified that if an aircraft was less than a mile from landing and an aircraft, vehicle or pedestrian violated the protected landing surface then it was considered a runway incursion. This also included loss of separation on a runway. If there were no other aircraft involved or the landing aircraft was one mile or mile from landing then it was considered a surface event and not an RI. The surface event database was populated with this column in 2001 for FY01-07 so as to provide senior leadership the amount of events that would meet the ICAO RI standard if it were implemented. The ICAO numbers for FY2001-2007 are prior to FAA implementation on 1 October 2007 and is included for analytical purposes only and is not to be misconstrued as actual FAA RI’s. The category rankings given in FAA briefings are base on converting the FY01-07 Category D's to "C" and adding them to the "C" totals. The other events that were not RI's prior to 1 Oct 07 but met the ICAO RI standard were converted to Category "D" events. The Category A/B remained the same. |
| FAC_ATC_DESC1 | FACILITY ATC DESCRIPTION 1 | The ATC facility in control of the first aircraft involved in the NMAC. |
| FAC_ATC_DESC2 | FACILITY ATC DESCRIPTION 2 | The ATC facility in control of the second aircraft involved in the NMAC. |
| ACFT_CTL_DESC1 | AIRCRAFT CONTROL DESCRIPTION 1 | Describes the operational control area (airspace) of the first aircraft at the time of the NMAC. |
| ACFT_CTL_DESC2 | AIRCRAFT CONTROL DESCRIPTION 2 | Describes the operational control area (airspace) of the second aircraft at the time of the NMAC. NOTE: This field is used only if the operational control area of the second aircraft is different from the first aircraft. |
| ACFT_HDG_DEGM_QTY1 | AIRCRAFT HEADING DEGREES MINUTES QUANTITY 1 | The direction, in degrees magnetic (i.e., 0-359), that the first aircraft was heading at the time of the NMAC. |
| ACFT_HDG_DEGM_QTY2 | AIRCRAFT HEADING DEGREES MINUTES QUANTITY 2 | The direction, in degrees magnetic (i.e., 0-359), that the second aircraft was heading at the time of the NMAC. |
| ACFT_IAS_KT_QTY1 | AIRCRAFT AIRSPEED KNOTS QUANTITY 1 | The airspeed, in knots, as indicated on the first aircraft's airspeed indicator at the time of the NMAC. |
| ACFT_IAS_KT_QTY2 | AIRCRAFT AIRSPEED KNOTS QUANTITY 2 | The airspeed, in knots, as indicated on the second aircraft's airspeed indicator at the time of the NMAC. |
| OPRTR_MIL_BRANCH_CODE1 | OPERATOR MILITARY BRANCH CODE 1 | The code for the branch of service, if a military operator, of the first aircraft. NOTE: This field is left blank if the aircraft is not military. |
| OPRTR_MIL_BRANCH_CODE2 | OPERATOR MILITARY BRANCH CODE 2 | The code for the branch of service, if a military operator, of the second aircraft. NOTE: This field is left blank if the aircraft is not military. |
| OPRTR_MIL_BRANCH_DESC1 | OPERATOR MILITARY BRANCH DESCRIPTION 1 | The branch of service, if a military operator, of the first aircraft. NOTE: This field is left blank if the aircraft is not military. |
| OPRTR_MIL_BRANCH_DESC2 | OPERATOR MILITARY BRANCH DESCRIPTION 2 | The branch of service, if a military operator, of the first aircraft. NOTE: This field is left blank if the aircraft is not military. |
| PLT_TOTAL_HR_QTY1 | PILOT TOTAL HOURS QUANTITY 1 | The total flight time, in whole hours, of the pilot of the first aircraft. |
| PLT_TOTAL_HR_QTY2 | PILOT TOTAL HOURS QUANTITY 2 | The total flight time, in whole hours, of the pilot of the second aircraft. |
| PLT_MKMD_HR_QTY1 | PILOT MAKE MODEL HOURS QUANTITY 1 | The flight time, in whole hours, of pilot of the first aircraft in the same make and model aircraft involved in the NMAC. |
| PLT_MKMD_HR_QTY2 | PILOT MAKE MODEL HOURS QUANTITY 2 | The flight time, in whole hours, of pilot of the second aircraft in the same make and model aircraft involved in the NMAC. |
| PILOT_CERT_DESC1 | PILOT CERTIFICATION DESCRIPTION 1 | Indicates the type of certificate held by the pilot of the first aircraft. |
| PILOT_CERT_DESC2 | PILOT CERTIFICATION DESCTIPTION 2 | Indicates the type of certificate held by the pilot of the second aircraft. |
| PILOT_RATING_DESC1 | PILOT RATING DESCRIPTION 1 | Indicates the type of rating held by the pilot of the first aircraft. |
| PILOT_RATING_DESC2 | PILOT RATING DESCRIPTION 2 | Indicates the type of rating held by the pilot of the second aircraft. |
| ACFT_TRNSPNDR_CODE1 | AIRCRAFT TRANSPONDER CODE 1 | The code indicating information about the transponder of the first aircraft. NOTE: A transponder is the airborne radar beacon transmitter/receiver portion of the Air Traffic Control Radar Beacon Sys |
| ACFT_TRNSPNDR_CODE2 | AIRCRAFT TRANSPONDER CODE 2 | The code indicating information about the transponder of the second aircraft. NOTE: A transponder is the airborne radar beacon transmitter/receiver portion of the Air Traffic Control Radar Beacon System |
| ACFT_TRNSPNDR_DESC1 | AIRCRAFT TRANSPONDER DESCRIPTION 1 | Information about the transponder of the first aircraft. NOTE: A transponder is the airborne radar beacon transmitter/receiver portion of the Air Traffic Control Radar Beacon System (ATCRBS) located |
| ACFT_TRNSPNDR_DESC2 | AIRCRAFT TRANSPONDER DESCRIPTION 2 | Information about the transponder of the second aircraft. NOTE: A transponder is the airborne radar beacon transmitter/receiver portion of the Air Traffic Control Radar Beacon System (ATCRBS) located on |