MIAMI ARTC CENTER AND JACKSONVILLE ARTC CENTER LETTER OF AGREEMENT

Similar documents
ATLANTA ARTC CENTER AND CHARLOTTE TOWER LETTER OF AGREEMENT

ZTL ARTCC / CLT ATCT LETTER OF AGREEMENT. EFFECTIVE: July 10, SUBJECT: APPROACH CONTROL SERVICE

Letter of Agreement by and between Jacksonville ARTCC and Miami ARTCC

NATIONAL BUSINESS AVIATION ASSOCIATION (NBAA) CONVENTION

JACKSONVILLE CENTER AND SAVANNAH TRACON. LETTER OF AGREEMENT EFFECTIVE: December 22, 2006

NATIONAL BUSINESS AVIATION ASSOCIATION (NBAA) CONVENTION

VATUSA PHOENIX TRACON and VATUSA PHOENIX ATCT LETTER OF AGREEMENT. SUBJECT: Interfacility Coordination Procedures

Jacksonville ARTCC. F11 TRACON Standard Operating Procedures

LETTER OF AGREEMENT 1. PURPOSE: 2. Cancellation: 3. vzdc Responsibilities, Arrivals: CAE MYR: FLO: CLT: 4. vzjx Responsibilities, Arrivals: RDU: FAY

VATUSA CHICAGO ARTCC AND VATUSA MINNEAPOLIS ARTCC LETTER OF AGREEMENT

VATUSA CHICAGO ARTCC AND VATUSA INDIANAPOLIS ARTCC LETTER OF AGREEMENT EFFECTIVE: 01/01/2017 SUBJECT: INTERFACILITY COORDINATION

Virtual Jacksonville Air Route Traffic Control Center Orlando International ATCT Standard Operating Procedures

ATLANTA ARTC CENTER AND JACKSONVILLE ARTC CENTER LETTER OF AGREEMENT

Virtual Jacksonville Air Route Traffic Control Center Daytona Beach ATCT Standard Operating Procedures

VATUSA C90 TRACON AND O HARE ATCT LETTER OF AGREEMENT

VATUSA CHICAGO ARTCC AND VATUSA INDIANAPOLIS ARTCC LETTER OF AGREEMENT EFFECTIVE: 10/15/2018 SUBJECT: INTERFACILITY COORDINATION

NAME ALTERNATE MINIMUMS NAME ALTERNATE MINIMUMS INSTRUMENT APPROACH PROCEDURE CHARTS IFR ALTERNATE AIRPORT MINIMUMS

VATUSA CHICAGO ARTCC AND C90 TRACON LETTER OF AGREEMENT

Letter of Agreement (LOA)

Letter of Agreement. Between Jacksonville ARTCC and Virtual United States Navy Effective Date: Sept 1, 2008

11/21/2008 ZDC-ZTL LOA Version 1. Letter of Agreement

VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT

ATM REGIONAL CONTINGENCY PLAN FOR.. CTA/UTA/FIR

CHAPTER 5 SEPARATION METHODS AND MINIMA

FEDERAL AVIATION ADMINISTRATION CENTRAL EN ROUTE AND OCEANIC AREA OPERATIONS FORT WORTH ARTC CENTER, MAJORS ATCT, AND SKYDIVE TANDEM GREENVILLE, LLC

Providence ATCT Standard Operating Procedures

Jacksonville ARTCC. En Route Standard Operating Procedures

Any queries about the content of the attached document should be addressed to: ICAO EUR/NAT Office:

TABLE OF CONTENTS. Florida Department of Transportation Analysis of Scheduled Air Service in Florida

AERONAUTICAL INFORMATION CIRCULAR

SPECIAL PROCEDURES FOR IN-FLIGHT CONTINGENCIES IN OCEANIC AIRSPACE OF SEYCHELLES FIR

Virtual Jacksonville Air Route Traffic Control Center Tallahassee ATCT Standard Operating Procedures

GOVERNMENT OF INDIA OFFICE OF DIRECTOR GENERAL OF CIVIL AVIATION

VATUSA-VATNZ-VATPAC OCEANIC PARTNERSHIP OAKLAND OCEANIC FSS GENERAL SOP 1 OCT 2012

Revised Routes Between Miami ARTC Center and Havana Area Control Center

ERIE ATCT STANDARD OPERATING PROCEDURES

RELEASE RECORD. Version Date Author Notes Dec 2006 SK Initial Release

Official Journal of the European Union L 186/27

1.2 An Approach Control Unit Shall Provide the following services: c) Alerting Service and assistance to organizations involved in SAR Actions;

- Updated formatting - Re-drawn airspace delegation diagram

Southern California Terminal Radar Approach Control and Ontario Airport Traffic Control Tower

RALEIGH-DURHAM ATCT/TRACON STANDARD OPERATING PROCEDURES

CLEARANCE INSTRUCTION READ BACK

MASTERS GOLF TOURNAMENT

Albany ATCT Standard Operating Procedures

Southern California TRACON and Lindbergh Tower LETTER OF AGREEMENT SUBJECT: INTER-FACILITY COORDINATION AND CONTROL PROCEDURES

FRENCH GUIANA ATM CONTINGENCY PLAN FOR ROCHAMBEAU FIR

International Civil Aviation Organization COMMON FORMAT LOA BETWEEN ATS UNITS. (Presented by United Arab Emirates) SUMMARY

Date: 01 Jun 2018 Time: 0959Z Position: 5121N 00048W Location: 6nm N Farnborough

BOSTON ARTCC (vzbw) STANDARD OPERATING PROCEDURE KALB) ALBANY APPROACH (ALB

ATLANTA ARTCC AND JACKSONVILLE ARTCC LETTER OF AGREEMENT. SUBJECT: INTERFACILITY COORDINATION EFFECTIVE: January 23, 2019

Burlington ATCT Standard Operating Procedures

VIRTUAL AIR TRAFFIC SIMULATION NETWORK UNITED STATES DIVISION. SUBJ: Phoenix (PHX) Air Traffic Control Tower (ATCT) Standard Operating Procedures

VERO BEACH VRB Chan 120 N W L-23-24, H-8 PHORD N W

Greenville Spartanburg International

Chapter 6. Airports Authority of India Manual of Air Traffic Services Part 1

Piedmont Triad International Airport

SID/STAR phraseology FAQ Canadian implementation April 27, 2017

2 Purpose and Need. 2.1 The Need for the CLT OAPM Project Description of the Problem

GENERAL REPORT. Reduced Lateral Separation Minima RLatSM Phase 2. RLatSM Phase 3

This Bulletin may be updated, as necessary, as progress is made toward the start date for Phase 2b of the NAT DLM.

SEATTLE AIR ROUTE TRAFFIC CONTROL CENTER SEATTLE GLIDER COUNCIL LETTER OF AGREEMENT. EFFECTIVE: June 1, 2015

ENR 1.1 GEN. RULES (Insert para 13 in ENR 1.1 of AIP India as follows)

LETTER OF AGREEMENT. Between. and RELATING TO

Chapter 6. Brize Radar, Speedbird 213 Heavy, request radar advisory. Speedbird 123 change call sign to BA 123

IFR SEPARATION WITHOUT RADAR

South Florida Customer Advisory Group: Quarterly Meeting. Federal Aviation Administration

Charlotte - Douglas International Airport Traffic Control Tower

Denver ARTCC Colorado Springs ATCT & TRACON STANDARD OPERATING PROCEDURES

Cleveland ARTCC and Boston Virtual ARTCC Letter of Agreement

EFFECTIVE NOTAM KOUN SPECIAL FLIGHT PROCEDURES 09/08 NORMAN, OK

Understanding Role of Flight Data Processing Across NAS Operational Domains

Oakland Air Route Traffic Control Center, Northern California Terminal Radar Approach Control, and Pacific Soaring Council LETTER OF AGREEMENT

Traffic Flow Management

MASTERS GOLF TOURNAMENT AUGUSTA, GEORGIA APRIL 7 15, 2019

SECTION 6 - SEPARATION STANDARDS

Pilot RVSM Training Guidance Material

USE OF RADAR IN THE APPROACH CONTROL SERVICE

KTPF PETER O. KNIGHT AIRPORT TAMPA, FL 10/27 NOTAM SPECIAL FLIGHT PROCEDURES EFFECTIVE

LETTER OF AGREEMENT. Between

c) Advisory service to IFR flights operating within advisory airspace.

International Civil Aviation Organization REVIEW OF STATE CONTINGENCY PLANNING REQUIREMENTS. (Presented by the Secretariat) SUMMARY

OPERATIONS MANUAL PART A

SECTION 4 - APPROACH CONTROL PROCEDURES

Chapter 6. Nonradar. Section 1. General DISTANCE

EFFECTIVE NOTAM KGON 10/06 SPECIAL FLIGHT PROCEDURES GROTON, CT

GENERAL OPERATING PROCEDURES FINLAND(GOP)

REPUBLIC OF KAZAKHSTAN

Section 5. Radar Separation

INTERNATIONAL CIVIL AVIATION ORGANIZATION FOURTH MEETING OF DIRECTORS OF CIVIL AVIATION OF THE CENTRAL CARIBBEAN

9/23/2010 RDU B. Raleigh-Durham Air Traffic Control Tower. Standard Operating Procedures

Version O January 21, 2019

VIRTUAL AIR TRAFFIC SIMULATION NETWORK NORTH AMERICA REGION - USA DIVISION vzkc KANSAS CITY ARTCC

CHAPTER 6 FLIGHT FOLLOWING

NBAA Making Traffic Flow Management Work for You The Basics of Operating in the National Airspace System (NAS)

Reliever Airports: NOISE ABATEMENT PLAN Flying Cloud Airport (FCM)


THE AREA CONTROL CENTRE (CTR) POSITION

D01 TERMINAL RADAR APPROACH CONTROL

LETTER OF AGREEMENT. between. and

Transcription:

MIAMI ARTC CENTER AND JACKSONVILLE ARTC CENTER LETTER OF AGREEMENT SUBJECT: INTER-CENTER PROCEDURES EFFECTIVE: 07/24/2014 1 PURPOSE. This agreement establishes Inter-facility procedures between Miami ARTC Center (ZMA) and Jacksonville ARTC Center (ZJX) and is supplementary to the procedures contained in the Air Traffic Control Handbook. 2 CANCELLATION: Miami ARTC Center and Jacksonville ARTC Center Letter of Agreement, Subject: INTER-CENTER PROCEDURES, Effective May 2, 2013. 3 RESPONSIBILITIES. This agreement covers coordination procedures, route and altitude assignments, delegation of airspace, and coordination/notification procedures for special use airspace. 4 PROCEDURES. 4.1 GENERAL 4.1.1 Aircraft on or east of J53/J81/V267 must be cleared northbound at ODD altitudes and southbound at EVEN altitudes. Aircraft on routes west of J53/J81/V267 must be cleared northbound at EVEN altitudes and southbound at ODD altitudes. 4.1.1.1 Aircraft transitioning between the ZEPHYR/MAYO/DARBS and CIGAR sectors may be delivered at any altitude. The receiving controller must initiate coordination for required altitude changes. 4.1.1.2 Aircraft transitioning North and South between the NEPTA and CIGAR sectors may be delivered at any altitude. The receiving controller must initiate coordination for required altitude changes. 4.1.2 Altitude Procedures 4.1.2.1 Interim altitude use is authorized between both facilities. 4.1.2.2 Use of an interim or assigned altitude must be considered valid coordination. Acceptance of a radar handoff constitutes approval for aircraft to be climbing, descending or level at the altitude passed in the data block. Note: The intent of this paragraph is not to supersede required altitudes specified within this letter. It merely gives the ability to use automated coordination,

including Interim Altitudes, in lieu of verbal coordination when compliance isn t possible. 4.1.3 Aircraft which are transitioning to the KEYSTONE Sector (FL350 and ), which have been pointed-out to the GREEN COVE Sector (FL240-260), underneath the ZMA Center delegated airspace, must not require further coordination with the GREEN COVE Sector, if the aircraft re-enters GREEN COVE airspace north of the ORL VORTAC (FL240-FL340), when climbing to requested altitude, unless ZMA Center initiates a change (e.g., altitude, speed, heading, etc.) 4.1.4 Multi-Center Advanced Navigation Routes are supplemental to routing requirements established in this Letter. 4.2 NORTHBOUND 4.2.1 Atlantic Overwater Routes Sector Route(s) Restrictions Filed AR3 AOB FL240 Established on the airway prior to Center boundary Filed AR3 AOA FL250 Direct ILM / Direct PANAL..DIW / AR3 Torry/ Filed over ILM or DIW Knemo (Except via NUCAR) AR16/AR18/AR23/AR24 M201 AOA FL310 Direct HANRI / AR18..M201 / AR3..M201 M202 Established on the airway at or prior to UKOKA. ZMA must add UKOKA estimate & MACH speed in 4 th line. 4.2.1.1 Aircraft filing over RIC/TYI/FAK via Atlantic Overwater routes must be cleared and routed over ILM. 4.2.1.2 Aircraft filing over ORF/J174 via Atlantic Overwater routes must be cleared and routed over DIW. 4.2.1.3 ZMA may clear aircraft direct ILM/DIW from ADOOR sector on or east of AR18. 4.2.1.4 ZMA ADOOR sector must ensure traffic cleared direct JAINS/HANRI are not in conflict with northbound traffic from the NUCAR sector. 4.2.1.4.1 ZJX must accept direct routings to JAINS, HANRI, METTA or SPIKY. 4.2.1.5 TORRY/KNEMO sector have control for speed change, beacon code change, and turns 30 degrees either direction 20 NM south of the ZMA/ZJX boundary. 2 Revision One Effective January 8, 2015

4.2.2 Overland Routes Sector Route(s) Restrictions J53 Established on airway prior to Center boundary. J81 Established on airway prior to Center boundary. J113 At or FL330. Established on airway prior to Center boundary. Green Cove Springs Keystone ORL.POGIE STAR ORL..HAINY.QUBEN STAR Direct CRG Direct VQQ Direct ORL Direct BARBS J53 J81 J113 Direct CRG Direct BARBS Direct VQQ Landing JAX/CRG/NIP/NRB/VQQ Landing JAX only At or FL330 on or west of J113 for R-NAV or advanced navigation aircraft only, or RSW complex departures west of J53. Only from within the lateral confines of BOYEL sector. Established on airway prior to Center boundary. Established on airway prior to Center boundary. At or FL350. Established on airway prior to Center boundary. At or FL350 on or west of J113 for R-NAV or advanced navigation aircraft only, or RSW complex departures west of J53. Only from within the lateral confines of BOYEL sector. St. Johns Via OMN J53 V267 Direct ORL Darbs Heading 350 Cedar Key LAL.J73 SMELZ.Q106 KPASA.Q110 / Q118 LAL..SZW LAL..CTY LAL.V7.CTY LAL.V521.CTY Direct GNV At or FL370 from within APOLO sector. COF/MLB/TTS departures shall join south of KIZER. COF/MLB/TTS departures shall join south of KIZER. At or FL230. Between PIE VORTAC and the PIE270008. Assigned heading 350 or SRKUS SID. ** Landing GNV only 3

Mayo/ Zephyr Route(s) J55/J85.INPIN.J91.CTY LAL Direct TAY Direct JOHNN LAL.J73 LAL..FAGAN..TAY Direct CTY Direct SZW SMELZ.Q106 KPASA.Q110 / Q118 Direct TEPEE Over or west of HILTI Restrictions Heading to join J91 south of CTY is acceptable. At or FL380 Filed LAL..CTY.J91 ATL and at or FL380 Filed J75 after TAY must be routed over ORL. Zephyr - Between LAL VORTAC and J20 Mayo Between LAL and WEST of INPIN Zephyr - Between LAL VORTAC and J20 Mayo Between LAL and WEST of INPIN Originating south of Miami Terminal area, at or FL360 APF/MKY departures at or FL360. ** If Heading is assigned to aircraft filed via the SRKUS SID it must be coordinated with DARBS 4.2.2.1 With the exception of COF Complex departures, J20/V159/V295 are not available north of ORL. 4.2.2.2 ZJX will accept parallel traffic entering the GREEN COVE/KEYSTONE sector, at or FL330, if traffic whose flight plan routing remains on or west of J53/J81 is on the west side, and traffic whose flight plan routing is on or east of J51/J121/J174 is on the east side. 4.2.2.3 TPA and RSW complex departures filed to ATL requesting at or FL180 must be cleared via the appropriate STAR. 4.2.2.4 FMY/RSW/APF/MKY departures filed to "Northeast" airports must be routed over ORL. 4.2.2.5 FMY/RSW/PGD departures over LAL/SMELZ/KPASA requesting FL340, must be assigned FL340. ZJX has control for climb to FL350 25 NM south of the LAL VORTAC, within the AVON Sector. 4.2.2.5.1 The CEDAR KEY sector is responsible for subsequent point outs to OCALA and DARBS sectors on all FMY/RSW/PGD departures west of INPIN. 4.2.2.6 SRQ/VNC departures requesting FL200, must be assigned FL200. ZJX has control for turns up to 20 degrees either direction and climb to FL260, 20 NM south of the PIE VORTAC. ZJX will be responsible for point outs to ZJX Sectors as a result of the turn. 4

4.2.2.7 OCF landing traffic must be delivered via ORL or TPA Approach. 4.2.2.8 GNV landing traffic must cross the Center boundary at or FL260. 4.2.2.9 JAX/CRG/NIP/NRB/VQQ landing traffic must cross 15 miles north of the ORL VORTAC at or FL270. Green Cove sector has control for turns up to 30 degrees to the west, north of the ORL VORTAC. 4.2.2.10 SGJ arrivals must cross the Center boundary at or FL230. 4.2.2.11 SSI/BQK landers must cross the Center boundary at or FL290. 4.2.2.12 Keystone sector has control on aircraft overflying OMN for speed change and turns up to 30 degrees, 30 miles south of the Center boundary from within the APOLO sector. ZJX will be responsible for point outs as a result of any turns issued by them. 4.3 SOUTHBOUND 4.3.1 Atlantic Overwater Routes DESTINATION FLL/FXE/HWO/OPF/PMP ROUTE AR21.CRANS.FISEL-STAR or AR21.CRANS..HIILL..FATHR..GISSH-STAR PBI BCT MIA/ TMB/ HST/ 07FA/ X51 MCO/SFB/ORL/ISM VRB/FPR/MLB/COF/SUA TPA/PIE RSW/FMY APF/ MKY OVERFLIGHTS OVER TADPO/MTH/CANOA OVERFLIGHTS OVER ZFP/URSUS AR19.AYBID.FRWAY-STAR or AR19.AYBID..MIMMI..NEUBE..SWOMP.. SANZZ..CASKI AR19.AYBID.CAYSL-STAR or AR19.AYBID..MIMMI..NEUBE..SWOMP.. SANZZ..CAYSL AR22.JORAY.HILEY-STAR or AR22.JORAY..OSOGY..ENVOY..YOSSI.. MILSY..BOYUR..HILEY..KAINS AR15.HIBAC.CWRLD-STAR AR15.HIBAC AR15.ORL.LZARD/DADES-STAR AR15.HIBAC.SHFTY-STAR AR17.VKZ or direct MTH AR23/AR24/AR3 4.3.1.1 HOBEE/APOLO must accept direct routings from TORRY/KNEMO Sector, direct to DULEE/MAJIK/HOAGG without FDP revision. 4.3.1.2 HOBEE/APOLO must accept direct routings from TORRY/KNEMO sector, 5 Revision One Effective January 8, 2015

direct to HIBAC from on or west of AR22 without FDP revision. 4.3.1.3 HOBEE, APOLO, NUCAR and ADOOR sectors have control for speed change, beacon code change, and turns 30 degrees either direction 20 NM north of the ZMA/ZJX boundary. 4.3.1.4 ADOOR must accept direct routings on aircraft on or east of AR23 to URSUS, ZFP (overflights), RAPPS (MYGF landing aircraft), NUCAR, ENAMO, HANKX, ANGLL with FDP revisions. 4.3.1.5 All aircraft transitioning to ZMA NUCAR sector from ZJX via the TORRY/KNEMO sectors must be established on AR3/G446 prior to the receiving facility s boundary. 4.3.1.6 When weather or Special Use Airspace closes the MALET ATA: 4.3.1.6.1 Aircraft on M202 will be accepted. 4.3.1.6.2 Aircraft south of ILM at the time of the closure will be accepted by ZMA. 4.3.2 East Coast Routes DESTINATION AIRCRAFT TYPE ROUTE FLL/FXE/HWO/ OMN.FISEL-STAR Turbojets OPF/PMP OMN.GISSH-STAR MLB.BLUFI-STAR FLL/FXE/HWO/ Turboprops LEBUR.BLUFI- OPF/PMP STAR Turbojets/ OMN.FRWAY-STAR PBI/06FA/LNA Turboprops OMN.TUXXI-STAR F45 All TRV.. BCT PBI/06FA/ BCT/LNA SUA FPR TTS VRB Turbojets/ Turboprops Props All All Tactical All OMN.CAYSL-STAR OMN.TUXXI-STAR V3.TRV.. OMN or east direct TUXXI ORL..TUXXI OMN or east direct TRV/FPR ORL Filed via SCOBE STAR OMN or east direct ORL 6 RESTRICTION Cross Center boundary AOB FL360 Cross Center boundary AOB FL300 Cross Center boundary AOB FL360 AOB FL220 AOB FL220 AOB FL220 AOB FL220 AOB FL220 Props and Turboprops via ZJX/ MCO LOA Turbojets Cross Center boundary at or FL220 AOB FL220 Revision One Effective January 8, 2015

DESTINATION MIA/ TMB/ HST/ 07FA/ X51 MIA/ TMB/ HST/ 07FA/ X51 AIRCRAFT TYPE Turbojets Turboprops ROUTE OMN.HILEY-STAR OMN.ANNEY-STAR OMN.HILEY-STAR OMN.ANNEY-STAR MLB.BLUFI-STAR Overflights All OMN..TRV..MTH RESTRICTION Overflying TADPO / MTH / CANOA via OMN 4.3.2.1 ZMA will accept direct routings, filed over OMN, direct PCMAN, DIINO, FILBE, TRV (overflights only), without FDP revisions. 4.3.2.2 ZJX will not clear aircraft filed Y585 direct farther southeast than ATTIK. 4.3.2.3 ZMA has control for speed change and turns to the east on southbound aircraft, on or east of J79, south of the OMN VORTAC. 4.3.2.4 ZMA will accept direct routings, filed over OMN, direct URSUS, ZFP (overflights only), and ZIN, at FL240 or with FDP revisions. 4.3.3 West Coast Routes DESTINATION FLL/FXE/ HWO/PMP/OPF* *OPF Turboprops/Props only AIRCRAFT TYPE Turbojets/ Turboprops *All *Turboprops/ Props *All JINGL-STAR ROUTE ALTITUDE RESTRICTION BALKE..RXXAN..RSW.FORT L-STAR PIE.FORTL-STAR LAL.V511.NEWER LAL..RSW..FORTL. JINGL- STAR LAL..RSW.FORTL- STAR FL130 and FL130 and FL130 and FL120 and FL230 and Advanced RNAV PTP Unable RNAV/PTP routing GNV departures and south only 7 Revision One Effective January 8, 2015

DESTINATION PBI/F45/06FA/LNA/ SUA AIRCRAFT TYPE Turbojets/ Turboprops All WLACE-STAR ROUTE ALTITUDE RESTRICTION FL240 and only Advanced RNAV Cross Center boundary AOB FL350 PIE..SRQ.WLACE-STAR FL130-FL230 Advanced RNAV MOLIE..RSTAA.. WLACE..PHK..PBI FL240 and only PTP Cross Center boundary AOB FL350 PIE..SRQ..PGD..PHK..PBI AOB FL350 Unable RNAV/PTP routing Turboprops/ Props LAL..PHK..PBI. FL120 and All LAL..RSTAA WLACE STAR LAL..RSW..PHK..PBI FL230 and GNV departures and south only Turbojets/ Turboprops PRRIE-STAR FL240 and only Advanced RNAV Cross Center boundary AOB FL350 PIE..SRQ.PRRIE-STAR FL130-FL230 Advanced RNAV BCT All MOLIE..RSTAA.. WLACE..PRRIE..TARTY..BCT FL240 and only PTP Cross Center boundary AOB FL350 PIE..SRQ..PGD..PHK.. PBI..BCT AOB FL350 Unable RNAV/PTP routing Turboprops/ Props All LAL..PHK..PBI..BCT LAL..RSTAA PRRIE-STAR LAL..RSW..PHK..PBI..BCT FL120 and FL230 and GNV departures and south only ORL/MCO/ISM Turbojets PIE.MINEE-STAR. PIE.COSTR-STAR FL130 and Cross PIE AOB FL210 TTS Tactical SCOBE STAR Tactical Turbojets FILED via SCOBE Arrival. SZW transition Cross Center boundary at or FL220. 8

DESTINATION AIRCRAFT TYPE *Turbojets/ Turboprops SSCOT-STAR JUULI..BAARY.CYY. CYY-STAR PIE.CYY-STAR ROUTE ALTITUDE RESTRICTION FL130 and FL130 and FL130 and Advanced RNAV PTP Unable RNAV/PTP routing MIA/ TMB/ HST/ X51/ 07FA OPF* Turboprops/ Props LAL.V157.LBV.V529. SWAGS..SSCOT/WORPP. SSCOT/CYY-STAR FL120 and *OPF Turbojets only LBV.V529..V35.CURVE All LAL..RSW..CYY. SSCOT- STAR FL230 and GNV departures and south only LAL..RSW.CYY-STAR RSW/FMY Turbojets/ Turboprops OGGER.TYNEE STAR INPIN.SHFTY STAR OGGER..FRZBE.. TYNEE.. INPIN..VALCH..WRTRS.. MOEMO..LBV INPIN..LBV.. SRQ..JOSFF-STAR LAL..SHFTY.SHFTY-STAR LAL..LBV.. FL130 and FL170 and FL130 and FL170 and FL270 and Advanced RNAV Cross OGGER/INPIN AOB FL270 PTP Cross OGGER/INPIN AOB FL270 Unable RNAV/PTP routing FL270 and Unable RNAV/PTP routing FL150 and Props LAL.V521.QUNCY.. ALL Turbojets/ Turboprops HODAR..FRZBE.TYNEE STAR FL130 and SHFTY Weather route, Requires TMU Approval PGD All LAL FL 190 PIE.V35.SABEE..PGD FL 170 Cross Center boundary AOB FL190 Cross Center boundary AOB FL190 descending to FL 170 9

DESTINATION AIRCRAFT TYPE ROUTE ALTITUDE RESTRICTION WHITL.PIKKR-STAR FL130 and Advanced RNAV Cross WHITL AOB FL350 INPIN.SHFTY-STAR FL170 and Advanced RNAV Cross INPIN AOB FL270 APF/MKY Turbojets/ Turboprops WHITL..CODGR..ZEILR.. INPIN..VALCH..WRTRS.. MOEMO..LBV FL130 and FL270 and PTP Cross WHITL AOB FL350 PTP Cross INPIN AOB FL270 SRQ.ZEILR-STAR INPIN..LBV.. FL270 and Unable RNAV/PTP routing LAL..SHFTY.SHFTY-STAR LAL..LBV.. FL150 and Props LAL.V521.QUNCY.. ALL 4.3.3.1 ZJX may clear SHFTY Arrival traffic direct VALCH between 17,000 and FL230. 4.3.3.2 The ZMA SARASOTA Low sector has control from the ZJX DARBS sector for descent to 17,000 feet, after the aircraft has passed the DARBS intersection on MCO Terminal Area arrivals. 4.3.3.3 Overflight Aircraft routed into AVON Sector (FL350 and ) must be cleared INPIN..LLAKE then flight plan route. 10

4.3.5 Gulf Routes Destination Route(s) Restrictions BLOND STAR* Tampa (TPA) Complex When W470 is not in use: Direct BLOND.BLOND STAR* *For non-advanced RNAV or if STAR not applicable: BLOND..PIE direct destination Cross Center boundary at or FL330 When W470 is not in use: Cross common boundary descending to FL250 and released for lower 10NM from the boundary. Orlando (F11) Complex BOXKR.COSTR/MINEE STAR Departure Point Route Restrictions Orlando (F11) Complex CAMDT..KNOST Jets Only 4.4 SPECIAL USE AIRSPACE 4.4.1 Whenever CAPE ATCAA activity requires reroutes, and W497B is not hot, ZMA will allow PBI/BCT/F45/LNA/06FA/SUA arrivals to fly via east coast routes (normal STARS, J79, or J45). ZMA will issue altitude restrictions to allow these aircraft to remain on the east coast. Usually this altitude will not be FL260. ZMA may require ZJX to ensure PBI Terminal landing traffic is under other like type aircraft. ZMA will strive to keep east coast routes to MIA/FLL/PBI open during these events. 4.4.2 If W497B is hot, aircraft landing PBI/BCT must be routed over TRV..CHADO or TRV.TUXXI-STAR AOB FL220. 4.4.3 ZMA Mission Coordinator must advise the ZJX South Area Supervisor thirty minutes prior activation of CAPE ATCAA. Deactivation will be coordinated on a real time basis. The South Area Supervisor must coordinate with affected ZJX sectors. 4.4.3.1 When CAPE A & B are in use, aircraft at affected altitudes must be issued V3/J79 TRV by ZJX Center. 4.4.4 ZJX South Area Supervisor must advise the ZMA Everglades Area Supervisor of real time changes regarding the status of Palatka Hi ATCAA and Hi Strike ALTRV. When Palatka Hi ATCAA is active, all affected J81 aircraft must be rerouted via J53. When the Hi Strike ALTRV is active, ZMA must not allow traffic to enter the GREENCOVE or ST. AUGUSTINE sectors at FL270 or FL280. 11 Revision One Effective January 8, 2015

4.5 NON-RADAR 4.5.1 Atlantic Route 3 (AR3) 4.5.1.1 Non-radar procedures must apply for traffic on or east of AR3 at FL240 and. 4.5.1.2 Automated transfer of data between facilities will constitute coordination of flight plan information. 4.5.1.3 ZJX shall advise southbound traffic on AR3 at FL230 and, to monitor 123.67/379.25 until ANGLL Intersection, then contact ZMA on 134.2/363.05. 4.5.1.4 ZMA must advise northbound traffic on AR3 at FL230 and, to contact ZJX on 134.85/327.1 at CARPX Intersection. 4.5.1.5 Transfer of the radar data block at or FL240 is required, but does not constitute a radar handoff. 5 AUTOMATION. 5.1 GENERAL 5.1.1 ZMA is designated as the automation host facility for Tampa Approach Control. 5.1.2 ZJX is designated as the automation host facility for Orlando Approach Control. 5.2 SCHEDULED OUTAGES 5.2.1 Advance notification must be given with sufficient time prior to the outage to allow the non-host facility to extract all required flight plan information. 5.2.2 Unsuccessful Transmission Messages (UTMs) will be transmitted to the FDCS KVDT. The FDCS must be responsible for forwarding all UTM data. 5.3 UNSCHEDULED OUTAGES 5.3.1 In the event of a host facility computer failure, the host facility FDCS shall forward required flight plan information for aircraft departing Tampa or Orlando Approach Control airspace to the non-host facility. 12

6 EDST 6.1 EDST Interfacility Automation (IFA): To the extent it is mutually and operationally advantageous; IFA shall be established between the facilities. 6.2 RESTRICTIONS 6.2.1 The facility in whose airspace the arrival airport resides will be considered as the facility owning mutual facility-boundary restrictions. 6.2.2 The receiving facility will be considered as the facility owning mutual facilityboundary restrictions on over flight traffic. 6.2.3 Upon establishing IFA each facility will set the restrictions they own to on, and those they do not own to off in accordance with 6.2.1 and 6.2.2. 6.3 SPECIAL ACTIVITY AIRSPACE - SAA 6.3.1 For SAA s overlapping center boundaries, the facility responsible for coordination of the status of the Special Use Airspace will be responsible for changing status of SAAs within EDST. 6.4. IFA FAILURE 6.4.1 The Operations Manager (OM) in the failing facility must notify the OM of the adjacent facility of the failure. 6.4.2 In the event of an IFA outage, each facility must turn on restrictions that are in an off status according to paragraph 6.2.3. 6.5 IFA RECOVERY 6.5.1 The OM in the recovering facility, must notify the adjacent facility that they are ready to reestablish IFA. 13 Revision One Effective January 8, 2015

6 EDST 6.1 EDST Interfacility Automation (IFA): To the extent it is mutually and operationally advantageous; IFA shall be established between the facilities. 6.2 RESTRICTIONS 6.2.1 The facility in whose airspace the arrival airport resides will be considered as the facility owning mutual facility-boundary restrictions. 6.2.2 The receiving facility will be considered as the facility owning mutual facilityboundary restrictions on over flight traffic. 6.2.3 Upon establishing IFA each facility will set the restrictions they own to on, and those they do not own to off in accordance with 6.2.1 and 6.2.2. 6.3 SPECIAL ACTIVITY AIRSPACE - SAA 6.3.1 For SAA s overlapping center boundaries, the facility responsible for coordination of the status of the Special Use Airspace will be responsible for changing status of SAAs within EDST. 6.4. IFA FAILURE 6.4.1 The Operations Manager (OM) in the failing facility must notify the OM of the adjacent facility of the failure. 6.4.2 In the event of an IFA outage, each facility must turn on restrictions that are in an off status according to paragraph 6.2.3. 6.5 IFA RECOVERY 6.5.1 The OM in the recovering facility, must notify the adjacent facility that they are ready to reestablish IFA. 13 Revision One Effective January 8, 2015

MIAMI ARTC CENTER AND JACKSONVILLE ARTC CENTER LETTER OF AGREEMENT ANNEX 1 SUBJECT: DELEGATION OF MALET AREA AIRSPACE 1 RELEASE OF AIRSPACE. When adverse weather conditions are affecting arrivals and departures to the Orlando Terminal Area, ZMA will release, upon the request of ZJX, the MALET Area as depicted in Annex 1A. 2 PROCEDURES. 2.1 Activation/Deactivation. The ZJX TMU will coordinate the release/return of the MALET Area with the ZMA TMU. The airspace will be released/returned at a time mutually agreed upon by both facilities. 2.1.1 ZJX must advise Orlando and Daytona Approach controls of the release/return of the MALET Area. 2.2.1 MCO terminal arrivals from ZMA must cross APOLO at 14,000, SFB arrivals shall be at 250k. 15

MIAMI ARTC CENTER AND JACKSONVILLE ARTC CENTER LETTER OF AGREEMENT DELEGATION OF AIRSPACE ANNEX 1A MALET AREA A 28 43 40 /80 59 10 B 28 49 10 /80 50 45 C 28 51 28 /80 47 34 D 28 54 00 /80 44 00 E 28 56 15 /80 32 25 F 29 00 00 /80 12 00 G 28 50 11 /80 02 03 H 28 43 00 /80 27 59 I 28 34 00 /81 00 00 J 28 40 00 /80 59 00 16

MIAMI ARTC CENTER AND JACKSONVILLE ARTC CENTER LETTER OF AGREEMENT ANNEX 2 SUBJECT: DELEGATION OF M203 RELEASE AREA AIRSPACE 1 RELEASE OF AIRSPACE. ZJX transfers control of the M203 Release Area (depicted ) to the ZMA NUCAR sector continuously, unless otherwise coordinated. 17

MIAMI ARTC CENTER AND JACKSONVILLE ARTC CENTER LETTER OF AGREEMENT ANNEX 3 SUBJECT: ZJX RAINY AREA AIRSPACE 1. During periods of severe weather, the Green Cove/St. Augustine sectors may implement the Rainy Area. Portions of the St. Augustine sector west of the line at or FL 240 are delegated to the Green Cove sector. All handoffs and point outs within the Rainy Area airspace must be DIRECTED to the Green Cove sector during implementation. The Green Cove sector will coordinate with the ZMA BOYEL sector. 18