|
|
|
The controlling documents for traffic counting and classification index (CI) calculation are the Position Classification Standard for Air Traffic Control, Series ATC-2152 Terminal and En Route, dated January 12, 1999 and FAA Order 7210.57, Traffic Counting, Reporting, and Processing for Determining Facility Classification Levels, dated November 11, 1998. The following Frequently Asked Questions must be read in conjunction with these documents and is intended to clarify counting procedures addressed therein. In the unlikely event of a conflict between these Frequently Asked Questions and the above referenced documents, the issue will be elevated to the National Validation Team for resolution. The material contained herein reflects the best intention of the parties and may be modified if it becomes apparent that the counting procedure does not meet the intent or spirit of the controlling documents.
Documents and Definitions The Position Classification Standard for Air Traffic Control, Series ATC-2152 Terminal and En Route, dated January 12, 1999 and FAA Order 7210.57, Traffic Counting, Reporting, and Processing for Determining Facility Classification Levels, dated November 11, 1998. On the internet at the Air Traffic Compensation website ( http://atpay.faa.gov) or the National Air Traffic Controllers Association website at http://atpayplan.natca.net/
Over-Flight Operations The definition of over-flight is as follows: "Aircraft that transit a facility’s airspace that neither originate nor terminate within that facility’s airspace." Simply, to be considered an overflight, the aircraft must neither land nor depart within your airspace. Additionally, the traffic must penetrate the actual airspace of the receiving facility. Protected airspace outside of the actual airspace limits does not qualify. Actual airspace does not include receiving facility airspace delegated to another facility via Letter of Agreement, Memorandum of Understanding or Agreement, or any other arrangement (written or verbal) between the facilities. For the Tower count, each aircraft operation will be counted as one overflight even though the aircraft may penetrate your airspace numerous times. Once that aircraft is identified and provided a clearance, it is the controller’s responsibility to keep track of the movements of that aircraft and to relay that information to any additional control positions impacted by this operation. However, an exception to this may occur if the helicopter flies an extended route away from the tower that requires a point-out, hand-off or termination of service each time before returning and penetrating tower airspace. A separate count for each such occurrence may be taken.Normally, a single point out from approach is sufficient to provide adequate service and monitoring for these aircraft. However, if the route of flight is such that the aircraft leaves the area and approach is required to point out the aircraft again, you can take one overflight count for each occurrence. If approach does not point the aircraft out again it is a one count The operation must not be landing or departing your airport. The Tower must own the airspace the operation is occurring in. If your Tower owns the airspace then delegates it away for any reason (e.g. runway configuration) this no longer considered your airspace. No. Facility airspace delegated to another facility via Letter of Agreement, Memorandum of Understanding or Agreement, or any other arrangement (written or verbal) between the facilities becomes the other facility’s airspace and any operations within that airspace cannot be counted by your facility. No. The TRACON would count this as 1 secondary VFR departure and 1 secondary VFR arrival. If these operations occurred fully within tower airspace the tower would get two VFR overflight counts. Since there are no provisions in the TTAP program for Towers to count secondary operations, it has been determined that Towers be permitted to count these operations as overflights. For example, a hospital is located 2 miles from the airport in Towers’ airspace where helicopter traffic frequently depart and exit Towers’ airspace. The Tower would count that helicopter operation as an overflight. No. Once the aircraft enters your facility airspace you get only one count for that operation. Towers and TRACON count this operation independently of one another. No. You are already working the aircraft and have received the appropriate count. In order to receive another count the aircraft must be handed off, communications transferred, the aircraft must have left your facility airspace and subsequently re-entered your airspace via a point out or hand-off. The facility should count this aircraft as an IFR overflight since the aircraft does not originate or terminate within your airspace. . Local Operations The Tower will get a local count for each arrival and each departure. No. Assuming you have provided the original takeoff clearance, this is considered one local aircraft operation. After that point you have given the helicopter approval to operate without ATC service. It depends. If you are providing taxi clearance (movement area) or acknowledging taxi within a non-movement area there is no count authorized. . If the operation is structured as such that you must provide a departure clearance to the practice area, and a landing clearance upon completion, you may count only the initial departure and final arrival operation as a local operation. The auto-rotation activity is considered to be operating independently of ATC control and no count is authorized unless ATC must provide departure and landing clearance for each individual operation. No. The Tower is already getting an itinerant arrival and an itinerant departure for this aircraft conducting the practice approach. To also take a local arrival and a local departure would be double counting the aircraft operation. No. The TRACON receives no credit for local operations. If you point out the aircraft each and every time, a separate count for each occurrence may be taken as long as the aircraft penetrates the TRACON’s airspace and there is no agreement to allow the operation to take place without the point out. Practice Approaches A VFR practice instrument approach is counted as an IFR operation for that segment of the flight where the aircraft is provided IFR separation. In most cases this is only the approach phase of the flight. The departure phase will be counted as a VFR unless the pilot REQUESTS and receives authorization to fly the published missed approach in it's entirety. If the latter occurs then the departure segment would be counted as an IFR. Assigning a heading and altitude to the aircraft on the departure phase is not the published missed approach procedure and requires the count to be a VFR departure. No, the same rules for counting practice approaches apply to secondary airports. In the event that IFR separation services are not provided, the operation is counted as VFR. If the controlling authority has a published letter to airman that states separation services will not be provided, then all flight segments shall be counted as a VFR. The approach phase is counted as an itinerant IFR arrival, then all subsequent operations will be counted as local operations. Practice approach aircraft that are provided separation services can be counted as both an IFR arrival and an IFR (or VFR) departure only if the practice approach aircraft actually penetrates Tower’s airspace before being ‘broken-off’ the approach.
Point-Outs This aircraft can only be counted if it actually penetrates your facility’s airspace. No aircraft can be counted if there is only the potential of entering a facility’s airspace. No, overflights can only be counted if the aircraft penetrates your airspace. In this case, your Tower does not own any airspace. Departure corridors are not considered Tower airspace. In this example, Tower airspace is surface to 3,000’, 5 miles. Although this procedure facilitates expeditious handling of departure traffic, Tower does not own that airspace and therefore cannot count traffic that transits above 3,000’. No. The Tower can only count this aircraft as an itinerant (IFR/VFR) arrival to the primary airport. Yes, provided that the aircraft operation meets the definition of an overflight. The Tower hourly classification index is calculated separately from the TRACON’s hourly classification index. They are added together to obtain a combined hourly classification index. If you have an agreement (verbal or written) with the facility that is actually working the aircraft, which requires the penetrating aircraft to remain identified by some means be it a transponder code or some other method of identification, you may only count one overflight even though the aircraft may transverse your airspace numerous times. If that same aircraft is verbally coordinated and pointed out each time it actually penetrates your airspace, you can count each point-out that it is called to your facility.
Miscellaneous Operations No. This isn’t a new operation just a change in flight status for an existing one. The facility should take credit for the operation that provides the greatest weight. Since a portion of this flight was flown IFR, the facility gets credit for working this aircraft as an IFR overflight. This is considered one IFR aircraft operation. You do not get to count this as a VFR overflight as well. No, the count to be taken is what provides the facility the greatest weight. In this case, the greater weight is to count this aircraft as an IFR departure since the facility gets more credit than if this aircraft was counted as a secondary VFR departure. If it can be determined upon initial contact that the aircraft originated from a satellite airport within your airspace, count this aircraft as an IFR departure off a secondary airport. If the aircraft originated outside of your facility airspace but is landing at an airport within facility airspace, this would be counted as an IFR arrival in the appropriate category. If the aircraft continues through your airspace this would be considered an IFR overflight. This operation cannot be counted as an overflight and an arrival and/or departure. Yes. Helicopters that depart or arrive from movement or non-movement areas located on the airport are counted as itinerant operations provided they receive a takeoff or landing clearance or proceed instructions from ATC that indicates the aircraft is receiving ATC service. Helicopters that are taxing, air or hover-taxiing cannot be counted as departures, arrivals or overflights.
These operations are to be counted as IFR/VFR operations to a secondary airport within 15 miles of the primary airport.
The same counting requirements apply to balloons as all other traffic. Those airships that do not contact either the TRACON or the Tower cannot be counted at all. As soon as possible, at the end of each month, each facility shall use the export feature of TTAP to create a file for that month and any additional information placed in TTAP since the last export. Any additional information entered should be exported using the TTAP date range feature. Although FAAO 7210.57 doesn’t specify a timeframe for submission of data, facility classification indices are run on the 15th of each month. The facility classification index is based upon a full year of data. Therefore, if facility data isn’t received in a timely manner, data will be identified as missing and the CI for their facility will be impacted. From FAA Order 7210.57: (1) Terminals, non-HOST equipped centers, and combined control facilities shall use the TTAP to submit hourly traffic data on a monthly basis. (a) Traffic data may be put into TTAP via manual or locally developed automated procedures. All locally developed extraction software must be registered with ATX-400. (b) At the end of each month, each facility shall use the export feature of TTAP to create a file for that month and any additional information placed in TTAP since the last export. (c) This file shall be attached to a cc:mail message addressed to the 9-AWA-MSDT mailbox or as an internet message to 9-AWA-MSDT@FAA.DOT.GOV. (d) The message subject box shall state the term DATA and the facility three letter identifier (e.g. DATA PHL). (e) The file being submitted shall be sent in original format (or zipped version) without making any changes or additions to the file. NOTE – In order to allow for time to process data and still run CI’s by the 15th of the Month, Data needs to be exported by the 5th of each month for the previous month .NOTE 2 – Due to data security issues it was determined that any facility that does not use the INTRANET or FAA cc:mail system to transmit TTAP data must coordinate with FAA Washington ATX-20. INTERNET submissions may be rejected. http://atpay.faa.gov
|
| http://atpayplan.natca.net/ is for informational purposes only. http://atpayplan.natca.net/ makes no promises or guarantees as to the accuracy, completeness, or adequacy of the contents of this web site and expressly disclaims liability for errors and omissions in the contents of this web site. http://atpayplan.natca.net/ is not responsible for the content, truthfulness or propriety of any links to this homepage or website. Further, http://atpayplan.natca.net/ does not expressly or implicitly endorse the services, products, statements or content of other sites which may be linked to this homepage or website. Statements made on this, linking sites or homepages do not reflect the opinions or policy of the National Air Traffic Controllers Association (NATCA), and may not be construed in any part as endorsements by http://atpayplan.natca.net/, NATCA, The Federal Aviation Administration (FAA) or the Federal Government. |