Effective 7/9/2021
Revision 3.1
Changes
Rev. 3.1
Replaced HOU_APP with I90_APP as default and subsequent callsigns.
Rev.2
Comprehensive rewrite replacing existing I90 Standard Operating Procedures.
Eliminated duplication of VATUSA and VATSIM policies.
*CHAPTER 1: GENERAL*
Purpose
This document establishes and provides the standard operating procedures for the I90 TRACON.
This document is considered a supplement to any VATSIM, Executive Committee, VATNA, VATUSA, and vZHU policies, procedures, and controlled documentation.
Audience
All vZHU Controllers and Visitors
Distribution
This document is authorized for unrestricted public release.
Effective
This policy is effective immediately and cancels any previous revisions. This document cancels the I90 Terminal Radar Approach Control Standard Operating Procedures Rev 1 dated May 2.
Cancellation
This policy is effective until superseded by a newer revision or May 28, 2021.
Abbreviations
Abbreviation STARS Keyboard Symbol Meaning
M IM Departure North
R IR Tomball Satellite
W IW Departure West
P IP Lakeside Satellite
N IN West Arrival
X IX Eagle Lake Arrival
U IU College Satellite
T IT College Final
Z IZ Industry Satellite
E IE Departure East
L IL Departure South
B IB SanJac Satellite
J IJ Beaumont Satellite
D ID East Arrival
G IG Gulf Arrival
H IH Hobby Final
A IA Final North
I II Final Center
O IO Final South
MN IA Monitor Final North
MC II Monitor Final Center
MS I0 Monitor Final South
Definitions
a. The Houston Terminal Area is that area contained within the Houston TRACON airspace, excluding these satellite sectors:
1. Beaumont
2. College
3. Industry
b. The College Station Terminal Area is that area contained within these satellite sectors:
1. College
2. Industry
c. Satellite airports in the Houston Terminal Area are defined as:
1. South, if South of V222
2. North, if North of V222
d. The following terms must be used to describe IAH runway flow/status:
1. Simos – Indicates override checks are completed for the 2 specified arrival runways in use.
2. Trips – Indicates override checks are completed for the 3 specified arrival runways or specified direction of flow in use.
3. Widely-Spaced – Indicates that requirements for widely-spaced parallel approaches without monitors have been met, and are in use, for the specified direction of flow.
4. Outboards – Indicates that approaches to 26R/27 or 8L/9 are in use, verbally stated as “West” or “East”, and standard radar separation is being provided by the final controller(s)
Sectorization
West Side Common East Side
Departure North College Satellite Departure East
Departure West College Final Departure South
West Arrival Industry Satellite East Arrival
Eagle Lake Arrival Final Center Gulf Arrival
Lakeside Satellite Final North SanJac Satellite
Tomball Satellite Final South Beaumont Satellite
Monitor Final Center Hobby Final
Monitor Final North
Monitor Final South
Frequency and Position List
VATSIM CALLSIGN Radio Callsign Position Frequency
I90_M_DEP HOUSTON DEPARTURE DEPARTURE NORTH 132.250
I90_E_DEP HOUSTON DEPARTURE DEPARTURE EAST 133.600
I90_L_DEP HOUSTON DEPARTURE DEPARTURE SOUTH 127.125
I90_W_DEP HOUSTON DEPARTURE DEPARTURE WEST 126.675
I90_R_APP HOUSTON APPROACH TOMBALL SATELLITE 119.700
I90_P_APP HOUSTON APPROACH LAKESIDE SATELLITE 123.800
I90_N_APP HOUSTON APPROACH WEST ARRIVAL 124.350
I90_X_APP HOUSTON APPROACH EAGLE LAKE 119.170
I90_U_APP HOUSTON APPROACH COLLEGE SATELLITE 134.300
I90_T_APP HOUSTON APPROACH COLLEGE FINAL 127.470
I90_Z_APP HOUSTON APPROACH INDUSTRY SATELLITE 124.220
I90_B_APP HOUSTON APPROACH SANJAC SATELLITE 134.450
I90_J_APP HOUSTON APPROACH BEAUMONT SATELLITE 121.300
I90_D_APP HOUSTON APPROACH EAST ARRIVAL 120.050
I90_G_APP HOUSTON APPROACH GULF ARRIVAL 119.620
I90_H_APP HOUSTON APPROACH HOBBY FINAL 133.050
I90_FN_APP HOUSTON APPROACH FINAL NORTH 119.100
I90_FC_APP HOUSTON APPROACH FINAL CENTER 120.650
I90_FS_APP HOUSTON APPROACH FINAL SOUTH 134.000
I90_MN_APP FINAL MONITOR NORTH
I90_MC_APP FINAL MONITOR CENTER
I90_MS_APP FINAL MONITOR SOUTH
I90_D_APP is to be the first approach control position and the combined sector.
If only a single approach is expected to be on, the designation may be dropped.
AIRSPACE
*CHAPTER 2: PROCEDURES*
********************************SECTION 1: GENERAL**************************************
Control must be transferred at the time of completion of a radar handoff and frequency change as specified in JO 7110.65.
Note: Aircraft landing at IAH must be handed off and issued a frequency change prior to the lateral boundary of the receiving final controller’s airspace.
After control transfer, the receiving controller is responsible for coordination (s) affecting his/her aircraft. The receiving controller may climb departure aircraft, descend arriving aircraft, adjust airspeed, and/or make course changes of 60 degrees or less in the transferring controller’s airspace.
IAH Runway Utilization
The following preferential runway configurations must be used at IAH to the extent possible:
West Flow/Departing South.
(a) Arrivals on Runways 26L/26R/27.
(b) Departures on Runways 15L/15R/26L/26R.
West Flow/Departing North.
(a) Arrivals on Runways 26L/26R/27.
(b) Departures on Runways 33R/33L.
East Flow.
(a) Arrivals on Runways 8L/8R/9.
(b) Departures on Runways 15L/15R/8R/8L/9.
IAH Runway Flow Change Checklist
When performing an east/west flow runway change at IAH, utilize the following checklist. Items on this checklist are not necessarily sequential. Any task on this list may be delegated; however, it is the responsibility of the TRACON CIC to ensure that all items are completed.
Coordinate with TMC and TMT to determine the most advantageous time to transition from one runway configuration to another.
Note: If an arrival must land opposite direction to an East/West parallel runway, then the outboard runways must be used, unless weather or runway closures dictates otherwise.
During the hours of 0700-2200 LCL, the East/West Flow configuration should not be used unless runway changes or special circumstances dictate.
Advise I90 controllers and IAH Tower of the last aircraft to land on each runway in the old configuration and the first aircraft to land under the new configuration, then ensure IAH Tower is using transitional headings until the runway change is completed.
Ensure IAH Tower changes the ATIS to reflect the new runway configuration.
Ensure Hobby Final (H) is on the “Short Box” if landing RWY 13R prior to activating both descent areas.
Notify HOU Tower when a runway change has occurred at IAH.
Notify ZHU of the new runway configuration and the availability of dual routes or OPD’s.
Change the system area to reflect the new runway configuration.
HOU Runway Flow Change Checklist
Coordinate with HOU Tower to determine the most advantageous time to transition from one runway configuration to another.
Notify IAH Tower when a runway change has occurred at HOU.
Ensure HOU Tower changes the ATIS to reflect the new runway configuration.
Advise I90 controllers and HOU Tower of the last aircraft to land in the old configuration and the first aircraft to land under the new configuration.
DWH Runway Flow Change Checklist
Ensure the departure list is moved to Tomball Satellite (R) or Lakeside Satellite (P) as appropriate.
Notify all positions about the runway change. This notification must include the first and last aircraft of each flow.
Notify IAH Tower of new arrival flow.
Reduced Longitudinal Separation
Reduced longitudinal separation (2.5 NM) between arrivals may be applied for all east/west runways at IAH for aircraft established on the final approach course within 10 NM for the landing runway, except as prescribed in I90 O 7110.1 Chapter 8.
Authorized Approach Pairings
a. The instrument approach pairings authorized for EoR operations are:
(1) Simultaneous Independent Approaches to Widely-Spaced Parallel Runways without Final Monitors:
a. RNAV (RNP) Y RWY 26R with all RWY 27 instrument approaches.
b. RNAV (RNP) Y RWY 9 with all RWY 8L instrument approaches.
(2) Simultaneous Independent Approaches- Dual & Triple:
a. RNAV (RNP) Y RWY 26R with all RWY 26L and/or RWY 27 instrument approaches.
b. RNAV (RNP) Y RWY 9 with all RWY 8R and/or RWY 8L instrument approaches.
Mode C Altitude
Aircraft being handed off in level flight with altitude information displayed (Mode C or scratchpad) must be considered to be at their assigned altitude. Pilot reported altitude for aircraft in level flight during mode C outages must be entered in to the STARS data tag.
Airspace Configuration Changes
Any change to the airspace configuration cancels all previously coordinated procedures pertinent to that airspace configuration. If, after an airspace configuration change, nonstandard headings or other procedures are needed, they must be re-coordinated on the basis of the new airspace configuration
Approach Breakout Areas
Satellite or departure airspace, at or below 3,000 feet MSL, within the lateral confines of final airspace is for IAH departures, go-arounds, and/or breakouts only. Final controllers, Final Monitor controllers, and IAH Local controllers have control to vector breakouts within this airspace for resequencing.
Optimized Profile Descent (OPD) Operations
Aircraft that are capable of utilizing OPD procedures but have been altitude restricted must be coordinated with the receiving controller if the altitude is different than the bottom altitude on the procedure.
Altitude Restrictions for PRARI Gate Departures
10,000ft and 12,000ft must not be assigned to aircraft departing out the PRARI gate (J, P, N and Z).
Note: This restriction separates from the KIDDZ and QTRBK Arrivals.
Wake Turbulence Separation Requirements
I90 is authorized the use of Consolidated Wake Turbulence (CWT) procedures and separation minima contained in National Directives, Facility Authorization, and Letters of Agreement.
*********************************SECTION 2: EQUIPMENT********************************
Minimum Vectoring Altitudes
Wind Information
Use the METAR wind information for operational purposes.
RVR Availability
Controllers must ensure that the applicable RVR runways are displayed at their position of responsibility.
I90/BPT/CLL Altimeter
Issue the appropriate altimeter to aircraft transitioning into and out of Houston Terminal airspace, Beaumont Satellite airspace, and the College Satellite airspace.
********************************SECTION 3: CONTROL PROCEDURES********************************
Advance Approach Information
The first controller to work an aircraft that intends to land at an airport in his/her terminal area must inform the pilot of the appropriate approach/weather/airport condition information, unless the pilot states that appropriate ATIS code or indicates ASOS weather has been received.
ATIS Requirements
a. All operational positions must, upon being advised of a new ATIS code for airports within their terminal area, broadcast the information on their respective frequencies.
b. Acknowledge the new ATIS codes displayed in the STARS GI text portion of the system status area by entering the delta symbol via the STARS keyboard if utilizing the vSTARS Client.
Arrival Runway and Altitude Assignments
a. Unless otherwise stated in this order, aircraft being handed off to final controllers must be assigned 6,000 feet MSL.
b. Provide runway assignment information in the scratchpad when multiple runway options exist.
c. Place RNP in the second scratchpad of IAH arrivals that have been instructed to expect RNAV (RNP) Y approach.
d. Absent a Traffic Management Initiative (TMI), the East Arrival (D) and West Arrival (N) short-side feeders are responsible for runway balancing. Runway balancing is defined as keeping equal pressure on the available arrival runways. Gulf Arrival (G) and Eagle Lake Arrival (X) must assist East Arrival (D) and West Arrival (N) when balancing needs exist (e.g. vectors for spacing).
e. If short side feeders assign a runway that is not on a STAR transition, aircraft must be vectored. (Example: Runway 8R from the GUSHR Arrival)
f. Utilize the charts below for optimal runway assignment and altitudes related thereto. Runway assignments are listed in preferential order.
Speed Control
Aircraft being handed off to final controllers must be assigned 210 knots, or less, prior to communication transfer, unless a different speed is coordinated by the final controller. In addition, Arrival positions must not delete the STAR/OPD speeds, except to break a tie or stack.
Wharton (ARM)/Bay City (BYY) Shelf Procedures
1. All positions handing aircraft off to the Eagle Lake Low Sector destined ARM or BYY must coordinate with SANJAC, LAKESIDE, and INDUSTRY for the release of the ARM/BYY shelf prior to communications transfer to ZHU.
2. The SANJAC, LAKESIDE and INDUSTRY positions must be advised when the ARM/BYY shelf has been returned by ZHU.
3. Automated point outs may be used for coordinating the release of the ARM/BYY shelf. The STARs scratch pad must contain ARM/BYY identifying these aircraft. Acceptance of the point out grants approval for the release of the ARM/BYY shelf to Eagle Lake low.
***************************SECTION 4: STARS CONTROLLER ENTRIES***************************
Tracks
Tracks must be initiated and automated functions used to the maximum extent possible on all aircraft that are being provided approach control services. Targets that will not hold a tag must be coordinated.
Scratch Pad Information
a. Information entered in the scratch pad must be kept up to date.
Approach/Runway Information
Display in the scratch pad area, information from a and b below to indicate the type of approach and the runway to which the approach is applicable.
a. Approach Abbreviations
T - VOR Approach
C - Contact Approach
I - ILS Approach
A - Assigned Runway
N - NDB Approach
R - Requested Runway
G - GLS Approach
S - RNAV Approach
V - Visual Approach with aircraft in sight
W - Radar separated Visual with airport in sight
VA- Visual Approach to an uncontrolled airport
P- RNP Approach
b. IAH Runway Identifiers
6R = Runway 26R
8R = Runway 8R
09 = Runway 9
6L = Runway 26L
8L = Runway 8L
27 = Runway 27
5R = Runway 15R
3R = Runway 33R
5L = Runway 15L
3L = Runway 33L
Note 1 -Controllers must make these scratch pad entries as an aid to final controllers when assigning a runway other than that specified elsewhere in this order. Final controllers must ensure that the required entries are made for coordination to the Tower.
Note 2 - I90 may be used to indicate the ILS Runway 9 Approach.
Automated Point-Out Procedures
Automated point-out procedures may be used in lieu of verbal point-out procedures in accordance with FAAO 7110.65 and the following:
a. Limitations.
1. Automated point-outs must not be used without a validated Mode C.
2. Automated point-out procedures must not be used to point out aircraft to any control tower, except as per letter of agreement.
3. Automated point-outs must be initiated and completed for one position at a time.
b. The transferring controller must ensure all data block information is accurate prior to initiating an automated point-out.
The transferring controller must define the following in the Scratch Pad:
1. Route of Flight (e.g., V70, T254, etc.) or
2. Exit Fix (e.g., L34, T33, N22, etc.) or
3. Destination Airport (e.g., CLL, LCH, AUS, etc.)
4. Altitude when not included in the route of flight.
Note: Final Controllers are not required to enter altitude information in the scratch pad for aircraft landing IAH or HOU.
d. The receiving controller must evaluate the information contained in the data block and may:
1. Approve the point-out, (“SLEW”).
2. Disapprove the point-out (“U, N, SLEW”).
3. Verbally coordinate as necessary (e.g., airspace/traffic/altitude restrictions/aircraft’s route/type aircraft/, etc.).
e. After an automated point-out is approved, any change to the aircraft flight path, altitude, or data block/scratch pad must be verbally coordinated, or pointed out again via the automated process.
*CHAPTER 3: PREARRANGED COORDINATION*
***************************SECTION 1: USAGE***************************
Prearranged Coordination Procedures
a. Controllers who penetrate another controller’s airspace using P- ACP must display data block information of that controller’s aircraft which must contain, at a minimum, the position symbol and altitude information.
b. Arrival controllers must coordinate verbally, or by use of automation, with the appropriate Departure Controller(s) for all aircraft either entering or within the Houston Terminal designated prearranged airspace when their route does not follow a published STAR, PAR or other defined route.
c. Hobby Final controller must coordinate verbally, or by use of automation, with the appropriate Departure Controller(s) prior to altering any aircraft’s route that does not follow the published STAR, PAR, or other defined route.
Note: In the scratchpad, “LDW” indicates left downwind and “RDW” indicates right downwind.
Departure West P-ACP
Departure West may use P-ACP to climb aircraft departing the Houston Terminal Area.:
(a) Within the lateral limits of Departure West airspace, excluding satellite airspace.
(b) Within Eagle Lake Ar
Departure North P-ACP
Departure North may use P- ACP to climb aircraft departing the Houston Terminal Area:
(a) Within the lateral limits of Departure North airspace, excluding Satellite airspace.
(b) Within Departure West, West Arrival, and Eagle Lake Arrival airspace as depicted in Appendix 19-1 & Appendix 19-2.
Departure South P-ACP
Departure South may use P- ACP to climb aircraft departing the Houston Terminal Area:
(a) Within the lateral limits of Departure South airspace, excluding satellite airspace.
(b) Within Departure North and Gulf Arrival airspace, as depicted in Appendix 19-3 thru 19-6.
Note: When HOU is landing RWY 22 and Departure East and Departure South are open, Departure South has approval to transition through Departure East airspace with all IAH departures. Departure South has approval to climb and turn aircraft in accordance with this chapter and as depicted in Appendix 19-5.
Departure East P-ACP
Departure East may use P- ACP to climb aircraft departing the Houston Terminal Area:
(a) Within the lateral limits of Departure East airspace, excluding satellite airspace.
(b) Within Departure North airspace, as depicted in Appendix 19-7 thru 19-9.
(c) Within Departure South airspace as depicted in Appendix 19-7 and 19-9, and for left turns enroute to Departure East airspace.
Note: When Departure East and Departure South are open, Departure East has approval to transition through Departure South airspace with all IAH departures. Departure East has approval to climb and turn aircraft in accordance with this chapter and as depicted in Appendices 19-7 & 19-9.
(d) Within Gulf Arrival airspace, as depicted in Appendices 19-7 thru 19-9.
Hobby Final P-ACP
Hobby Final may use P- ACP to descend aircraft landing Hobby:
(a) Within Lakeside airspace, on the 13R final approach course from JABBS intersection, or from the boundary of the Hobby Final descent area, when HOU is landing Runway 13R/L.
(b) Within Lakeside airspace that underlies the 4,000 – 6,000 feet MSL shelf of HOU Final descent area, when HOU is landing Runway 13R/L.
(c) Within Lakeside airspace when HOU is landing Runway 4 as depicted in Appendix 19-14.
Final North P-ACP
Final North may use P- ACP:
Within Departure North airspace, in a west flow, in the area specified in Appendix 19-10.
Final South P-ACP
Final South may use P- ACP:
Within Departure South/East airspace, in a west flow, in the area specified in Appendix 19-10.
IAH Final(s) P-ACP
IAH Final(s) may use P- ACP
When IAH is in an east flow with Lakeside Satellite and Tomball Satellite airspace east of DWH Runway 17R/35L extended centerline.
SanJac Satellite P-ACP
SanJac Satellite may use P- ACP for turns only:
Within Departure South/East airspace that is within the IAH departure corridor once the satellite departure aircraft is clear of the IAH surface area airspace (this includes IAH airspace that is surface to 1,200 feet MSL).
Lakeside Satellite P-ACP
Lakeside Satellite may use P- ACP for turns only:
Within Departure West airspace, that is within the IAH departure corridor, once the satellite departure aircraft is clear of the IAH surface area airspace (this included IAH airspace that is surface to 1,200 feet MSL).
Tomball Satellite P-ACP
Tomball Satellite may use P- ACP for turns only:
Within Departure North airspace, that is within the IAH departure corridor, once the satellite departure aircraft is clear of the IAH surface area airspace (this includes IAH airspace that is surface to 1,200 feet MSL).
Beaumont Satellite P-ACP
Beaumont Satellite may use P-ACP:
Within East Arrival airspace, in an east flow, in the area specified in Appendix 19-13.
*CHAPTER 4: VFR TO IFR POP-UPS, VFR ON TOP (OTP) AND SVFR CLEARANCES *
***************************SECTION 1: HANDLING VFR TO IFR POP-UPS **************************
Flight Plan Requirements
Aircraft identification, type, destination, and fuel, must constitute an abbreviated IFR flight plan.
Local
If the aircraft will remain within I90 airspace, or if the pilot is unable to maintain VFR, issue an IFR clearance as soon as traffic conditions permit.
Point-out Requirements
Arrival controllers must coordinate with the appropriate departure controller(s) on VFR to IFR pop-up aircraft prior to entering Class B or issuing an IFR clearance in order to ensure the proper application of prearranged coordination procedures
***************************SECTION 2: LOCAL VFR ON TOP CLEARANCES**************************
OTP Requirements
Upon receipt of a local OTP request, the controller handling must:
a. Ensure the following conditions are met prior to issuing a clearance.
1. Tops are reported at or below 4,500 feet MSL.
2. The pilot has stated that he/she will cancel IFR upon reaching OTP.
b. Assign altitude of OTP/3,000 feet MSL.
c. Assign clearance limits consistent with direction of flight as follows.
1. West – BOCCK intersection.
2. North – ALIBI LOM.
3. South – VUH VORTAC.
4. East – MHF VOR/DME.
d. (If aircraft is on the ground) Obtain departure release instructions from the controller who will initially work the aircraft and issue these instructions to the pilot.
***************************SECTION 3: SVFR CLEARANCES**************************
SVFR
a. When the associated Tower is closed at GLS, SGR, CLL, CXO, and BPT Airports:
1. The satellite position must issue the SVFR clearance, and provide the release/clearance.
b. When TME Tower closes, Lakeside Satellite must issue the SVFR clearance, and provide the release/clearance.
c. When DWH Tower closes, the airspace reverts to Class G, therefore SVFR is not authorized.
*CHAPTER 5: POSITION DUTIES AND RESPONSIBILITIES *
***************************SECTION 1: DEPARTURE CONTROL**************************
DEPARTURE NORTH (M) 132.25
Departure North must:
a. Provide radar service to aircraft in airspace depicted in Appendix 1.
b. Upon completion of communications transfer from the appropriate Local Control, advise departure aircraft of radar identification and verify Mode C altitude information of aircraft received via the “quick look” function. Prior to turning departure aircraft, ensure separation exists between his/her aircraft and aircraft under control of the underlying satellite position.
c. Vector OHIIO north satellite arrivals clear of the descent area in use at IAH and hand off to Tomball Satellite.
d. Advise Tomball Satellite of any aircraft, at or below 3,000 feel MSL, other than IAH departures that will enter the Departure North surface to 5,000 feet MSL airspace.
e. Provide Class B services within the lateral boundaries of Departure North airspace from 500 feet MSL below delegated IFR altitudes to the vertical limits of Class B airspace.
DEPARTURE EAST (E) 133.6
Departure East must:
a. Provide radar service to aircraft in airspace depicted.
b. Upon completion of communications transfer from Local Control, advise departure aircraft of radar identification and verify Mode C altitude information of aircraft received via the “quick look” function. Prior to turning departure aircraft, ensure separation exists between his/her aircraft and aircraft under control of the underlying satellite position.
c. When approaches are in progress to Runway 33R at IAH, Runway 22 or 31 at HOU with IAH East flow, or Runway 22 at HOU with IAH West flow, Departure East may initially work U, H, and F departures and handoff to Departure South.
d. When departures initially enter Departure South airspace, coordinate with Departure South for adjustments to IAH departure headings.
e. Provide Class B services within the lateral boundaries of Departure East airspace from 500 feet MSL below delegated IFR altitudes to the vertical limits of Class B airspace.
DEPARTURE SOUTH (L) 127.125
Departure South must:
a. Provide radar services to aircraft in airspace depicted.
b. Upon completion of communications transfer from Local Control, advise departure aircraft of radar identification and verify Mode C altitude information of aircraft received via the “quick look” function. Prior to turning departure aircraft, ensure separation exists between his/her aircraft and aircraft under control of the underlying satellite position.
c. Initially work HOU departures assigned the ELOCO SID and SBI 270016 ADR.
d. Advise Departure East of any aircraft other than IAH departures that are within Departure South airspace within 20 DME of IAH.
e. Work inbounds from BAYYY/TKNIQ landing south satellite airports and handoff to SanJac Satellite on a heading clear of the descent area in use at HOU.
f. Provide Class B services within the lateral boundaries of Departure South airspace from 500 feet MSL below delegated IFR altitudes to the vertical limits of Class B airspace.
g. Climb HOU departures going out the TRIOS gate to 10,000 feet MSL, direct CHPEE and hand off to Departure East when IAH is on an east flow and Departure East is open.
h. Climb HOU departures going out the TRIOS gate to 11,000 feet MSL, direct CHPEE and hand off to Departure East, when IAH is on a west flow and Departure East is open.
DEPARTURE WEST (W) 126.675
Departure West must:
a. Provide radar services to aircraft in airspace depicted.
b. Upon completion of communications transfer from Local Control, advise departure aircraft of radar identification and verify Mode C altitude information of aircraft received via the “quick look” function. Prior to turning departure aircraft, ensure separation exists between his/her aircraft and aircraft under control of the underlying satellite position.
c. Provide Class B services within the lateral boundaries of Departure West airspace from 500 feet MSL below delegated IFR altitudes to the vertical limits of Class B airspace.
d. Climb South Satellite departures going out the TRIOS gate to 11,000 feet MSL on a southeast heading and hand off to Departure South, when Departure East is open.
***************************SECTION 2: ARRIVAL CONTROL**************************
EAST ARRIVAL (D) 120.05
East Arrival must:
a. Provide radar service to aircraft in airspace depicted.
b. Ensure arrivals are assigned appropriate runway transition if applicable and airspeed.
c. Hand off HOU arrivals not on an OPD to Gulf Arrival at 10,000 feet MSL, Gulf Arrival has control for descent to 8,000 feet MSL.
d. Assign HOU arrivals the appropriate runway transition, when applicable, or heading as follows:
1. HOU Runway 31L/R, to depart LUDVG/PRTCH on a 120-degree track.
2. HOU Runway 22, to depart LUDVG/PRTCH on a 150-degree track.
3. HOU Runway 13R/L, to depart IAH165019 on a 250-degree track.
4. HOU Runway 4, to depart LUDVG/PRTCH on a 170- degree track.
e. Handoff conventional arrivals destined GLS, LBX, EFD, BYY, ARM and SGR to Gulf Arrival at 10,000 feet MSL, Gulf Arrival has control for descent to 8,000 feet MSL.
Note: Aircraft on OPD’s that have been altitude restricted shall use the same procedure as conventional arrivals and coordinated with Gulf Arrival.
f. Descend and vector all other satellite arrivals to remain clear of the descent areas in use, and handoff to the appropriate controller.
g. Provide Class B service between 5,500 feet and 10,000 feet MSL within the lateral boundaries of Class B airspace within East Arrival airspace.
h. Make appropriate primary scratchpad entries as an aid to final controllers when assigning a runway other than the preferential runway as specified in the arrival charts.
i. Must coordinate with Gulf Arrival prior to assigning runway 27.
j. Ensure the correct assigned runway is entered in the Data Block (scratchpad) for aircraft landing at IAH. (Example: A6L, A27, A8R).
k. Long side feeders must APREQ pull up/pull downs with the TMU and coordinate with the other feeders.
l. Force all long side IAH arrival data blocks that are pulled up/pulled down to all appropriate departure controllers.
l. When assigning an aircraft, a RNP approach with RF legs, the aircraft must be handed off and communications transferred prior to the Final Controller’s lateral boundary.
WEST ARRIVAL (N) 124.35
West Arrival must:
a. Provide radar service to aircraft in airspace depicted.
b. Ensure arrivals are assigned the appropriate runway transition if applicable, and airspeed.
c. Provide Class B service between 5,500 feet MSL and 10,000 feet MSL, within the lateral boundaries of Class B airspace, within West Arrival airspace.
d. Make appropriate primary scratchpad entries as an aid to final controllers when assigning a runway other than the preferential runway as specified in the arrival charts.
e. Must coordinate the use of RWY 8R with Eagle Lake Arrival.
f. Ensure the correct assigned runway is entered in the Data Block (SCRATCHPAD) for aircraft landing at IAH. (Example: A6L, A27, A8R).
g. Long side feeders must APREQ pull up/pull downs with the TMU and coordinate with the other feeders.
h. Force all long side IAH arrival data blocks that are pulled up/pulled down to all appropriate departure controllers.
i. When assigning an aircraft an RNP approach with RF legs, the aircraft must be handed off and communications transferred prior to the Final Controller’s lateral boundary
EAGLE LAKE (X) 119.17
Eagle Lake Arrival must:
a. Provide radar service to aircraft in airspace depicted.
b. Ensure arrivals are assigned appropriate runway transition if applicable and airspeed.
c. When it becomes necessary to enter a downwind to HOU Runway 13R, assign the aircraft 7,000 feet MSL.
d. Provide Class B service between 5,500 feet MSL and 10,000 feet MSL, within the lateral boundaries of Class B airspace, within Eagle Lake Arrival airspace.
e. Make appropriate primary scratchpad entries as an aid to final controllers when assigning a runway other than the preferential runway as specified in the arrival charts.
f. Assign HOU arrivals the appropriate runway transition, when applicable.
g. Ensure the correct assigned runway is entered in the Data Block for aircraft landing at IAH. (Example: A6L, A27, A8R)
h. Long side feeders must APREQ pull up/pull downs with the TMU and coordinate with the other feeders.
i. Force all long side IAH arrival data blocks that are pulled up/pulled down to all appropriate departure controllers.
j. When assigning an aircraft an RNP approach with RF legs, the aircraft must be handed off and communications transferred prior to the Final Controller’s lateral boundary.
GULF ARRIVAL (G) 119.62
Gulf Arrival must:
a. Provide radar service to aircraft in airspace.
b. Ensure arrivals are assigned appropriate runway transition if applicable.
c. Handoff or point-out TKNIQ arrivals (or arrivals assigned the non-RNAV SBI..SBI260020 routing) landing south satellite airports to Departure South, at or prior to DOCCC waypoint, on a southwest heading clear of the descent area(s) in use at HOU. If Departure South accepts a point-out, hand off aircraft to SanJac Satellite and descend aircraft to an altitude 1,000 feet MSL above SanJac Satellite airspace and on a heading to remain clear of the descent area in use.
d. Handoff or point-out TKNIQ arrivals (or arrivals assigned the non-RNAV SBI..SBI260020 routing) that are landing EFD Runway 17/22, T41, RWJ, T00, and HPY to South Departure at or prior to FRDDY waypoint, descending to 6,000 feet MSL on a northerly heading clear of the descent area(s) in use.
e. Handoff GLS, LBX, EFD, BYY, ARM and SGR arrivals on the WAPPL/HUDZY arrival to Departure South at or above 8,000 feet MSL. Assign HUDZY arrivals a heading to depart LUDVG on a 170-degree track. Departure South has control for turns within Gulf Arrival airspace, but no farther east than EFD.
NOTE- When HOU is landing Runway’s 4 or 13R SGR arrivals may be coordinated with HOU Final for routing through HOU Final Airspace.
f. Work HOU arrivals from BAYYY/PUCKS/TKNIQ and assign, as applicable, the appropriate runway transition or a heading to enter the HOU descent area in use.
g. Work HOU arrivals on the CESAN STAR via the appropriate runway transition.
(Note: Piston aircraft not capable of at least 180 knots that may impede upon other high-performance aircraft may be handed off to the SanJac Position (B)).
h. Work HOU arrivals assigned the non-RNAV SBI…SBI260020 routing and assign a heading to enter the appropriate descent area in use.
i. Provide Class B service between 5,500 feet MSL and 10,000 feet MSL, as applicable, within the lateral boundaries of Class B airspace and within Gulf Arrival airspace, as depicted.
j. Make appropriate primary scratchpad entries as an aid to final controllers when assigning a runway other than the preferential runway as specified in the arrival charts.
k. Must coordinate with East Arrival prior to assigning 26L/R.
l. Ensure the correct assigned runway is entered in the Data Block (scratchpad ) for aircraft landing at IAH. (Example: A6L, A27, A8R).
m. Long side feeders must APREQ pull up/pull downs with the TMU and coordinate with the other feeders.
n. Force all long side IAH arrival data blocks that are pulled up/pulled down to all appropriate departure controllers.
n. When assigning an aircraft a RNP approach with RF legs, the aircraft must be handed off and communications transferred prior to the Final Controller’s lateral boundary.
***************************SECTION 3: SATELLITE CONTROL**************************
SANJAC SATELLITE (B) 134.45
SanJac Satellite must:
a. Provide radar service to aircraft in airspace depicted.
b. Upon completion of communications transfer from Local Control, advise departure aircraft of radar identification and verify Mode C altitude information of aircraft received via the “quick look” function. SanJac Satellite must not climb or adjust the speed of departure aircraft until clear of the IAH surface area airspace (this includes IAH airspace that is surface to 1,200 feet) or the HOU airspace.
c. Advise HOU Tower prior to releasing LVJ departures.
d. Point-out to HOU Tower aircraft that will execute an instrument approach to EFD RWY 04 and TACAN RWY 17R.
e. Provide Class B service within the lateral boundaries of Class B airspace within SanJac Satellite airspace.
f. Advise EFD of appropriate MSAW alerts
g. Advise GLS Tower, of appropriate MSAW alerts.
h. Ensure the correct assigned runway is entered in the Data Block (scratchpad 1) for aircraft landing at IAH. (Example: A6L, A27, A8R)
i. Turbojet/turboprop aircraft landing HOU, originating inside the core airspace, must be coordinated with, or handed off to, Gulf Arrival (G).
TOMBALL SATELLITE (R) 119.7
Tomball Satellite must:
a. Provide radar service to aircraft in airspace depicted.
b. Upon completion of communications transfer from Local Control, advise departure aircraft of radar identification and verify Mode C altitude information of aircraft received via the “quick look” function. Tomball Satellite must not turn, climb, or adjust the speed of departure aircraft until clear of the IAH surface area airspace (this includes IAH airspace that is surface to 1,200 feet MSL)
c. When IAH is in any flow other than an east flow, and DWH is landing Runways 17L/R, advise IAH of all approaches to Runways 35L/R.
d. Release DWH departures in accordance with the DWH SOP.
e. When IAH is on an east flow, all Non-DWH satellite traffic must be vectored to remain west of 15 DME from IAH VORTAC.
f. Unless utilizing visual separation, IFR satellite aircraft must remain west of DWH Runway 17R/35L extended runway centerline on a heading that ensures divergence from IAH straight-in arrivals when IAH is on an east flow.
g. Provide Class B service within the lateral boundaries of Class B airspace within Tomball Satellite airspace.
h. Advise DWH Tower of appropriate MSAW alerts.
i. When DWH ATCT is closed, coordinate all IFR and/or practice instrument approaches to DWH with Lakeside Satellite (P).
j. Advise CXO Tower of appropriate MSAW alerts.
k. Ensure the correct assigned runway is entered in the Data Block (scratchpad 1) for aircraft landing at IAH. (Example: A6L, A27, A8R).
COLLEGE STATION (U) 134.3
College Satellite must:
a. Provide radar service to aircraft in airspace depicted.
b. Upon completion of communications transfer from CLL Tower, radar identifies the aircraft and verifies Mode C altitude information of aircraft received via the “quick look” function.
c. Hand off aircraft that are above 5,000 feet MSL to College Final (T) prior to 10 NM from CLL, descending or level at 5,000 feet MSL.
d. Advise CLL Tower of appropriate MSAW alerts.
BEAUMONT SATELLITE (J) 121.3
Beaumont Satellite must:
a. Provide radar service to aircraft in airspace depicted.
b. Upon completion of communications transfer from BPT Tower, advise departure aircraft of radar identification and verify Mode C altitude information of aircraft received via the “quick look” function.
c. Provide TRSA service within the lateral boundaries of TRSA airspace as depicted.
d. Advise BPT Tower of appropriate MSAW alerts
e. Restrict all DEPARTURES FILED PRARI/FREEP GATE at or below 16,000 feet to 6,000 feet or below.
f. Ensure aircraft on the CESAN STAR landing HOU are assigned the appropriate runway transition.
g. Hand-off aircraft on the CESAN STAR to the appropriate sector (flow Contingent) level at, or descending to an altitude at or above 6,000 feet.
h. Turbojets/turboprops landing HOU, originating outside of the core airspace, must be handed off to Gulf Arrival (G), at or above 6,000 feet MSL.
LAKESIDE SATELLITE (P) 123.8
Lakeside Satellite must:
a. Provide radar service to aircraft in airspace depicted.
b. Upon completion of communications transfer from Local control, advise departure aircraft of radar identification and verify Mode C altitude information of aircraft received via the “quick look” function. Lakeside Satellite must not climb or adjust the speed of departure aircraft until clear of the IAH surface area airspace (this includes IAH airspace that is surface to 1,200 feet) or HOU airspace.
c. When DWH is landing Runway 35L/R, remain at or below 2,000 feet MSL while operating within the Prearranged Coordination areas, with any traffic other than IAH departures.
d. When DWH is landing Runway 35L/R and IAH is in an east flow, all IFR aircraft landing DWH must be established on a straight-in final no closer than 8 NM from the runway.
e. Release DWH departures.
f. When IAH is on an east flow, all Non-DWH satellite traffic must be vectored to remain west of 15 DME from IAH VORTAC.
g. Advise Tomball Satellite of any aircraft that are within 8 NM west of DWH at or below 2,000 feet MSL when DWH is departing runway 17L/R. (Reference departures off of DWH to Tomball Satellite that make a wide turn).
h. Unless utilizing visual separation, IFR satellite aircraft must remain west of DWH Runway 17R/35L extended runway centerline on a heading that ensures divergence from IAH straight-in arrivals, when IAH is on an east flow.
i. When DWH is landing Runways 17L/R, advise IAH of all approaches to Runway 35L/R.
j. When DWH ATCT is closed, coordinate all IFR and/or practice instrument approaches to DWH with Tomball Satellite (R).
k. Turbojet/turboprop aircraft landing HOU, originating inside the core airspace, must be coordinated with, or handed off to, Eagle Lake Arrival (X).
l. Turbojets/turboprops landing HOU, originating outside of the core airspace, must be handed off to Eagle Lake Arrival (X) at or above 6,000 feet MSL.
m. Must force the display of datablocks (i.e. “splat”), on all piston aircraft landing HOU, to Eagle Lake Arrival (X) and Gulf Arrival (G).
n. Provide Class B service within the lateral boundaries of Class B airspace within Lakeside Satellite airspace
o. Advise SGR, TME, and DWH of appropriate MSAW alerts.
p. Ensure the correct assigned runway is entered in the Data Block (scratchpad) for aircraft landing at IAH. (Example: A6L, A27, A8R).
INDUSTRY SATELLITE (Z) 124.22
Industry Satellite must:
a. Provide radar service to aircraft in airspace depicted.
b. Ensure WHAEL arrivals cross WHAEL at or below 8000 feet MSL or the arrival must be pointed out to ZHU Industry Low sector.
***************************SECTION 4: FINAL CONTROL**************************
HOBBY FINAL (H) 133.05
Hobby Final must:
a. Provide radar service to aircraft in airspace depicted.
b. Advise HOU Tower, of appropriate MSAW alerts.
c. Provide Class B service within the lateral boundaries of Class B airspace within Hobby Final airspace.
COLLEGE FINAL (T) 127.47
College Final must:
a. College Final must provide radar service to aircraft in airspace depicted.
b. Advise CLL Tower of appropriate MSAW alerts.
FINAL NORTH (FN) 127.47
FINAL CENTER (FC) 120.65
FINAL SOUTH (FS) 134.0
Final Control Must:
a. Provide radar service to aircraft in delegated airspace as depicted. When approaches are being made to the east/west parallel runways and it becomes necessary to subdivide responsibilities between two or more controllers, the airspace division must be a line in the No Transgression Zone equidistant from the adjacent runway(s). When only the outboard runways are in use, the centerline of the middle runway becomes the airspace division line.
b. Transfer communications to the appropriate IAH tower frequency once the aircraft has been cleared for an approach and:
1. Before monitoring responsibilities begin during simultaneous independent approaches.
2. Between SKLER and DRKAR (Rwy 26R) or HOWLN and TEXXN (Rwy 9) for RNP Y approaches utilizing RF legs during simultaneous independent approaches.
NOTE: Monitoring responsibilities begin at DRKAR (RWY 26R) and TEXXN (Rwy 9) for RNP Y approaches utilizing RF legs during simultaneous independent approaches.
3. At or prior to the Final Approach Fix during all other approaches.
c. When more than one final is open, display visual approach box, inner, duals, or trips bar map(s) as depicted in Appendix A-17, as appropriate.
d. Turn base leg at or less than 210 knots.
e. When three final positions are open for IAH:
1. Ensure arrival aircraft data tags are associated with the final position normally assigned to each east/west runway.
Final North (A) = Runway 8L/26R
Final Center (I) = Runway 8R/26L
Final South (O) = Runway 9/27
2. Provide no less than 3 NM in-trail spacing and compatible speed behind a preceding aircraft at the runway threshold for Runway 26L. Additional spacing may be required for weather, construction, or departure volume (traffic management initiative).
f. Ensure that the required runway scratchpad entries are made.
g. Advise IAH Tower, of appropriate MSAW alerts.
h. When Runway 8L or Runway 8R and 27 are in use:
1. One final must vector aircraft to Runway 8L or Runway 8R.
2. One final must vector aircraft to Runway 27.
i. When simultaneous widely spaced parallel approaches without monitors, dual parallel, dual simultaneous, triple simultaneous, and visual approaches are being conducted with more than one final open, use the following altitudes:
Note - Altitudes do not apply for aircraft executing Established on RNP (EoR) approaches to RWY 26R or RWY 09.
FINAL: VISUAL APPROACHES
While conducting visual approaches:
1. Instruct aircraft assigned Runways 8L/8R/9 to cross FLIBZ/EELPO/SAYNO at or above 3,000 feet MSL. Final(s) must utilize P- ACP with Lakeside Satellite and Tomball Satellite airspace east of DWH Runway 17R/35L extended centerline/final approach course.
2. Provide no less than 2 NM in-trail spacing and compatible speed behind a preceding aircraft at the landing threshold. Additional spacing may be required for weather, construction, or departure volume (traffic management initiative).
3. ensure aircraft enter and join the final at the appropriate zone altitude when more than one final is open. Aircraft must be cleared for an approach prior to the inner, duals, or trips bars as appropriate. This is dependent upon procedures/runways in use (i.e. simuls, trips, or widely spaced).
4. The final controller for runways 26R or 9 may enter Zone C at 3,000’, with downwind aircraft, provided that prior to entering the visual approach box, the aircraft is issued a visual approach clearance and a heading to intercept the final approach course on a track not to exceed 20 degrees.
FINAL: WEST FLOW
1. West Arrival Flow:
(c) Runway 26L/27.
i. Straight-in traffic to Runway 26L must be routed to enter zone A at or above 7,000 feet MSL or zone B at or above 5,000 feet MSL. Downwind traffic must be routed to enter zones A or B at or above 5,000 feet MSL.
ii. All traffic to Runway 27 must be routed to enter zone A or B at or below 4,000 feet MSL, or enter zone C at 2,000 feet MSL.
(d) Runway 26R/26L.
i. All traffic to Runway 26R must be routed to enter zones A or B at or below 4,000 feet MSL, or enter zone C at 2,000 feet MSL.
ii. Straight-in traffic to Runway 26L must be routed to enter zone A at or above 6,000 feet MSL, or zone B at or above 5,000 feet MSL. Downwind traffic must be routed to enter zones A or B at or above 5,000 feet MSL.
(c) Runway 26R/27.
i. All traffic to Runway 26R must be routed to enter zone A at or above 5,000 feet MSL.
ii. All traffic to Runway 27 must be routed to enter zone A at or below 4,000 feet MSL, or enter zone B at or below 3,000 feet MSL, or enter zone C at or below 2,000 feet MSL.
NOTE - Aircraft landing 26R may enter zone B at or above 5,000 feet MSL if instructed in the approach clearance to cross RAIDS intersection at or above 5.000 feet MSL
(d) Runway 26R/26L/27.
i. All traffic to Runway 26R must be routed to enter zone A at 5,000 to 6,000 feet MSL.
ii. All traffic to Runway 26L must be routed to enter zone A at or above 7,000 feet MSL.
iii. All traffic to Runway 27 must be routed to enter zone A at or below 4,000 feet MSL, or enter zone B at or below 3,000 feet MSL, or enter zone C at or below 2,000 feet MSL.
FINAL: EAST FLOW
2. East Arrival Flow:
(a) Runway 8L/8R.
i. All traffic to Runway 8L must be routed to enter zones A or B at or below 4,000 feet MSL, or enter zone C at 3,000 feet MSL.
ii. Straight-in traffic to Runway 8R must be routed to enter zone A at or above 6,000 feet MSL, or zone B at or above 5,000 feet MSL. Downwind traffic must be routed to enter zones A or B at or above 5,000 feet MSL.
(b) Runway 8R/9.
i. Straight-in traffic to Runway 8R must be routed to enter zone A at or above 6,000 feet MSL, or zone B at or above 5,000 feet MSL. Downwind traffic must be routed to enter zones A or B at or above 5,000 feet MSL.
ii. All traffic to Runway 9 must be routed to enter zones A or B at or below 4,000 feet MSL, or enter zone C at 3,000 feet MSL.
(c) Runway 8L/9.
i. All traffic to Runway 8L must be routed to enter zone A at or below 4,000 feet MSL, or enter zones B or C at 3,000 feet MSL.
ii. All traffic to Runway 9 must be routed to enter zone A at or above 5,000 feet MSL.
NOTE - Aircraft landing RWY 9 may enter zone B at or above 5,000 feet MSL if instructed in the approach clearance to cross MEDIC intersection at or above 5,000 feet MSL.
(d) Runway 8L/8R/9.
i. All traffic to Runway 8L must be routed to enter zone A at or below 4,000 feet MSL, or enter zones B or C at 3,000 feet MSL.
ii. All traffic to Runway 8R must be routed to enter zone A at or above 7,000 feet MSL.
iii. All traffic to Runway 9 must be routed to enter zone A at 5,000 to 6,000 feet MSL.