TPA Order 7110.6E
Tampa Air Traffic Control Tower
Standard Operating Procedures
January 13, 2011
TPA 7110.6E
FAA FORM 1320-5 (6-20) use previous edition
01/13/2011
TPA 7110.6E
This page intentionally left blank
FOREWORD
01/13/2011
TPA 7110.6E
01/13/2011
TABLE OF CONTENTS
FOREWORD…………………………………………………………………………………..i
CHAPTER 1. INTRODUCTION
1-1.
1-2.
1-3.
1-4.
1-5.
1-6.
PURPOSE...............................................................................................................................1-1
DISTRIBUTION ....................................................................................................................1-1
CANCELATION....................................................................................................................1-1
EFFECTIVE DATE ...............................................................................................................1-1
GENERAL..............................................................................................................................1-1
DEFINITIONS .......................................................................................................................1-1
CHAPTER 2. WATCH SUPERVISION
SECTION 1. GENERAL POSITION DUTIES AND RESPONSIBILITIES
2-1. OBJECTIVE.................................................................................................................. 2-1
2-2. ASSIGNMENTS. .......................................................................................................... 2-1
2-3. EQUIPMENT PROBLEMS AND OUTAGES............................................................. 2-2
2-4. GENERAL RESPONSIBILITIES AND DATA COLLECTION................................. 2-2
2-5. TPA RUNWAY CHANGES/CLOSURES AND SYSTEM OUTAGES. .................... 2-4
2-6. ELECTRONIC FLIGHT STRIP TRANSFER SYSTEM (EFSTS).............................. 2-5
2-7. TRAFFIC COUNT. ....................................................................................................... 2-5
2-8. TOWER EVACUATION.............................................................................................. 2-6
2-9. thru 2-19. RESERVED.................................................................................................. 2-6
SECTION 2. OPERATIONS MANAGER (OM)
2-20. OPERATIONS MANAGER (OM) RESPONSIBILITIES......................................... 2-6
2-21. thru 2-29. RESERVED................................................................................................ 2-7
SECTION 3. FRONTLINE MANAGER (FLM)
2-30. FRONTLINE MANAGER (FLM) RESPONSIBILITIES.......................................... 2-8
2-31. thru 2-39. RESERVED................................................................................................ 2-9
SECTION 4. CONTROLLER IN CHARGE (CIC)
2-40. POSITION DUTIES AND RESPONSIBILITIES. ................................................... 2-10
2-41. MIDWATCH CIC. .................................................................................................... 2-10
2-42. thru 2-49. RESERVED.............................................................................................. 2-11
SECTION 5. NOTICES TO AIRMEN (NOTAMs)
2-50. PROCEDURES. ........................................................................................................ 2-11
TABLE OF CONTENTS
i
TPA 7110.6E
01/13/2011
2-51. thru 2-59. RESERVED.............................................................................................. 2-12
SECTION 6. CHECKLISTS
2-60. FLMIC/FLM/CIC POSITION RELIEF CHECKLIST. ............................................ 2-12
2-61. TOWER CHECKLIST. ............................................................................................. 2-13
2-62. WATCH CHECKLIST – TRACON. ........................................................................ 2-13
CHAPTER 3. GENERAL CONTROL
SECTION 1. APPLICABLE TO ALL POSITIONS
3-1.
3-2.
3-3.
3-5.
3-6.
3-7.
3-8.
3-9.
DUTY FAMILIARIZATION........................................................................................ 3-1
RESPONSIBILITIES OF ALL TOWER/RADAR TEAM MEMBERS. ..................... 3-1
thru 3-4. RESERVED................................................................................................... 3-1
POSITION LOG, FAA FORM 7230-10. ...................................................................... 3-1
POSITION RELIEF BRIEFING. .................................................................................. 3-3
POSITION RELIEF BRIEFING CHECKLIST ............................................................ 3-3
USE OF WIRELESS HEADSETS................................................................................ 3-3
thru 3-19. RESERVED............................................................................................. ....3-3
SECTION 2. STRIP MARKING
3-20. PURPOSE.................................................................................................................... 3-4
3-21. ARRIVAL FLIGHT PROGRESS STRIP MARKING. .............................................. 3-4
3-22. DEPARTURE STRIPS................................................................................................ 3-4
3-23. ADDITIONAL STRIP MARKING AUTHORIZED FOR IFR
ARRIVAL/DEPARTURE STRIPS. ...................................................................................... 3-6
3-24. STRIP MARKING EXAMPLES. ............................................................................... 3-7
3-25. thru 3-29. RESERVED................................................................................................ 3-8
SECTION 3. TRAFFIC MANAGEMENT
3-30. TRAFFIC MANAGEMENT MESSAGES. ................................................................ 3-8
3-31. thru 3-39. RESERVED................................................................................................ 3-9
SECTION 4. COMBINING/DECOMBINING POSITIONS
3-40. CHECKLIST. .............................................................................................................. 3-9
3-41. COMBINING POSITIONS......................................................................................... 3-9
3-42. DECOMBINING POSITIONS. ................................................................................ 3-11
3-43. MIDNIGHT CONFIGURATION ............................................................................. 3-11
3-44. thru 3-49. RESERVED.............................................................................................. 3-11
TABLE OF CONTENTS
ii
TPA 7110.6E
01/13/2011
SECTION 5. BACKUP COMMUNICATIONS EQUIPMENT
3-50. RDVS Voice Switch Bypass (VSBP)........................................................................ 3-11
CHAPTER 4. TOWER GENERAL
SECTION 1. GENERAL DUTIES AND PROCEDURES
4-1.
4-2.
4-3.
4-4.
4-5.
4-6.
4-7.
PRIMARY RESPONSIBILITIES OF THE TOWER TEAM POSITIONS. ................ 4-1
RESTRICTIONS. .......................................................................................................... 4-2
MEDIA AREA. ............................................................................................................. 4-2
CRITICAL AREAS....................................................................................................... 4-2
RUNWAY/TAXIWAY CLOSURES............................................................................ 4-2
TRANSCEIVERS ......................................................................................................... 4-3
TOWER TDW MAPS ................................................................................................... 4-3
SECTION 2. WEATHER INFORMATION
4-8. DISSEMINATION........................................................................................................ 4-4
CHAPTER 5. FLIGHT DATA/CLEARANCE DELIVERY (FDT)
SECTION 1. AUTOMATIC TERMINAL INFORMATION SERVICE (ATIS)
5-1. PREPARE ATIS INFORMATION............................................................................... 5-1
5-2. ATIS FORMAT............................................................................................................. 5-1
5-3. OPERATION................................................................................................................. 5-2
5-4. MONITOR ATIS........................................................................................................... 5-2
5-5. DISSEMINATION........................................................................................................ 5-3
5-6. RESTRICTIONS ........................................................................................................... 5-3
5-7. thru 5-10. RESERVED.................................................................................................. 5-3
SECTION 2. FLIGHT PLAN/STARS INFORMATION
5-11. IFR DEPARTURE AIRCRAFT.................................................................................. 5-4
5-12. VFR AIRCRAFT......................................................................................................... 5-4
5-13. SPECIAL VFR HELICOPTERS. ............................................................................... 5-5
5-14. VFR HELICOPTER DEPARTURES. ........................................................................ 5-5
5-15. STARS ENTRIES. ...................................................................................................... 5-5
5-16. thru 5-20. RESERVED................................................................................................ 5-6
SECTION 3. CLEARANCES/INSTRUCTIONS
5-21. DEPARTURES. .......................................................................................................... 5-6
5-22. PRE-DEPARTURE CLEARANCES (PDC). ............................................................. 5-8
TABLE OF CONTENTS
iii
TPA 7110.6E
01/13/2011
CHAPTER 6. GATE HOLD
6-1. LOCAL GATE HOLD PROCEDURES ....................................................................... 6-1
CHAPTER 7. GROUND CONTROL (GC)
7-1.
7-2.
7-3.
7-4.
7-5.
7-6.
7-7.
AREA OF RESPONSIBILITY. .................................................................................... 7-1
COORDINATION......................................................................................................... 7-1
RESTRICTED GROUND MOVEMENT INSTRUCTIONS....................................... 7-2
ILS CRITICAL AREAS................................................................................................ 7-3
MISCELLANEOUS...................................................................................................... 7-3
SPLIT LOCALS:........................................................................................................... 7-4
NOISE ABATEMENT PROCEDURES:...................................................................... 7-4
CHAPTER 8. LOCAL CONTROL (LC)
8-1.
8-2.
8-3.
8-4.
8-5.
8-6.
8-7.
8-8.
DEPARTURE RELEASES........................................................................................... 8-1
ARRIVAL/DEPARTURE PROCEDURES.................................................................. 8-4
LINE UP AND WAIT (LUAW) OPERATIONS. ........................................................ 8-4
LAND AND HOLD SHORT OPERATIONS (LAHSO) ............................................. 8-7
COORDINATION......................................................................................................... 8-9
TAXIWAY USAGE.................................................................................................... 8-10
RUNWAY USE PRIORITY. ...................................................................................... 8-13
ELECTRONIC FLIGHT STRIP TRANSFER SYSTEM (EFSTS)........................... .8-13
CHAPTER 9. SPLIT LOCAL / SPECIAL EVENT PROCEDURES
9-1. SPLIT LOCAL PROCEDURES ................................................................................... 9-1
9-2. SPECIAL EVENT PROCEDURES.............................................................................. 9-1
CHAPTER 10. CAB COORDINATOR (CC)
10-1. POSITION REQUIREMENTS ................................................................................. 10-1
10-2. RESPONSIBILITIES ................................................................................................ 10-1
CHAPTER 11. FLIGHT DATA RADAR (FDR)
SECTION 1. COMMUNICATE AND COORDINATE AIR TRAFFIC
INFORMATION
11-1. PRIORITIES.............................................................................................................. 11-1
11-2. DUTIES AND RESPONSIBILITIES. ...................................................................... 11-1
11-3. thru 11-10. RESERVED............................................................................................ 11-1
TABLE OF CONTENTS
iv
TPA 7110.6E
01/13/2011
SECTION 2. FLIGHT PLAN INFORMATION
11-11. PROCEDURES. ...................................................................................................... 11-2
11-12. STRIP MARKING. ................................................................................................. 11-2
11-13. WEATHER DISSEMINATION. ............................................................................ 11-3
CHAPTER 12. RADAR GENERAL
SECTION 1. GENERAL DUTIES AND PROCEDURES
12-1. PRIMARY RESPONSIBILITIES OF THE RADAR TEAM POSITIONS. ............ 12-1
12-2. TRANSCEIVERS. .................................................................................................... 12-2
12-3. AUTO ACQUISITION ............................................................................................. 12-2
12-4. TRANSFER OF CONTROL..................................................................................... 12-2
12-5. TRANSFER OF IDENTITY AND COMMUNICATIONS ..................................... 12-2
12-6. STARS COORDINATION/AUTOMATED POINT OUT PROCEDURES (APO).12-3
12-7. AIRSPACE................................................................................................................ 12-4
12-8. PREARRANGED COORDINATION ...................................................................... 12-4
12-9. CONTROLLED AIRSPACE INTRUSIONS. .......................................................... 12-8
12-10. STARS..................................................................................................................... 12-8
12-11. STARS OPERATIONAL MODE TRANSITION PROCEDURES (FSL/ESL) .. 12-12
SECTION 2. WEATHER INFORMATION
12-12. DISSEMINATION................................................................................................ 12-13
SECTION 3. EQUIPMENT
12-13. RADAR ................................................................................................................. 12-14
12-14. ELECTRONIC FLIGHT STRIP TRANSFER SYSTEM (EFSTS)...................... 12-15
12-15. TRACON OPERATING POSITIONS.................................................................. 12-16
CHAPTER 13. TRACON POSITIONS
13-1. FINAL (F)................................................................................................................. 13-1
13-2. WEST SATELLITE (P). .......................................................................................... 13-7
13-3. WEST ARRIVAL (W). .......................................................................................... 13-11
13-4. WEST DEPARTURE (D). ..................................................................................... 13-14
13-5. EAST SATELLITE (L) .......................................................................................... 13-19
13-6. EAST ARRIVAL (E) ............................................................................................. 13-22
13-7. EAST DEPARTURE (B) ....................................................................................... 13-25
13-8. SOUTH DEPARTURE (G).................................................................................... 13-30
13-9. SOUTH SATELLITE (S)....................................................................................... 13-33
13-10. LAKELAND LOW (R) ........................................................................................ 13-36
13-11. MACDILL (M)..................................................................................................... 13-37
TABLE OF CONTENTS
v
TPA 7110.6E
01/13/2011
CHAPTER 14. TRACON COORDINATORS
14-1.
14-2.
14-3.
14-4.
GENERAL................................................................................................................. 14-1
INTERNAL COORDINATOR (IC) ......................................................................... 14-1
EXTERNAL COORDINATOR (XC)....................................................................... 14-1
MISCELLANEOUS.................................................................................................. 14-1
CHAPTER 15. RUNWAY 10/28 PRIMARY RUNWAY OPERATION
15-1. GENERAL................................................................................................................. 15-1
15-2. TOWER. .................................................................................................................... 15-1
15-3. TRACON................................................................................................................... 15-1
CHAPTER 16. RADAR OUTAGE PROCEDURES
16-1.
16-2.
16-3.
16-4.
16-5.
BACKGROUND ....................................................................................................... 16-1
QFN RADAR OPERATIONAL. .............................................................................. 16-1
QFN RADAR OUT OF SERVICE. .......................................................................... 16-4
LOSS OF RADAR / NON-RADAR PROCEDURES. ............................................. 16-4
NON-RADAR HOLDING. ....................................................................................... 16-5
APPENDICES
APPENDIX A. TPA AIRPORT MAP, NON-MOVEMENT AREAS AND AREAS OF
NON-VISIBILITY................................................................................................................ A-1
APPENDIX B. LOW LEVEL WIND SHEAR ALERT SYSTEM (LLWAS) ................... B-1
APPENDIX C. MCF AIRSHOW AIRSPACE.................................................................... C-1
APPENDIX D. RUNWAY VISUAL RANGE (RVR)........................................................ D-1
APPENDIX E. CATEGORY II AND III ILS OPERATIONAL REQUIREMENTS .........E-1
TABLE OF CONTENTS
vi
TPA 7110.6E
01/13/2011
CHAPTER 1. INTRODUCTION
1-1. PURPOSE.
This order establishes the facility's Standard Operating Procedures (SOP) at Tampa Air Traffic
Control Tower. This directive is supplementary to the procedures contained in national/regional
directives and current Letters of Agreement with Tampa Tower/Approach Control.
1-2. DISTRIBUTION.
This order is distributed to facility files, Quality Control, Training, TRACON, and Tower Cab.
1-3. CANCELLATION.
TPA 7110.6D, Standard Operating Procedures, dated February 5, 2009 is canceled.
1-4. EFFECTIVE DATE.
This order is effective January 13, 2011.
1-5. GENERAL.
Operations Managers, Front Line Managers, Controllers, and Air Traffic Assistants are required to
be familiar with the provisions of this Order that pertain to their operational responsibilities and to
exercise their best judgment if they encounter situations that are not covered by it or
national/regional directives.
1-6. DEFINITIONS.
Where used in this Order, the following acronyms are defined as meaning:
ACFT = Aircraft
AFSS = Automated Flight Service Station
AOCC = Atlantic Operations Control Center
ASOS OID = Automated Weather Observation System Operator Interface Device
ATA = Arrival Transition Area
ATIS =Automatic Terminal Information Service
ATM = Air Traffic Manager
ATCSCC = Air Traffic Control System Command Center
CFR = Call For Release
CIC = Controller in Charge
CPC = Certified Professional Controller
DEN = Domestic Events Network
DSP = Digital Systems Processor
DTA = Departure Transition Area
EDCT = Expect Departure Clearance Time
INTRODUCTION
1-1
TPA 7110.6E
01/13/2011
EFSTS = Electronic Flight Strip Transfer System
ESL = Emergency Service Level (STARS)
FLM = Front Line Manager
FLMIC = Front Line Manager in Charge
FSL = Full Service Level (STARS)
F11 = Central Florida TRACON
GRE = Ground Run-Up Enclosure
HCAA = Hillsborough County Aviation Authority
HDG = Heading
IDS-4 = Information Display System
ITWS = Integrated Terminal Weather System
JAX = Jacksonville TRACON
LAHSO = Land and Hold Short Operations
LCL = Local Time
LLWAS = Low Level Wind Shear Alert System
LUAW = Line Up and Wait
MSAW = Minimum Safe Altitude Warning
NBV = North Bay Visual Approach
NOTAM = Notice to Airmen
OJT = On-the-Job Training
OM = Operations Manager
OMIC = Operations Manager in Charge
PDC = Pre departure Clearance
QFN = Fort Green Long Range RADAR
RCO = Remote Communications Outlet
RDVS = Rapid Deployment Voice Switch
ROC = Regional Operations Center
RWY = Runway
RSW = Fort Myers TRACON
SMGCS = Surface Movement Guidance and Control System
STARS = Standard Terminal Automation Replacement System
TARP = Traffic Analysis and Review Program
TCW = Terminal Controller Workstation
TDW = Tower Display Workstation
TDWR = Terminal Doppler Weather RADAR
TECH OPS = FAA Technical Operations
TMU = Traffic Management Unit
TRACON = Terminal RADAR Approach Control
VSBP = Voice Switch Bypass
ZJX = Jacksonville Air Route Traffic Control Center
ZMA = Miami Air Route Traffic Control Center
ZMA PIT = Miami ARTCC Flight Plan Control Position
INTRODUCTION
1-2
TPA 7110.6E
01/13/2011
CHAPTER 2. WATCH SUPERVISION
SECTION 1. GENERAL POSITION DUTIES AND RESPONSIBILITIES
This chapter identifies the various levels of operational supervision, defines areas of
responsibility, and assigns specific tasks and activities to each. Watch supervision may be
performed by an OM, FLM, or CIC.
2-1. OBJECTIVE.
The general objectives and tasks of all OMs/FLMs/CICs are as follows:
a. Establish goals for the shift.
b. Maintain situational awareness, defined as knowing what is going on around you.
c. Manage the operational environment with a goal toward eliminating distractions.
d. Monitor controller performance to ensure safe and expeditious service is provided.
e. Directly monitor the movement of presidential aircraft.
f. Monitor and manage traffic volume/flow.
g. Make position assignments consistent with operational needs.
h. Manage position relief.
i. Assign training, as required.
j. Assess leave requests against operational needs.
k. Establish equipment configuration based on operational needs. Monitor equipment
performance and report outages as required.
l. Collect data and report as required.
2-2. ASSIGNMENTS.
a. To the maximum extent feasible, there shall be one FLM in the TRACON as the FLMIC
until relieved by the mid-watch CIC.
b. During periods when only one FLM is available for watch supervision, they shall be
designated as the TRACON FLMIC and a CIC will be designated in the Tower.
WATCH SUPERVISION
2-1
TPA 7110.6E
01/13/2011
c. During periods when a FLM is not available for watch supervision, a CIC shall be
designated in the Tower and TRACON.
d. During periods when an OM is assigned to the TRACON, they shall be designated as the
OMIC.
e. During periods when two or more FLMs are on duty and in the absence of an OM, one must
be assigned as FLMIC, and the other as the OMIC.
2-3. EQUIPMENT PROBLEMS AND OUTAGES.
Identify and report equipment problems or outages to the appropriate work center. Make an
entry in the 7230.4, Daily Record of Facility Operations when the equipment is reported out of
service and when it is reported back in service.
a. FAA Equipment:
(1) During normal watch coverage, notify TECH OPS personnel.
(2) After normal watch coverage, notify the AOCC.
b. FTI (Federal Telecommunications, Inc) Communications Equipment. Report outage to
AOCC and give the circuit number, if requested.
c. STARS Failure. Immediately select ESL and notify TECH OPS personnel, if available. If
not, notify AOCC.
d. Remote Frequencies. Remote frequencies should be operated on the same position, i.e.,
Transmitter #1, Receiver #1. When a remote frequency is released to maintenance, both
transmitter and receiver must be shut off to prevent a tone.
e. HCAA. Report to HCAA Communications Center any maintenance or other problems
requiring HCAA response. This includes airport lighting, airport lighting panel, and foreign
objects on movement/non-movement area.
f. Automation Systems/Equipment Problems. During administrative hours, notify Tech Ops.
After administrative hours, notify the AOCC.
2-4. GENERAL RESPONSIBILITIES AND DATA COLLECTION.
a. Position Relief Briefing. Use the checklist to ensure proper position relief briefing when
assuming or relinquishing the OM/FLM/CIC position. Record the position relief briefing.
b. Checklists. Review the briefing checklist, equipment checklist, and daily facility log
carryover data. Make sure equipment is properly functioning; and if a discrepancy exists, ensure
appropriate notifications have been made.
WATCH SUPERVISION
2-2
TPA 7110.6E
01/13/2011
c. Accident or Incident:
(1) If it requires immediate action during normal duty hours, notify the Quality Control (QC)
Support Specialist for guidance/assistance.
(2) After duty hours, respond to unusual situations, emergencies, accidents and incidents, and
implement contingency plans as required.
d. IDS-4:
(1) Responsible for the accuracy of information in the Status Information Areas.
(2) When the IDS-4 is inoperative, immediately provide the affected position(s) pertinent
sections of the position information binder. Close any position for which a back up of essential
position information does not exist.
e. Special Operations. Coordinate special operations.
f. User Complaints. Forward any user complaints or requests for information to the QC
Specialist, and make appropriate entry.
g. Visitors. Coordinate visitors with the TPA ATM.
h. Media Inquiries. Forward inquiries from the news media to the FAA’s Public Affairs
Office.
i. Unauthorized Transmissions. Collect any pertinent information (identification used, what
was said, etc.) and forward it to the DEN.
j. Traffic Management Messages:
(1) Review the traffic management messages for operational impact.
(2) Disseminate the original or copy, as needed.
(3) When flow restrictions are necessary, coordinate with ZMA TMU for aircraft entering
TPA airspace from ZMA or RSW; and ZJX TMU for aircraft entering TPA airspace from ZJX,
JAX or F11.
(4) Log traffic management messages/flow restrictions as appropriate.
(5) Notify the TPA ATM and the ATCSCC when delays exceed 90 minutes. This does not
apply to EDCT delay times.
(6) Notify the appropriate TMU when a local ground stop is expected to reach 15 minutes.
k. National Delays:
(1) Record delays on the flight progress strips. Log all delays of fifteen (15) minutes or more
into the OPSNET System prior to 12:00 a.m. each evening. (NOT A CIC FUNCTION).
(2) Advise ZJX TMU when delays reach 15 minutes, and every 15 minute increment after
that (15, 30, 45 etc.). Advise ZJX TMU when delays fall below each 15 minute increment. This
information shall be included on the 7230.4, Daily Record of Facility Operations.
WATCH SUPERVISION
2-3
TPA 7110.6E
01/13/2011
l. CAT II or III. Include on the 7230.4, Daily Record of Facility Operations all time periods
when CAT II or III minimums are being used. This can be logged as intermittent when the
weather is fluctuating above and below RVR 2400 for CAT II or below RVR 1200 for CAT III.
m. Airspace Violations:
(1) If the suspected intruder lands within TPA airspace, coordinate with the satellite towers,
Fixed Base Operator (FBO), or other agencies, as appropriate, to determine the aircraft
registration.
(2) When these aircraft can be identified, enter any information regarding the incident on the
7230.4, Daily Record of Facility Operations and complete forms as required by FAAO 8020.16.
n. Invalid Mode C Readout. Record the occurrence on 7230.4, Daily Record of Facility
Operations and forward the following data to QC:
(1)
(2)
(3)
(4)
Aircraft call sign.
Date.
Time of incident.
Actual and reported altitude.
o. Aircraft Hijack:
(1) Immediately notify the DEN.
(2) Notify the OMIC of the associated ARTCC.
p. ELT. Forward ELT information to the ZMA or ZJX Missions desk.
q. Diversion of Military Aircraft. When aircraft inbound to MCF must divert to TPA, notify
HCAA. Relay to HCAA information such as hung bomb, number of aircraft, and approximate
arrival time. HCAA will determine the action needed for hung ordinances, security required, and
notification of the parking and ground handling of these aircraft. Notify the DEN.
2-5. TPA RUNWAY CHANGES / CLOSURES AND SYSTEM OUTAGES.
a. Notification. A TPA runway change, and any outage that impacts system flow, causes
restrictions, or results in aircraft delays, requires notification. These outages include RADAR or
computer system outages, runway or taxiway closures, and key NAVAIDs.
(1) Notify ZMA and ZJX TMU, and other outlying facilities as appropriate. ZMA/ZJX TMU
will notify the ATCSCC.
(2) Notification should be effected as soon as practicable, but not more than 72 hours in
advance of a scheduled closure/outage. Ensure impact statement is issued.
(3) Notification should take place when a previous closure/outage is canceled.
(4) The Tower FLM/CIC shall designate the TPA active runways and coordinate any changes
with the TRACON OMIC/FLMIC/CIC. Inform all Tower positions of the runway change and
WATCH SUPERVISION
2-4
TPA 7110.6E
01/13/2011
assist controllers as required. The TRACON OMIC/FLMIC/CIC shall coordinate with all
TRACON positions, F11, and ZMA / ZJX TMUs of the new runways in use at Tampa, and
reconfigure the STARS and the EFSTS.
(5) Advise the OMIC/FLMIC of changes in the status of TPA runways, taxiways, and other
movement areas.
b. Closing / Opening Runways. HCAA has the sole authority to change the operational status
of runways and taxiways. When any pavement is closed to aircraft, the following individuals are
responsible for completing a final inspection and re-opening pavement for aircraft use:
(1)
(2)
(3)
(4)
(5)
(6)
Airport #2, #8 or #9
Senior Director of Operations
Director of Operations
Deputy Director of Operations
Assistant Director of Operations (ADO)
Airport Operations Specialist (AOS)
NOTE:
This does not preclude tower personnel from identifying an unsafe airport condition and issuing
advisories to all affected traffic. Advise HCAA of the unsafe condition and for issuance of a
NOTAM.
2-6. ELECTRONIC FLIGHT STRIP TRANSFER SYSTEM (EFSTS).
a. Ensure the EFSTS is set on the correct configuration (North or South) and scan the
corresponding configuration strip when TPA changes runways.
b. Notify TECH OPS in the event of an EFSTS computer, scanner, keypad, or printer failure.
c. Ensure the EFSTS printers have paper.
2-7. TRAFFIC COUNT.
a. Automated Traffic Count. The Count Ops computer located at the TRACON Watch Desk
provides the automated traffic count for the facility. This information is compiled and fed
directly into the OPSNET program.
b. Ensure TRACON and Tower flight progress strips are collected daily and forwarded to the
staff.
c. Non-Automated Traffic Count and Retention of Air Traffic Activity Records. (During
computer shutdown/outage).
(1) Airport Operations.
(a) Begin counting the daily airport operations in the tower at 2200 LCL.
WATCH SUPERVISION
2-5
TPA 7110.6E
01/13/2011
(b) Local Control, or Cab Coordinator when staffed, shall record each arriving aircraft at
TPA using aircraft identification.
(c) In the event the aircraft makes multiple landings and take-offs during the same hour, or
when an aircraft makes a missed approach, care must be taken to record each operation properly.
Either write the identification down again, or use a check mark each time an operation is
completed.
(2) Instrument Operations.
(a) Begin counting the instrument and Class B/C airspace operations as of 2200 LCL.
(b) Separate the strips into instrument operations and Class B/C airspace operations.
Practice instrument approaches provided IFR separation are counted the same as instrument
operations. Do not count duplicate strips, strips with insufficient information to determine that
TPA had control jurisdiction over the aircraft and authority to issue control instructions, or VFR
aircraft not in Class B or Class C airspace.
(c) Separate the Class B/C operations into primary airport (TPA) and overflights by user
category.
(d) Separate the instrument operations into primary airport, individual secondary airports,
and overflights by user category.
(e) After the strips are counted and the count has been logged, the strips will be banded
together and the package dated and filed.
(f) Forward the traffic count to the staff for further handling.
2-8. TOWER EVACUATION.
Take action to evacuate the Tower Cab when wind gusts reach a velocity of 55 knots or more.
2-9. thru 2-19. RESERVED.
2-9 See Notice TPA 7110.001
SECTION 2. OPERATIONS MANAGER (OM)
2-20. OPERATIONS MANAGER (OM) RESPONSIBILITIES.
The OM shall perform as an extension of the ATM in the operation and management of the
facility and make on-the-spot decisions pertaining to operational and management matters.
a. In concert with the FLMIC/CIC, establish goals for the shift and provide guidance to
operational personnel in accomplishing those goals.
b. Monitor FLM/CIC/CPC performance; provide training to FLM/CIC; make on-the-spot
corrections and/or acknowledge outstanding performance of FLM/CIC; hold FLM accountable
for their employees’ review of the Read & Initial (R & I ) material.
c. Ensure the accuracy and completion of the facility watch checklist, CRU-ART, and CRUART certification.
d. Monitor and manage traffic volume and flow through direct communication with the
FLM/CIC.
WATCH SUPERVISION
2-6
TPA 7110.6E
01/13/2011
e. Make position assignments consistent with operational needs and rotate personnel to
provide appropriate relief periods, including time for OJT pre-brief, de-brief, skill checks and
certifications.
f. Make training assignments, establish the priority for OJT, and assign refresher training,
supplemental training, and team briefings. Periodically review the pre-duty R & I binder to
ensure that all duty personnel have read and initialed for pre-duty briefing items.
g. Coordinate with TECH OPS and adjacent facilities as appropriate for routine equipment
outages and shutdowns.
h. Ensure operational equipment is configured properly for the current operational
configuration.
i. Process leave requests in accordance with local directives and the NATCA/FAA Collective
Bargaining Agreement (NOT A CIC FUNCTION).
j. Determine the need for overtime staffing and complete employee overtime notifications.
k. Eliminate distractions in the operational environment.
l. Maintain 7230-4, Daily Record of Facility Operations in accordance with JO 7210.3, Facility
Operation and Administration. Document all noteworthy incidents, i.e. accidents, flight assists,
pilot deviations, etc.
m. In the event of a Man Portable Air Defense System (MANPADS) incident or threat:
(1) Advise the DEN.
(2) Advise the ROC.
(3) Advise ZJX and ZMA Operations Manager.
(4) For a threat, ensure the following statement is broadcast on all frequencies and on the
ATIS: "MANPADS ALERT. EXERCISE EXTREME CAUTION. MANPADS THREAT
REPORTED BY TSA, TAMPA AREA, ADVISE IF YOU WANT TO DIVERT."
(5) For a specific incident, ensure the following statement is broadcast on all frequencies and
on the ATIS: "MANPADS ALERT. EXERCISE EXTREME CAUTION. MANPADS
ATTACK OBSERVED BY TOWER, (location and time), ADVISE IF YOU WANT TO
DIVERT."
2-21. thru 2-29. RESERVED.
WATCH SUPERVISION
2-7
TPA 7110.6E
01/13/2011
SECTION 3. FRONT LINE MANAGER (FLM)
2-30. FRONT LINE MANAGER (FLM) RESPONSIBILITIES.
The FLM shall perform the responsibilities of the OM in their absence, and make on-the-spot
decisions pertaining to operational and management matters.
a. Monitor and report equipment status to TECH OPS.
b. Monitor/manage traffic volumes and flows to ensure positions are properly combined or
decombined for optimum efficiency. Ensure that all appropriate facilities and positions of
operations are aware of the new configuration.
c. Ensure breaks are equitable and of reasonable duration.
(1) Meal and break periods should be planned in advance so that the facility operates
efficiently.
(2) Unless operational requirements do not permit, employees shall not be required to spend
more than two consecutive hours performing operational duties without a break away from
operational areas.
(3) Know the whereabouts of employees to ensure their availability for position assignments.
d. Assist control positions during unusual or emergency situations to ensure quality service
and to prevent position overloads.
e. Resume TPA automatic departures, if canceled. Automatic departures may be canceled by
any position, however the TRACON FLM/CIC must be notified. Only the TRACON FLM/CIC
may resume automatic departures. It is permissible for sector traffic management, at the
controllers’ discretion, to start and stop individual headings as needed, without notifying the
FLM/CIC.
f. Coordinate the use of the Final Shelf A extension, and return the airspace to the affected
sectors when no longer required by Final.
g. Assign and monitor On-the-Job Training (OJT) in accordance with TPA 3120.4.
h. Manage traffic volume, flow, and weather impacts and proactively coordinate with adjacent
facilities.
i. Ensure critically dependent positions are not relieved simultaneously as follows:
(1) During the periods of 8:00 a.m. until 9:00 p.m., do not simultaneously relieve critically
dependent positions. Critically dependent position combinations are: LC/GC, L/B, P/D, and
S/G.
WATCH SUPERVISION
2-8
TPA 7110.6E
01/13/2011
(2) Do not simultaneously relieve hand-off positions and their associated sectors. Do not
simultaneously relieve B and D, if the Final sector is combined to either position.
(3) A minimum of 2 minutes after the first critical dependent position must occur before
beginning the relief process for the other critical dependent position.
j. Enter/update IDS Traffic Management information, such as in-trail restrictions, Ground
Delay Programs, Ground Stops, reroutes, Call-for-Release, and Special Events.
k. Enter in the IDS equipment outages/ NOTAM information by airport.
l. Notify TECH OPS of equipment malfunctions or alarms. Monitoring of the digital voice
recorder is accomplished automatically with an aural alarm in the Tower.
m. Ensure that any reported bird strikes or trend toward an increase in bird activity on or
around the airport are reported to HCAA. Process bird strikes in accordance with the checklist in
the FLM/CIC binder in the TRACON.
(1) Coordinate with the HCAA for possible issuance of NOTAMS.
(2) Relay bird activity information to adjacent facilities and AFSS whenever it appears it will
become a factor in their areas.
n. Ensure PIREPs are solicited and handled in accordance with JO 7110.65. Ensure the
selective dissemination of SIGMET/CWA weather data within the facility and to satellite towers.
o. Disseminate LLWAS reports:
(1) Record the pertinent information along with the time of the report, and calculate the
proper expiration period for the necessary broadcast.
(2) Ensure that appropriate specialists are aware of the necessary information and adhere to
the appropriate time frames for dissemination of this information.
(3) Inform the Tower Flight Data Position when it is necessary to include a statement on the
ATIS concerning low level wind shear advisories.
p. The Tower FLM/CIC shall advise the TRACON FLM/CIC of significant weather changes
that might affect aircraft operations. (CAT II & III operations.)
q. The Tower FLM/CIC is responsible for determining the prevailing visibility and making
appropriate notifications per JO 7110.65.
r. Tower FLM/CIC shall inform the TRACON FLM/CIC when weather conditions are below
ceiling 3,000 feet and visibility less than 5 miles, and shall keep the TRACON FLM/CIC
informed where visual separation can be applied on final.
2-31. thru 2-39. RESERVED.
WATCH SUPERVISION
2-9
TPA 7110.6E
01/13/2011
SECTION 4. CONTROLLER-IN-CHARGE (CIC)
2-40. POSITION DUTIES AND RESPONSIBILITIES.
A CIC shall have the same authority, responsibility, and accountability as a FLM, and shall
perform the responsibilities of the FLM in their absence, whether the authority and
responsibilities were assigned by written directive, verbal direction, or local practice, with the
following exceptions:
a. Evaluating and counseling employees on their performance.
b. Recommending selections, promotions, awards, disciplinary actions and separations.
c. Serving as Site Coordinator for drug or alcohol testing.
2-41. MIDWATCH CIC.
The TRACON will remain open during midnight shifts. The CPC signed on the "SR" position is
CIC of the entire midnight shift operation. The midwatch CIC serves as the FLMIC and is
responsible for:
a. Maintaining FAA Form 7230-4, Daily Record of Facility Operations in accordance with JO
7210.3.
(1) Review the briefing checklist, equipment checklist, and carryovers data. Make sure
equipment is properly functioning, and if a discrepancy exists, appropriate notifications have
been made. Make an entry on the form when the watch checklist has been completed (WCLC).
(2) Record equipment malfunctions and notify the organization responsible for the
equipment.
(3) Record airport problems and report them to the HCAA.
(4) Document all noteworthy incidents, i.e., accidents, flight assists, noise complaints, etc.
b. Handling an accident or incident that requires immediate action/notification. Notify the OM
for guidance/ assistance. (A checklist is located in the accident/incident binder and the CIC
Guide.) In the event of an accident, incident, OE/OD, etc., during the midnight shift, the CIC
shall transition to TPA VFR Tower operations in accordance with the TPA ATCT Contingency
Plan as soon as the traffic situation allows. This will allow the CIC to begin the notification and
paperwork process. TPA ATCT shall operate as a VFR Tower until the CIC completes the
necessary notification/paperwork, or is relieved by a management official.
c. SIGMET and PIREP handling.
d. Briefing checklist for relieving supervisor. Include any significant occurrence, flight assist,
low altitude alerts, customs alert, sick leave, etc.
WATCH SUPERVISION
2-10
TPA 7110.6E
01/13/2011
e. Notifying facility management in the order listed below when assistance or guidance is
needed:
(1) Next scheduled FLMIC
(2) Operations Manager
(3) Air Traffic Manager
2-41. thru 2-49. RESERVED.
SECTION 5. NOTICES TO AIRMEN (NOTAMs)
2-50. PROCEDURES.
The following situations require issuance of a NOTAM. Notify AFSS for issuance and make an
entry in the 7230-4, Daily Record of Facility Operations.
a. Class B/C Airspace. When unable to provide this service due to RADAR failure.
b. ASR (TPA & SRQ). When RADAR is unusable.
c. Beacon Only. When primary RADAR is out and service is being provided by using beacon
only.
d. Approach lights. If out of service, or partial outage affecting approach minimums.
e. CAT II/III. When a component fails which requires CAT II or III suspension.
f. LLWAS. If there is a system failure rendering the LLWAS unusable.
g. Localizer. If one transmitter inoperative, CAT II/III unavailable.
h. Markers. If a Marker fails.
i. RVR. If inoperative.
j. Lights. When HCAA advises the runway, touchdown zone, centerline lights do not meet
CAT II tolerance.
k. Published frequencies. When the primary and backup transmitters or receivers are
inoperative (TPA & Remoted).
l. NDB. Out of service.
m. Other. Any condition limiting CAT II or III operations.
WATCH SUPERVISION
2-11
TPA 7110.6E
01/13/2011
n. Runway Closures. Requests for closure of operational area pavement for maintenance or
repair, other than emergency situations, will be coordinated with HCAA to enable issuance of a
NOTAM 48 hours before scheduled closing.
2-51. thru 2-59. RESERVED.
SECTION 6. CHECKLISTS
2-60. FLMIC/FLM/CIC POSITION RELIEF BRIEFING CHECKLIST.
Record Position Relief Briefing.
a. Review FAA Form 7230-4, Daily Record of Facility Operations.
b. Current weather and forecast.
c. Runway configuration.
d. Equipment status.
e. Equipment released or pending with TECH OPS.
f. Local/National flow restrictions.
g. FLM/CPC/ATA coverage.
h. Leave requests.
i. PIREPS, as necessary.
j. OJT.
k. Tower MSAW test (F7,Z,A,Enter).
l. Review FLM/CIC read binder.
m. Suspicious aircraft/pilot activities.
WATCH SUPERVISION
2-12
TPA 7110.6E
01/13/2011
2-61. WATCH CHECKLIST – TOWER.
The items on this checklist should be accomplished at the beginning of each shift, unless
otherwise noted. (For the purpose of this requirement, shifts begin at 0000, 0800, and 1600
LCL).
a. Emergency frequencies. Ensure 121.5 and 243.0 are selected at LC position.
b. Altimeter check. Check monthly on the first Saturday at 0800 LCL. Compare Digital
Altimeter Setting Indicator (DASI) to ASOS altimeter.
(1) If the difference exceeds 0.02 inches, remove the instrument from service and notify
TECH OPS.
(2) If the difference is 0.02 or less, post the correction factor, or zero if no correction needed,
and the date of the check, on or near the display(s) and notify TECH OPS.
c. ALS/SFL. Check daily between 0000 and 0100 LCL.
d. ILS monitor panel.
e. TDW.
f. Minimum Safe Altitude Warning (MSAW). Check the aural alarm at all operating positions.
g. Emergency phone. Check daily between 0700 and 0800 LCL.
h. VSBP Backup Communications System/Battery-Powered Transceivers. Check each
Saturday during low activity.
i. Light guns. Check daily between 0700 and 0800 LCL.
j. RVR. One hour prior to the anticipated need for RVR, turn the equipment on and evaluate
its performance.
k. Weather radio test, to include battery operation. Check each Saturday during low activity.
2-62. WATCH CHECKLIST – TRACON.
The items on this checklist should be accomplished at the beginning of each shift, unless
otherwise noted. (For the purpose of this requirement, shifts begin at 0000, 0800, and 1600
LCL).
a. Emergency frequencies. Ensure 121.5 and 243.0 are selected at the B position in the
TRACON. Conduct two-way, ground-to-air checks during low activity each Saturday.
b. Time check. Compare digital and STARS clocks for accuracy.
WATCH SUPERVISION
2-13
TPA 7110.6E
01/13/2011
c. ASR performance checks. Check daily.
d. Conflict Alert/Mode C Intruder/MSAW. Visually inspect and test aural alarms at each
operating position. Test with satellite towers.
e. NOTAMs. Between 0700 and 0800 LCL, check for current local NOTAMs on the FAA
NAIMES Pilotweb NOTAM System web site.
f. Severe weather. Notify TECH OPS of approaching severe weather activity.
g. HCAA Communications Center. Notify the Communications Center of any maintenance or
problem areas requiring HCAA response.
h. VSBP Back-up Communications System/Battery-Powered Transceivers. Test each
Saturday during a period of low activity.
i. EFSTS. Each morning at the beginning of the day shift, scan the correct runway
configuration.
WATCH SUPERVISION
2-14
TPA 7110.6E
01/13/2011
CHAPTER 3. GENERAL CONTROL
SECTION 1. APPLICABLE TO ALL POSITIONS
3-1. DUTY FAMILIARIZATION.
All operational personnel are required to familiarize themselves with current operational issues at
the beginning of each shift, prior to assuming responsibility for control positions. This shall
include reviewing, initialing, and dating for all new information on the Read & Initial Computer
Display, reviewing any missed team briefing information, any required face to face briefings and
reviewing the Status Information Area and Weather pages of the IDS-4.
3-2. RESPONSIBILITIES OF ALL TOWER/RADAR TEAM MEMBERS.
a. Advise other team members of operational situations that may require attention/immediate
action or affect efficient performance of operational requirements.
b. Initiate actions/recommendations to resolve situations that create unnecessary workload or
that may require attention/immediate action by the team.
c. Participate in sector/position/team planning.
d. Scan/monitor the environment, i.e. equipment, traffic workload, etc., to maintain situational
awareness to assess team status and provide feedback or assistance in a supportive manner when
warranted.
e. Issue MSAW and other safety alerts. The Tower geographic locations where aural alarms
sound for prominent obstructions is that airspace within 10NM of the Airport Reference Point
(ARP) for facilities with STARS TDWs. However, do not assume that because someone else
has responsibility for the aircraft that the unsafe situation has been observed and the safety alert
issued: inform the appropriate controller.
3-3. thru 3-4. RESERVED.
3-5. POSITION LOG, FAA FORM 7230-10.
a. Position logs shall be maintained by the CRU-ART software program. Hard copies of
position logs can be printed, if necessary. In the event of CRU-ART failure, paper logs shall be
used.
GENERAL CONTROL
3-1
TPA 7110.6E
01/13/2011
b. The following position identifiers and types shall be used within CRU-ART.
Figure 3-1 POSITION IDENTIFIERS
GENERAL CONTROL
Position
Final RADAR
Final Hand-off
Identifiers
F
FH
Type
FR
HO
East Departure
B
DR
East Departure Hand-Off
East Arrival
BH
E
HO
AR
East Arrival Hand-Off
East Satellite
EH
L
HO
SR
East Satellite Hand-Off
LH
HO
Flight Data RADAR
South Departure
FDR
G
FD
DR
South Departure Hand-Off
South Satellite
GH
S
HO
SR
South Satellite Hand-Off
SH
HO
West Arrival
West Departure
W
D
AR
DR
West Departure Hand-Off
West Arrival Hand-Off
DH
WH
HO
HO
West Satellite
P
SR
West Satellite Hand-Off
MacDill
PH
M
HO
SR
Lakeland Low
Lakeland Low Hand-Off
TRACON FLMIC/FLM/CIC
R
RH
SR/SR2
SR
HO
SI
Local Control One
LC1
LC
Local Control Two
Ground Control One
LC2
GC1
LC
GC
Ground Control Two
Cab Coordinator
GC2
CC
GC
CC
Flight Data/Clearance Delivery
FDT
CD
Internal Coordinator
External Coordinator
IC
XC
CI
CI
Tower FLM/CIC
SC
SC
Operations Manager
OM
SI
3-2
TPA 7110.6E
01/13/2011
3-6. POSITION RELIEF BRIEFING.
All position relief briefings shall be recorded. A two minute overlap period shall be applied
between the relieving and relieved specialist. The relieved specialist shall remain plugged into
the position and monitor the frequency during the overlap period.
3-7. POSITION RELIEF BRIEFING CHECKLIST.
Review position checklist to ensure that all required information has been relayed to the relieving
specialist. Record the position relief briefing.
a. STATUS INFORMATION AREA -- FLOW CONTROL, SPECIAL ACTIVITIES,
NOTAMS.
b. WEATHER -- ALTIMETER/WEATHER TRENDS.
c. EQUIPMENT – NAVAIDS, RADAR, RADIO, ETC.
d. AIRPORT CONDITIONS/ACTIVITIES and VERBALLY STATE RUNWAY
STATUS: unavailable, closed, occupied.
e. COMMUNICATION STATUS and TRAFFIC.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
Special activities, holding, NON-RADAR operations.
Aircraft standing by.
Coordination agreements with other positions.
Aircraft handed off but still in the airspace.
Primary targets, non-tagged targets.
Point-out aircraft/VFR advisory aircraft.
Aircraft released but not yet airborne.
Special problems, requests, or instructions.
Brief communications status of all known aircraft.
3-8. USE OF WIRELESS HEADSETS.
Wireless headsets may be used in the operating environment for purposes of general supervision
and position monitoring. Wireless headsets may not be used at any Tower or RADAR
operational positions including RADAR Hand Off, Coordinators or any assist positions for any
purpose, to include inter or intra facility coordination or for two-way communication with
aircraft. Wireless headsets may not be used while performing skill checks or certification
evaluations.
3-9. thru 3-19. RESERVED.
GENERAL CONTROL
3-3
TPA 7110.6E
01/13/2011
SECTION 2. STRIP MARKING
Figure 3-2.
3-20. PURPOSE.
The purpose of minimum strip marking is to reduce the controller's diversion time from the
position and is not intended to imply that necessary control / data information may be omitted
from the strip.
3-21. ARRIVAL FLIGHT PROGRESS STRIP MARKING.
IFR, Class B, Class C and Practice Approaches:
BLOCK:
1 = Aircraft Identification.
3 = Type Aircraft (number of aircraft if formation).
8 = Time in four digits that service was requested.
9 = Destination Airport.
9A = Other information as needed to control the aircraft.
3-22. DEPARTURE STRIPS.
a. IFR or VFR-on-TOP. Put information as required in the following blocks:
(1) Block 8A - Single letter DTA:
F=
GIRLE / GANDY RNAV
B=
SHOWW / SYKES RNAV
H=
BGTOP / CROWD RNAV
U=
ENDED / ENDED RNAV
N=
BAYPO / BAYPO RNAV (above 10,000 feet)
X=
BRNUM (10,000 feet and below, Tower Enroute to JAX).
A=
V441/LAL DTA
R=
KNEED DTA/Orlando Satellite arrivals (excluding ISM)
M=
MINEE/COSTR/LAL R-060/ISM
D=
DARBS/V97 (10,000 feet and below)
PT"C" = IR046 (Point C entry)
PT"E" = IR046 (Point E entry)
DAM = IR049, 50, and 51 entry
Y=
RSW West Sector (10,000 feet and below)
(2) Block 8 - A check mark (  ) following the departure airport to indicate clearance
delivered to satellite tower.
(3) Block 9 - Clearance limit.
GENERAL CONTROL
3-4
TPA 7110.6E
01/13/2011
(4) Block 10 = TPA Departures.
(a) Departure Procedure (DP).
T = TAMPA DP
C = CROWD RNAV
E = ENDED RNAV
G = GANDY RNAV
B = BAYPO RNAV
S = SYKES RNAV
NOTE: Indicating the DP in block 10 is optional.
(b) Assigned Heading.
(5) Block 12 - Assigned departure frequency (may be abbreviated, example .8, .65).
NOTE: Indicating the departure frequency in block 12 is optional.
(6) Block 14 - Gate Hold engine start time.
(7) Block 16 - Check mark (  ) or departure ATIS code indicates clearance delivered to
aircraft.
(8) Block 17 -Taxi time.
(9) Block 18 - Departure time when delays are being incurred.
b. Undelivered clearance changes shall be denoted in RED until delivered to the
aircraft/satellite tower (as appropriate). When delivered, place a checkmark next to the change to
indicate it has been forwarded.
c. VFR. A handwritten strip is required with the following information in the following blocks
on TPA departures:
(1) Block 1 - Aircraft Identification.
NOTE: Aircraft ID suffixed by "X" indicates aircraft in pursuit and requesting priority.
(2) Block 3 - Aircraft type.
(3) Block 5 - Beacon code assigned by STARS.
(4) Block 7 - Requested altitude.
(5) Block 8 – Letter “T” to indicate a TPA VFR departure.
(6) Block 9 - Destination or direction of flight. Special VFR, Class B, helicopters only.
Indicate in SVFR departure instruction(s) symbology per JO 7110.65.
(7) Block 10 - Departure heading.
(8) Block 12 - Assigned departure frequency (may be abbreviated, example .8, .65).
NOTE: Indicating the departure frequency in block 12 is optional.
(9) Blocks 13 thru 15 - UTC Time.
(10) Block 16 - Check mark (  ) or departure ATIS code indicates Class B clearance
delivered to aircraft.
GENERAL CONTROL
3-5
TPA 7110.6E
01/13/2011
3-23. ADDITIONAL STRIP MARKING AUTHORIZED FOR IFR
ARRIVAL/DEPARTURE STRIPS.
Put information as required in the following blocks:
a. Block 9 - Assigned (Center/TRACON) altitude.
b. Block 10 - Arrival Transition Fix (DADES, etc.).
c. Block 11 - Time over Arrival Transition Fix/time departed fix (split block).
d. Block 12 - Center/approach transfer of control time/fix.
e. Block 13 - Inner fix (PICNY, COSME, etc.).
f. Block 14 - Time over inner fix/time departed fix (split block).
g. Block 15 - "Z" to indicate transfer of control to the Tower.
h. Block 16 - Approach fix/time over fix (split block).
i. Block 17 - Time told to depart approach fix/time departed fix on final (split block) or
assumed departure time.
j. Block 18 - Arrival, missed approach, or departure time.
NOTE: Blocks 10 thru 15 on departure strip as needed for NON-RADAR. These blocks may
also be used for optional markings such as abbreviations for DP issued, heading, altitude and
departure frequency issued.
GENERAL CONTROL
3-6
TPA 7110.6E
01/13/2011
3-24. STRIP MARKING EXAMPLES.
IFR
H/B767/Q
GENERAL CONTROL
3-7
TPA 7110.6E
01/13/2011
3-24. STRIP MARKING EXAMPLES (continued)
3-25. thru 3-29. RESERVED.
SECTION 3. TRAFFIC MANAGEMENT
3-30. TRAFFIC MANAGEMENT MESSAGES.
a. Dissemination.
(1) FDIO and verbal traffic management messages shall be forwarded to the Tower
FLM/CIC and TRACON FLMIC/CIC.
(2) Post in strip bay at flight data and other Tower Cab positions as appropriate.
b. IDS-4. Applicable FDIO/verbal messages shall be entered on the SIA page in the IDS-4 by
the FLMIC/CIC.
GENERAL CONTROL
3-8
TPA 7110.6E
01/13/2011
c. Flow messages from ZMA TMU shall be considered valid for:
(1) All traffic that will initially enter ZMA airspace.
(2) Flow messages pertaining to TPA and RSW airspace.
(3) All airports with a ground delay program. This includes all messages and EDCT times,
including amendments.
(4) All ground stop messages.
d. Restrictions. ZJX TMU will only coordinate miles in-trail, minutes in-trail, or call for
release for aircraft that will initially enter ZJX or F11 Airspace. This coordination will be
handled by the TRACON FLMIC/CIC.
e. Coordination. The TRACON FLMIC/CIC will coordinate with ZMA TMU for aircraft
entering TPA airspace from ZMA and FMY airspace; and with ZJX TMU for aircraft entering
TPA airspace from F11, JAX and ZJX airspace.
3-31. thru 3-39. RESERVED.
SECTION 4. COMBINING/DECOMBINING POSITIONS
3-40. CHECKLIST.
The following actions must be completed prior to combining/decombining positions of
operation:
a. The CPC who had been working the position shall provide complete position relief briefing
to the controller who is taking the new combined or decombined position. Flight progress strips
will be passed as necessary.
b. RADAR positions shall hand-off all active traffic to the position of operation that will
assume control of the traffic and make appropriate STARS keyboard entries to consolidate or
deconsolidate the positions.
c. The FLMIC/CIC approving the combining/decombining of the position is responsible for
notifying all appropriate facilities and positions of operation within the facility of the action.
d. The FLMIC/CIC shall make appropriate entries on the CRU-ART reflecting the time of the
position combining/decombining.
3-41. COMBINING POSITIONS.
a. Transferring controller shall:
(1) Get FLMIC/CIC approval.
(2) Cancel automatic releases, if appropriate, and advise the FLMIC/CIC.
(3) Review the normal position relief checklist.
GENERAL CONTROL
3-9
TPA 7110.6E
01/13/2011
(4) Begin hand-off of pertinent traffic and exchange appropriate information.
(5) Verify that the receiving controller is ready to accept position responsibility. After
receiving positive confirmation, discontinue making interphone/radio transmissions relative to
the position released.
(6) Deselect the frequencies of the position transferred.
(7) Configure the STARS and call forward the RDVS as appropriate.
(8) LOGOUT on the IDS-4.
(9) Turn off the EFSTS printer.
b. Receiving controller shall:
(1) Quick look, via STARS, the active RADAR position.
(2) Select and monitor the proper frequencies.
(3) Review the normal position relief checklist and pertinent information.
(4) Make no interphone/radio transmissions regarding the position you are receiving until you
have received a complete briefing and assumed responsibility for the position.
(5) Indicate to the transferring controller when ready to assume position responsibility.
(6) Begin the full range of responsibilities for the position.
(7) If appropriate, advise the FLMIC/CIC when ready for automatic releases to resume.
c. Positions are normally combined as follows:
TRACON FLMIC/CIC to East Departure (Mid-Shift)
Lakeland Low RADAR to East Satellite
East Satellite to East Arrival
East Arrival
to East Departure
West Satellite
to West Arrival
West Arrival to West Departure
West Departure
to East Departure
South Departure to South Satellite
South Satellite to East Departure
MacDill
to South Satellite
Final RADAR:
Runway 1
to East Departure
Runway 19
to East Arrival
Flight Data RADAR to South Departure
Hand-off Positions to the appropriate RADAR position.
Tower FLM/CIC to Cab Coordinator 2
Flight Data/Clrnc. Del. to Ground Control 1
Ground Control 1 to Local Control 1
Ground Control 2 to Ground Control 1
Local Control 2 to Local Control 1
Cab Coordinator 1 to Cab Coordinator 2
Cab Coordinator 2 to Local Control 1
GENERAL CONTROL
3-10
TPA 7110.6E
01/13/2011
NOTE: This is not intended to mandate the order in which positions of operation are to be
combined. It is a method to determine the location of all positions and the person responsible
for the operations. Deviation from this manner of combining positions may be accomplished
only after thorough coordination with all affected positions of operation.
3-42. DECOMBINING POSITIONS.
When opening a position, the controller shall:
a. Ensure FLMIC/CIC is aware of the situation.
b. LOGIN on IDS-4.
c. After receiving approval, make STARS entry to configure the position open.
d. Coordinate active traffic transfer.
e. Cancel call forwarding on RDVS when needed.
f. Select appropriate frequencies on the RDVS.
g. Review the Position Relief Checklist.
h. Turn on the EFSTS printer.
3-43. MIDNIGHT CONFIGURATION.
a. All Tower positions to LC-1.
b. All TRACON positions to East Departure (B).
3-44. thru 3-49. RESERVED.
SECTION 5. BACKUP COMMUNICATIONS EQUIPMENT
3-50. Voice Switch Bypass (VSBP).
The VSBP provides access to one primary UHF/VHF frequency at each operating position.
Local Control and the South Satellite positions have the capability to select one of two frequency
sets by using a toggle switch located at the VSBP jack for those positions. To utilize the VSBP,
plug headset into the orange headset jack located at each position.
GENERAL CONTROL
3-11
TPA 7110.6E
01/13/2011
This page intentionally left blank
GENERAL CONTROL
3-12
TPA 7110.6E
01/13/2011
CHAPTER 4. TOWER GENERAL
SECTION 1. GENERAL DUTIES AND PROCEDURES
4-1. PRIMARY RESPONSIBILITIES OF THE TOWER TEAM POSITIONS.
a. LC and GC Position(s):
(1) Ensure separation.
(2) Initiate control instructions.
(3) Monitor and operate communications equipment.
(4) Utilize TDW.
(5) Utilize alphanumerics on the STARS keyboard.
(6) Assist the Cab Coordinator position.
(7) Visually scan Tower Cab environment.
(8) Ensure computer entries are complete.
(9) Ensure strip marking is complete.
(10) Process and forward flight plan information. Flight plan information shall be entered on
flight progress strips and inserted into strip holders in order to be processed and forwarded to the
appropriate strip bays.
(11) Perform any functions of the Tower Team that will assist in meeting situational
objectives.
b. CC Position:
(1) Ensure separation.
(2) Operate interphones.
(3) Maintain awareness of Tower Cab activities.
(4) Utilize alphanumerics on the STARS keyboard.
(5) Utilize TDW.
(6) Assist tower position(s) by accepting/initiating coordination for the continued smooth
operation of the Tower Cab and ensure that the Tower position(s) are made immediately aware
of any actions taken.
(7) Manage flight plan information.
(8) Ensure computer entries are complete.
(9) Ensure strip marking is complete.
(10) Perform interfacility/position coordination for traffic actions.
(11) Advise all Tower Team positions of Tower Cab actions required to accomplish overall
objectives.
(12) Perform any of the functions of the Tower Team that will assist in meeting situational
objectives.
(13) Manage traffic flows.
c. FDT Position(s):
(1) Operate communications equipment (i.e. interphones/radios).
TOWER GENERAL
4-1
TPA 7110.6E
01/13/2011
(2) Process and forward flight plan information. Flight plan information shall be entered on
flight progress strips and inserted into strip holders in order to be processed and forwarded to the
appropriate strip bays.
(3) Compile statistical data.
(4) Assist Tower Cab in meeting situation objectives.
(5) Report weather information.
(6) Utilize alphanumerics on the STARS keyboard.
(7) Issue clearances and ensure accuracy of pilot readback.
(8) Operate Tower equipment.
4-2. RESTRICTIONS.
When flow restrictions are in effect, use the following strip marking:
a. EDCT's issued by ZJX/ZMA in Block 13/14.
b. Underline airport identification in RED and write "CFR" in RED in Block 9 of the flight
progress strip when a release is required.
c. Place large RED "H" in Block 9 to indicate a ground hold.
4-3. MEDIA AREA.
In accordance with the TAMPA TOWER AND NEWS MEDIA AIRCRAFT USERS LOA, a
Media Area may be established for use by signatories of this LOA. The SC/CIC shall perform
all coordination required in the establishment and shut down of a Media Area.
4-4. CRITICAL AREAS.
ILS Localizer and Glideslope Critical Areas: When conditions in JO 7110.65 warrant, the ILS
Localizer and Glideslope Critical Areas shall be protected, as appropriate. The hold line for the
ILS glideslope critical area is on Taxiway E. These areas are depicted on the airport diagram at
GC and LC.
4-5. RUNWAY/TAXIWAY CLOSURES.
a. Only the following personnel are authorized to change the operational status of runways and
taxiways:
(1)
(2)
(3)
(4)
(5)
(6)
Airport #2, #8 or #9
Senior Director of Operations
Director of Operations
Deputy Director of Operations
Assistant Director of Operations (ADO)
Airport Operations Specialist (AOS)
TOWER GENERAL
4-2
TPA 7110.6E
01/13/2011
NOTE: When any of the above mentioned individuals close pavement for use by aircraft, they
are expected, under normal conditions, to be the ones who complete a final inspection and open
pavement for aircraft use.
b. This does not preclude Tower personnel from identifying an unsafe airport condition,
issuing advisories to all affected traffic, and having a NOTAM issued describing the condition.
c. Requests for closure of operational area pavement for maintenance or repair, other than
emergency situations, will be coordinated with HCAA to enable issuance of a NOTAM 48 hours
before scheduled closing.
d. When a runway is closed and/or a vehicle is on the runway, LC shall place the appropriate
memory aid in the strip bay/podium.
4-6. TRANSCEIVERS.
Tower:


2 VHF Portable Transceivers.
1 UHF Portable Transceiver.
4-7. TOWER TDW MAPS.
The TDWs are capable of displaying the same maps as the TCWs.
FIGURE 4-1 TOWER OPERATING POSITIONS.
North
TOWER GENERAL
4-3
TPA 7110.6E
01/13/2011
SECTION 2. WEATHER INFORMATION
4-8. DISSEMINATION.
a. National Weather Service observations are received via the ASOS OID located at Flight
Data Tower, and the Digital ATIS (D-ATIS).
b. RVR values are obtained from the instruments in the Tower and TRACON.
c. SIGMETS, AIRMETS, and CWA are received via FDIO.
d. ASOS --- relays current weather, temperature, dewpoint, wind, altimeter and remarks for
D-ATIS update.
e. DASI ---Issue current values for voice communications.
f. ITWS/LLWAS --- Issue current values for voice communications.
TOWER GENERAL
4-4
TPA 7110.6E
01/13/2011
CHAPTER 5. FLIGHT DATA/CLEARANCE DELIVERY
Frequency 133.6
SECTION 1. AUTOMATIC TERMINAL INFORMATION SERVICE (ATIS)
Arrival 126.45 - Departure 128.475
5-1. PREPARE ATIS INFORMATION.
a. Include in the ATIS content all items in JO 7110.65, as appropriate.
NOTE: The Air Traffic Manager has determined that a statement to readback instructions to
hold short of a runway is not required on the ATIS.
b. Digital arrival ATIS codes will be "Alpha" through "Mike" and digital departure ATIS
codes will be "November through Zulu."
c. In consideration of noise abatement procedures, include the following statements on each
ATIS broadcast, as appropriate:
(1) North Operation: Runway 1R is noise sensitive for jet arrivals.
(2) South Operation: Runway 19L is noise sensitive for air carrier jet departures.
d. When visual approaches to RWY 19L/19R or RWY 1L/1R are advertised, the term
"simultaneous visual approaches" shall be included as part of the ATIS broadcast.
5-2. ATIS FORMAT.
a. "TAMPA INTERNATIONAL AIRPORT ARRIVAL INFORMATION (Letter "A" thru
"M"). Time (Zulu). Wind three four zero at one zero. Visibility four, mist. Ceiling four
thousand five hundred broken. Temperature three four. Dew point two eight. Altimeter three
zero zero niner. Approaches in use (as appropriate). When on a north operation, insert statement
from para. 5-1 c. (1). Advise on initial contact you have information (letter)."
b. "TAMPA INTERNATIONAL AIRPORT DEPARTURE INFORMATION (Letter
"N" thru "Z"). Time (Zulu). Wind two one zero at one zero. Visibility seven. Ceiling four
thousand five hundred broken. Temperature three four. Dew point two eight. Altimeter three
zero one zero. Departing Runways (as appropriate). When on south operation, insert statement
from para. 5-1 c. (2). Advise on initial contact you have information (letter)."
FLIGHT DATA/CLEARANCE DELIVERY
5-1
TPA 7110.6E
01/13/2011
5-3. OPERATION.
a. Digital ATIS (D-ATIS) Equipment:
(1) Enter the Edit Screen by pressing "EDIT."
(2) Select appropriate options by pressing "ENTER." If a sub-menu drops down, select the
appropriate option by pressing "ENTER." When no sub-menu appears, you have finished with
the option. Press "SEND/ SAVE" on each sub-menu until you are back at the main edit screen.
After editing the ATIS, press "SEND/SAVE."
(3) By pressing "Send/Save," the Arrival ATIS Voice Text Message (AVTM) is generated
and is displayed on the D-ATIS screen. Monitor the pending Arrival ATIS by pressing the
"REVIEW" button on the Channel Monitoring Unit (CMU). If pronunciation changes need to be
made, do it here. If content changes need to be made, return to the edit screen (press "EDIT"),
make the changes, press "SEND/SAVE" and return to the AVTM screen to review. After the
Arrival ATIS is verified, press "SEND/SAVE". The Departure ATIS Voice Text Message
(AVTM) is displayed on the D-ATIS screen. Monitor the pending Departure ATIS. Follow the
same editing procedures as for the Arrival ATIS. After accuracy is verified, press
"SEND/SAVE" to return to the main screen.
(4) At the main screen, press "SEND/SAVE" again, and the send window will appear.
(5) Select "SEND ALL ATM’s" and press "ENTER."
(6) ARINC will acknowledge, the ATIS status will change from pending to transmitted to
current, and the new ATIS will start transmitting automatically.
b. Manual ATIS Equipment (Voice Recorders) Use the following switch settings to ensure the
manual ATIS equipment is not transmitting while being recorded.
(1)
(2)
(3)
(4)
Set ON LINE/OFF LINE switch to OFF LINE.
Set MONITOR RECORD switch to RECORD.
Depress the START/RESET switch and release.
Press push to talk button on handset record.
5-4. MONITOR ATIS.
a. Use the following to monitor the D-ATIS equipment:
(1) On the Voice Text Message Screen, press "REVIEW" button on the CMU to listen.
(2) To ensure the D-ATIS is transmitting, press "ARR BCST" and/or "DEP BCST" on the
CMU.
b. Use the following steps to monitor the manual ATIS equipment:
(1)
(2)
(3)
(4)
In OFF LINE MODE, set MONITOR/RECORD switch to MONITOR position.
Depress the START/RESET switch and release.
Hold the press to talk button on handset down.
Listen to recording.
NOTE: Aircraft Operators may call 878-2627 to monitor ATIS.
FLIGHT DATA/CLEARANCE DELIVERY
5-2
TPA 7110.6E
01/13/2011
c. Use the following steps to ensure the manual ATIS is transmitting:
(1) Set MONITOR/RECORD switch to MONITOR position.
(2) Set ON LINE/OFF LINE switch to ON LINE.
(3) Use the handset to monitor transmission.
5-5. DISSEMINATION.
a. Enter into the STARS Systems Area and the IDS the following items:
(1) Arrival ATIS alpha character in the STARS Systems Area (the absence of an ATIS alpha
character (letter) indicates the ATIS is inoperative).
(2) Type approach and runway information for TPA as follows:
(a) V19 - Simultaneous Visual Approaches to Runways 19L and 19R.
(b) 19 - Instrument approaches to Runways 19L and 19R.
(c) 1 - Instrument approaches to Runways 1L and 1R.
(d) V1 - Simultaneous Visual Approaches Runways 1L and 1R.
NOTE: When single runway approaches are in use, indicate in the Systems Area the runway
identifier for the active runway. (Example--V1L, 1L)
(3) TPA altimeter (STARS Systems Area only).
(4) TPA weather and current TPA ATIS codes in the IDS.
b. Advise the Tower FLM/CIC of ATIS code changes.
5-6. RESTRICTIONS.
When flow restrictions are in effect, use the following strip marking:
a. EDCT's issued by ZJX/ZMA in Block 13/14.
b. Underline airport identification in RED and write "CFR" in RED in Block 9 of the flight
progress strip when a release is required.
c. Place large RED "H" in Block 9 to indicate ground hold.
5-7. thru 5-10. RESERVED.
FLIGHT DATA/CLEARANCE DELIVERY
5-3
TPA 7110.6E
01/13/2011
Figure 5-1
SECTION 2. FLIGHT PLAN/STARS INFORMATION
5-11. IFR DEPARTURE AIRCRAFT.
a. Record the following information on a flight progress strip:
(1) Place single letter DTA identifier in Block 8A (IFR only).
NOTE: When no DTA appears on the flight progress strip, take appropriate action to determine
whether a DTA is required. If required, coordinate with ZMA PIT.
(2) Departure heading, or DP in Block 10.
(3) Departure frequency in Block 12.
NOTE: Indicating the DP in Block 10 and/or the frequency in Block 12 is optional.
(4) Place a check mark in Block 16 to indicate aircraft has received the clearance or place the
appropriate ATIS code in Block 16 to indicate the aircraft has received the clearance and the
current ATIS.
b. Ensure all FDIO generated TPA departure strips have printed barcodes in Block 4. Advise
the Tower FLM/CIC if a TPA departure strip does not have a barcode.
5-12. VFR AIRCRAFT.
a. Record the following information on a flight progress strip:
(1) Block 1 - Aircraft identification preceded by the letter "Z".
(2) Block 3 - Type aircraft.
(3) Block 5 - Assigned local VFR beacon code from STARS.
(4) Block 7 - Requested altitude.
(5) Block 8 - Letter "T" to indicate a TPA VFR departure.
(6) Block 9 - Destination airport or direction of flight.
(7) Block 10 - Assigned heading.
(8) Block 12 - Departure frequency (Optional).
(9) Blocks 13-15 - UTC Time.
(10) Block 16 - Check mark or ATIS code, if stated.
b. Determine the desired direction of flight and clear the aircraft out of Class B Airspace.
FLIGHT DATA/CLEARANCE DELIVERY
5-4
TPA 7110.6E
01/13/2011
5-13. SPECIAL VFR HELICOPTERS.
a. Determine the pilot’s intentions.
b. Enter the following information on a flight progress strip:
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
Block 1 - Aircraft ID preceded by the letter "Z".
Block 3 - Type aircraft.
Block 5 - Assigned local VFR beacon code from STARS.
Block 7 - Requested altitude.
Block 8 - Letter "T" to indicate a TPA VFR/Special VFR departure.
Block 9 - Special VFR symbol.
Block 9 - Destination airport or direction of flight.
Blocks 13-15 - UTC Time.
Block 16 - Check mark or ATIS code, if stated.
c. Issue the Special VFR clearance.
NOTE: Fixed wing aircraft are not authorized.
5-14. VFR HELICOPTER DEPARTURES.
Helicopters that call Clearance Delivery for clearances out of the TPA Class B Airspace shall be
issued a local VFR squawk and advised that TPA Tower (LC) will issue departure instructions.
Clearance Delivery shall enter the track file into the Tower STARS and record the information
on a flight progress strip.
5-15. STARS ENTRIES.
a. VFR Departures/Special VFR, beacon code assigned from STARS.
Aircraft call sign preceded by the letter "Z".
Space
NOTE: The following entries can be made in any order.
Space
Number one (1) followed by STARS Position Symbol ( 1L )
Space
Delta key (), Destination 3-letter identifier, or, if within the local area, single letter identifier
Space
Type Aircraft
Space
Requested Altitude
ENTER
FLIGHT DATA/CLEARANCE DELIVERY
5-5
TPA 7110.6E
01/13/2011
b. Modifying Tracks:
Multifunction key (F7)
Modify (M)
OK
Space
Beacon code or aircraft identification
Space
Position symbol
ENTER
5-16. thru 5-20. RESERVED.
SECTION 3. CLEARANCES/INSTRUCTIONS
5-21. DEPARTURES.
Make altitude and routing amendments in accordance with current LOAs.
a. Assign initial altitudes to departures assigned the TPA DP, RNAV or ATC assigned
headings as indicated in sub paragraph f below.
b. Aircraft that file 11,000 feet into ZJX airspace shall be amended in the FDIO to 10,000 feet.
c. On a Runway 19 operation: Issue non-turbojet aircraft departing 19 on an assigned heading
of 185 a restriction to cross PIE 116R (IFR) at or above 2,600 feet, or Runway 4 at MCF (VFR)
at or above 2,100 feet, maintain 3,000 feet or lower requested altitude. If advised unable, mark
the flight progress strip "UNABLE MCF" and assign a heading of 060, 1,600 feet, and East
Satellite frequency. Modify the STARS track to the "L", if necessary.
d. Expect further clearance to filed altitude 10 minutes after departure.
e. When a primary runway change occurs, issue appropriate clearance amendments to all
aircraft returned to clearance delivery frequency.
f. IFR TPA Departures. Assign the following instructions based on the departure runway and
direction of flight.
(1) NORTH OPERATION:
JETS
TPA DPs, Altitude 6,000
NOTE: Turbojet aircraft landing within TPA airspace may be assigned requested altitudes
lower than 6,000.
FLIGHT DATA/CLEARANCE DELIVERY
5-6
TPA 7110.6E
TURBOPROPS
OTHER ACFT
01/13/2011
DTA
U, N
10X & below
A, H, M, R
B, F, Y, D
HDG
340
025
025
310
B, D, F, U, N, Y 310
10X & below
060
A, H, M, R
060
Altitude
3,000
3,000
3,000
1,600
1,600
1,600
1,600
NOTE 1: Between 1900 LCL and 0700 LCL assign F, B, Y and D turboprops heading
340/3,000 feet.
NOTE 2: Aircraft landing in TPA airspace and CGC:
 Turboprops and props landing airports in P or S airspace or CGC shall be issued
heading 310/1,600 feet (except turboprops between 1900 LCL and 0700 LCL).
 Turboprops landing airports in L airspace shall be issued heading 025/3,000 feet.
 Props landing airports in L airspace shall be issued heading 060/1,600 feet.
(2) SOUTH OPERATION:
JETS
TPA DPs, Altitude 6,000
NOTE: Turbojet aircraft landing within TPA airspace may be assigned requested altitudes
lower than 6,000 feet.
DTA
TURBOPROP U, N, D, B
10X and below
A, M, R, H, F, Y
HDG
310
185 or TPA DP
185 or TPA DP
ALTITUDE
1,600
3,000
3,000
310
060
060
185 or TPA DP
1,600
1,600
1,600
3,000
OTHER ACFT U, N, D, B,
10X & below
A, M, R
H, F, Y
NOTE: Aircraft landing in TPA airspace and CGC:
 Turboprops and props landing airports in P airspace or at CGC shall be issued
heading 310/1,600 feet.
 Turboprops landing airports in S or L airspace, shall be issued TPA DP or
heading 185/3,000 feet.
 Props landing airports in S airspace shall be issued TPA DP or heading 185/3,000 feet.
 Props landing airports in L airspace shall be issued heading 060/1,600 feet.
FLIGHT DATA/CLEARANCE DELIVERY
5-7
TPA 7110.6E
01/13/2011
g. VFR TPA Departures. Assign the following departure instructions based on runway
configuration in use and direction of flight.
(1) NORTH OPERATION:
JETS
HDG
005
Altitude
6,000
NOTE: Turbojet aircraft landing within TPA airspace may be assigned requested altitudes
lower than 6,000 feet.
TURBOPROPS
310
340
025
1,600
3,000
3,000
OTHER ACFT
310
060
1,600
1,600
(2) SOUTH OPERATION:
JETS, RWY 19R
RWY 19L
HDG
205
215
Altitude
6,000
6,000
NOTE: Turbojet aircraft landing within TPA airspace may be assigned requested altitudes
lower than 6,000 feet.
TURBOPROPS
310
185
1,600
3,000
OTHER ACFT
310
060
185
1,600
1,600
3,000
NOTE: Assign headings closest aligned to requested direction of flight. Requested altitudes
lower than those listed above may be assigned. All 185 heading aircraft must cross MCF as
described in Section 5-21 c. LC shall have the option to change these departure headings for
maximum traffic flow efficiency.
h. Track files shall be modified to appropriate position in the STARS.
5-22. PRE-DEPARTURE CLEARANCES (PDC).
a. Clearance Delivery shall ensure the following is accomplished before transmitting predeparture clearances to the participating users:
FLIGHT DATA/CLEARANCE DELIVERY
5-8
TPA 7110.6E
01/13/2011
(1) Review the Flight Select Mode Screen for incoming flight plans for accuracy and route
integrity.
(a) If an aircraft's flight plan has been revised, but the flight has not yet been processed by
the computer "*REV*" will appear next to the aircraft identification. Clearance Delivery must
issue the clearance via radio. The flight plan may be dumped after the clearance is issued.
(b) If an aircraft's flight plan has been revised, and the clearance has already been
processed, "*REV*" will appear next to the aircraft's identification. FDT shall verbally notify
GC of any revisions. It is the responsibility of GC to relay any revisions.
(2) Enter the appropriate:
(a) TPA DP, or RNAV DP/transition and initial altitude restrictions.
(b) Appropriate Departure Control frequency.
(c) Instructions for the crew to advise GC of current ATIS code.
(d) Special information in options 4, 5 or 6. Improvised or controller-generated text shall
not contain ATC instructions. Only additional information such as traffic management or other
operational information may be included. All improvised text shall be clear and concise.
(3) Review the clearance items in the clearance for accuracy and understanding. The
following shall not be transmitted via PDC to the participating users:
(a) Any revised, amended, or duplicate flight plans.
(b) Full Route Clearances (FRC).
(c) Re-routes.
(d) Any clearances generated that may cause misunderstanding on the pilot’s interpretation
of a clearance.
(e) PDR/PDAR’s that do not reconnect to the filed route. (PDC software is programmed to
suppress this field)
(f) Clearances off satellite airports.
b. Transmit clearance to the participant network computer via data communication transfer and
indicate the clearance has been issued by placing a check mark in Block 16 of the flight progress
strip.
c. In the event of a problem with the PDC, switch systems by following the directions in
Fig. 5-2.
d. Notify TECH OPS if an outage/problem occurs with the system.
FLIGHT DATA/CLEARANCE DELIVERY
5-9
TPA 7110.6E
01/13/2011
FIGURE 5-2. PERFORMING A SYSTEM SWITCH OVER.
FLIGHT DATA/CLEARANCE DELIVERY
5-10
TPA 7110.6E
01/13/2011
CHAPTER 6. GATE HOLD
Frequency 121.7
6-1. LOCAL GATE HOLD PROCEDURES.
If the total anticipated delay at the runway will exceed 15 minutes, or the Tower FLM/CIC
deems it necessary, implement gate hold procedures as follows:
a. FLM/CIC shall:
(1) Advise the TRACON FLMIC/CIC when gate hold is initiated and when delays increase
or decrease in 15-minute increments.
(2) Staff the CC position as necessary.
(3) When feasible, advise the appropriate airline operations of ground hold delays for aircraft
that have already received a clearance.
b. FDT shall:
(1) Advise the pilot, when clearance is issued, to contact GC for engine start/gate release
time/taxi time.
(2) Forward all strips to GC after the clearance has been issued.
c. GC shall:
(1) Issue an expected engine start time. Enter the time (UTC) the delay begins in Block 17,
and gate release time in Block 14. The time shall be in four digits.
(2) Forward the strip to CC when taxi instructions have been issued.
d. CC shall obtain release from the appropriate TMU on aircraft requiring release.
e. LC shall record the departure time in four digits in Block 18 and distribute as appropriate.
f. The TRACON FLMIC/CIC shall:
(1) Advise satellite towers if they are affected.
(2) Advise the appropriate TMU when gate hold procedures are in effect, and when delays
exceed 15 minutes or more.
g. Satellite towers will coordinate with CC or GC for expect departure clearance times.
h. Aircraft operators will decide whether to absorb the delay at the gate, have the aircraft
towed, or taxi to a delay absorbing area.
GATE HOLD
6-1
TPA 7110.6E
01/13/2011
This page intentionally left blank
GATE HOLD
6-2
TPA 7110.6E
01/13/2011
CHAPTER 7. GROUND CONTROL (GC)
GC-1 Frequency 121.7 / GC-2 Frequency 121.35
7-1. AREA OF RESPONSIBILITY.
GC is responsible for all movement areas, excluding active runway(s).
7-2. COORDINATION.
a. Initiate coordination for runway crossing or temporary use of all or any portion of active
runways directly with LC.
b. Initiate requests at times when approval is likely to the maximum extent feasible. This will
require GC to become more keenly aware of LC's "picture".
c. GC Phraseology: Requests shall be made by first stating the active runway and position
along that runway where the crossing will take place, and then the aircraft company(s) name(s)
or type(s). If more than one aircraft is at the same position, also state the number of aircraft
involved.
EXAMPLE: "Cross Runway 1 Right at Juliet with a Cessna and Learjet." or "Cross Runway 1
Right at departure end with a Delta B757."
d. GC requests for use of a portion of, or all of, an active runway shall include all information
concerning the need for the operation, estimated time frames involved, and advise when
operation is complete.
EXAMPLE: "Clear of Runway 1L."
e. LC shall keep GC advised of the status of RWY 10/28. The following procedures shall be
used to accomplish this:
(1) When LC advises GC RWY 10/28 is not active, LC releases use of RWY 10/28 to GC
without additional coordination.
(2) LC shall verbally request to activate RWY 10/28, and upon approval, illuminate the red
light located at the GC position indicating the runway is active. GC will utilize the brightlycolored "RWY 10/28 ACTIVE" strip holder.
(3) LC shall verbally advise GC and turn off the red light when RWY 10/28 is no longer
active and released back to GC. GC will discontinue use of the "RWY 10/28 ACTIVE" strip
holder.
f. GC shall verbally coordinate with LC for intersection/inactive runway departures.
Intersection/inactive runway departures shall be indicated in Block 8.
EXAMPLES: "XU", "10XE" or "28"
GROUND CONTROL
7-1
TPA 7110.6E
01/13/2011
g. GC may indicate in Block 8, which parallel taxiway an aircraft is on, as an aid to assist local
control in determining the taxiing sequence.
EXAMPLES: "V", "W" / "E", "D"
h. When the CC position is not staffed, GC shall ensure aircraft that need a release from TMU
are verbally released by TMU and the strip properly marked.
i. GC shall forward flight progress strips to the appropriate LC position.
j. When TPA changes runways and such conditions warrant amendments to departure
instructions, GC shall instruct aircraft to contact clearance delivery for amended
clearances/departure instructions and/or STARS modifications.
7-3. RESTRICTED GROUND MOVEMENT INSTRUCTIONS.
a. When traffic is landing RWY 10, hold traffic on Taxiway W at the RWY 10 hold lines to
protect the RWY 10 clear zone.
b. Reduced Visibility Conditions: When aircraft cannot be seen from the tower, use the
following phraseology at the time of initial taxi clearance or when conditions dictate.
"CAUTION, AIRCRAFT NOT VISIBLE FROM THE TOWER."
c. During periods when runways are not visible from the tower and the SMGCS plan is not
applicable, GC shall taxi aircraft in such a manner so as not to inhibit LC’s ability to exit the
active runways at normal exit points.
(1) Runway 1.
(a) If RWY 1R RVR is 1,200 or greater, use RWY 1R for departures and land on RWY 1L.
If RWY 1R RVR decreases below 1,200, then RWY 1L shall be used for arrivals and departures.
(b) GC when taxiing outbound, shall utilize Taxiways Y1, Y, or V4 from the west airsides,
and taxiways A13, A14, and L from the east airsides.
(c) LC shall exit RWY 1L at Taxiway W5 or beyond and RWY 1R at Taxiway H or
beyond.
(2) Runway 19.
(a) All departures from the terminal gates should be assigned RWY 19R allowing LC
exclusive use of RWY 19L for arrivals.
(b) GC when taxiing outbound shall utilize taxiways V5, V6, A7 from the west airsides, and
taxiways A12 and beyond from the east airsides.
(c) LC shall exit RWY 19R at Taxiway W4 or beyond and RWY 19L at Taxiway J or
beyond.
d. When the runways are visible from the tower, GC and LC should adhere to the described
taxiway, exit points and taxiing routes, to the extent practical.
GROUND CONTROL
7-2
TPA 7110.6E
01/13/2011
e. RWY 10/28 is not normally available for air carrier operations. However, operational
conditions may dictate RWY 10/28 use by these aircraft. Such conditions may be:
(1)
(2)
(3)
(4)
wind/velocity factor.
the unavailability of the north/south runways.
noise abatement.
other reasons.
7-4. ILS CRITICAL AREAS.
a. ILS Localizer Critical Areas: When conditions in JO 7110.65 warrant, the ILS Localizer
Critical Area shall be protected, as appropriate. These areas are depicted on the airport diagram
at GC.
b. ILS Glide Slope Critical Area for RWY 19L: When conditions in JO 7110.65 warrant, the
ILS Glide Slope Critical Area for RWY 19L shall be protected. The hold line for the ILS Glide
Slope Critical Area is on Taxiway E.
7-5. MISCELLANEOUS.
a. Run-ups: Turbojets shall conduct run-ups at the airport’s Ground Run-Up Enclosure (GRE)
located on the east side of RWY 19L/1R. Users are responsible to contact HCAA to schedule
use of the GRE.
b. Bomb Threat Area: Contact HCAA for instructions on directing the aircraft to a secure
area.
c. General Aviation Aircraft Parking/Unloading. Unless approved by the appropriate
authority, (i.e. airlines, HCAA, etc.) all arriving non-air carrier aircraft should be directed to the
General Aviation areas. If the pilot advises he wants to go to the terminal or a specific gate,
direct him to the desired area. When the aircraft is clear of the movement area, issue the
following:
"Contact (appropriate air carrier/air taxi) on (appropriate frequency) for security area
approval."
d. Military aircraft parking is normally located on the east end of the Signature ramp.
e. Customs gates are to be assigned as follows: (As requested by Customs)
(1) Aircraft with a General Aviation call sign go to the Customs ramp, located between
Signature and Tampa International Jet Center.
(2) All other aircraft go to Gates 88-90.
(3) Other gate assignments from Customs are relayed to aircraft as requested on an individual
basis.
GROUND CONTROL
7-3
TPA 7110.6E
01/13/2011
7-6. SPLIT LOCALS.
When split locals are in operation, GC should assign aircraft the runway best suited for direction
of flight to reduce coordination.
7-7. NOISE ABATEMENT PROCEDURES.
When TPA is on RWY 19, GC shall assign RWY 19R to air carrier type turbojets and may
assign RWY 19L or 19R, as appropriate, to corporate turbojets.
NOTE: If the pilot requests an operation contrary to the informal noise and runway use
program, and does not state the reason, it is understood that an operational necessity exists.
GROUND CONTROL
7-4
TPA 7110.6E
01/13/2011
CHAPTER 8. LOCAL CONTROL (LC)
LC-1 Frequency 119.5 / LC-2 Frequency 119.05 / 269.4 Shared
8-1. DEPARTURE RELEASES.
a. When the TRACON FLMIC/CIC has approved automatic releases for departure traffic
("Automatics"), LC may clear IFR/VFR aircraft for departure without individual coordination,
using headings specified below.
b. When changing runways, automatic departures are canceled. Automatics can be canceled
by any position, but the TRACON OMIC/FLMIC/CIC must be notified. Only the TRACON
OMIC/FLMIC/CIC may resume automatics.
c. Initial Departure Tracks. Headings shall be assigned to ensure aircraft remain on the
designated tracks.
(1)
(2)
(3)
(4)
(5)
Runways 1L or 1R --- track 025, 340, 360
Runway 19R ------------- track 180, 200
Runway 19L ------------- track 180, 210
Runway 28 --------------- track 270
Runway 10 --------------- track 090
d. Initial departure headings may be amended (subject to noise abatement) as conditions or
traffic warrant, with appropriate coordination and/or STARS track modification.
e. Use of the EFSTS is not considered coordination, except for a nonverbal rolling/boundary
notification.
f. Release IFR departure aircraft as follows:
(1) NORTH OPERATION:
JETS
TPA DPs, Altitude 6,000 feet.
NOTE: Turbojet aircraft landing within TPA airspace may be assigned requested altitudes
lower than 6,000 feet.
TURBOPROPS
OTHER ACFT
LOCAL CONTROL
DTA
U, N
10X & below
A, H, M, R
B, F, Y, D
HDG
340
025
025
310
B, D, F, U, N, Y 310
10X & below
060
A, H, M, R
060
Altitude
3,000
3,000
3,000
1,600
1,600
1,600
1,600
8-1
TPA 7110.6E
01/13/2011
NOTE 1: Between 1900 LCL and 0700 LCL assign F, B, Y and D turboprops heading
340/3,000 feet.
NOTE 2: Aircraft landing in TPA airspace and CGC:
 Turboprops and props landing airports in P or S airspace or CGC shall be issued
heading 310/1,600 feet (except turboprops between 1900 LCL and 0700 LCL).
 Turboprops landing airports in L airspace shall be issued heading 025/3,000 feet.
 Props landing airports in L airspace shall be issued heading 060/1,600 feet.
(2) SOUTH OPERATION:
JETS
TPA DPs, Altitude 6,000 feet.
NOTE: Turbojet aircraft landing within TPA airspace may be assigned requested altitudes
lower than 6,000 feet.
DTA
TURBOPROP U, N, D, B
10X and below
A, M, R, H, F, Y
OTHER ACFT U, N, D, B,
10X & below
A, M, R
H, F, Y
HDG
310
185 or TPA DP
185 or TPA DP
310
060
060
185 or TPA DP
ALTITUDE
1,600
3,000
3,000
1,600
1,600
1,600
3,000
NOTE: Aircraft landing in TPA airspace and CGC:
 Turboprops and props landing airports in P airspace or at CGC shall be issued heading
310/1,600 feet.
 Turboprops landing airports in S or L airspace, shall be issued TPA DP or heading
185/3,000 feet.
 Props landing airports in S airspace shall be issued TPA DP or heading 185/3,000 feet.
 Props landing airports in L airspace shall be issued heading 060/1,600 feet.
g. Release VFR TPA departure aircraft as follows:
(1) NORTH OPERATION:
JETS
HDG
005
ALTITUDE
6,000
NOTE: Turbojet aircraft landing within TPA airspace may be assigned requested altitudes
lower than 6,000 feet.
LOCAL CONTROL
8-2
TPA 7110.6E
TURBOPROPS
OTHER ACFT
01/13/2011
310
340
025
310
060
1,600
3,000
3,000
1,600
1,600
(2) SOUTH OPERATION:
JETS, 19R
19L
HDG
205
215
ALTITUDE
6,000
6,000
NOTE: Turbojet aircraft landing within TPA airspace may be assigned requested altitudes
lower than 6,000 feet.
TURBOPROPS
310
185
1,600
3,000
OTHER ACFT
310
060
185
1,600
1,600
3,000
NOTE: Assign headings closest aligned to requested direction of flight. Requested altitudes
lower than those listed above may be assigned. All 185 heading aircraft must cross MCF as
described in 5-21 c. LC shall have the option to change these departure headings for maximum
traffic flow efficiency.
h. LC shall ensure that aircraft assigned headings 310 or 060 on a runway 19 operation are on
a track of 310 or 060 prior to transfer of communications.
i. Traffic Management Guidelines:
(1) Review flight progress strips for Traffic Management restrictions.
(2) Aircraft with EDCT may be released up to 5 minutes prior to or 5 minutes after the
EDCT.
(3) Review flight progress strips for a Release/Clearance Void Time.
(a) Plan and control departure sequence to meet these times or coordinate for new times.
(b) LC shall not depart an aircraft whose strip is marked CFR (call for release), until
released by TMU.
j. TPA departures are released for turns upon transfer of communications, however, the
departure controller shall protect the automatic departure headings.
LOCAL CONTROL
8-3
TPA 7110.6E
01/13/2011
8-2. ARRIVAL/DEPARTURE PROCEDURES.
a. LC shall provide visual separation within 5 miles on arrivals when the reported ceiling is
3,000 feet or greater, and visibility 5 miles or greater. LC may apply visual separation when
conditions are less, as coordinated. Inform Final in a timely manner when visual separation can
not be applied with or between particular aircraft. Wake turbulence separation is the Final
Controller’s responsibility.
b. Helicopter Operations:
(1) Landing Areas: Runways, taxiways, and non-movement areas (police ramp, general
aviation ramps, mosquito control ramp, etc.).
(2) VFR Helicopter Departures. LC shall issue a clearance to helicopters requesting to depart
the TPA Class B airspace, via the pilot's requested direction of flight, if able.
(3) Special VFR Helicopters. Determine the pilot's intentions. Clear the aircraft to operate
within the TPA Class B surface area, to enter/out of/through the TPA surface area.
c. Flight progress strips are required on all departing aircraft. Handwritten strips are required
for all non-computer-counted operations.
8-3. LINE UP AND WAIT (LUAW) OPERATIONS.
a. Scope. Traffic demand and complexity mandate that an operational need exists at TPA to
conduct LUAW operations. A review is conducted dynamically on a day-to-day basis by
management of the airport configuration, staffing, weather and the Traffic Situation Display
(TSD) before authorizing LUAW operations. Personnel shall maintain an emphasis on situational
awareness and management of the operational environment with a goal toward eliminating
distractions.
b. TPA Procedures (General). The general requirements for conducting LUAW are contained
in JO 7110.65, Air Traffic Control, and JO 7210.3, Facility Operation and Administration.
Requirements specific to TPA LUAW operations have been consolidated into this directive.
(1) The Tower FLM/CIC shall advise all Tower Cab positions when LUAW is authorized
and terminated.
(2) When an aircraft is authorized to LUAW, inform it of the closest traffic inbound to the
same runway.
(3) LUAW may be utilized in both VFR and IFR weather conditions, however, do not
authorize an aircraft to LUAW when the departure point is not visible from the Tower.
(4) LUAW is authorized from an intersection from sunrise to sunset only.
(5) Do not authorize aircraft to LUAW on the same runway.
c. Methods to assist LC.
(1) GC must ensure LC receives the departure information in the taxi sequence for each
runway, and must advise LC when taxiing an aircraft for an intersection departure.
LOCAL CONTROL
8-4
TPA 7110.6E
01/13/2011
(2) LC shall indicate an aircraft is in position to hold by offsetting the strip in the strip bay.
(3) Ensure the "LUAW AUTHORIZED" memory jogger is posted at the LC position when
LUAW procedures are authorized.
(4) Ensure the "LUAW NOT AUTHORIZED" memory jogger is posted at the LC position
when LUAW procedures are not authorized.
d. Consolidation and Staffing of Positions.
(1) LC shall not be combined with any other position, except LC-1 and LC-2 may be
combined.
(2) Supervisor/CIC position is not combined with LC.
(3) CC shall be staffed.
e. Landing Clearance.
(1) Withhold landing clearance: Do not clear an aircraft to land, touch-and-go, option or low
approach on the same runway with an aircraft that has been cleared to LUAW until the aircraft in
position starts takeoff roll.
(2) Withhold LUAW clearance: Do not clear an aircraft to LUAW if an aircraft has been
cleared to land, touch-and-go, option or low approach on the same runway.
f. Runway Geometry.
(1) The airport diagram for the Tampa International Airport is depicted in Figure 8-1.
(2) LUAW is authorized for Runways 10/28 simultaneously with LUAW on Runways
19L/1R. Traffic must be issued between affected aircraft.
g. Fleet Mix. There are no unique fleet mix considerations for LUAW operations at TPA.
h. Volume/Complexity. There are no restrictions to LUAW operations at TPA based on
volume or complexity. However, vigilance must be exercised to maintain situational awareness.
i. Obstructions to Visibility. There are no known or permanent obstructions or limitations to
visibility from controller-to-aircraft or aircraft-to-aircraft perspectives that impact LUAW
operations at TPA.
LOCAL CONTROL
8-5
TPA 7110.6E
01/13/2011
FIGURE 8-1. TPA INTERNATIONAL AIRPORT.
LOCAL CONTROL
8-6
TPA 7110.6E
01/13/2011
8-4. LAND AND HOLD SHORT OPERATIONS (LAHSO).
These procedures were developed in accordance with FAAO 7110.118, Land and Hold Short
Operations, (LAHSO). The purpose of these procedures is to increase airport capacity, reduce
delays and mitigate controller workload.
a. TPA Tower is authorized to apply the following procedures when utilizing LAHSO for
aircraft landing on RWY 28 to hold short of RWY 19L/1R and for aircraft landing on RWY 19L
to hold short of RWY 28 in accordance with the following:
(1) LAHSO operations will only be conducted with Part 91, General Aviation users.
(2) Weather conditions must be equal to or greater than a ceiling of 1,000 feet and a visibility
of 3 statute miles (basic VFR).
(3) The LAHSO runway must be dry.
(4) The tailwind on the hold short runway shall be calm (less than 3 knots).
(5) Experimental aircraft and solo student pilots are excluded from LAHSO.
(6) LAHSO operations shall NOT be utilized if wind shear advisories are in effect.
(7) LAHSO operations are not authorized at night. There are no nighttime hold short
markings.
(8) The following message shall be broadcast on the ATIS; "LAHSO in Effect for Part 91
users only" or each involved aircraft must be advised of LAHSO operations.
b. Runway Available Landing Distances (ALD) for LAHSO are:
(1) RWY 28 has 4,350 feet of runway to RWY 19L/1R intersection.
(2) RWY 19L has 5,650 feet of runway to RWY 28 intersection.
c. Only group 1 through 4 aircraft, as listed in JO 7110.65 Appendix A, will be allowed to
participate in LAHSO, when the aircraft holding short is landing on RWY 28. These aircraft are
listed in the IDS.
d. Only group 1 through 6 aircraft, as listed in JO 7110.65 Appendix A, will be allowed to
participate in LAHSO, when the aircraft holding short is landing on RWY 19L. These aircraft
are listed in the IDS.
e. RWY 1R traffic shall not be assigned to hold short of RWY 10/28. RWY 10 traffic shall not
be assigned to hold short of RWY 1R.
f. Traffic may depart RWY 1R or RWY 19L with traffic landing RWY 28 to hold short of
RWY 19L/1R.
g. Traffic may depart RWY 10 or RWY 28 with traffic landing RWY 19L to hold short of
RWY 10/28.
LOCAL CONTROL
8-7
TPA 7110.6E
01/13/2011
FIGURE 8-2 AIRCRAFT GROUP/DISTANCE MINIMA.
RWY 19L holding short of RWY 10/28, 5650 feet available, Groups 1-6 authorized.
RWY 28 holding short of RWY 19L/1R, 4350 feet available, Groups 1-4 authorized.
LOCAL CONTROL
8-8
TPA 7110.6E
01/13/2011
8-5. COORDINATION.
Other operations that require coordination are:
a. Runway 10/28.
(1) LC shall keep GC advised of the status of RWY 10/28. When LC advises GC RWY 10/28
is not active, LC releases use of RWY 10/28 to GC without coordination.
(2) LC shall verbally request to activate RWY 10/28, and upon approval, illuminate the red
light located at the GC position indicating the runway is active. The green light illuminated at
LC indicates RWY 10/28 is active.
(3) LC shall verbally advise GC and turn off the red light when RWY 10/28 is no longer
active and when the runway is released back to GC.
b. Failure to Autoacquire. LC shall advise the appropriate TRACON controller within two (2)
miles of the departure runway in the event a departure fails to autoacquire. On aircraft without a
transponder, start a track on the primary target and modify or handoff to the appropriate RADAR
position.
c. Speed Adjustment. Speed adjustment of aircraft on final approach course.
d. In the event of a go around or missed approach, instruct the aircraft to climb or descend, as
necessary, to maintain 1,600 feet. Then verbally coordinate the missed approach instructions
with the appropriate RADAR position.
e. Transfer of Identity.
(1) LC shall monitor the TDW in accordance with JO 7110.65, utilizing the quick-look
feature of the STARS for transfer of identity from Final.
(2) In the event TDW is out of service, advise Final to forward arrival information to Tower,
and verbally coordinate as necessary.
f. Coupled Approach / Autoland / CATIII. When advised by Final that a "coupled approach",
etc., is in use, advise Final of any aircraft/vehicle that is within the ILS critical areas.
g. TPA Runway Change. When runway changes occur, LC may instruct aircraft to contact
Clearance Delivery for amended clearances/climbout instructions and/or STARS modifications
when required.
h. Windshear Reports. Forward automated and pilot reported windshear to the Tower
FLM/CIC and disseminate per JO 7110.65.
i. Bird Advisories. Forward Bird Activity reports to the Tower FLM/CIC and disseminate per
JO 7110.65.
LOCAL CONTROL
8-9
TPA 7110.6E
01/13/2011
8-6. TAXIWAY USAGE.
a. Provide taxi instructions, as appropriate to arriving aircraft when clearing the active runways
per JO 7110.65.
b. Unless LC can visually ascertain when an arrival is clear of the landing runway, LC shall
retain communications with arriving aircraft until the pilot reports clear of the runway.
c. During periods when runways are not visible from the tower, LC shall verbally coordinate
with GC if aircraft will exit the runway prior to the normal exit points described below:
(1) RWY 1:
LC shall exit RWY 1L at Taxiway W5 or beyond and RWY 1R at Taxiway H or beyond.
(2) RWY 19:
LC shall exit RWY 19R at Taxiway W4 or beyond and RWY 19L at Taxiway Juliet or
beyond.
(3) When the runways are visible from the tower, GC and LC should adhere to the described
taxiway exit points and taxiing routes, to the extent practical.
NOTE: The adjacent parallel taxiways may be used by LC for air carrier type aircraft clearing
the runways at the described normal exit points. Communications change to GC frequency may
not occur until LC is assured the arriving aircraft is clear of the runway.
LOCAL CONTROL
8-10
TPA 7110.6E
01/13/2011
FIGURE 8-3. TOWER AIRSPACE RWY 1
TOWER AIRSPACE
RWY 1
16
0
LOCAL CONTROL
8-11
TPA 7110.6E
01/13/2011
FIGURE 8-4. TOWER AIRSPACE RWY 19
TOWER AIRSPACE
RWY 19
16
0
LOCAL CONTROL
8-12
TPA 7110.6E
01/13/2011
8-7. RUNWAY USE PRIORITY.
From 12:00 Midnight to 6:00 a.m. When traffic, wind, weather, and field conditions permit, and
no reportable delays to arrivals or departures will result, LC shall use RWY 19R for turbojet
departures and RWY 1L for turbojet arrivals.
8-8. ELECTRONIC FLIGHT STRIP TRANSFER SYSTEM (EFSTS).
LC shall:
a. Scan all bar-coded departure strips prior to communications transfer. VFR departure strips
will be handwritten and will not have a barcode. The scanner emits different beeps:
(1) 1 Beep (2-toned) = strip successfully scanned.
(2) 3 Beeps = strip previously scanned.
(3) 5 Beeps = flight plan timed out or not in system.
b. Redirect to the correct TRACON position (by scanning a "Redirect to Printer" strip) any
strip that has been modified to a different position in the STARS.
c. Store all strips in the strip holder at the LC position.
d. Advise the FLM/CIC if the scanner or keypad fails.
e. Coordinate with departure any flight plans that have timed out.
f. Ensure that other than normal headings and altitudes are printed on the strips for the
TRACON by inputting the heading/altitude on the keypad before scanning the strip. The keypad
entries are:
(1)
(2)
(3)
(4)
(5)
(6)
HDG = Press this, then enter 3-digit heading
ALT = Press this, then enter 2-digit altitude
310 = Press this to enter a 310 heading
060 = Press this to enter a 060 heading
340 = Press this to enter a 340 heading
025 = Press this to enter a 025 heading
g. To have a heading/altitude printed on a strip AND redirect the strip to the correct departure
position, use this sequence: type the heading/altitude, scan the redirect to printer strip, and then
scan the flight progress strip.
LOCAL CONTROL
8-13
TPA 7110.6E
01/13/2011
This page intentionally left blank
LOCAL CONTROL
8-14
TPA 7110.6E
01/13/2011
CHAPTER 9. SPLIT LOCAL / SPECIAL EVENT PROCEDURES
9-1. SPLIT LOCAL PROCEDURES.
When LC-1/LC-2 are split, the following procedures apply:
a. Local Control 1 (LC-1), West Local, frequency 119.5/269.4.
b. Local Control 2 (LC-2), East Local, frequency 119.05.
c. Runways and delegated airspace are depicted in Figures 8-3 and 8-4.
d. Departure Procedures. Departure headings are delegated to the respective LC as follows.
Each LC shall coordinate aircraft entering into the other LC's delegated airspace.
(1) North Operation
LC-1
310, 340
LC-2
TPA DPs, 005, 025, 060
NOTE: LC-1 shall coordinate all TPA DPs and 005, 025, 060 headings with LC-2.
(2) South Operation
LC-1
TPA DPs (except 183), 310, 215, 205
LC-2
TPA DP (heading 183 only), 185, 060
NOTE: LC-2 shall coordinate all TPA DPs (except 183), 205, 215, and 310 headings with LC-1.
9-2. SPECIAL EVENT PROCEDURES.
a. LC-2 may be utilized as a special event or media control position as needed to accommodate
local events and Temporary Flight Restrictions (TFR).
b. During Special Event / Media Procedures, LC-1 retains all responsibility for all arrivals and
departures, and retains all headings for the runway configuration in use.
c. In accordance with the Tampa Tower and News Media Aircraft Users LOA, a Media Area
may be established for use by signatories of this LOA. The FLM/CIC shall perform all
coordination required in the establishment and shut down of a Media Area.
d. LC-2 shall be delegated airspace as needed to accommodate the requested operation. The
FLM/CIC shall clearly define this airspace delegated to LC-2, and shall coordinate the operation
with LC-1 and all affected TRACON positions.
SPLIT LOCAL/SPECIAL EVENT PROCEDURES
9-1
TPA 7110.6E
01/13/2011
FIGURE 9-1. NORTH OPERATION LC-1 (WEST) / LC-2 (EAST) AIRSPACE
West Local Control
(LC-1)
East Local Control
(LC-2)
16
0
SPLIT LOCAL/SPECIAL EVENT PROCEDURES
16
0
9-2
TPA 7110.6E
01/13/2011
FIGURE 9-2. SOUTH OPERATION LC-1 (WEST) / LC-2 (EAST) AIRSPACE
East Local Control
(LC-2)
West Local Control
(LC-1)
16
0
SPLIT LOCAL/SPECIAL EVENT PROCEDURES
16
0
9-3
TPA 7110.6E
01/13/2011
This page intentionally left blank
SPLIT LOCAL/SPECIAL EVENT PROCEDURES
9-4
TPA 7110.6E
01/13/2011
CHAPTER 10. CAB COORDINATOR (CC)
10-1. POSITION REQUIREMENTS.
To perform the duties of the CC position, the specialist shall be certified on all other Tower
positions.
10-2. RESPONSIBILITIES.
The CC position shall not be combined with FDT. The specialist shall maintain awareness of the
traffic situation. Additionally, it is CCs duty to scan LC and GC areas of responsibility to
perform the necessary duties required to assist with the following:
a. Preventing runway incursions and losses of separation.
b. Determining active runways.
c. Coordination with the TRACON for sequencing of TPA arrivals.
d. Monitoring the TDW, in accordance with JO 7110.65, utilizing the quick-look feature of the
STARS for transfer of identity from the TRACON Final position.
e. Coordinating initial departure headings when conditions or traffic warrant non-standard
headings.
f. Coordination required between TPA Tower/TRACON and satellite facilities during times of
flow control/gate hold to ensure delays are absorbed equitably within the terminal area.
g. Entry or modification of STARS track files for TPA departures as appropriate.
h. Ensuring that aircraft that need a release from TMU are verbally released by TMU and the
strip properly marked.
CAB COORDINATOR
10-1
TPA 7110.6E
01/13/2011
This page intentionally left blank
CAB COORDINATOR
10-2
TPA 7110.6E
01/13/2011
CHAPTER 11. FLIGHT DATA RADAR (FDR)
SECTION 1. COMMUNICATE AND COORDINATE AIR TRAFFIC INFORMATION
11-1. PRIORITIES.
a. Active amendments.
b. Weather posting.
c. Strip posting.
d. Pre-taxi clearances.
e. Other duties.
11-2. DUTIES AND RESPONSIBILITIES.
a. Make altitude and routing amendments in accordance with current LOAs.
b. DTA identifiers are required on flight progress strips for aircraft filed into ZJX or ZMA
airspace. FDR shall contact ZMA PIT for a DTA.
c. Make other amendments as requested.
d. Issue clearances to AFSS only when authorized by TRACON RADAR controller.
e. Issue pre-taxi clearances or amended information to BOW Tower, and other towered
facilities without an operational FDIO as follows:
(1) Pre-taxi clearances include the aircraft identification, aircraft type, transponder code,
proposed time of departure, requested altitude, destination identifier, and route of flight and
DTA. These clearances shall be void 1 hour + 30 minutes after the proposed departure time or
when the satellite tower closes, whichever is earlier.
(2) Forward any amended flight plan information.
(3) A check mark in Block 8 of the flight progress strip, following departure airport, indicates
clearance delivered to the satellite tower.
f. Overflights IFR. Blocks 10 thru 18 - an arrow denoting the general direction of flight.
g. Post and keep satellite weather current on the IDS.
h. All pertinent messages, such as weather and flow, received on the FDIO shall be given to
the TRACON FLMIC/CIC.
11–3. thru 11–10. RESERVED.
FLIGHT DATA RADAR
11-1
TPA 7110.6E
01/13/2011
SECTION 2. FLIGHT PLAN INFORMATION
11-11. PROCEDURES.
a. All flight plans must be entered into the FDIO, except flight plans that will remain within
TPA approach control airspace may be processed manually.
b. During normal operations, arrival flight progress strips shall not be posted.
c. Overflight and departure flight progress strips shall be posted at the position where initial
communications with the aircraft will occur.
d. During RADAR and/or STARS outages, all flight progress strips shall be posted at the
position where initial communications with the aircraft will occur.
e. Pertinent flight information, including departure amendments, shall be relayed to towered
facilities without an operational FDIO, and to AFSS, if necessary.
11-12. STRIP MARKING.
Place in Block 8 of the proposed departure strip the assigned DTA, using these single-letter
identifiers:
a. U = END3D/ENDED RNAV-- above 10,000 feet; and V35/CTY 10,000 feet & below.
b. N = BAYPØ/BAYPO RNAV -- above 10,000 feet.
c. D = DARBS/V97 10,000 feet and below.
d. H = BGTOP/CROWD RNAV
e. F = GIRLE/GANDY RNAV
f. B = SHOWW/SYKES RNAV
g. X = BRNUM 10,000 feet and below.
h. A = V441/LAL DTA
i. R = V152/Orlando Satellite arrivals
j. M = MCO arrivals
k. Y = RSW West Sector 10,000 feet and below.
l. PT "C" = IR046 (Point C entry); PT "E" = IR046 (Point E entry)
FLIGHT DATA RADAR
11-2
TPA 7110.6E
01/13/2011
11-13. WEATHER DISSEMINATION.
a. FDR shall relay/deliver all pertinent AIRMETs, SIGMETs, convective SIGMETs, CWAs,
and PIREPs received by FDIO or landlines to the TRACON OMIC/FLMIC/CIC immediately.
b. The hourly weather sequences and forecasts remain at the FDR position.
c. Braking action reports will remain at the FDR position.
d. The TRACON OMIC/FLMIC/CIC shall be advised when the weather conditions are less
than 5,000 feet ceiling and/or visibility less than five (5) miles.
e. FDR shall enter current weather sequences for MCF, PIE, SRQ, LAL, SPG and BOW into
the IDS4. Approach, runway information and ATIS codes received from BOW shall be entered
into the IDS4. Use two-digit UTC (Z) times for record observations and four digit Z times for
special observations. In the event the hourly weather is not received from a satellite facility, FDR
will attempt to obtain the current weather by whatever means available (FDIO, satellite facility
via landline, AFSS, etc.) to ensure prompt posting. If unable to obtain, notify the TRACON
OMIC/FLMIC/CIC.
FLIGHT DATA RADAR
11-3
TPA 7110.6E
01/13/2011
This page intentionally left blank
FLIGHT DATA RADAR
11-4
TPA 7110.6E
01/13/2011
CHAPTER 12. RADAR GENERAL
SECTION 1. GENERAL DUTIES AND PROCEDURES
12-1. PRIMARY RESPONSIBILITIES OF THE RADAR TEAM POSITIONS.
a. RADAR Position(s):
(1) Ensure separation.
(2) Initiate control instructions.
(3) Monitor and operate communications equipment.
(4) Accept and initiate automated hand-offs.
(5) Assist the RADAR Handoff Position with non-automated hand-off actions when needed.
(6) Assist the RADAR Handoff Position with coordination when needed.
(7) Scan RADAR display and correlate with flight progress strip information.
(8) Ensure computer entries are completed on instructions or clearances issued or received.
(9) Ensure strip marking is completed on instructions or clearances issued or received.
(10) Adjust equipment at RADAR Position(s) to be useable by all members of the team.
(11) During normal operations, departure/overflight flight progress strips shall be forwarded
between positions.
b. RADAR Hand-Off Position(s):
(1) Operate interphones.
(2) Maintain awareness of facility / sector activities.
(3) Accept and initiate handoffs.
(4) Perform required coordination, including point outs.
(5) Manage flight progress strips, if posted.
(6) Assist RADAR Position(s) by making computer entries and strip marking as appropriate.
(7) Advise the RADAR Position of actions required to accomplish overall objectives and
goals.
(8) Adjust equipment at RADAR Handoff Position(s) to be usable by all members of the
RADAR Team.
(9) Final Hand-Off will assist the Final Controller by monitoring aircraft separation. All
available resources will be utilized including, but not limited to, STARS "J-Rings", "Cones", and
"*T" function.
NOTE: The RADAR Position has the responsibility of managing the overall sector operations,
including aircraft separation and traffic flows. The Hand-Off Position assumes the responsibility
for managing traffic flows and the RADAR Position retains responsibility for aircraft separation
when the Hand-Off Position is staffed.
c. FDR.
(1) Operate interphones.
(2) Process and forward flight plan information.
(3) Compile statistical data.
RADAR GENERAL
12-1
TPA 7110.6E
01/13/2011
(4) Assist facility/sector in meeting situation objectives.
12-2. TRANSCEIVERS.
TRACON:


7 VHF Portable Transceivers.
1 UHF Portable Transceiver.
NOTE: The antennas for the transceivers are on top of the Tower. The distance from Tampa
and the altitude that the frequencies will work is uncertain, especially on 119.65, 124.95 or
353.575.
12-3. AUTO ACQUISITION.
Each TRACON position is responsible for determining if automatic STARS acquisition has
occurred on a departure track within/into his/her delegated airspace.
NOTE: As long as equipment/hours of operation permit, LAL, SPG, PIE, SRQ, MCF, and TPA
Towers will perform this function per appropriate LOAs/Directives.
12-4. TRANSFER OF CONTROL.
a. The receiving TPA TRACON position may assume control of an aircraft handed off from
another TPA TRACON position for turns 30 degrees either side of course, provided that the turn
will not penetrate another sector’s airspace. This procedure is in addition to the transfer of
control information specified in this order, prearranged coordination procedures, and LOAs.
b. All departures off TPA are released for turns towards the DTA or destination upon transfer of
communications. However, the receiving controller shall protect tower standard automatic
release headings and shall comply with noise requirements.
12-5. TRANSFER OF IDENTITY AND COMMUNICATIONS.
The following procedures shall be used to accomplish the "Transfer of Identity and
Communications" between the TRACON and TPA Tower.
a. Transfer of communications shall occur no sooner than 15 but no later than 6 flight path
miles from the airport.
b. Transfer of Identity.
(1) STARS handoff feature may be used, using scratch pad as appropriate.
(2) Aircraft not displaying STARS full data block shall be coordinated via the override
system.
(3) The override system may be used to coordinate an inbound as deemed necessary.
RADAR GENERAL
12-2
TPA 7110.6E
01/13/2011
c. Final shall assure that the aircraft being transferred to the Tower by use of the quick-look
procedure is displaying a full data block and is associated with the appropriate aircraft target.
d. All other positions of operation shall use the STARS handoff feature (the scratch pad should
be used as needed to denote runway), or coordinate via the override system.
12-6. STARS Coordination/Automated Point-Out Procedures (APO).
a. All RADAR positions and LC may utilize automated point out procedures.
b. APO may be accomplished by either of the following two methods:
(1) Utilizing the STARS APO function as follows:
(a) Controller A initiates an APO in STARS.
(b) Controller B may take any of the following actions:
 Approve the point out.
 Reject the point out.
 Accept a handoff.
NOTE: At any time prior to controller B taking action, Controller A may recall the APO.
(2) Utilizing the STARS automated handoff function as follows:
(a) Controller A initiates a handoff to Controller B.
(b) Controller B may initiate a point out by immediately directing the handoff to the next
controller. This constitutes approval of a point out through Controller B’s airspace subject to the
limitations and procedures listed below.
(c) This procedure may be used through multiple sectors. Controller A may transfer
communications to any of the sectors that have redirected the handoff, or to the position
accepting the final handoff.
c. Limitations:
(1) APO will not be used without a validated Mode-C altitude.
(2) APO will not be used to point-out aircraft to any satellite control tower, except as per
LOA.
(3) The initiating controller will ensure all data block information is accurate, to include the
Mode-C read-out, prior to initiating APO.
(4) This procedure is only available in STARS FSL.
d. Procedures:
(1) Either the "Y" or the "+" Scratch Pads will be used to define route, altitude or airport
information.
RADAR GENERAL
12-3
TPA 7110.6E
01/13/2011
(2) For aircraft operating in the "Bridge", upon acceptance of the APO by the receiving
controller, the initiating controller may turn towards the airport identified in the scratchpad and
begin descent after crossing the parallel runways at TPA.
(3) For arrival aircraft, acceptance of the APO is approval for turns towards the airport
identified in the scratchpad, and descent in accordance with TPA SOP or as indicated in the
scratch pad.
(4) For departure aircraft, acceptance of the APO is approval for departures to climb and turn
towards the DTA identified in the scratchpad. The initiating controller is expected to turn in the
shorter direction towards the DTA.
(5) For overflight aircraft, acceptance of the APO is approval for the aircraft to continue
through the receiving controller’s airspace on the present altitude and heading.
e. The APO procedures should only be used when there is an operational advantage and should
not be used when a handoff or verbal point out is more appropriate. Any deviation from the
specified procedures above invalidates the procedure and requires that verbal coordination be
completed.
12-7. AIRSPACE.
a. Depicted Altitudes. All drawings depict IFR altitudes only. Overlying sectors are
responsible for all altitudes below their base altitude down to but not including the top altitude
delegated to the underlying sector. Overlying sectors are responsible for applying appropriate
vertical separation above underlying sectors/Class C/Class D airspace.
b. Tower Enroute Shelf. The Tower enroute airspace south of SRQ shall be retained by TPA
when the SRQ ASR-9 is OTS, and at least one other RADAR site is available. Alternate
RADAR sites to be used by South Departure (G) and Satellite (S) are QFN (Ft. Green ASRS-4
Long-Range RADAR) and TPA ASR-9.
c. MCF Tower Airspace. Any position that receives coordination from MCF Tower releasing
MCF airspace to TPA, or returning MCF airspace to MCF, shall advise the TRACON
FLMIC/CIC.
d. Final Shelf A airspace. Should the Final Control (F) position require additional airspace
during periods of heavy TPA arrival traffic on a RWY 1 configuration, F will notify the
TRACON FLMIC/CIC to activate the Final Shelf A airspace extension. The TRACON
FLMIC/CIC is responsible for coordinating with all of the affected adjacent sectors, for advising
F when the extended airspace is available for use by the Final position, and for returning the
airspace when no longer required.
12-8. PREARRANGED COORDINATION.
Prearranged coordination areas are areas in which a controller allows an aircraft to penetrate
another controller's airspace in a manner that assures standard separation without individual
coordination for each aircraft.
RADAR GENERAL
12-4
TPA 7110.6E
01/13/2011
a. General conditions for applying prearranged coordination:
(1) All non-beacon aircraft must have a full data block and be tracked by STARS.
(2) Prearranged coordination shall only be used when the STARS system is operational.
(3) Controllers who penetrate another controller's airspace using prearranged coordination
procedures shall display data block information of that controller’s aircraft which shall contain,
at a minimum, the position symbol and altitude information.
(4) Controller applying prearranged coordination shall be responsible for providing RADAR
separation from the other position’s aircraft while operating within the designated airspace.
(5) Controller applying prearranged coordination shall be responsible for providing wake
turbulence separation.
(6) Coordinate with the other position prior to utilizing visual separation.
(7) Be in communication with the aircraft.
(8) APO procedures shall not be used.
b. East and West Departure are authorized to penetrate the protected airspace of East and West
Arrival in the areas depicted in Figures 12-1 and 12-2.
c. West Satellite and East Satellite are authorized to penetrate the protected airspace of the East
and West Departure, and Final positions in the area depicted in Figure 12-3. The use of this area
is "The Bridge".
(1) The Bridge is defined as a course extending along an east/west line directly over TPA
Runway 10/28 from the East Satellite boundary to the West Satellite boundary, above 1,600 feet
to 4,000 feet. This airspace is delegated as follows:
(a) West Satellite may transition eastbound VFR traffic at 2,500 feet and eastbound VFR or
IFR traffic at 3,000 feet.
(b) East Satellite may transition westbound VFR traffic at 3,500 feet and westbound VFR
or IFR traffic at 4,000 feet.
NOTE: West Satellite is authorized to climb or descend west of RWY 19R/1L. East Satellite is
authorized to climb or descend east of RWY 19L/1R.
d. East and West Arrival shall:
(1) Point out untracked/untagged targets to the departure controller that are operating in and
within 5 miles of the airspace depicted in Figures 12-1 and 12-2.
(2) Have the option to temporarily suspend this procedure when traffic and or weather
conditions dictate. East and West Arrival shall advise the TRACON FLMIC/CIC upon
suspension of these procedures.
(3) Traffic flowed to the opposite downwind shall be coordinated with departure.
e. East and West Departure, and Final shall:
(1) Point out untracked/untagged targets to the West Satellite or East Satellite controller that
are operating in and within 5 miles of the airspace depicted in Figure 12-3.
RADAR GENERAL
12-5
TPA 7110.6E
01/13/2011
(2) Have the option to temporarily suspend this procedure when traffic and or weather
conditions dictate. East and West Departure or Final shall advise the TRACON FLMIC/CIC
upon suspension of these procedures.
FIGURE 12-1. DEPARTURE PREARRANGED COORDINATION AREA, RWY 1
RADAR GENERAL
12-6
TPA 7110.6E
01/13/2011
FIGURE 12-2. DEPARTURE PREARRANGED COORDINATION AREA, RWY 19
FIGURE 12-3. SATELLITE PREARRANGED COORDINATION AREA
RADAR GENERAL
12-7
TPA 7110.6E
01/13/2011
12-9. CONTROLLED AIRSPACE INTRUSIONS.
a. Class B/C Violations:
(1) All personnel shall, to the extent possible, track (initiate a data block) and/or identify any
aircraft observed to violate or enter the Class B/C without authorization. The controller initiating
the track shall handoff or point out the traffic to other positions whose airspace the aircraft may
enter. Verification of aircraft's altitude and position in the Class B/C is critical for any effective
follow-up action to be taken.
TRACK EXAMPLES: CLASB/CLASC/CLASD
(2) Coordinate with and/or assist adjacent facilities when the aircraft is observed to enter
another facility's airspace. Cooperation will enhance safety and aid in identifying the aircraft.
(3) Notify the TRACON FLMIC/CIC of the suspected intrusion.
(4) If the suspected intruder lands within TPA airspace, the TRACON FLMIC/CIC shall
coordinate with the satellite towers, FBO, or other agencies, as appropriate, to determine the
aircraft registration.
(5) When these aircraft can be identified, enter any information regarding the incident on
FAA Form 7230-4 and comply with FAAO 8020.11, Pilot Deviations, in a timely manner.
12-10. STARS.
a. Invalid Mode C. When aircraft have invalid Mode C readouts and the pilot has been
advised to stop altitude squawk, advise the TRACON FLMIC/CIC of the aircraft's call sign and
time of incident.
b. Unique Features. The operational program has several features that prove useful to
controllers. Among these are the "host" ATIS, systems data area, and the scratch pad area.
However, there are limitations as to the number of characters that can be displayed in these areas.
In order to ensure that the information displayed is understood by all, the procedures described
below shall be strictly adhered to by all personnel.
(1) Host ATIS and Systems Data Area. (13 characters maximum) shall be used as follows:
(a) ATIS alpha character (the absence of an ATIS alpha character indicates the ATIS is
inoperative).
(b) Blinking System Area: The Main GI line will blink anytime a change is entered into the
TPA ATIS code or the Main GI line. All TRACON positions shall acknowledge receipt of TPA
ATIS code changes received from Tower with the appropriate STARS keyboard entry. Use
keystrokes: ∆ enter, to stop the blinking. (A change to satellite towers runway in use will also
cause the Main GI line to blink).
(c) Type approach and runway information for TPA as follows:
 V19 -- Simultaneous visual approaches to Runways 19L and 19R.
 19 --- Instrument approaches to Runways 19L and 19R.
 V1 -- Simultaneous visual approaches to Runways 1L and 1R.
 1 --- Instrument approaches to Runways 1L and 1R.
RADAR GENERAL
12-8
TPA 7110.6E
01/13/2011
(d) Runway in use at MCF as follows:
 4 -- RWY 04
 22 -- RWY 22
(e) Runway in use at PIE as follows:
 17 -- RWY 17L
 35 -- RWY 35R
 9, 9N -- RWY 9 (N indicates RWY 35 is in use in addition to RWY 9)
 27 -- RWY 27
(f) Runway in use at SRQ as follows:
 14 -- RWY 14
 4 -- RWY 04
 32 -- RWY 32
 22 -- RWY 22
NOTE 1: The primary use of the "host" ATIS and systems data area is to indicate the TPA ATIS
and runway/approach information. After TPA information is displayed, the next priority is
MCF, then PIE, and SRQ, as character capacity allows.
NOTE 2: The systems data area ten-second blinking feature is installed at the five STARS
umbrella locations to draw attention to current information being entered into the system data
area.
(2) GI Text Filter: TPA controllers are frequently handling aircraft landing at satellite
airports, and it is necessary to verify that these aircraft have the current ATIS information. At
STARS-adapted airports, this is accomplished by selecting the appropriate GI Text Filter. When
only one area is selected, it will be displayed where Area 1 is shown. If two areas are selected,
they will be displayed where Areas 1 and 2 are shown.
(a) MCF, PIE, SRQ, SPG, and LAL will keep their GI Text Filter areas current with the
following information:
 ATIS code
 Altimeter
 Runway in use
 Advertised approach
(b) Appropriate GI Text Filters are selected using the display control bar (DCB).
(3) Scratch Pad Area. (displayed in Field 2 of data block) The information in Field 2 will be
displayed for a time period shared with the Altitude/Mode C readout. Scratch pad information
will be followed by a * (splat). When the aircraft is not squawking Mode C (or if inhibited); the
scratch pad information will appear constantly. The scratch pad area shall be used to display
flight data information and coordination data for the controller controlling the aircraft and the
controller receiving a RADAR handoff. The information may also be used by other controllers
in issuing traffic information. Scratch pad information shall be kept current.
(a) Altitude/flight level in the scratch pad area shall be denoted as follows:
1. An altitude/flight level, followed by a single alpha character denoting a Departure
Transition Area (DTA), shall be indicated in thousands of feet.
RADAR GENERAL
12-9
TPA 7110.6E
01/13/2011
EXAMPLE:
26N = Flight level 260, BAYPO DTA
10X = Altitude 10,000 feet, BRNUM DTA
06B = Altitude 6,000 feet, SHOWW DTA
NOTE: There must be a DTA following the altitude.
2. Altitudes NOT followed by a DTA shall be indicated in HUNDREDS of feet.
EXAMPLE:
35 = Aircraft level at 3,500 feet
P21 = Aircraft level at 2100 feet, landing PIE
D30 = Aircraft descending to 3,000 feet
C45 = Aircraft climbing to 4,500 feet
R85 = Aircraft requesting 8,500 feet
NOTE: Mode C aircraft may be transitioning or level at the altitude specified in the scratch pad
unless dictated otherwise in this order. Non-Mode C aircraft must be level at the altitude
specified in the scratch pad unless otherwise coordinated.
(b) When used as the first character and/or by themselves, the following single letters are
authorized by the Tower and the TRACON for use in the STARS scratch pad and local strip
markings to denote DTAs, Airports, and function indications. The only other alpha characters
authorized for the scratch pad are those listed in JO 7350.8, Location Identifier Handbook.
B = BOW
C = Climbing
D = Descending
E = CLW
F = FMY Area
G = GIF
H = BKV
I = FD77
J = FA40
K = TPF
L = LAL
M = MCF
N = X39
P = PIE
Q = 48X
R = Req.Alt.or RWY
S = SRQ
T = TPA
U = VDF
V = VNC
W = SPG
Y = PCM
Z = ZPH
(c) The following single-letter identifiers will represent DTAs when preceded by altitude
information:
A = V441/LAL DTA
B = ZMA SHOWW DTA / SYKES RNAV
D = ZJX DARBS DTA / V97 (10,000 feet and below)
F = ZMA GIRLE DTA/ GANDY RNAV
H = ZMA BGTOP DTA / CROWD RNAV
M = MCO Arrivals
RADAR GENERAL
12-10
TPA 7110.6E
01/13/2011
N = ZJX BAYPØ DTA/BAYPO RNAV
R = KNEED/V152/Orlando Satellite Arrivals
U = ZJX ENDED DTA/ENDED RNAV
X = JAX BRNUM (10,000 feet and below)
Y = RSW West Sector (10,000 feet and below)
(d) For operations not covered by a LOA, the following two and three-letter scratch pad
entries are authorized:
EXAMPLE: Aircraft destination BKV requesting multiple practice ILS approaches. Scratch
Pad 1 (Y) indicates destination airport, Scratch Pad 2 (Y+) indicates IMA for multiple practice
approaches.
**K = (Two digits plus letter "K" to indicate airspeed, i.e. 21K=210 Knots).
AIS = Airport in Sight (Includes runway and field in sight).
BCH = Flying over Gulf beaches.
JFA = Non-Specific destination usually associated with pleasure flights.
JMP = Aircraft is engaged in parachute jumping operations.
PHO = Aircraft is engaged in aerial photographic mission or survey.
XRY = Law Enforcement/X-Ray mission.
YC = Your Control (Receiving controller's control for turn and descent in transferring
controller's airspace).
GMA = GPS or RNAV Missed Approach.
GMP = GPS or RNAV Published Missed Approach.
IMA = ILS Missed Approach.
IMP = ILS Published Missed Approach.
LMA = LOC Missed Approach.
LMP = LOC Published Missed Approach.
NMA = NDB Missed Approach.
NMP = NDB Published Missed Approach.
VMA = VOR Missed Approach.
VMP = VOR Published Missed Approach.
(e) VFR departure aircraft shall have a single letter identifier or destination three letter
identifiers along with the type aircraft in the scratch pad.
(f) IFR departure aircraft shall have the requested altitude with a DTA identifier displayed
in the scratch pad and the aircraft type.
(g) Altitude information is mandatory in field two for non-mode C aircraft.
(h) All data in the STARS ATIS, systems data area, data block, and scratch pad, shall be
kept current. All aircraft taken off of an RNAV routing, the RNAV indicator must be removed
from the data block prior to intrafacility transfer of RADAR identification.
(4) VFR Aircraft. Identify VFR aircraft by placing the letter "Z" as the first character of the
ACID in the STARS data block.
RADAR GENERAL
12-11
TPA 7110.6E
01/13/2011
(5) TRACON Sector Configurations:
 1 = TPA Runway 1 MCF Runway 4
 2 = TPA Runway 19 MCF Runway 4
 3 = TPA Runway 1 MCF Runway 22
 4 = TPA Runway 19 MCF Runway 22
12-11. STARS OPERATIONAL MODE TRANSITION PROCEDURES (FSL/ESL).
a. The TRACON FLMIC/CIC is responsible for making the decision to transition to ESL and
return to FSL.
b. When transitioning from FSL to ESL, or ESL to FSL, the TRACON FLMIC/CIC shall
notify all positions in the TRACON and Tower, all adjacent facilities.
c. When operating in the ESL mode, the following apply:
(1) ESL provides backup in the event FSL is not available.
(2) Filter limits are automatically set to the lowest selected filter and the highest selected
filter.
(3) Automatic handoffs are not available. A manual intrafacility handoff to Final for aircraft
landing TPA shall be accomplished.
(4) Where more than one keyboard is associated with a TCW/TDW, only one keyboard per
position may act as the core keyboard in ESL. To enable a hand-off or coordinator position
keyboard as core, select the "Core" menu key and <ENTER>.
(5) Data blocks in ESL mode only have 3 lines and contain:
(a) Special Conditions (EM, RF, HJ and MI), if applicable.
(b) ACID/Beacon Code (ACID may be entered manually to replace the beacon code
readout if it is a discrete beacon code.
(c) Mode C readout.
(6) Preference Sets are not available.
(7) Fields containing ground speed readout, scratchpad entries, type aircraft, requested
altitude, etc. are not available.
(8) TAB Lists are not available.
(9) Quick Look functions are not available.
(10) The use of APO procedures and Prearranged Coordination procedures is prohibited.
(11) Track ownership is not applicable. Position symbols will not be displayed for each
track. Each data block is associated with an asterisk (*).
d. Transition from FSL to ESL Checklists:
(1) TRACON FLMIC/FLM/CIC:
(a) Notify all TRACON positions, satellite towers and the TPA Tower FLM/CIC that TPA
is transitioning to ESL mode.
(b) Advise the Tower FLM/CIC that automatic departure releases are suspended.
(c) Ensure that "ESL" is selected on all TCWs.
(d) Ensure that the MSAW/CA volume is set to no lower than "1" on each TCW.
RADAR GENERAL
12-12
TPA 7110.6E
01/13/2011
(e) Advise all adjacent facilities and the ATCSCC that TPA is operating in ESL mode.
(f) Advise TECH OPS that TPA is operating in ESL mode.
(g) As traffic conditions warrant, ensure the appropriate RADAR hand-off positions and/or
coordinator positions are staffed.
(h) Make an entry in the daily log indicating that TPA is operating in ESL mode.
(2) Tower FLM/CIC:
(a) Ensure "ESL" is selected on all TDWs.
(b) Ensure the MSAW / CA volume is set no lower than "1" on all TDWs.
(c) Ensure that releases are obtained for all departures.
e. Transitioning from ESL to FSL Mode Checklists:
(1) TRACON FLMIC/CIC:
(a) Notify all TRACON positions, satellite towers and the TPA Tower FLM/CIC that TPA
is transitioning to FSL mode.
(b) Ensure that "FSL" is selected on all active TCWs.
(c) Advise all adjacent facilities and the ATCSCC that TPA is operating FSL mode.
(d) Advise TECH OPS that TPA is operating in FSL mode.
(e) Make an entry in the Daily Facility Log indicating that TPA is operating in FSL mode.
(2) Tower FLM/CIC:
(a) Ensure that "FSL" is selected on all TDWs.
(b) Coordinate the resumption of automatic departure releases with the TRACON
FLMIC/CIC.
f. Warm and Cold Starts: During a cold start, it takes approximately 3 minutes for the system
to recover. A warm start takes approximately 45 seconds. At any time you are working with
TECH OPS to do a warm or cold start, ensure the following:
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
Notify all positions in the TRACON, the Tower, and all satellite facilities.
Place pens and paper at each operational position.
During peak traffic times, two management officials shall be in the TRACON.
Verify that the workforce is ready and they are in ESL.
Ensure all coordination is complete.
Release to TECH OPS.
Restore the database upon return to FSL in each case (warm/cold start).
Inform each satellite facility to restore their system area.
SECTION 2. WEATHER INFORMATION
12-12. DISSEMINATION.
a. Retrieve satellite airport weather from the AISR computer.
b. RVR values are obtained from the instruments in the Tower and TRACON.
c. SIGMETS, AIRMETS, and CWA are received via FDIO.
RADAR GENERAL
12-13
TPA 7110.6E
01/13/2011
d. DASI -- Issue current values for voice communications.
e. ITWS/LLWAS -- Issue current values for voice communications.
SECTION 3. EQUIPMENT
12-13. RADAR.
a. STARS RADAR System. All ATC personnel are responsible for determining that the
RADAR presentation and equipment performance is adequate for the service provided.
Immediately report any RADAR discrepancy to the TRACON FLMIC/CIC.
(1) Alignment. RADAR alignment is automatically monitored by the system. TECH OPS
will receive alarms if there is a problem with RADAR alignment.
(2) STARS Weather Display. Each position of operation should adjust their weather setting
selections to optimize the weather presentation for their position of operation. As a minimum,
the Level 3 through 6 weather setting will be selected, if weather in that range is available. The
weather displayed on the TCWs is a mosaic of the TPA and SRQ ASR-9 RADARS. The
weather from the QFN long range RADAR is inhibited via software. When controllers go to
QFN long range RADAR only (TPA and SRQ RADAR are both out of service), and need
weather displayed, TECH OPS must be notified.
(3) Safeguarding the ASR-9 antenna. Steady wind or gusts to velocity of 80 knots shall be
reason to stop the antenna. The decision to stop the antenna rotation shall be made jointly
between Air Traffic and TECH OPS personnel. The TRACON FLMIC/CIC shall make the
decision to stop the antenna rotation when TECH OPS personnel are not available. DO NOT stop
antenna rotation with the high voltage on. This may cause the RADAR transmitter to miss
trigger, resulting in possible equipment damage.
(a) High voltage turn off procedures:
1. The system control must be at the ASR-9 Control Box.
2. At the DSP RX/TX on and off line channel: Turn high voltage to the OFF position.
(b) Shut down the Antenna procedures:
1. System control must be at the ASR-9 Control Box.
2. Turn high voltage OFF.
3. At antenna rotation, select OFF.
(4) RADAR channel change. Shall be accomplished in the following sequence:
(a) Select "High Voltage Off" for the operating channel.
(b) Select the standby channel "On Line".
(c) Wait approximately 3 seconds.
(d) Select "High Voltage On" for the on line channel.
(5) The primary return, computer generated, is always closest to the main bang and the
beacon control slash of the secondary return is the most distant from the main bang.
(6) Select beacon codes 12 and 40 are required to be selected on each position. These codes
can be saved in STARS "PREF" sets.
RADAR GENERAL
12-14
TPA 7110.6E
01/13/2011
(7) STARS Video Maps. Six primary maps are available on the Display Control Panel
(DCP). These maps and an additional twenty-six maps are available on the Display Control Bar
(DCB).
(8) If either the TPA or SRQ RADAR systems are changed to Circular Polarization (CP), the
TRACON FLMIC/CIC shall notify TPA Tower or the satellite facilities as appropriate.
b. Azimuth and range of permanent beacon targets (Parrot), moving target indicator (MTI)
reflectors, and the name, range/azimuth, altitude, and coordinates of prominent obstructions:
(1) Parrots: 1273 is located at 130.96 degrees, 14.97 miles from TPA ASR9.
1274 is located at 240.29 degrees, 24.83 miles from TPA ASR9.
(2) MTI Reflector: located one tenth of a mile west of the extended centerline for RWY 10.
(3) Prominent Obstructions:
Name
Azimuth
Distance
Altitude
St Petersburg Tower
213°
8.4
660
Tarpon Towers
318°
17.4
1549
Pebbledale Tower
108°
32.2
1242
Riverview Towers
123°
18.5
1649
Wimauma Tower
131°
29.5
1649
Parrish Tower
162°
26.5
849
Verna Tower
158°
37.1
1749
Coordinates
27/51/23.0N
82/37/26.0W
28/10/57.04N
82/46/5.36W
27/50/16.0N
81/56/52.0W
27/49/47.0N
82/15/58.0W
27/40/24.0N
82/6/34.0W
27/33/30.0N
82/21/59.0W
27/24/31.15N
82/14/59.32W
12-14. ELECTRONIC FLIGHT STRIP TRANSFER SYSTEM (EFSTS).
EFSTS printers are located at the P, D, L, B, S, and G positions. Controllers working these
positions shall:
a. Turn on the printer when opening the position, and turn it off when closing the position.
This allows the strips to print at the correct position.
b. Advise LC and the FLM/CIC if no strip is received.
c. Advise the FLM/CIC if the EFSTS printer is not working, or is out of paper.
RADAR GENERAL
12-15
TPA 7110.6E
01/13/2011
12-15. TRACON OPERATING POSITIONS.
FIGURE 12-4. TRACON OPERATING POSITIONS
P = WEST SATELLITE = 125.3 / 119.125 / 316.05 F = 118.5 / 307.175 (SHARED WITH M)
D = WEST DEPARTURE = 118.8 / 239.3
E = EAST ARRIVAL = 118.15 / 285.62
W = WEST ARRIVAL = 132.52 / 269.1
R = LAKELAND LOW = 120.65
L = EAST SATELLITE = 119.9 / 119.8 / 290.3 G = SOUTH DEPARTURE = 134.25 / 354.0
B = EAST DEPARTURE = 135.5 / 279.6
M = MACDILL = 126.0 / 307.175
S = SOUTH SATELLITE = 119.65 / 353.57/118.075
RADAR GENERAL
12-16
TPA 7110.6E
01/13/2011
CHAPTER 13. TRACON POSITIONS
13-1. FINAL (F).
Assigned frequencies 118.5, 307.17 (Shared with (M) MacDill).
a. Duties and responsibilities are as follows:
(1) Provide service for aircraft within designated TPA Final airspace.
(2) When additional airspace is needed to sequence TPA arrivals during periods of heavy
traffic on a RWY 1 configuration, notify the TRACON FLMIC/CIC to activate the Final Shelf
A, (F16,F,N) airspace extension. The TRACON FLMIC/CIC will perform all required
coordination with the affected sectors, and will advise Final when the airspace extension is
available for use. When Final Shelf A is no longer needed, advise the TRACON FLMIC/CIC as
soon as practicable to return the extended airspace to the adjacent sectors.
b. Final has sequencing authority for ALL runways.
c. Final is responsible for coordinating and issuing missed approach instructions for all
practice approaches at TPA.
d. Aircraft making a planned missed approach shall be handed off to the Tower.
e. All traffic handed off to Final is released for turns on transfer of communications.
f. LC shall provide visual separation on arrivals within 5 miles of the TPA airport under the
following conditions - ceiling 3,000 feet or greater, and visibility 5 miles or greater. LC shall
inform Final when visual separation cannot be applied. LC may apply visual separation when
conditions are less, as coordinated. Wake turbulence is the Final Controller’s responsibility.
g. Ensure that aircraft will remain clear of the following:
(1) Airspace released to satellite towers.
(2) To avoid MCF airspace, RWY 1 visual approaches and VFR arrivals shall be instructed to
"maintain 2,600 until northwest of RWY 4 at MCF." Non-heavy VFR RWY 1 arrivals may be
descended to 2,100 feet until northwest of RWY 4 at MCF.
EXCEPTION: When TPA is on RWY 1, and MCF Tower is closed, Final will assume the
airspace normally controlled by MCF Tower.
(3) The Bridge as referenced in Par. 12-8 c (1). In the event of a go-around, instruct aircraft
to maintain 1,600 feet.
h. Separation between aircraft may be reduced to 2.5 NM on the final approach course within
10 NM of the landing runway in accordance with JO 7110.65.
TRACON POSITIONS
13-1
TPA 7110.6E
01/13/2011
i. The runway centerlines for the parallel runways 19L/1R and 19R/1L are 4,301 feet apart. As
a result, the provisions of JO 7110.65 apply when conducting ILS or LOC approaches to those
runways, and the minimum "staggered" separation from aircraft on the parallel approach course
is 2.0 miles.
j. Final shall indicate the type of approach and runway (by utilizing the STARS scratch pad)
when:
(1) Aircraft are making visual approaches to one of the parallel runways. Use the following
scratch pad entries:
(a) VR = Visual approach RWY 19R/1R, visually following traffic.
(b) VL = Visual approach RWY 19L/1L, visually following traffic.
(c) VRA = Visual approach RWY 19R/1R, NOT visually following traffic.
(d) VLA = Visual approach RWY 19L/1L, NOT visually following traffic.
(2) Aircraft are making approaches other than advertised on the ATIS, or an aircraft is making
an approach to one of the parallel runways that is not normally used by this aircraft or type of
aircraft. Other than aircraft subject to noise abatement, Final normally sequences aircraft to the
runway closest to the aircraft's gate/parking. Use the following scratch pad entries:
 IL = ILS RWY 19L/1L
 IR = ILS RWY 19R
 LL = LOC RWY 19L/1L
 LR = LOC RWY 19R/1R
 GR = RNAV or GPS approach 19R / 1R
 GL = RNAV or GPS approach 19L / 1L
 19R/19L/1R/1L = VFR aircraft to appropriate RWY.
(3) When an aircraft is making a practice approach with a planned missed approach, Final
shall issue the appropriate missed approach/climbout instructions, and use scratch pad entries to
relay this information to Tower.
NOTE: The first character indicates the type of approach. The second character indicates the
runway. The third character indicates the position that will work the aircraft after missed
approach or climbout.
Examples:
 ILL = ILS approach, RWY 1L/19L, heading 060, maintain 1,600 feet, and East
Satellite frequency.
 ILP = ILS approach, RWY 1L/19L, heading 310, maintain 1,600 feet, and West
Satellite frequency.
 IRD = ILS approach; RWY 19R, heading 205; RWY 1R; heading 005; maintain 5,000
feet, and West Departure frequency.
 ILD = ILS approach, RWY 19L, heading 215, maintain 5,000 feet, and West Departure
frequency.
k. When weather conditions are such that CAT II/CAT III approaches are not required, advise
the LC when an aircraft is making a "coupled" or "auto-land" approach.
TRACON POSITIONS
13-2
TPA 7110.6E
01/13/2011
l. When TPA is on RWY 1, Final shall ensure that turbojet right base legs remain south of
MCF RWY 4 and shall utilize RWY 1L for turbojet arrivals (except for operational needs,
volume, Lifeguard aircraft, weather).
NOTE: If the pilot requests an operation contrary to the informal noise and runway use
program, and does not state the reason, it is understood that an operational necessity exists.
m. Aircraft on opposing base-legs shall be assigned altitudes that ensure vertical separation
unless other approved separation has been applied. This requirement will ensure approved
separation in the event of an overshoot or late turn-on to final.
TRACON POSITIONS
13-3
TPA 7110.6E
01/13/2011
FIGURE 13-1. RUNWAY 1 FINAL
TRACON POSITIONS
13-4
TPA 7110.6E
01/13/2011
FIGURE 13-2. RUNWAY 1 FINAL SHELF "A"
50
40
TRACON POSITIONS
13-5
TPA 7110.6E
01/13/2011
FIGURE 13-3. RUNWAY 19 FINAL
TRACON POSITIONS
13-6
TPA 7110.6E
01/13/2011
13-2. WEST SATELLITE (P).
Assigned frequencies 125.3, 316.05, 119.125 (BKV RCO).
a. Duties and Responsibilities:
(1) Provide service to aircraft within West Satellite delegated airspace.
(2) Handoff arrivals to Final at 3,000 or 4,000 feet, as indicated in the scratch pad.
(3) Traffic transiting the Bridge shall be westbound IFR at 4,000/3,500 VFR, and eastbound
IFR at 3,000/2,500 VFR.
(4) NO TURBOJET AIRCRAFT SHALL USE THE BRIDGE.
(5) Aircraft entering IR046 at PIE 332/20 shall be cleared into the route and RADAR service
terminated prior to transfer of communications. Aircraft will be at or below 3,000 feet. West
Satellite shall enter time that aircraft crosses PIE 332/20 in Blocks 13, 14, and 15 of flight
progress strip and ensure a 5-minute interval between aircraft in the IR046 route prior to transfer
of communications to JAX. Add 10 minutes to the time in Blocks 13-14-15 and enter that time in
Block 8 of the flight progress strip. The time in Block 8 is the estimated time that the aircraft will
depart the vicinity of TPA airspace. Advise JAX of aircraft entering the IR046 prior to
communications transfer.
(6) West Satellite shall advise East Satellite and/or Lakeland Low when IR046 is active.
(7) West Satellite has sequencing authority for TPA RWY 10 arrivals. These operations
must be coordinated with Final. Coordination can be accomplished via APO.
(a) Aircraft making approaches to other than the advertised runway on the ATIS, use the
following scratch pad entries:
 V28 = Visual Approach RWY 28
 R28 = VFR Arrival RWY 28
 GF2 = GPS/RNAV RWY 28
 V10 = Visual Approach RWY 10
 R10 = VFR Arrival RWY 10
 VF1 = VOR RWY 10
 GF1 = GPS/RNAV RWY 10
(8) West Satellite is responsible for arrival sequencing and departure releases at BKV and
shall coordinate with East Satellite as appropriate.
(9) All traffic handed off from South Satellite is released for turns towards West Satellite's
airspace.
(10) Establish the arrival sequence on all IFR arrivals and all VFR practice approaches to
SPG. Coordinate all IFR releases from SPG with South Satellite (or MacDill sector if
decombined).
b. PIE NOISE ABATEMENT. The following noise abatement procedures shall apply for air
carrier turbojet aircraft weighing 60,000 pounds or more arriving or departing from PIE. ATC
will inform pilots on initial contact that the NBV or RNAV (GPS) A approach is in use and the
approach to expect. The approach in use will be announced on the PIE ATIS:
(1) When RWY 17L is in use, arriving air carrier turbojet aircraft may use the following:
(a) North Bay Visual Approach (NBV) provided all of the following conditions apply:
TRACON POSITIONS
13-7
TPA 7110.6E
01/13/2011
 Ceiling at or above 2100 feet.
 Visibility 3 miles or greater.
 PIE Tower in operation.
 Between hours of official sunrise and sunset.
(b) RNAV (GPS) A approach when conditions do not allow the NBV or when pilot
requests.
(c) A request for an ILS or other instrument approach to Runway 17L when above
conditions apply must be initiated by the pilot-in-command and not ATC; however, such
requests will be honored by ATC.
NOTE: When applying these procedures, controllers should consider known restrictions to
visibility, traffic, special handling, etc. and not apply these procedures so stringently that safety
is compromised.
(2) Departing aircraft on RWY 35R will be assigned the PIE DP or a departure heading of
030 degrees after take-off to intercept and fly outbound on the PIE VOR 016 degree radial, until
reaching 3,000 feet.
TRACON POSITIONS
13-8
TPA 7110.6E
01/13/2011
FIGURE 13-4. RUNWAY 1 WEST SATELLITE
TRACON POSITIONS
13-9
TPA 7110.6E
01/13/2011
FIGURE 13-5. RUNWAY 19 WEST SATELLITE
Excludes Tower airspace
1,600 and below.
TRACON POSITIONS
13-10
TPA 7110.6E
01/13/2011
13-3. WEST ARRIVAL (W).
Assigned frequencies 132.52, 269.1.
a. Provide service for aircraft within West Arrival designated airspace. Duties and
responsibilities are as follows:
b. West Arrival shall hand off TPA arrivals to Final:
(1) Runway 19:
(a) On the FOOXX/BLOND RNAV STAR descending to 6,000 feet.
(b) On a vector for a base leg no closer than 15 miles from the airport descending to 6,000
feet or on a downwind vector descending to 6,000 feet.
(2) Runway 1:
(a) On the FOOXX/BLOND RNAV STAR descending to 5,000 feet.
(b) On a downwind vector descending to 5,000 feet.
c. West Arrival will initiate altitude amendment on IR20 aircraft to 7,000 feet via FDIO.
d. SRQ and VNC arrivals shall be descended to 12,000 feet and handed off to West Departure.
e. When TPA is using RWY 1, traffic flowed to the opposite downwind shall be coordinated
with East and West Departure.
TRACON POSITIONS
13-11
TPA 7110.6E
01/13/2011
FIGURE 13-6. RUNWAY 1 WEST ARRIVAL
TRACON POSITIONS
13-12
TPA 7110.6E
01/13/2011
FIGURE 13-7. RUNWAY 19 WEST ARRIVAL
TRACON POSITIONS
13-13
TPA 7110.6E
01/13/2011
13-4. WEST DEPARTURE (D).
Assigned frequencies 118.8, 239.3.
a. Provide service for aircraft within West Departure designated airspace. Duties and
responsibilities are as follows:
b. NOISE ABATEMENT:
(1) Do not vector turbojet aircraft departing TPA until the aircraft leaves 3,000 feet except for
aircraft departing RWY 19 and making a west or northwest turn.
(2) Unless operationally required, from 7:00 p.m. to 7:00 a. m, turboprop aircraft departing
RWY 1L/1R should not turn left until the aircraft has passed 3 NM.
c. When TPA is on RWY 1, initial departure headings are joint-use headings with East
Departure. On RWY 19 departures, initial departure headings are joint-use headings with South
Departure.
d. GIRLE departures shall be vectored to pass east of SRQ.
e. Prearranged coordination may be used in designated areas.
f. All arrivals handed off to South Departure shall be at 6,000 feet. These aircraft are released
for descent to 5,000 feet upon transfer of communications.
g. MCF arrivals should be vectored north of TPA when MCF is on RWY 22, and west of
MILNE intersection when MCF is on RWY 4.
h. West Departure has control for climb on all aircraft handed off from South Departure at
5,000 feet per 13-8.g.
TRACON POSITIONS
13-14
TPA 7110.6E
01/13/2011
FIGURE 13-8. RUNWAY 1 WEST DEPARTURE
Initial departure headings are
shared between West and
East Departure. Excludes
Tower airspace 1,600 and
below.
TRACON POSITIONS
13-15
TPA 7110.6E
01/13/2011
FIGURE 13-9. RUNWAY 1 WEST ARRIVAL / DEPARTURE COMBINED
Initial departure headings are
shared between West and
East Departure. Excludes
Tower airspace 1,600 and
below.
TRACON POSITIONS
13-16
TPA 7110.6E
01/13/2011
FIGURE 13-10. RUNWAY 19 WEST DEPARTURE
Initial departure headings are
shared between West and
South Departure. Excludes
Tower airspace 1,600 and
below.
TRACON POSITIONS
13-17
TPA 7110.6E
01/13/2011
FIGURE 13-11. RUNWAY 19 WEST ARRIVAL / DEPARTURE COMBINED
Initial departure headings
are shared between West
and South Departure.
Excludes Tower airspace
1,600 and below.
TRACON POSITIONS
13-18
TPA 7110.6E
01/13/2011
13-5. EAST SATELLITE (L).
Assigned frequencies 119.9*, 119.8 (TPF RCO)**, 290.3.
(* Main/Stby at VDF - ** Main/Stby at TPF).
a. Provide service for aircraft within East Satellite designated airspace. Duties and
responsibilities are as follows:
b. East Satellite has sequencing authority for TPA RWY 28 arrivals. These operations must be
coordinated with Final. Coordination may be accomplished via APO.
c. Aircraft making approaches to other than the advertised runway on the ATIS, use the
following scratch pad entries:
 V28 = Visual Approach RWY 28
 R28 = VFR Arrival RWY 28
 GF2 = GPS/RNAV RWY 28
 V10 = Visual Approach RWY 10
 R10 = VFR Arrival RWY 10
 VF1 = VOR RWY 10
 GF1 = GPS/RNAV RWY 10
d. Handoff IFR arrivals to Final at 3,000 or 4,000 feet, as indicated in the scratch pad.
e. Traffic transiting the Bridge shall be westbound IFR at 4,000/3,500 feet VFR, and eastbound
IFR at 3,000/2,500 feet VFR.
f. NO TURBOJET AIRCRAFT SHALL USE THE "BRIDGE."
g. East Satellite shall point out V7 traffic to West Satellite.
h. IR046: Estimated time in Block 8 of the enroute strip is the estimated time that the aircraft
leaves TPA airspace. East Satellite shall protect 10 minutes (NON-RADAR) past the indicated
time. Aircraft entering IR046 at Point E shall be handed off to JAX at 4,000 feet. JAX shall
coordinate any IR046 Point E entries from the north.
i. East Satellite will be responsible for releasing departures off MCF RWY 4, and for
establishing arrival sequence for MCF RWY 22, and shall coordinate with the appropriate sector.
j. When TPA is on RWY 1, East Satellite must coordinate IFR TPF arrival and departures, and
MCF RWY 22 approaches with Final, as appropriate. When TPA is on Runway 19, East
Satellite shall coordinate MCF Runway 22 approaches with South Departure.
TRACON POSITIONS
13-19
TPA 7110.6E
01/13/2011
FIGURE 13-12. RUNWAY 1 EAST SATELLITE
TRACON POSITIONS
13-20
TPA 7110.6E
01/13/2011
FIGURE 13-13. RUNWAY 19 EAST SATELLITE
Excludes Tower airspace
1,600 and below.
TRACON POSITIONS
13-21
TPA 7110.6E
01/13/2011
13-6. EAST ARRIVAL (E).
Assigned frequencies 118.15, 285.625.
a. Provide service for aircraft within designated East Arrival airspace. Duties and
responsibilities are as follows:
b. East Arrival shall hand off TPA arrivals to Final as follows:
(1) Runway 19:
(a) On the DADES RNAV STAR descending to 5,000 feet.
(b) A vector for a base leg no closer than 15 miles from the airport descending to 5,000 feet,
or on a downwind vector descending to 6,000 feet.
(2) Runway 1:
(a) On the DADES RNAV STAR descending to 5,000 feet.
(b) Downwind vector descending to 5,000 feet.
c. PIE arrivals shall be handed off to West Departure prior to DADES heading 270 degrees at
10,000 feet.
d. Turbojets arriving from the north landing SRQ or VNC shall be routed via LAL, descended
to 12,000 feet and handed off to East Departure.
e. When TPA is using RWY 1, traffic flowed to the opposite downwind shall be coordinated
with East and West Departure.
f. East Arrival shall point out V7 traffic to West Departure.
TRACON POSITIONS
13-22
TPA 7110.6E
01/13/2011
FIGURE 13-14. RUNWAY 1 EAST ARRIVAL
TRACON POSITIONS
13-23
TPA 7110.6E
01/13/2011
FIGURE 13-15. RUNWAY 19 EAST ARRIVAL
TRACON POSITIONS
13-24
TPA 7110.6E
01/13/2011
13-7. EAST DEPARTURE (B).
Assigned frequencies 135.5, 279.6.
a. Provide service for aircraft within designated East Departure airspace. Duties and
responsibilities are as follows:
b. When TPA is on RWY 1, initial departure headings are joint-use headings with West
Departure.
c. NOISE ABATEMENT: Do not vector turbojet aircraft departing RWY 1 until leaving 3,000
feet.
d. All arrivals handed off to South Departure shall be at 6,000 feet.
e. Prearranged coordination may be used in designated areas.
f. East Departure shall point out V7 traffic to West Departure.
g. SRQ jet arrivals received from East Arrival may be descended on contact.
h. Aircraft departing LAL, PCM, and X49 requesting 10,000 feet or above and transitioning to
ZMA via the LALS /BGTOP DTA shall be climbed to 9,000 feet and handed off to the ZMA
Lakeland Low sector.
i. East departure has control for climb on all aircraft handed off from South Departure at 5,000
feet per 13-8.g.
TRACON POSITIONS
13-25
TPA 7110.6E
01/13/2011
FIGURE 13-16. RUNWAY 1 EAST DEPARTURE
Initial departure headings are
shared between East and
West Departure. Excludes
Tower airspace 1,600 and
below.
TRACON POSITIONS
13-26
TPA 7110.6E
01/13/2011
FIGURE 13-17. RUNWAY 1 EAST ARRIVAL / DEPARTURE COMBINED
Initial departure
headings are shared
between East and West
Departure. Excludes
Tower airspace 1,600
and below.
TRACON POSITIONS
13-27
TPA 7110.6E
01/13/2011
FIGURE 13-18. RUNWAY 19 EAST DEPARTURE
TRACON POSITIONS
13-28
TPA 7110.6E
01/13/2011
FIGURE 13-18. RUNWAY 19 EAST ARRIVAL / DEPARTURE COMBINED
TRACON POSITIONS
13-29
TPA 7110.6E
01/13/2011
13-8. SOUTH DEPARTURE (G).
Assigned frequencies 134.25, 354.0.
a. Provide service for aircraft within South Departure designated airspace. Duties and
responsibilities are as follows:
b. On RWY 19, initial departure headings are joint-use headings with West Departure.
c. NOISE ABATEMENT: Do not vector turbojet aircraft departing RWY 19 until leaving
3,000 feet.
d. SHOWW departures shall be pointed out or handed off to West Departure.
e. SRQ RWY 14 departures are South Departure’s control for turns from South Satellite.
f. South Departure shall handoff TPA arrivals to Final as follows:
(1) RWY 19:
(a) On the DEAKK RNAV STAR at 5,000 feet.
(b) On a downwind vector at 5,000 feet.
(2) RWY 1:
(a) On the DEAKK RNAV STAR at 6,000 feet.
(b) On a vector to final no closer than 15 miles from the airport descending to 6,000 feet.
(c) If TPA arrival aircraft need to be vectored to downwind, handoff the aircraft to East
Departure descending to 7,000 feet.
g. Aircraft departing SRQ or VNC requesting at or below 10,000 feet filed northbound, shall
be handed off to East Departure or West Departure (as appropriate) at 5,000 feet. East Departure
and West Departure have control to climb these aircraft on contact.
h. When TPA is on Runway 19, South Departure is responsible to ensure separation between
H185 automatic departures and approaches inbound to MCF Runway 4 or Runway 22.
TRACON POSITIONS
13-30
TPA 7110.6E
01/13/2011
FIGURE 13-19. RUNWAY 1 SOUTH DEPARTURE
TRACON POSITIONS
13-31
TPA 7110.6E
01/13/2011
FIGURE 13-20. RUNWAY 19 SOUTH DEPARTURE
120
SFC
Initial departure headings
are shared between West
and South Departure.
Excludes Tower airspace
1,600 and below.
TRACON POSITIONS
13-32
TPA 7110.6E
01/13/2011
13-9. SOUTH SATELLITE (S).
Assigned frequencies 119.65 and 353.57 remoted at SRQ, 118.075 (VNC RCO).
a. Provide RADAR service for aircraft within South Satellite designated airspace. Duties and
responsibilities are as follows:
b. South Satellite will handoff TPA arrivals to Final as follows:
(1) RWY 1:
(a) Props at 3,000 feet.
(b) Turbojets/Turboprops should be handed off to South Departure.
(2) RWY 19:
(a) Props handed off to East Satellite at 3,000 feet on a vector towards East Satellite’s
airspace.
(b) Turbojets/Turboprops climbed to 3,000 feet or 4,000 feet, and handed off to South
Departure.
c. Coordinate MCF arrivals with the appropriate sector(s) when MCF Tower is closed.
d. Responsible for establishing 5-minute interval between aircraft entering IR049 and IR050,
and the 10 minute interval between aircraft entering IR051.
e. RWY 14 departures are released for turns to South Departure.
f. West Satellite shall establish the arrival sequence on all IFR arrivals and all VFR practice
approaches to SPG, and shall coordinate all IFR releases from SPG with South Satellite (or
MacDill sector if decombined).
TRACON POSITIONS
13-33
TPA 7110.6E
01/13/2011
FIGURE 13-21. RUNWAY 1 SOUTH SATELLITE
TRACON POSITIONS
13-34
TPA 7110.6E
01/13/2011
FIGURE 13-22. RUNWAY 19 SOUTH SATELLITE
TRACON POSITIONS
13-35
TPA 7110.6E
01/13/2011
13-10. LAKELAND LOW (R).
Assigned frequency 120.65 remoted at LAL.
a. Provide service for aircraft within LAL Low designated airspace. Duties and
responsibilities are as follows:
b. Receive an overflight strip on IR-046 traffic that has the estimated time the flight will be
clear of TPA delegated airspace and shall protect the IR046 airspace 10 minutes (NON-RADAR)
past the indicated time.
FIGURE 13-21. LAKELAND LOW AIRSPACE
TRACON POSITIONS
13-36
TPA 7110.6E
01/13/2011
13-11. MACDILL SECTOR (M).
Assigned frequencies 126.0 , 307.175 shared with Final.
a. Duties and responsibilities are as follows:
(1) Provide service for aircraft within designated MacDill sector airspace when MCF is
operating on Runway 4. MacDill sector is responsible for MCF Runway 4 approaches.
(2) When TPA is on Runway 19, MacDill sector shall coordinate MCF Runway 4 approaches
with South Departure.
b. Ensure that coordination has been accomplished with adjacent sectors/ facilities as
appropriate.
c. Missed approach instructions shall be issued in accordance with the MCF/TPA LOA.
d. West Satellite establishes the arrival sequence on all IFR arrivals and all VFR practice
approaches to SPG, and must coordinate all IFR releases from SPG with the MacDill sector.
e. When TPA is on RWY 19, and MCF Tower is closed, the MacDill sector will assume the
airspace normally controlled by MCF Tower.
FIGURE 13-22. MACDILL SECTOR AIRSPACE
TRACON POSITIONS
13-37
TPA 7110.6E
01/13/2011
This page intentionally left blank
TRACON POSITIONS
13-38
TPA 7110.6E
01/13/2011
CHAPTER 14. TRACON COORDINATORS
14-1. GENERAL.
a.. When coordinator position(s) are not staffed, the position is closed and not combined with
any other position(s).
b. Coordinator assumes responsibility for managing traffic flows and the RADAR position
retains responsibility for aircraft separation. Coordinator communicates directly with any and all
affected sectors and associated TRACON FLMIC/CIC to change any conditions impacting
traffic flows and to meet situation objectives.
c. All in-trail restrictions will be initiated through TRACON FLMIC/CIC.
d. Only FLM/CPC qualified personnel will staff coordinator positions.
14-2. INTERNAL COORDINATOR (IC).
IC shall assist all RADAR positions by:
a. Provide traffic flow instructions (speed, downwind entry, etc.) to adjacent internal RADAR
sectors.
b. Coordinate between positions to ensure efficient operations (handoffs, pointouts, etc).
c. Monitor spacing on final approach course(s) at TPA and initiate cancellation of approaches
(breakouts).
14-3. EXTERNAL COORDINATOR (XC).
XC shall assist arrival/departure sectors by:
a. Provide traffic flow instructions (speeds, headings, weather deviations, etc.) to adjacent
ARTCCs, approach control and tower facilities including TPA Tower.
b. Coordinate with adjacent ARTCCs, approach control and tower facilities including TPA
tower (handoffs, pointouts, headings, etc.).
c. Stop departures as necessary to ensure efficient operations. Resume departures only after
consulting the TRACON FLMIC/CIC.
14-4. MISCELLANEOUS.
a. IC will normally be opened at position 233 overhead (W/F) or 213 overhead (S/G) as
applicable.
TRACON COORDINATORS
14-1
TPA 7110.6E
01/13/2011
b. XC will normally be opened at position 223 overhead (D/P), 203 overhead (B/L) or 213
overhead (S/G) as applicable.
c. Coordinator positions can be staffed separately or combined.
EXAMPLES: IC can be open with XC closed, XC can be opened with IC closed, or IC/XC can
be open combined with a single CPC/FLM staffing the position.
NOTE: By having multiple (4) overhead positions available the possibility exists to open
coordinator positions in different combinations.
TRACON COORDINATORS
14-2
TPA 7110.6E
01/13/2011
CHAPTER 15. RUNWAY 10/28 PRIMARY RUNWAY OPERATION
15-1. GENERAL.
a. Because of the uniqueness of this operation, it is understood that coordination will be
necessary in specific cases to accomplish the flow required for both arrivals and departures. The
intent is, however, to provide as much standardization as feasible with the least amount of
disruption of "normal" operating procedures. Any additional departure headings and/or
procedures shall be coordinated, as necessary.
b. The "Bridge" airspace is not authorized.
c. RADAR controllers or handoff/data assistants will determine and update the initial departure
RADAR in-trail separation required, and the status of automatic departures. All prearranged
coordination procedures are canceled.
d. Turbojet departures shall not be turned prior to leaving 3,000 feet.
15-2. TOWER.
a. Tower will own RWY 1 airspace. Departure headings specified herein shall be assigned as
appropriate, and tower will ensure aircraft are established on assigned headings and proper
separation exists before changing frequency to departure control.
b. Runway 28 departure headings, altitudes, and frequencies:
(1) All Turbojets: Heading 270, climb to 3,000 feet, frequency 125.3.
(2) All others: Heading 270, climb to 3,000 feet; or heading 060 or 310 and climb to 1,600
feet, frequency 125.3/119.9.
c. Runway 10 departure headings, altitudes, and frequencies.
(1) All Turbojets: Heading 090, climb to 3,000 feet, frequency 119.9.
(2) All others: Heading 090, climb to 3,000 feet; or heading 060 or 310 climb to 1,600 feet,
frequency 119.9/125.3.
15-3. TRACON.
a. Runway 28 operation.
(1) Handoffs to East Satellite. (TPA Final Controller)
(a) West Arrival/Satellite: On the downwind abeam COSME; Turbojets at 4,000 feet,
Turboprops/Props IFR at 3,000 feet, VFR at 2,100 to 3,000 feet.
(b) East Arrival: Base leg or downwind at 5,000 feet.
(c) South Departure: On the downwind abeam MCF; Turbojets at 5,000 feet,
Turboprops/Props IFR at 3,000 feet, VFR at 3,000 feet or below.
RUNWAY 10/28 PRIMARY RUNWAY OPERATION
15-1
TPA 7110.6E
01/13/2011
(2) East Satellite has control for turns toward final and descent on contact for TPA arrivals.
(3) Any departures off RWY 19 or 1 shall be coordinated with the appropriate sectors to
protect the downwind pattern.
(4) South Satellite will operate with MCF RWY 4, TPA RWY 1 airspace configuration.
b. Runway 10 Operation.
(1) Handoffs to West Satellite. (TPA Final Controller)
(a) East Arrival/Satellite: On the downwind abeam COSME; Turbojets at 4,000 feet,
Turboprops/Props IFR at 3,000 feet, VFR at 2,100 to 3,000 feet;.
(b) West Arrival: Base leg or downwind at 5,000 feet.
(c) South Departure: On the downwind abeam MCF; Turbojets IFR at 5,000 feet,
Turboprops/Props IFR at 3,000 feet, VFR at 3,000 feet or below.
(2) West Satellite has control for turns toward final and descent on contact for TPA arrivals.
(3) Any departures off RWYs 19 or 1 shall be coordinated with the appropriate sectors to
protect the downwind pattern.
(4) South Satellite will operate with MCF RWY 4, TPA RWY 1 airspace configuration.
RUNWAY 10/28 PRIMARY RUNWAY OPERATION
15-2
TPA 7110.6E
01/13/2011
CHAPTER 16. RADAR OUTAGE PROCEDURES
16-1. BACKGROUND.
a. These procedures are designed to help transition through various levels of RADAR failure
to Operational Capability Level Zero, and are supplementary to those contained in the ZMA
ARTCC, ZJX ARTCC, F11 TRACON, JAX ATCT, RSW ATCT, PIE ATCT, MCF ATCT,
SRQ ATCT, SPG ATCT, AND LAL ATCT, Letters of Agreement, and the Contingency Plan.
b. TPA utilizes RADAR information from three RADAR sites; TPA ASR-9, SRQ ASR-9, and
QFN ASRS-4.
c. When all three sites are operational, operations shall be conducted normally.
d. RADAR sites can be selected via the STARS DCB / TDW at each RADAR and tower
position.
16-2. QFN RADAR OPERATIONAL.
When the QFN ASRS-4 is operational and either the TPA or SRQ ASR-9 fails, proceed as
follows:
a. SRQ ASR-9 out of service:
(1) Utilize the TPA ASR-9 for all sectors, except S and G shall utilize the QFN ASRS-4 and
apply appropriate separation criteria.
(2) Notify ZMA ARTCC that SRQ ASR-9 is OTS, and advise which alternate RADAR site
is being used by TPA.
(3) Notify SRQ, and advise that Class C services are not available.
(4) Notify RSW and advise utilizing TPA ASR-9 RADAR site. Advise RSW to provide 5
NM in-trail spacing on all TPA area arrivals.
(5) Notify AOCC and AFSS of the outage. Verify AFSS will issue a NOTAM on the SRQ
RADAR outage and non-availability of Class C services.
b. TPA ASR-9 out of service.
(1) Utilize the SRQ ASR-9 for S, G, M and F sectors (F sector if TPA is landing north).
(2) Utilize the QFN ASRS-4 for all other sectors and apply appropriate separation criteria.
(3) Cancel automatic departures at PIE. Automatic departures may be canceled at TPA and
SRQ at the discretion of the TRACON FLMIC / CIC.
(4) Cancel all prearranged coordination procedures except the Bridge procedure may remain
in use.
(5) Notify the following facilities of the outage.
 ZMA and ZJX ARTCC.
 F11 TRACON and JAX ATCT.
 PIE, MCF, SPG, and LAL ATCTs.
RADAR OUTAGE PROCEDURES
16-1
TPA 7110.6E
01/13/2011
 AFSS. Send NOTAMs on RADAR outage and non-availability of Class B services.
(6) Institute flow control restrictions as needed.
(7) Broadcast on the ATIS: "TPA RADAR OUT OF SERVICE. VFR SERVICES ARE
AVAILABLE TO TRANSPONDER EQUIPPED AIRCRAFT ONLY AND ARE LIMITED TO
SAFETY ALERTS, TRAFFIC ADVISORIES, AND SEQUENCING TO TPA
INTERNATIONAL".
c. Separation criteria when using QFN:
(1) Lateral separation minima:
(a) Targets = 5 NM if more than 40 NM from the QFN RADAR site and 3 NM if 40 NM or
less from the site.
(b) Adjacent airspace = 2 ½ NM if more than 40 NM from the QFN RADAR site, and 1 ½
NM if 40 NM or less from the site.
(c) Obstructions = 5 NM if more than 40 NM from the QFN RADAR site and 3 NM if 40
NM or less from the site.
(2) STARS map 37 depicts a 40 NM circle centered on the QFN RADAR site.
(3) Normal departure headings from TPA will apply while using the QFN RADAR, however
LC will provide 5 miles in trail between like type departures on each heading.
d. STARS Multi Mode Separation Criteria:
 Targets = 5 NM.
 Adjacent airspace = 2 ½ NM.
 Obstructions = 5 NM.
RADAR OUTAGE PROCEDURES
16-2
TPA 7110.6E
01/13/2011
FIGURE 16-1 FT. GREEN (QFN) RADAR 40 NM RANGE.
Ft. Green
■
RADAR OUTAGE PROCEDURES
16-3
TPA 7110.6E
01/13/2011
16-3. QFN RADAR OUT OF SERVICE.
When the QFN ASRS-4 is not operational, and the TPA or SRQ ASR-9 fails, proceed as follows.
a. SRQ ASR-9 out of service:
(1) All sectors select the TPA ASR-9 RADAR.
(2) Cancel automatic departure releases at SRQ.
(3) Notify the following facilities of the outage:
(a) ZMA and advise the TPA ASR-9 is being used for the SRQ area.
(b) SRQ and advise that Class C services are not available.
(c) RSW and advise TPA is Single-Sensor TPA ASR-9. RSW will provide 5NM in-trail
spacing on all TPA area arrivals.
(d) AFSS. Send NOTAMs on SRQ RADAR outage and non-availability of Class C
services.
(4) FDR shall post arrival flight progress strips at the appropriate positions.
b. TPA ASR-9 out of service:
(1) All sectors select the SRQ ASR-9 RADAR site.
(2) Cancel automatic departures at all airports. LC shall call for release on all departures and
shall be responsible for NON-RADAR separation of all aircraft until RADAR contact is
established by the initial departure sector.
(3) LC shall sequence all VFR arrivals to TPA.
(4) Cancel all prearranged coordination procedures except the Bridge procedure may remain
in use.
(5) Transition to, and provide services in accordance with the TPA/ZJX/ZMA/MCO/JAX
Single Sensor (ASR) Outages within the Tampa Complex LOA.
(6) Notify the following facilities of the outage:
 ZMA and ZJX.
 F11 and JAX.
 PIE, MCF, SPG, and LAL.
 AFSS. Send NOTAMs on RADAR Outage and non-availability of Class B
services.
(7) FDR shall post arrival flight progress strips at the appropriate positions.
(8) Broadcast on the ATIS: "TPA RADAR OUT OF SERVICE. VFR SERVICES ARE
AVAILABLE TO TRANSPONDER EQUIPPED AIRCRAFT ONLY AND ARE LIMITED TO
SAFETY ALERTS, TRAFFIC ADVISORIES, AND SEQUENCING TO TPA
INTERNATIONAL".
16-4. LOSS OF RADAR / NON-RADAR PROCEDURES.
The following guidelines are to be utilized in the event of a total RADAR failure at TPA. This
section outlines procedures to follow to transition from a RADAR environment.
RADAR OUTAGE PROCEDURES
16-4
TPA 7110.6E
01/13/2011
a. Transitioning. Immediately following the complete loss of RADAR, the following actions
should be taken.
(1) Controllers.
(a) Take immediate action to establish and maintain NON-RADAR separation between all
aircraft under your control and to contain all aircraft within sector airspace.
(b) Cancel all automatic departures.
(c) Do not accept any more aircraft into sector airspace.
(d) Terminate services to all VFR aircraft.
(e) Notify adjacent sectors and towers as needed for separation and / or holding of aircraft.
(f) FDT shall stop issuing departure clearances.
(g) Broadcast on the ATIS "TPA RADAR AND SRQ RADAR OUT OF SERVICE.
CLASS B AND CLASS C SERVICES ARE NOT AVAILABLE. GATE HOLD
PROCEDURES ARE IN EFFECT".
(h) FDR shall post all available flight progress strips at the appropriate positions and assist
RADAR sector controllers to the extent possible.
(2) FLMIC/CIC.
(a) Assist RADAR sector controllers with establishing NON-RADAR separation of all
aircraft.
(b) Cancel all automatic departures.
(c) Notify the following facilities of the outage:
 ZMA and ZJX ARTCC.
 F11 TRACON, RSW and JAX ATCTs.
 PIE, MCF, SPG, and LAL ATCTs.
 AFSS. Send NOTAMs on RADAR outage and non-availability of Class B
services.
(d) Coordinate with ZJX and ZMA ARTCCs for the release of TPA airspace from 7,000
feet and above after NON-RADAR separation of all aircraft under TPA control has been
established.
(e) Coordinate with all satellite towers that tower delegated airspace is cancelled.
b. After NON-RADAR separation and holding has been established, and inter / intra-facility
coordination completed, the FLMIC/CIC will coordinate the sequencing of arrivals from the
holding fixes to the final controller and release the airspace to the Centers as specified in the
ZJX, ZMA, F11, RSW, and JAX LOAs.
16-5. NON-RADAR HOLDING.
If NON-RADAR holding is necessary, TRACON RADAR positions will hold as follows.
a. TPA Final:
(1) Runway 19 -- hold north of COSME, 1-minute left turns, 2,000 feet to 5,000 feet.
NOTE: If additional holding is required immediately following the loss of RADAR, coordinate
with East and West Arrival for additional altitudes at COSME.
RADAR OUTAGE PROCEDURES
16-5
TPA 7110.6E
01/13/2011
(2) Runway 1 -- hold south of PICNY, 1-minute legs, 3,000 feet to 5,000 feet.
NOTE: If additional holding is required immediately following the loss of RADAR, coordinate
with South Departure and West Arrival for additional altitudes at PICNY.
(3) After separation is ensured, and ready to commence making approaches to TPA,
coordinate with the TRACON FLMIC who will initially sequence holding traffic at the outer
fixes to the final controller. Begin calling inbounds to the tower.
b. East Arrival. Hold at DADES, north on V581, 1-minute legs, left turns, 9,000 feet to 12,000
feet.
c. South Departure. Hold at GIBBS, southeast, 1-minute legs, right turns, 5,000 feet-11,000
feet. (coordinate with EAST departure).
d. East Departure:
(1) DADES: hold north on V581, 1-minute legs, left turns, 6,000 feet-8,000 feet.
(2) LAL: hold north on V157, 1-minute legs, right turns, 5,000 feet-12,000 feet.
NOTE: Holding aircraft at DADES and LAL VOR must not conflict with north or south
overflight traffic.
e. East Satellite:
(1) DADES: Hold north on V581, 1-minute legs, left turns, 3,000 feet to 5,000 feet.
(2) LAL: Hold north on V157, 1-minute legs, right turns, 4,000 feet.
NOTE: Holding aircraft at DADES and LAL must not conflict with north/south overflight
traffic.
f. Lakeland Low (combine with East Satellite when possible): Hold at LAL VOR, north on
V157, 1-minute leg, right turns, 3,000 feet.
g. West Arrival:
(1) DARBS: Hold northwest, 1-minute legs, right turns, 9,000 feet to 12,000 feet.
(2) BLOND: Hold west, 1-minute legs, right turns, 5,000 feet to 12,000 feet.
h. West Departure: Hold at DARBS, northwest, 1-minute legs, right turns, 6,000 feet to 8,000
feet. (Coordinate with West Arrival.)
i. West Satellite:
RADAR OUTAGE PROCEDURES
16-6
TPA 7110.6E
01/13/2011
(1) DARBS: hold northwest, 1-minute legs, right turns, 3,000 feet to 5,000 feet. (Coordinate
with West Departure)
(2) BLOND: hold west, 1-minute legs, right turns, 3,000 feet and 4,000 feet.
j. South Satellite:
(1) GIBBS: Hold southeast, 1-minute legs, right turns, 4,000 feet. (Coordinate with East
Departure and East Satellite
(2) RINGY: hold southeast, 1-minute legs, left turns, 3,000 feet and 4,000 feet.
(3) FRUGL: hold northwest, 1-minute legs, right turns, 3,000 feet and 4,000 feet.
(Coordinate with West Satellite.)
k. South Departure:
(1) SRQ VOR: hold southeast on SRQ 140 degree radial, 1-minute legs, right turns, 5,000
feet to 10,000 feet.
(2) GIBBS: hold southeast, 1-minute legs, right turns, 5,000 feet to 10,000 feet. (coordinate
with EAST departure).
RADAR OUTAGE PROCEDURES
16-7
TPA 7110.6E
01/13/2011
This page intentionally left blank
RADAR OUTAGE PROCEDURES
16-8
TPA 7110.6E
01/13/2011
APPENDIX A
FIGURE 1. TPA AIRPORT MAP, NON-MOVEMENT AREAS
AND AREAS OF NON-VISIBILITY.
APPENDIX A
A-1
TPA 7110.6E
01/13/2011
This page intentionally left blank
APPENDIX A
A-2
TPA 7110.6E
01/13/2011
APPENDIX B
LOW LEVEL WIND SHEAR ALERT SYSTEM (LLWAS).
a. The TPA Low Level Wind Shear Alert " Network Expansion" System (LLWAS-NE++) is
integrated with Terminal Doppler Weather RADAR (TDWR) and Integrated Terminal Weather
System (ITWS). This provides the capability of displaying microburst alerts, windshear alerts
and wind information oriented to the threshold or departure end of the runway. TDWR and
ITWS are designed to detect windshear and microburst activity, and ITWS adds other
capabilities such as gust front and storm cell motion predictions. The associated ribbon display
allows the controller to read the displayed alert without any need for interpretation. The TPA
System consists of three centerfield wind sensors (two serve as backup sensors) and eight (8)
remote sensors located at various positions around the airport. The data is sampled and
transmitted to the computer, where wind direction and speed, centerfield averages, and
centerfield gust calculations are made. The centerfield reading is a 2 minute average of the
centerfield wind. The other remote stations will be updated every twenty (20) seconds. The
centerfield wind will be displayed on the Ribbon Display as "AW" (Airport Wind).
b. Wind issued by TPA Tower/Approach will be the centerfield wind, which is based on a two
(2) minute average.
DISPLAY EXAMPLE: AW 340 15
PHRASEOLOGY: WIND THREE FOUR ZERO AT ONE FIVE.
c. If a windshear or microburst alert is received for the runway in use, issue the alert
information for that runway to arriving and departing aircraft as it is displayed on the Ribbon
Display.
PHRASEOLOGY: (Runway) (Arrival, Departure), WINDSHEAR / MICROBURST ALERT,
(Wind Speed) KNOT GAIN / LOSS, (Location).
DISPLAY EXAMPLE: 19LA MBA 40K - 3MF
PHRASEOLOGY: RUNWAY 19L ARRIVAL, MICROBURST ALERT 40 KNOT LOSS, 3
MILE FINAL.
DISPLAY EXAMPLE: 19RD WSA 25K + 2MD
PHRASEOLOGY: RUNWAY 19R DEPARTURE, WINDSHEAR ALERT 25 KNOT GAIN, 2
MILE DEPARTURE.
d. If requested by pilot or deemed appropriate by the controller, issue the displayed wind
information oriented to the threshold or departure end of the runway.
PHRASEOLOGY: (Runway) DEPARTURE / THRESHOLD WIND (Direction) AT (Velocity).
APPENDIX B
B-1
TPA 7110.6E
01/13/2011
e. Sensor failure:
(1) The LLWAS under normal operation will always display wind direction to the nearest 10
degrees (i.e. 130, 140).
(2) If the centerfield sensor fails, the top reading will display 999 in the direction and 99 in
the speed. Line 2 will display all 9's.
(3) The LLWAS-NE++ is designed to operate with as many as five (5) sensors inoperative.
APPENDIX B
B-2
TPA 7110.6E
01/13/2011
APPENDIX C
MCF AIRSHOW AIRSPACE.
This airspace is used for aerial demonstration of low-level precision aerobatic maneuvers by
military flight demonstration teams. The airspace consists of 2 areas described below:
Area "A" - From the surface to 15,000 feet AGL within a 5 nautical mile radius of MCF AFB,
except as indicated below.
Area "B" - From 4,000 feet to 15,000 feet, as indicated below.
FIGURE 1. MCF AIRSHOW AIRSPACE
APPENDIX C
C-1
TPA 7110.6E
01/13/2011
This page intentionally left blank
APPENDIX C
C-2
TPA 7110.6E
01/13/2011
APPENDIX D
RUNWAY VISUAL RANGE (RVR).
a. DEFINITIONS.
(1) Runway Visual Range (RVR). Runway Visual Range is a value determined by
instruments located along side and 14 feet higher than the centerline of the runway that
represents the horizontal distance a pilot will see down the runway from the approach end. It is
based on the sightings of either High-Intensity Runway Lights (HIRL) or on the visual contrast
of other targets, whichever yields the greater visual range. RVR, in contrast to prevailing or
runway visibility, is based on what a pilot in a moving aircraft should see looking down the
runway. It is based on the measurement of a visibility sensor made near the touchdown point of
the instrument runway and is reported in hundreds of feet.
(2) Touchdown RVR System. The Touchdown RVR System is that system whose visibility
sensor is located near the touchdown end of the runway.
(3) Midpoint-RVR System. The Mid-RVR System is that system whose visibility sensor is
located within 1,000 feet of half the distance of the length of the runway, and the distance from
runway centerline shall conform to standards designated for Touchdown and Rollout RVR.
(4) Rollout RVR System. The Rollout RVR System is that system whose visibility sensor is
located approximately 1,000 feet from the rollout end of the runway.
(5) Designated RVR Runway. The designated RVR Runway is the runway officially
designated by FAA for the reporting of ten-minute maximum and minimum RVR values in longline dissemination. This will normally be the runway having the lowest instrument minima.
(This definition is for flight planning purposes).
b. SYSTEM DESCRIPTION.
A full RVR System consists of the following:
(1) Data Processing Unit (DPU).
(2) Visibility Sensors (VS).
(3) Ambient Light Sensor (ALS).
(4) Runway Light Intensity Monitors (RLIM).
(5) Sensor Interface Electronics (SIE).
(6) Control Displays (CD).
c. PROCEDURES FOR OPERATING TPA RVR.
(1) Runway Selection: A runway can be selected in the RVR mode. When selecting a
runway from the LIMITS mode (Low Visibility Alarm Threshold (LVAT) fields are being
changed), an alarm sounds to let the controller know that LIMITS mode is active and the
controller must press the RVR key before selecting a runway. Available RVR settings for
viewing are for the following runways:
- 1L/19R - TD, MP, RO
- 1R/19L - TD, RO
(2) Press the RUNWAY key: the cursor moves to the first available runway designator field.
APPENDIX D
D-1
TPA 7110.6E
01/13/2011
(3) Press and release this button until the desired runway appears in the selected field. (There
is a blank field).
(4) When correct runway is displayed, press ENTER. The cursor will move to the next
runway field.
(5) Repeat these steps for additional runways.
(6) When finished, press RVR or LIMITS.
d. REPORTABLE RVR.
(1) The RVR can be viewed in feet and meters.
(2) RVR reporting increments are as follows:
(a) 100-foot increments below 800 feet.
(b) 200-foot increments between 800 feet - 3,000 feet.
(c) 500-foot increments between 3,000 feet = 6,500 feet.
(3) Arrows show the trend of visibility change: upward indicates improvement, downward
indicates deterioration.
e. ALARM. An additional feature of the RVR Digital Display is the alarm. If RVR value
falls below the LVAT, the display sounds 3 beeps of an audible alarm and the display flashes.
f. LIMITS (LVAT - Low Visibility Alarm Threshold).
(1) A value of 2,400 feet should initially be set. When the RVR equals 2,400 feet, the alarm
sounds and informs the controller that the emergency generators for the ALS and for the
runways/taxiways MUST be turned on.
(2) Additional settings can be displayed according to the Approach Category and Minimums.
LVATs are assigned to a runway, and are not row position dependent.
(3) To change the LVAT:
(a) Press LIMITS.
(b) Enter the numeric value.
(c) Press ENTER - cursor moves to next field.
(d) When all fields are entered, press RVR.
(e) The FILL key can be used to insert same values into different fields. After pressing
ENTER to accept the first field, press FILL. This repeats the last entered value in the next field.
(f) Use above procedures to change LVATs after they have been entered.
(g) If RVR value falls below the LVAT, the display sounds 3 beeps of an audible alarm and
the display flashes.
g. LIGHTS.
(1) CENTERLINE: Field blank, RVR sensor not configured for the CL lights.
(2) RVR SENSOR FIELD: "FFF" in sensor field means sensor inoperative or out of service.
(3) LIGHT INTENSITY FIELD:
(a) "F" in field means valid runway light settings not available.
(b) "0" in field indicates the lights are off.
APPENDIX D
D-2
TPA 7110.6E
01/13/2011
NOTE: If edge and centerline runway light settings do not match, after 15 seconds the display
will flash and an audible alarm will beep 3 times. The display will continue to flash until runway
light settings match, or the ALARM ACK key is pushed.
h. INSTRUMENT APPROACH CATEGORIES. All-weather instrument approach
operations are divided into categories corresponding to different standards of instrumentation in
the aircraft and on the ground. For each category, there is a specific minimum RVR value which
operations are not permitted. The following table identifies the categories and LOWEST minima
associated with each:






CATEGORY
RVR
Nonprecision 2,400 feet
Category I
1,800 feet
Category II
1,200 feet
Category IIIA
700 feet
Category IIIB
600 feet
Category IIIC
0 feet
APPENDIX D
D-3
TPA 7110.6E
01/13/2011
This page intentionally left blank
APPENDIX D
D-4
TPA 7110.6E
01/13/2011
APPENDIX E
CATEGORY II AND III ILS OPERATIONAL REQUIREMENTS.
1. This information is an abbreviated composite of material contained in several documents
referring to Category (CAT) II and III ILS operations. These documents describe in depth the
various equipment requirements and actions specific to RWY 1L (CAT II and III) and RWY 19L
(CAT II) operations. Not every pilot or aircraft is qualified for the lowest minimums. The pilotin-command is responsible for compliance with minima prescribed for their class of operation in
appropriate FAR and/or operation specifications. A pilot's request to exercise CAT II or III
authority may be honored even when the weather is above the approach minimums. In all these
cases, CAT II or III ground equipment will be operational and ILS critical area protection
provided.
2. RUNWAY 1L CAT ll & lll OPERATIONS.
a. Requirements for Operation:
(1) CAT I: Operations down to a minima of 212 feet DH and RVR 1,800 feet.
(2) CAT II: Operations down to a minima of 162 feet DH and RVR 1,600 feet, to as low as
112 feet decision height and RVR 1,200 feet.
(3) CAT IIIA: Operations without a DH minimum and RVR 700 feet.
(4) CAT IIIB: Operations without a DH minimum and RVR 600 feet.
(5) The following facility requirements shall be met prior to beginning CAT II or CAT III
ILS operations:
(a) Verify Main and Standby Localizer and Glide Slope transmitters are operational.
(b) Verify Far Field Monitor (FFM) operational.
(c) Verify the status of the Outer Marker. If the Outer Marker is out of service, advise the
TRACON FLMIC/CIC that CAT II or CAT III approaches may commence provided approach
control advises aircraft when over the final approach fix, PICNY.
(d) Approach Light System (ALS), and Sequence Flashing Lights (ALSF-2), Touchdown
Zone Lights, High Intensity Runway Edge Lights, and Centerline Lights operational.
(e) Approach Light System (ALSF-2) and HCAA Engine Generators running with
commercial power available as alternate power source. Engine generator start and stop
instructions are contained in section d, below.
(f) Touchdown RVR required CAT II or CAT III operations. For RVR below 1,600 to
1,200, CAT II operations are allowed if either the Midpoint or the Rollout RVR is operational.
For CAT III operations to commence, Touchdown, Midpoint and Rollout RVRs must be
operational.
(g) When facilities do not meet the functional requirements as stated above, to either
commence or continue CAT II or CAT III operations, the TRACON FLMIC/CIC shall ensure
that a NOTAM is issued. It shall specify, "TPA (components) OTS, RWY 1L CAT III (CAT II)
approaches not authorized". The effect of equipment outages and actions required pertaining to
the above referenced equipment can be verified in FAAO 6750.24.
APPENDIX E
E-1
TPA 7110.6E
01/13/2011
(h) Advise HCAA via the Comm. Center, when commencing CAT II operations. Also,
advise HCAA if RVR visibility below 1,200 will likely occur. This starts the clock for HCAA to
conduct required runway and taxiway light inspections every two hours.
(i) When RVR values drop below 1,200 (CAT III operations), the TRACON FLMIC/CIC
shall:
(1) Ensure that HCAA is advised, via the Comm. Center, that low visibility operations
have been officially implemented.
(2) Ensure the Runway Guard Lights are illuminated.
(3) Ensure that a low visibility operations message is included on the ATIS. Phraseology;
"Low visibility operations are in effect".
(4) If RWY 1R RVR is 1,200 or greater, use RWY 1R for departures and land on RWY
1L. If RWY 1R RVR decreases below 1,200, then RWY 1L shall be used for arrivals and
departures.
(j) When RVR values exceed and will likely remain above 1,200, the TRACON
FLMIC/CIC shall:
(1) Ensure that HCAA is advised, via the Comm. Center, that low visibility operations
have been terminated.
(2) Reconfigure airfield lighting as necessary.
(3) Remove the low visibility operations message from the ATIS.
b. Far Field Monitor (FFM) Procedures: Application of procedures used in conjunction with
the FFM are outlined in JO 7110.65 and FAAO 6750.24. The following local procedures
pertaining to the FFM shall be used when the Remote Status Sensing Unit indicates that the
localizer FFM is in alarm (aural warning following the preset delay):
(1) The aircraft is outside the Outer Marker (OM): Check for encroachment in those portions
of the critical area that can be seen from the Tower. It is understood that the entire critical area
may not be visible due to low ceilings and poor visibility. The check is strictly to determine
possible causal factors for the out-of-tolerance situation. If the alarm has not cleared prior to the
aircraft's arriving at the OM, immediately issue an advisory that the FFM Remote Status Sensing
Unit indicates the Localizer is unreliable for CAT III or CAT II.
(2) The aircraft is between the OM and the Inner Marker (IM): Immediately issue an
advisory that the FFM Remote Status Sensing Unit indicates the Localizer is unreliable for CAT
III or CAT II.
PHRASEOLOGY: "CAUTION, MONITOR INDICATES RUNWAY 1L LOCALIZER,
UNRELIABLE".
(3) The aircraft has passed the IM: There is no action requirement. Although the FFM has
been modified with filters that dampen the effect of false alarms, you can expect alarms when
aircraft are located between the FFM and the Localizer antenna, either when landing or on
takeoff.
c. Mark 20 ILS Runway 1L Monitor Panel. The system monitors all ILS components required
for the various ILS categories (CAT I, II or III) to RY 1L. Whenever a component of the ILS
fails, an indicator light on the panel, as well as an aural alarm, reflects the failed component(s)
APPENDIX E
E-2
TPA 7110.6E
01/13/2011
and the effect on approach categories (reducing from CAT III to II or I or Localizer only). Aural
alarms are silenced by simply depressing the "silence" button located on the monitor panel.
d. ALS and HCAA Engine Generator Operation.
(1) Start engine generators when the RVR goes below 2,400. The tower shall start the engine
generators at the ALS and HCAA Power Vaults, using the following instructions:
(a) ALSF-2 Engine Generator: (This generator supplies power for the ALS and SFL).
(1) Turn Sequence Flashing Lights (SFL) OFF.
(2) Turn Approach Lights (ALSF-2) to Step 2.
(3) Turn switch (located above the RWY 1L ALSF-2 panel) to "ON". The red indicator
light will come on. This light will pulsate as long as the ALS engine generator is running.
(4) Turn Approach Lights and Sequence Flashing Lights to the appropriate setting.
(b) Activate the West Field Lighting Generator. The two HCAA generators ("W. GEN"
and "E. GEN") supply power for all three runways, 10/28, 19L/1R, 19R/1L, Runway Edge
Lights, Touchdown Zone Lights, Centerline Lights, parallel taxiways to the runways, overpass
taxiway, and terminal ramp Edge Lights. To start the West Generator, depress the emergency
generator switch labeled "W. GEN." on the Field Lighting Panel. The upper part of the switch
will illuminate; also the RED indicator light labeled "GEN RUN" next to the ON/OFF switch
will light while the engine generator is running.
NOTE: It may take up to fifteen seconds, depending on the outside air temperature, for the
engine generator to come on.
(2) Stopping Engine Generators. The Tower will turn off the engine generators ONLY when
the RVR increases to more than 2,400 and indications are that it will not decrease below 2,400
within a half hour. Use the following instructions to turn off the generators:
(a) ALSF-2 Engine Generator:
(1) Turn Sequence Flashing Lights (SFL) OFF.
(2) Turn Approach Lights to Step 2.
(3) Turn switch (located above the ALSF-2 Panel) to "OFF", the engine generator will not
immediately shut down. The generator will continue to run approximately three minutes for a
cool-down period.
(4) Turn Approach Lights and Sequence Flashing Lights to the appropriate setting.
(b) HCAA Engine Generators: Depress the emergency generator switch labeled "W. GEN"
on the Field Lighting Panel. The switch lights should indicate "ON" for six and one-half minutes.
The generator will wait three and one-half minutes to be sure there is no fluctuation in
commercial power. When this time is up, the lights should blink once. The generator will then
run three more minutes for a cool-down period and shut off.
3. RUNWAY 19L CAT ll OPERATIONS.
a. Requirements for Operation:
(1) CAT I: Operations down to a minima of 226 feet DH and RVR 1,800 feet.
(2) CAT II: Operations down to a minima of 126 feet DH and RVR 1,200 feet.
APPENDIX E
E-3
TPA 7110.6E
01/13/2011
(3) The following facility requirements shall be met prior to beginning CAT II ILS
operations:
(a) Verify Main and Standby Localizer and Glide Slope Transmitters are operational.
(b) Verify Far Field Monitor (FFM) operational.
(c) Verify the status of the Outer Marker. If the Outer Marker is out of service, advise the
TRACON FLMIC/CIC that CAT II approaches may commence provided approach control
advises aircraft when over the final approach fix, COSME.
(d) Approach Light System (ALS), and Sequence Flashing Lights (ALSF-2), Touchdown
Zone Lights, High Intensity Runway Edge Lights, and Centerline Lights operational.
(e) Approach Light System (ALSF-2) and HCAA Engine Generators running with
commercial power available as alternate power source. Engine generator start and stop
instructions are contained in section e, below.
(f) Touchdown RVR required CAT II operations. For RVR below 1,600 to 1,200, CAT II
operations are allowed if either the Midpoint or the Rollout RVR is operational.
(g) When facilities do not meet the functional requirements as stated above, to either
commence or continue CAT II operations, the TRACON FLMIC/CIC shall ensure that a
NOTAM is issued. It shall specify, "TPA (components) OTS, RWY 19L CAT II approaches not
authorized". The effect of equipment outages and actions required pertaining to the above
referenced equipment can be verified in FAAO 6750.24.
(h) Advise HCAA Airport Operations (HCAA), via the Comm. Center, when commencing
CAT II operations. Also, advise HCAA if RVR visibility below 1,200 will likely occur. This
starts the clock for HCAA to conduct required runway and taxiway light inspections every two
hours.
(i) The minimum RVR for CAT II operations on RWY 19L is 1,200. When the RVR drops
below 1,200, or is anticipated to drop below this value, low visibility operations (RWY 1L only)
will be implemented.
b. Far Field Monitor (FFM) Procedures: Application of procedures used in conjunction with
the FFM are outlined in JO 7110.65 and FAAO 6750.24. The following local procedures
pertaining to the FFM shall be used when the Remote Status Sensing Unit indicates that the
localizer FFM is in alarm (aural warning following the preset delay):
(1) The aircraft is outside the outer marker (OM): Check for encroachment in those portions
of the critical area that can be seen from the Tower. It is understood that the entire critical area
may not be visible due to low ceilings and poor visibility. The check is strictly to determine
possible causal factors for the out-of-tolerance situation. If the alarm has not cleared prior to the
aircraft's arriving at the OM, immediately issue an advisory that the FFM Remote Status Sensing
Unit indicates the Localizer is unreliable for CAT II.
(2) The aircraft is between the OM and the Inner Marker (IM): Immediately issue an
advisory that the FFM Remote Status Sensing Unit indicates the Localizer is unreliable for
CAT II.
PHRASEOLOGY: "CAUTION, MONITOR INDICATES RUNWAY 19L LOCALIZER,
UNRELIABLE".
(3) The aircraft has passed the IM: There is no action requirement. Although the FFM has
been modified with filters that dampen the effect of false alarms, you can expect alarms when
APPENDIX E
E-4
TPA 7110.6E
01/13/2011
aircraft are located between the FFM and the Localizer antenna, either when landing or on
takeoff.
c. Mark 20 ILS Runway 19L Monitor Panel. The system monitors all ILS components
required for the various ILS categories (CAT I or II) to RWY 19L. Whenever a component of
the ILS fails, an indicator light on the panel, as well as an aural alarm, reflects the failed
component(s) and the effect on approach categories (reducing from CAT II to I or Localizer
only). Aural alarms are silenced by simply depressing the "silence " button located on the
monitor panel.
d. ALS and HCAA Engine Generator Operation.
(1) Start engine generators when the RVR goes below 2,400. The Tower shall start the
engine generators at the ALS and HCAA Power Vaults, using the following instructions:
(a) ALSF-2 Engine Generator: (This generator supplies power for the ALS and SFL).
(1) Turn sequence flashing lights (SFL) OFF.
(2) Turn approach lights (ALSF-2) to Step 2.
(3) Start the RWY 19L ALSF-2 Engine Generator. (Control panel located just below the
RWY 19L ALSF-2 Panel.) To start the generator, push and release the "Select E/G" button. The
generator will start, the "E/G Running" light will illuminate, and the "E/G ON-LN" light will
also illuminate, indicating the generator is on-line. When the generator is on-line, the "COMML
ON-LN" light will go out, indicating that commercial power is off-line. The "COMML AVAIL"
light is illuminated whenever commercial power is available.
(4) Turn Approach Lights and Sequence Flashing Lights to the appropriate setting.
(b) Activate the East Field Lighting Generator. The two HCAA generators ("W. GEN" and
"E. GEN") supply power for all three runways, 10/28, 19L/1R, 19R/1L, Runway Edge Lights,
Touchdown Zone Lights, Centerline Lights, parallel taxiways to the runways, overpass taxiway,
and terminal ramp Edge Lights. To start the East Generator, depress the emergency generator
switch labeled "E. GEN." on the Field Lighting Panel. The upper part of the switch will
illuminate; also the RED indicator light labeled "GEN RUN" next to the On/Off switch will light
while the engine generator is running.
NOTE: It may take up to fifteen seconds, depending on the outside air temperature, for the
engine generator to come on.
(2) Stopping Engine Generators. The tower will turn off the engine generators ONLY when
the RVR increases to more than 2400 and indications are that it will not decrease below 2400
within a half hour. Use the following instructions to turn off the generators:
(a) ALSF-2 Engine Generator:
(1) Turn Sequence Flashing Lights (SFL) OFF.
(2) Turn Approach Lights to Step 2.
(3) Turn off the RWY 19L ALSF-2 Engine Generator (located just below the RWY 19L
ALSF-2 Control Panel.) To turn the generator off, push and release the "SELECT
COMMERCIAL" button. The E/G lights will go out and the "COMML ON-LN" light will
illuminate, indicating that the generator is off and the ALSF-2 is on commercial power.
(4) Turn Approach Lights and Sequence Flashing Lights to the appropriate setting.
APPENDIX E
E-5
TPA 7110.6E
01/13/2011
(b) HCAA Engine Generators: Depress the emergency generator switch on the field
lighting panel. The switch lights should indicate "ON" for six and one-half minutes. The
generator will wait three and one-half minutes to be sure there is no fluctuation in commercial
power. When this time is up, the lights should blink once. The generator will then run three
more minutes for a cool-down period and shut off.
4. APPROACH LIGHTS CRITERIA. When conditions dictate, operate approach lights as
follows:
a. When the prevailing visibility is 3/4 miles or less or the RVR is 4,000 or less, operate the
ALSF-2 system. Also,
(1) As requested by the pilot.
(2) As you deem necessary if not contrary to pilot request.
b. Operate the SSALR system when the conditions in subparagraph 1 are not a factor.
c. Form 7230-4 Entries.
(1) Log entries shall be made indicating all time periods when CAT II or III minimums are
being used. This can be logged as intermittent when the weather is fluctuating above and below
RVR 2,400 for CAT II or below RVR 1,200 for CAT III.
(2) NOTAM information will be logged as appropriate.
APPENDIX E
E-6