ZHU LOA: Difference between revisions

From ZJX ARTCC SOPs
Jump to navigation Jump to search
(Created page with "== ARTCC Information == {| class="wikitable" style="width: 100%;" |+ !ARTCC Code !ARTCC Name !Effective Date |- |ZHU |Houston ARTCC |15 July 2020 |} '''Purpose:''' This agreement establishes coordination procedures and defines delegation of airspace between VATUSA Jacksonville ARTCC (ZJX) and VATUSA Houston ARTCC(ZHU). This agreement is supplemental to procedures contained within FAA Order 7110.65. '''Distribution:''' This order is distributed to all Jacksonville...")
 
No edit summary
 
(23 intermediate revisions by the same user not shown)
Line 8: Line 8:
|ZHU
|ZHU
|Houston ARTCC
|Houston ARTCC
|15 July 2020
|
|}
|}
'''Purpose:'''
This agreement establishes coordination procedures and defines delegation of airspace between VATUSA Jacksonville ARTCC (ZJX) and VATUSA Houston ARTCC(ZHU). This agreement is supplemental to procedures contained within FAA Order 7110.65.


'''PURPOSE:''' This Letter of Agreement (LOA) between Houston ARTCC (ZHU) and Jacksonville ARTCC (ZJX) covers radar handoff and intercenter coordination procedures and is supplementary to procedures contained in FAA JO 7110.65, Air Traffic Control, and other FAA directives.


'''Distribution:'''


This order is distributed to all Jacksonville and Houston ARTCC personnel.
'''CANCELLATION''': This letter of agreement cancels and supersedes the Jacksonville Air Route Traffic Control Center and Houston Air Route Traffic Control Center Letter of Agreement dated July 15, 2020.


== [[General Responsibilities]] ==
Handoffs shall be accomplished no later than 10nm from the ZJX/ZHU Boundary.<br>
It will not be necessary to coordinate inappropriate altitude for direction of flight on aircraft departing the Pensacola Terminal Area assigned an interim altitude of FL230.<br>
When using vERAM or VRC, mandatory radar handoffs suffice for coordination on aircraft climbing or descending to the altitude displayed in the data block. The altitude may be an interim altitude, or the altitude forwarded by the Controller Client. It will be the responsibility of the receiving controller to verbally impose any necessary restrictions for an aircraft for the purpose of separation, through the transferring controller. <br>
Transponder codes may be changed within 15nm of the mutual boundary without prior coordination provided both facilities are operating under EAS/ERAM. <br>


== [[Route Restrictions]] ==
'''DISCLAIMER''': The information contained herein is designed and specifically for use in a virtual air traffic control environment and is not applicable in, nor should it be referenced for, live operations in the National Airspace System (NAS).
Eastbound aircraft, from the ZHU Leeville (24) Sector, landing MCO, PIE, TPA, or DAB, must be cleared to remain north of aircraft landing MIA, FLL, FXE, or EYW.<br>
Eastbound aircraft, from the ZHU Leeville (24) Sector, landing MIA, FLL, FXE, or EYW, must be cleared to remain south of aircraft landing MCO, PIE, TPA, or DAB.<br>
Westbound aircraft filed over HRV must be cleared to remain north of aircraft filed over LEV.<br>
Westbound aircraft filed over LEV must be cleared to remain south of aircraft filed over HRV.<br>


== [[Airport Specific Restrictions to ZHU]] ==
<tabs>
<tab name="DFW">
Aircraft landing in the Dallas/Fort Worth Terminal Area must be routed on airways or a filed STAR, or direct AEX for the filed STAR.
</tab>
<tab name="Gulfport Terminal Area">
Aircraft landing the Gulfport Terminal Area must cross the common ZHU/ZJX boundary at or below FL300, descending to FL240.
</tab>
<tab name="Houston Terminal Area">
Aircraft landing the Houston Terminal Area must be routed on airways or a filed STAR and may be cleared direct no farther west than SJI, HRV, LEV, SNYDE Intersection or SHREQ Waypoint.
</tab>
<tab name="Jackson Terminal Area">
Aircraft landing in the Jackson Terminal Area must cross the ZHU/ZJX boundary level at an altitude correct for direction of flight at or below FL340, or must be routed via direct GCV..(direct destination)
</tab>
<tab name="MSY">
Aircraft landing MSY must be cleared over SJI or GPT, and issued the SLIDD STAR.
</tab>
<tab name="NEW">
Aircraft landing NEW must be cleared over SJI or GPT, and issued the SLIDD STAR.
</tab>
<tab name="New Orleans Terminal">
Aircraft landing the New Orleans Terminal Area must cross the ZHU/ZJX boundary level at an altitude correct for direction of flight at or below FL320.
</tab>
</tabs>


== [[Airport Specific Restrictions from ZHU]] ==
'''ABBREVIATIONS:'''
 
{| class="wikitable sortable"
|+
!ABBREVIATION
!MEANING
|-
|PNST
|Pensacola Terminal Area
|-
|VPST
|Meridian Terminal Area
|-
|MSYT
|New Orleans Terminal Area
|-
|GPTT
|Gulfport Terminal Area
|-
|JANT
|Jackson Terminal Area
|-
|AOB
|At or below
|}
 
 
'''COORDINATION PROCEDURES:'''
 
a. Deviations from procedures outlined in this agreement may be made only after completion of coordination, which defines responsibility in each case.
 
b. An automated radar handoff constitutes approval for aircraft climbing/descending to the altitude in the data block. Controllers are still responsible for pointouts if the aircraft will climb/descend through another controller’s stratum.
 
c. Inappropriate Altitude For Direction Of Flight (IAFDOF) must be coordinated, except for aircraft departing the Pensacola Terminal Area assigned an interim altitude of FL230.
 
d. Transponder codes may be changed without coordination on initial contact.
 
e. Aircraft routed via a STAR shall not be cleared past the transition of the arrival.
 
f. Anytime ZHU or ZJX is split, all controllers must be notified how the center is being split.
 
 
'''ARRIVALS / OVERFLIGHTS:'''
{| class="wikitable"
|+ENTERING ZJX
!TO
!QUALIFIER
!ROUTE
!RESTRICTION
|-
|PNST
|On v198, v241, or via LOXLY..PENSI
|ALL
|LOXLY at 11,000 and 250kt or less
|-
|MCO,TPA,DAB,PIE
|From ZHU sector 24 LEV, or sector 92 VOODO
|Routed to remain north of MIA, FLL, EYW, FXE traffic (Y280)
|
|-
|MIA, FLL, EYW, FXE
|From ZHU sector 24 LEV, or sector 92 VOODO
|Routed to remain south of MCO, TPA, DAB, PIE traffic (Y290)
|
|-
|CEW, VPST
|FL240+
|J2.CEW..(Direct destination)
|AOB FL240
|-
|ECP
|ALL
|V198/J2.DEFUN..CUGAR.. KECP
|AOB FL250
|}
{| class="wikitable"
|+ENTERING ZHU
!TO
!QUALIFIER
!ROUTE
!RESTRICTION
|-
|I90
|ALL
|Via airways or a STAR
|Cannot be cleared further west than SJI, HRV, LEV, SNYDE, or SHREQ
|-
|MSY, NEW, NBG
|From ZJX sector 11 BREWTON
|SJI / GPT.MNSTR# STAR
|AOB FL320
|-
|Other MSYT
|From ZJX sector 11 BREWTON
|ALL
|AOB FL320
|-
|GPTT
|From ZJX sector 11 BREWTON
|ALL
|AOB FL300 Descending FL240
|-
|JANT
|North of J50
|ALL
|Level at an altitude AOB FL340, or routed via GCV direct
|-
|HRV
|ALL
|(Y280)
|Remain north of LEV traffic
|-
|LEV
|ALL
|(Y290)
|Remain south of HRV traffic
|-
|D10
|ALL
|Via airways or a STAR
|
|}
 
== [[Micellaneous|ATTACHMENTS:]] ==
<tabs>
<tabs>
<tab name="CEW">
<tab name="Houston Center Airspace (Ultra High and High)">
Turbojet aircraft at or above FL240 landing CEW or the Eglin Terminal Area must be routed via J2.CEW..(direct destination). These aircraft must cross the ZHU/ZJX boundary at FL240.
[[File:ZHULOA11.PNG]]
</tab>
</tab>
<tab name="ECP">
<tab name="Houston Center Airspace (Low)">
Aircraft landing ECP must be routed V198/J2.DEFUN..CUGAR..ECP. These aircraft must cross the ZHU/ZJX boundary at or below FL250.
[[File:ZHULOA12.PNG]]
</tab>
</tab>
<tab name="PNS (and Satellite)">
<tab name="Jacksonville Center Airspace (High)">
Aircraft landing the Pensacola Terminal Area which are established on V198/V241, or cleared via direct LOXLY..PENSI, must cross LOXLY at 11,000 feet and 250 knots or less.
[[File:ZHULOA13.PNG]]
</tab>
</tab>
</tabs>
<tab name="Jacksonville Center Airspace (Low)">
 
[[File:ZHULOA14.PNG]]
== [[Micellaneous]] ==
<tabs>
<tab name="Micellaneous">
Deviations from procedures outlined in this agreement may be made only after completion of coordination, which defines responsibility in each case.
</tab>
</tab>
<tab name="Delegation of Airspace">
<tab name="ZJX/ZHU Ultra Low Airspace">
[[File:HOU1.JPG]]<br>
[[File:ZHULOA15.PNG]]
[[File:HOU2.JPG]]<br>
[[File:HOU3.JPG]]<br>
[[File:HOU4.JPG]]
</tab>
</tab>
<tab name="Terminal Areas and Other Airports">
<tab name="Terminal Areas and Other Airports">
[[File:HOU5.JPG]]
[[File:ZHULOA16.PNG]]
</tab>
</tab>
</tabs>
</tabs>[https://drive.google.com/file/d/1iAFJjw5lx97kT4AvTFxZI2TNzbdf3GtN/view?usp=drive_link Source Document]

Latest revision as of 23:33, 20 December 2023

ARTCC Information

ARTCC Code ARTCC Name Effective Date
ZHU Houston ARTCC

PURPOSE: This Letter of Agreement (LOA) between Houston ARTCC (ZHU) and Jacksonville ARTCC (ZJX) covers radar handoff and intercenter coordination procedures and is supplementary to procedures contained in FAA JO 7110.65, Air Traffic Control, and other FAA directives.


CANCELLATION: This letter of agreement cancels and supersedes the Jacksonville Air Route Traffic Control Center and Houston Air Route Traffic Control Center Letter of Agreement dated July 15, 2020.


DISCLAIMER: The information contained herein is designed and specifically for use in a virtual air traffic control environment and is not applicable in, nor should it be referenced for, live operations in the National Airspace System (NAS).


ABBREVIATIONS:

ABBREVIATION MEANING
PNST Pensacola Terminal Area
VPST Meridian Terminal Area
MSYT New Orleans Terminal Area
GPTT Gulfport Terminal Area
JANT Jackson Terminal Area
AOB At or below


COORDINATION PROCEDURES:

a. Deviations from procedures outlined in this agreement may be made only after completion of coordination, which defines responsibility in each case.

b. An automated radar handoff constitutes approval for aircraft climbing/descending to the altitude in the data block. Controllers are still responsible for pointouts if the aircraft will climb/descend through another controller’s stratum.

c. Inappropriate Altitude For Direction Of Flight (IAFDOF) must be coordinated, except for aircraft departing the Pensacola Terminal Area assigned an interim altitude of FL230.

d. Transponder codes may be changed without coordination on initial contact.

e. Aircraft routed via a STAR shall not be cleared past the transition of the arrival.

f. Anytime ZHU or ZJX is split, all controllers must be notified how the center is being split.


ARRIVALS / OVERFLIGHTS:

ENTERING ZJX
TO QUALIFIER ROUTE RESTRICTION
PNST On v198, v241, or via LOXLY..PENSI ALL LOXLY at 11,000 and 250kt or less
MCO,TPA,DAB,PIE From ZHU sector 24 LEV, or sector 92 VOODO Routed to remain north of MIA, FLL, EYW, FXE traffic (Y280)
MIA, FLL, EYW, FXE From ZHU sector 24 LEV, or sector 92 VOODO Routed to remain south of MCO, TPA, DAB, PIE traffic (Y290)
CEW, VPST FL240+ J2.CEW..(Direct destination) AOB FL240
ECP ALL V198/J2.DEFUN..CUGAR.. KECP AOB FL250
ENTERING ZHU
TO QUALIFIER ROUTE RESTRICTION
I90 ALL Via airways or a STAR Cannot be cleared further west than SJI, HRV, LEV, SNYDE, or SHREQ
MSY, NEW, NBG From ZJX sector 11 BREWTON SJI / GPT.MNSTR# STAR AOB FL320
Other MSYT From ZJX sector 11 BREWTON ALL AOB FL320
GPTT From ZJX sector 11 BREWTON ALL AOB FL300 Descending FL240
JANT North of J50 ALL Level at an altitude AOB FL340, or routed via GCV direct
HRV ALL (Y280) Remain north of LEV traffic
LEV ALL (Y290) Remain south of HRV traffic
D10 ALL Via airways or a STAR

ATTACHMENTS:

ZHULOA11.PNG

ZHULOA12.PNG

ZHULOA13.PNG

ZHULOA14.PNG

ZHULOA15.PNG

ZHULOA16.PNG

Source Document

Retrieved from "https://www.idszjxartcc.org/index.php?title=ZHU_LOA&oldid=1032"