Order AT 7110.5A Tower En Route Control (TEC) Service
This document is cancelled. It may have been replaced. Check the official source before relying on it.
Text read by OCR from a scanned file. Check the original, as some words may be misread.
SMAP .RECD APR 13 1939
SMAP .RECD APR 13 1939
ORDER U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION WP AT 7110.5A AGIFIC REGION 5/25/99
SECATIES ALLLL RIS LIBARY
SUBJ: TOWER EN ROUTE CONTROL (TEC) SERVICE
1. PURPOSE. This order provides guidelines for the development and use of Tower En Route Control (TEC) services.
SUBJ: TOWER EN ROUTE CONTROL (TEC) SERVICE
2. DISTRIBUTION. All Branches in the Air Traffic Division and all Western-Pacific Air Traffic Field Facilities, Military RAPCON's and RATCF's and Regional Military Representatives. 3. CANCELLATION. Order WP 7430.1, Southern California Terminal Route System (SO-CAL), dated May 20, 1982, and Order WP AT 7110.5, Tower En Route Control (TEC), dated October 28, 1991.
4. EFFECTIVE DATE. May 25, 1999.
5. POLICY. TEC should be established/expanded only within areas of radar coverage. In areas without radar coverage where a specific operational benefit will be gained present service to users will be equal to or greater, and an equivalent level of safety is maintained TEC may be established and/or expanded.
a. TEC is primarily for flights of two (2) hours duration or less. Flight profiles of turbojet aircraft shall not be changed for the purpose of removing them from the high altitude structure to include them in TEC.
b. When proposing to establish/expand TEC service, consider the following:
(1) Staffing capability of facilities involved.
(2) Current airspace configurations of each facility.
(3) Adaptation, airspace, operational, and procedural requirements.
(4) Radar coverage limitations.
(5) Special use airspace requirements, heavily traveled VFR routes, airports, etc.
(6) Current preferential routes, city pairs.
(7) Aircraft requirements for routes over mountainous terrain, water, etc.
Distribution:A-FAT-0, AWP-910, AWP-920, AWP-930 (8 copies each)Initiated By: AWP-530
WP AT 7110.5A 5/25/99
responsible for TEC. 6. RESPONSIBILITIES. The Operations Branch, AWP-530, is designated the regional representative
a. AWP- 530 shall: (1) Provide TEC objectives and policy to ensure a cooperative and coordinated effort. balanced system, and evaluate the effectiveness of the routes. (2) Monitor the development of TEC, assist the efforts to achieve maximum benefit and a
(3) Review change requests in TEC routes, verify accuracy and completeness. Should conflicts exist after the originating facility has received comments from all participating radar facilities, AWP-530 shall resolve the conflict prior to any adaptation changes and/or TEC routes being printed. (4) Approved additions/changes including special instructions/information, as required, shall be forwarded to the Aeronautical Information Division, ATA-100, for publication in the appropriate Airport/Facility Directory (A/FD) edition. All changes must be formatted according to the examples dates as specified in the A/FD. (Appendices 1 and 2) and sample (Appendix 3). All changes must be submitted in accordance to cutoff
(5) Distribute to each participating facility all finalized changes, with effective date. (6) Ensure a review of Terminal En Route System is conducted annually each October. b. Approach Control Facilities shall: (1) Originating facility shall distribute the request for change/additions to all participating facilities, including military, for comment. Should any comment result in an unresolved conflict, those comments shall be included in the submission to AWP-530 for resolution. (2) Establish to the extent feasible, a common TEC ceiling. (3) Review the Terminal En Route System annually each October and complete written certification. This certification shall be submitted to AWP-530 by October 31 each year. (4) Develop, and revise, Letters of Agreements as required. If necessary, radar facilities may include local instructions or altitude restrictions not included on TEC routes. is not overloaded. (5) Maintain an equitable plan to integrate TEC and Traffic Management to ensure the system
program. (6) As appropriate, conduct briefings to user groups to ensure understanding of the TEC
(7) Submit request for Airway Facilities requirements through normal coordination process. (8) Submit TEC changes to AWP-530 in a timely manner (see paragraph 6a(4)). Page 2
5/25/99 WP AT 7110.5A
ARTCC. (9) When TEC delays and/or holding is anticipated or occurring, advise the appropriate (10) Advise ARTCC's of changes to TEC routes for en route metering program updates. traffic to achieve an equitable balance with other en route traffic. delay to TEC aircraft as incurred by other departing aircraft bound for the same airport. Limit TEC (11) Balance traffic demand with the most effective use of airspace. Apply an equal ground
c. Airport Traffic Control Towers shall: (12) Advise the local AFSS of departure delays or anticipated restrictions.
(1) Ensure all pilots issued an abbreviated clearance have current TEC routes. (2) Issue current TEC routes to all departures destined to TEC airports. unless otherwise specified by Letter of Agreement. (3) Advise departures to expect the altitude indicated in the TEC five minutes after departure, d. Air Route Traffic Control Centers shall: equitable traffic flows. (1) Monitor the arrival demand at pacing airports. If necessary, initiate restrictions to ensure
gained. TEC and reassign airspace to accommodate vertical expansions where operational benefit will be (2) Provide assistance to ATCT's/TRACON's in meeting their objectives of maximum use of e. Flight Service Stations shall: (1) Encourage pilots to file TEC routes published in the A/FD. (2) Advise pilots of known delays or restrictions. John Clancy teneLmauni Manager, Air Traffic Division
Par 6.b.(9)
5/25/99
WP AT 7110.5A Appendix 1
APPENDIX 1. FORMAT EXAMPLE (GRAPHICS)
APPENDIX 1. FORMAT EXAMPLE (GRAPHICS)
Changes to TEC Information Published in the Airport/Facility Directory (A/FD)
GRAPHICS:
Delete Approach Control Area:
Delete Lines Between:
Add Approach Control Area:
Add lines between:
Revisions:
Name State
1. 2. 3.
Identifiers
1. 2. 3.
Name State
1. 2. 3.
Identifiers
1. 2. 3.
Identifiers
OLD NEW
OLD NEW
1. 2. 3.
PAGE OF
Identifier
Identifier
5/25/99 WPAT7110.5A Appendix 2
APPENDIX 2. FORMAT EXAMPLE (TEXTUAL DATA)
Changes to TEC information Published in the Airport/Facility Directory (A/FD)
PAGE OF
TEXTUAL DATA:
Name of Approach Control Route Id Route Altitude Destination
PAGE OF
Deletions:
Additions:
Revisions: Old: New:
Old: New:
5/25/99
WP AT 7110.5A Appendix 3
APPENDIX 3. SAMPLE CHANGES TO TEC
Changes to TEC Information Published in the Airport/Facility Directory (A/FD)
SOUTHWEST U.S.
GRAPHICS:
Add Approach Control Area:
Add Lines Between:
TEXTUAL DATA:
APPENDIX 3. SAMPLE CHANGES TO TEC
Name of Approach Control Route Id
Bakersfield
Deletions:
Additions: BFLG1 V59 DARTS V186
Additions: BFLG1 V459 DARTS V186
PAGE 1 OF 2
Name State Identifier 1. Bakersfield CA BFL 2. Southern Calif CA VVR
Identifiers 1. BFL-LGB
Route Altitude Destination
BFL V165 AMONT 9000 Fullerton Airport
V394 SLI (ALL)
V394 SLI (ALL)
BFL SLI AMONT 9000 Long Beach
V394 SLI (ALL)
NOTE: Make additions for each airport destination that is being added.
WP AT 7110.5A Appendix 3
5/25/99
Southern California
Revisions: Old:
New:
New:
BURG1
BURG1
BURG1
V186 V394 SLI (JM)
V186 V394 SLI (M)
V186 V394 SLI (J)
V186 V394 SLI (J)
7000
7000
9000
Fullerton Airport
Fullerton Airport
Fullerton Airport
NOTE: Make additions for each airport destination that is being revised.
San Diego
Additions:
SANG28
SANG28
MZB 293 SLI 148 SLI V23 BFL (M)
MZB 293 SLI 148 SLI V23 BFL (M)
8000
10000
Bakersfield
Bakersfield
NOTE: Make additions for each airport destination that is being added.