PART 244 – Tarmac Delay Data

PDF

OMB No: 2105-0561

EXPIRATION DATE: 10/31/2021

REQUIREMENTS

RECORD DESCRIPTION: Tarmac Delay Data

RECORD FORMAT:

The Tarmac Delay Data reports must be reported in the following format, according to PART 244 of CFR 14, and as required by Directive No. 303, Issue Date: June 10, 2011, Effective Date: August 23, 2011.

This data is reported by all U.S and foreign air carriers that operate to a U.S. non-hub, small hub, medium hub, or large hub airport with at least one aircraft having an original manufacturer’s design capacity of 30 seats or more. Please refer to additional guidance below, copied from Directive 303.

This report must be created as an electronic “comma separated values” file, using ASCII text character encoding, for uploading via the “eSubmit” application.

The comma separated values file MUST BE indicated when naming the file, by using the letters [CSV] or [csv] following the file name, as the file name extension.

The file name is flexible and may be determined by the individual air carrier, but the comma separated values (csv) file format is required, as outlined in the rule entitled, Submitting Airline Data via the Internet.

The fields in the sample record shown below follow the same order as the above record description, separated by commas, and saved with the file name extension of .csv.

Suggested file name: XX201003-244Tarmac.csv

Sample Record Format using data shown in the above table:

XX,1234,DFW,BNA,20110823,0737,1245,1410,1417,N736ZZ,,,,,,,,,,,,

Part 244 – Reporting of Tarmac Delay Data

Reporting Air Carriers are all U.S and foreign air carriers that operate to a U.S. non-hub, small hub, medium hub, or large hub airport with at least one aircraft having an original manufacturer’s design capacity of 30 seats or more. Must register to E-submit Part 244 data by August 26, 2011. Carriers are not required to submit reports for the months where no 3-hour tarmac times occurred.

1. U.S. air carriers that submit Airline Service Quality Performance Reports must now submit a secondary report under Part 244 for any charter passenger flight or any international passenger flight that is on the tarmac at any U.S. large hub airport, medium hub airport, small hub airport or non-hub airport for 3 or more hours if the passengers were not provided an opportunity to deplane. Tarmac delays experienced at foreign airports are not reported. Also, flights that are reported under the requirements of Part 234 Airline Service Quality Performance Reports are not reported under Part 244.

2. Commuter air carriers that operate at least one aircraft having an original manufacturer’s design capacity of 30 seats or more must report tarmac delay data for all passenger operations that experience a tarmac time of 3 hours or more at a U.S. airport. Tarmac delays experienced at foreign airports are not reported.

3. Certificated air carriers that do not submit Airline Service Quality Performance Reports and operate at least one aircraft having an original manufacturer’s design capacity of 30 seats or more must report tarmac delay data for all passenger operations that experience a tarmac time of 3 hours or more at a U.S. airport. Tarmac delays experienced at foreign airports are not reported.

4. Foreign air carriers that operate at least one aircraft having an original manufacturer’s design capacity of 30 seats or more must report tarmac delay data for all passenger operations that experience a tarmac time of 3 hours or more at a U.S. airport. Tarmac delays experienced at foreign airports are not reported. Also, charter flights are not subject to this rule when the foreign air carrier operates from a foreign airport to a U.S. airport and returns to a foreign airport, if the carrier did not enplane any new passengers in the United States.

5. Carriers are not required to report actual times for gate departures and arrivals and wheels-off and wheels-on at foreign airports. Carriers have the option of reports nil fields, a 0, or the actual time.

6. Do not report all-cargo flights (no passengers on-board).

Reporting Frequency

With the exception of the initial report, Part 244 data submissions are based on calendar months; and the reports are due 15 days after the end of the calendar month. Due dates falling on Saturdays, Sundays and federal holidays are automatically extended to the next federal work day

The initial report will cover the reporting period from August 23 through September 30, 2011; and will be due on October 17, 2011, as October 15 falls on a Saturday.

Record Format:

The Tarmac Delay Data reports must be created as an electronic “comma separated values” file, using ASCII text character encoding, for uploading via the “eSubmit” application.

The comma separated values file MUST BE indicated when naming the file, by using the letters [CSV] or [csv] following the file name, as the file name extension.

The file name is flexible and may be determined by the individual air carrier, but the comma separated values (csv) file format is required, as outlined in the rule entitled, Submitting Airline Data via the Internet.

The fields in the sample record shown below follow the same order as the above record description, separated by commas, and saved with the file name extension of .csv.

Suggested file name: XX201003-244Tarmac.csv

The web address for data submission is http://esubmit.rita.dot.gov

We are scheduled to have the web reporting application ready for you to access on August 1, 2011. Please contact Marianne Seguin at marianne.seguin@dot.gov to set up your carrier’s account for reporting Part 244 data. Your account will need to be established and ready for reporting this data by August 26, 2011.

Definitions:

1. 'Gate arrival time' is the instance when the pilot sets the aircraft parking brake after arriving at the airport gate or passenger unloading area. If the parking brake is not set, record the time for the opening of the passenger door. Also, carriers using a Docking Guidance System (DGS) may record the official “gate-arrival time” when the aircraft is stopped at the appropriate parking mark.

2. 'Gate departure time' is the instance when the pilot releases the aircraft parking brake after passengers have loaded and aircraft doors have been closed. In cases where the flight returned to the departure gate before wheels-off time and departed a second time, report the last gate departure time before wheels-off time. In cases of an air return, report the last gate departure time before the gate return. If passengers were boarded without the parking brake being set, record the time that the passenger door was closed. Also, carriers using a DGS may record the official “gate-departure time” based on aircraft movement. For example, DGS records gate departure time when the aircraft moves more than 1 meter from the appropriate parking mark within 15 seconds. Fifteen seconds is then subtracted from the recorded time to obtain the appropriate out time.

3. “Gate Return” is when an aircraft leaves the boarding gate only to return to a gate for the purpose of allowing passengers to de-board the aircraft.

4. “Time”- all times are reported in local time using a 24 hour clock; e.g. 3:15 p.m. will be 1515, midnight is 2400, and one minute after midnight is 0001.

Reporting Example – A flight with a 308 minute taxi-out time:

Items 13 through 17 are for diverted flights; and items 18 through 22 are for reporting a second diverted flight segment.

Use consecutive commas (,,) to identify ‘nil’ fields. If there are no diversions use consecutive commas (,,) to identify those ‘nil’ fields.

Sample Record Format:

ZZ,1234,DFW,BNA,20110823,0737,1245,1410,1417,N736ZZ,,,,,,,,,,,,

Reporting Example – Flight was on the tarmac for 201 minutes then returned to the gate to allow passengers to deplane and then after another hour re-departed:

Items 13 through 17 are for diverted flights; and items 18 through 22 are for reporting a second diverted flight segment.

Use consecutive commas (,,) to identify ‘nil’ fields. If there are no diversions use consecutive commas (,,) to identify those ‘nil’ fields.

Sample Record Format:

ZZ,1234,DFW,BNA,20110823,1230,1245,1410,1417,N736ZZ,201,201,,,,,,,,,,

Note: In this case, the flight returned to the departure gate before wheels-off time and departed a second time, therefore, you must report the last gate departure time which is before wheels-off time.

Reporting Example – Flight diverted to an alternate airport and spent 185 minutes on the tarmac:

Use consecutive commas (,,) to identify ‘nil’ fields.

Sample Record Format:

ZZ,1234,DFW,BNA,20110823,0737,0757,1306,1317,N736ZZ,,,MEM,0914,185,185,1219,,,,,

Reporting Example – Flight experiencing two diversions:

Use consecutive commas (,,) to identify ‘nil’ fields.

Sample Record Format:

ZZ,1234,DFW,BNA,20110823,0737,0757,1650,1657,N736ZZ,,,MEM,0914,185,185,1219,DFW,1359,60,60,1459

Reporting Example – Foreign Carrier who is not reporting foreign Gate Departure or Wheels-Off Time – but is reporting the 4 hour 23 minute taxi-in time at JFK

Use consecutive commas (,,) to identify ‘nil’ fields.

Sample Record Format:

FF,1234,LHR,JFK,20110711,,,1942,2355,X763FF,,,,,,,,,,,,