ATO Metric Reports:AJR-1 Summary Reports

From ASPMHelp
Jump to: navigation, search

The AJR-1 Summary Reports of ATO Metric Reports display data about totals system delays, diversions, and customer comments for the selected date. Summary reports can be generated for the eight days prior to the current date.


Field definitions are available in ASPM ATO Metric Reports: Definitions of Variables.

ATO AJRSummary.png

The AJR-1 Summary Reports displays the following fields:

  • Total System Delays. Total number of NAS System Impacted delays affecting operations on the selected date.
  • Diversions. Counts of flights that were diverted from their originally intended arrival airport. Listed are diversion totals from ASPM 77 and Core 30. Also listed are the facilities and count of diversions to the right of it for the Core 30 airports and any facility that is a member of the ASPM 77 with eight or more diversions listed beside “Other[8+].”
  • Facilities with 26+ Delays. All facilities (including ARTCCs and TRACONs) that had 26+ of more NAS system impacted delays. (Source: OPSNET)
    • Facility. Three-letter code identifying the facility.
    • Total. Total number of system impacted delays.
    • Traffic Management Initiative (TMI) To Delays. Delays resulting from a national or local traffic management initiative as reported in OPSNET and charged to the facility that is the originating cause of the restriction. The facility may be either an airport, TRACON, or ARTCC. Such initiatives include departure spacing (DSP), en route spacing (ESP), arrival spacing (ASP), miles-in-trail (MIT), minutes-in-trail (MINIT), Estimated Departure Clearance Time (EDCT), Ground Stops, and Severe Weather Avoidance Plan (SWAP). These delays may be experienced by aircraft at another facility, but are charged to the causal facility. They are a component of System Impact Delays.
    • Departure Delays. Number of total local departure delays attributed to conditions at the departure airport, local TRACON, or Center. A component of System Impact Delays (departure) and Occurred at Delays (TMI from: Local).
    • Airborne Holding. The number of airborne holds that experience a delay of 5 minutes or more (individual flight entry reported by PDARS through OPSNET).
  • Ground Stops. Ground Stop Program details by facility.
    • Facility. Three-letter code identifying the facility.
    • Date. Local date the program occurred (day of week, month, and day).
    • Time. GMT Time the program occurred.
    • Reason. Reason for Ground Stop program.
  • Ground Delay Programs. Ground delay Program details by facility.
    • Facility. Three-letter code identifying the facility.
    • Date. Local date the program occurred (day f week, month, and day).
    • Time. GMT time the program occurred.
    • Reason. Reason for Ground Delay program.
  • AFPs. Airspace Flow Programs details by facility in effect for the specified date(s). An AFP is a traffic management initiative that identifies en route constraints en route and distributes Expect Departure Clearance Times (EDCT) to aircraft with flight plans through that airspace to meter the demand through the area. The principal goal is to provide en route traffic management during severe weather events, but they are also applied to other constraints.
    • Facility. Three-letter code identifying the facility.
    • Date. Local date the program occurred (day of week, month, and day).
    • Time. GMT Time the program occurred.
    • Reason. Reason for program.
  • CTOPs. Collaborative Trajectory Options Programs in effect for the specified date(s). A CTOP is a traffic management initiative that automatically assigns delay and/or reroutes aircraft around one or more flow constrained areas. CTOP is collaborative in that it allows operators to submit a set of desired reroute options in advance of the issuance of the program, and may allow aircraft to avoid GDPs.
    • Facility. Three-letter code identifying the facility.
    • Date. Local date the program occurred (day of week, month, and day).
    • Time. GMT Time the program occurred.
    • Reason. Reason for program.
  • Customer Comments. Customer comment and ATCSCC Comments (NOM comments).
    • Facility. Three-letter code identifying the facility.
    • Date. Local date the program occurred (day of week, month, and day).
    • Time. GMT Time the program occurred.
    • Memo. Comment content.

For information about other available reports in the ATO Metric Reports module, see the ATO Metrics manual.