Aviation System Performance Metrics (ASPM)
The Aviation System Performance Metrics (ASPM) online access system provides data on flights to and from the ASPM airports (including the Core 30 and OEP 35 aiports), and all flights by ASPM carriers, including flights by those carriers to international and domestic non-ASPM airports. All IFR and some VFR flights are included. ASPM data can be viewed on the FAA Operations & Performance Data website.
ASPM flight records fall into two groupings:
- Efficiency flights are intended to capture all traffic handled by controllers at the ASPM airports. Some Efficiency records may be missing one or more pieces of key data, especially next-day before they are updated/finalized. ASPM Metrics flights include flights to or from the ASPM airports, as well as all other flights by the ASPM carriers. Metric flights are the basis of delay calculations displayed in the Analysis and Individual Flights modules. They only include complete records and records for which accurate estimates are possible for the few pieces of missing data.
- Metrics flights exclude general aviation and military traffic, as well as local (non-itinerant) traffic and records for international flights missing data on the non-U.S. portion of the flight.
The purpose of these two groupings is to allow for a more complete traffic count (Efficiency flights) while ensuring that only records with fully specified flight information are used for calculating delay and other metrics. Flight cancellations are excluded from both Efficiency and Metrics flights.
ASPM reports also provide data on airport weather, runway configuration, and airport arrival and departure rates. This combination of flight and airport information provides a robust picture of air traffic activity for these airports and air carriers. Preliminary next-day ASPM data (login required) are used by the FAA for close monitoring of airport efficiency and other aspects of system performance and finalized ASPM data are invaluable for retrospective trend analysis and targeted studies.
The ASPM database is compiled piece by piece beginning with basic flight plan and other message data for flights captured by the Traffic Flow Management System (TFMS), enhanced with next-day OOOI data, updated with published schedule data, and further updated and enhanced with BTS Airline Service Quality Performance (ASQP) records which include OOOI data, final schedule data, and carrier-reported delay causes for the largest U.S. carriers.
The components of today's ASPM have been developed and extensively examined over many years by stakeholders, including FAA internal organizations and many of the major airlines and aviation research groups. Each step of the ASPM process has been debated, tested, and tuned. At each point, our goal has been to implement decision rules that result in the most complete and valid representation of air traffic possible given the quality and quantity of data available.
The ASPM system consists of the following modules:
- Airport Analysis: Provides information on aircraft departure and arrival times and flight delays at selected airports compared to the schedule and flight plan times. Flights included are Arrivals and Departures for Metric Computation.
- City Pair Analysis: Provides information on aircraft departure and arrival times and flight delays between city pairs compared to the schedule and flight plan times. Flights included are Arrivals and Departures for Metric Computation.
- Taxi Times: Contains data on actual and unimpeded taxi times by airport.
- Individual Flights: Provides information on aircraft departure and arrival times and flight delays for individual flights compared to the schedule and flight plan times. Flights included are Arrivals and Departures for Metric Computation.
- Cancellations: Provides reports of cancelled flights and completion rates.
- Airport Efficiency: Contains data on Terminal and System airport efficiency measures and the flights used for those computations. Flights included are Arrivals and Departures for Efficiency Computation. It also includes certain general aviation, military, and other flights not included in the Airport Analysis, City Pair Analysis, and Individual Flights modules.
- Throughput: Contains data on actual airport throughput (number of arrivals and departures) in a defined period of time.
- City Pair Enroute: Provides average distance and time data on city pair routes of 300 miles or more.
- Arrival Airport Enroute: Provides average distance and time data on all flights of 300 miles or more arriving at a selected airport.
- AERO: Limited distribution next day airport and system dashboards.
- ATO Metric Reports:
- Weather Factors: Categorizes and reports on the severity of individual weather factors in terms of their impact on flight delays at selected airports. Similar weather can have different delay impacts across airports.
- Diversions: Provides information on flight diversions as detected by an algorithm written by Mitre.
- Advisories: Provides detail and summary reports on traffic management initiatives, operations plans, and other advisories from the NTML data warehouse.
- Data Download: Provides detailed APM data for Airport (by hour and by quarter), Individual Flights, and Cancellations. Data are provided via e-mail in Excel format.
A username and password is required to access ASPM reports that contain preliminary data, individual flight information, and other restricted areas. You may request a login from the FAA by following the login prompt on the FAA Operations & Performance Data website.
General public customers without a login can access Airport Analysis, City Pair Analysis, and Taxi Time data within 60 days after the end of the month; i.e., June data will be available no later than September 1.
Data Sources and Update Cycle
ASPM data come from the following sources:
- Traffic Flow Management System (TFMS): Every day, ASPM is updated using preliminary next-day TFMS data and enhanced five-day data which revises records received in the previous five days with additional information. In addition, approximately 10 days after the end of each month, TFMS data for the previous month are finalized.
- Airline Service Quality Performance (ASQP): ASQP data are loaded on a monthly basis, approximately 25 days after the end of the month. At that time, ASPM records are updated/modified with new or revised flight information from ASQP records including OOOI data, final schedule data, and carrier-reported delay causes for the largest U.S. carriers.
- OOOI Data: ASPM is updated daily with OOOI data provided by ARINC and TFMS for several airlines. When ASQP data are received at the end of the month, the OOOI data from ASQP supplants the ARINC and TFMS OOOI data for matching flights.
- CountOps: CountOps provides individual flight data for OPSNET. Since October 1, 2012, ASPM records are updated daily with Threshold Crossing Times for departures and arrivals from CountOps. The Threshold Crossing Time is typically within seconds of the Wheels Off and Wheels On times and is now being used to populate those fields when no ARINC, TFMS, or ASQP data are available.
- Flight Schedule Data System (FSDS): From January 2000 through November 2008 the data source for the FSDS was the Official Airline Guide (OAG). Beginning December 2008 the data source was changed to Innovata.
The following applies to the availability of ASPM data:
- Data are available from January 2000 to present for 55 airports. Data for 20 additional airports are available from October 2004 to present. Data for two additional airports are available from January 2007 to present.
- Access to preliminary data and certain reports is restricted by password.
- Data are internet-accessible by 0700 each weekday.
Aside from periodic updates corresponding with the availability of new data, historical ASPM data are modified once per year, typically in May, based on revised unimpeded taxi times by airport as calculated using data from the previous calendar year. At that time, records for the current calendar year through the previous month are modified. In addition, ASQP data and other input files are occasionally re-reported to correct an error or omission. As a result, ASPM data should not be considered final until approximately 90 days after the end of each fiscal year.
The following links provide more detail on the calculation of measures contained in ASPM.
For a detailed explanation of how to create reports using the ASPM interface, use the manual specific to each ASPM views as listed in ASPM Manuals.
Definitions of Variables
For more information about these topics, please see the Definitions of Variables specific to each module of the APM system as listed in ASPM Manuals.