VATUSA CHICAGO ARTCC AND C90 TRACON LETTER OF AGREEMENT

Similar documents
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

Chicago TRACON (C90) Standard Operating Procedures ORDER K CHICAGO TRACON C90 SOP 1/10/2019

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

VATUSA CHICAGO ARTCC AND VATUSA MINNEAPOLIS ARTCC LETTER OF AGREEMENT

CHICAGO TRACON (C90) O HARE INTERNATIONAL AIRPORT MIDWAY INTERNATIONAL AIRPORT SATELLITE AIRFIELDS STANDARD OPERATING PROCEDURES

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

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

ERIE ATCT STANDARD OPERATING PROCEDURES

CHICAGO MIDWAY INTERNATIONAL AIRPORT (KMDW) STANDARD OPERATING PROCEDURES

RALEIGH-DURHAM ATCT/TRACON STANDARD OPERATING PROCEDURES

ATLANTA ARTC CENTER AND CHARLOTTE TOWER LETTER OF AGREEMENT

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

VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT

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

Piedmont Triad International Airport

CHICAGOLAND SPEEDWAY NASCAR RACES

CHICAGOLAND SPEEDWAY NASCAR RACES

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

D01 TERMINAL RADAR APPROACH CONTROL

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

Jacksonville ARTCC. F11 TRACON Standard Operating Procedures

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

Albany ATCT Standard Operating Procedures

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

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

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

Letter of Agreement by and between Jacksonville ARTCC and Miami ARTCC

ZTL ARTCC. Asheville Regional. Air Traffic Control Tower. Standard Operating Procedures AVL B. Effective: May 1, 2011

Project Consultant (PC) Alternative 5 Runway 22R/L RNAV Departures

Burlington ATCT Standard Operating Procedures

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

Denver ARTCC Colorado Springs ATCT & TRACON STANDARD OPERATING PROCEDURES

HOUSTON AIR ROUTE TRAFFIC CONTROL CENTER VATSIM United States Division. Letter of Agreement. Revised: July 25, 2004 Effective: July 25, 2004

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

Providence ATCT Standard Operating Procedures

Greenville Spartanburg International

Chapter 6. Nonradar. Section 1. General DISTANCE

Cleveland ARTCC and Boston Virtual ARTCC Letter of Agreement

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

2 Purpose and Need. 2.1 The Need for the Proposed Action Description of the Problem

PITTSBURGH ATCT STANDARD OPERATING PROCEDURES

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

Virtual Air Traffic Simulation Network (VATSIM) United States Division Fort Worth vartcc (ZFW)

- Updated formatting - Re-drawn airspace delegation diagram

San Juan CERAP. Standard Operation Procedures. Version 2.2 May 5th, Welcome to San Juan CERAP (ZSU ARTCC, TJZS FIR)

Anchorage ARTCC Phraseology Guide. Clearance Delivery Operations

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

Charlotte - Douglas International Airport Traffic Control Tower

Version O January 21, 2019

Instrument Proficiency Check Flight Record

Cape Area Airports Standard Operating Procedures

Standard Operating Procedures Atlanta Intl Airport (ATL) Air Traffic Control

New York ARTCC (ZNY) & Potomac TRACON (PCT)

SOUTHERN CALIFORNIA TRACON BURBANK AREA STANDARD OPERATING PROCEDURES VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES ARTCC

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

vzny ARTCC & vzbw ARTCC

LETTER OF AGREEMENT. Between

ZTL ARTCC. Augusta Regional

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

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

Letter of Agreement. between. and

ORDER MSY V. New Orleans. Standard Local Operating Procedures. Rev 3 December 7, 2011

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

GOVERNMENT OF INDIA OFFICE OF DIRECTOR GENERAL OF CIVIL AVIATION

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

Section 5. Radar Separation

STANDARD OPERATING PROCEDURES (CLE SOP) December 3, 2016

Albuquerque Center Standard Operating Procedures

VATUSA Approval 3/21/18

FLIGHT STRIP MANAGEMENT - APPROACH LEVEL

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

BOSTON ARTCC (vzbw) TRAINING SYLLABUS LEVEL: Center Controller (C1)

St. Paul Downtown Airport (STP)

EXPLANATION OF TPP TERMS AND SYMBOLS

Optimized Profile Descents A.K.A. CDA A New Concept RTCA Airspace Working Group

40 BEALEAFBI OCTOBER Chapter 8 RQ-4 OPERATIONS

USE OF RADAR IN THE APPROACH CONTROL SERVICE

Approach (TMA) Air Traffic Control. An Introduction to Approach/Departure Control Airspace and Operating Positions... 2

Charlotte - Douglas International

IRISH AVIATION AUTHORITY DUBLIN POINT MERGE. Presented by James O Sullivan PANS-OPS & AIRSPACE INSPECTOR Irish Aviation Authority

FLIGHT ADVISORY WASHINGTON D.C. SPECIAL FLIGHT RULES AREA LEESBURG MANUVERING AREA

THE AREA CONTROL CENTRE (CTR) POSITION

IFR SEPARATION WITHOUT RADAR

SULAYMANIYAH INTERNATIONAL AIRPORT MATS CHAPTER 11

CHAPTER 5 SEPARATION METHODS AND MINIMA

LETTER OF AGREEMENT (LOA)

Denver International Airport Air Traffic Control Tower. and. Denver Approach D01 LETTER OF AGREEMENT

Federal Aviation Administration. Air Traffic 101. By: Michael Valencia & Dianna Johnston Date: Feb. 26, 2017

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

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

SID/STAR phraseology FAQ Canadian implementation April 27, 2017

AERONAUTICAL INFORMATION CIRCULAR 18/18

PASCO (Pacific Soaring Council) ADVISORY TO GLIDER PILOTS

AREA NAVIGATION RNAV- MANAGEMENT

Pilot Briefing Document Cross The Pond 2013 Heathrow Airport EGLL/LHR

Continuous Descent? And RNAV Arrivals

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

Understanding Role of Flight Data Processing Across NAS Operational Domains

SECTOR ROUTE/STAR INSTRUCTION NOTES

Transcription:

VATUSA CHICAGO ARTCC AND C90 TRACON LETTER OF AGREEMENT EFFECTIVE: 01/16/2019 SUBJECT: INTERFACILITY COORDINATION 1. PURPOSE: This agreement establishes coordination procedures and defines delegation of airspace between VATUSA Chicago ARTCC (ZAU) and C90 TRACON. This agreement is supplemental to procedures contained within FAA Order 7110.65. 2. DISCLAIMER: Information contained herein is designed and specifically for use in a virtual air traffic control environment. It is not applicable, nor should it be referenced for live operations in the National Airspace System (NAS). 3. CANCELLATION: None 4. PROCEDURES: a.) General Procedures. (1) Clearance limit shall be the airport of intended landing until in-trail hand-offs cease. (2) Known traffic is defined as an aircraft that C90 has accepted the handoff. (3) No enroute aircraft shall be cleared through the Chicago TRACON Airspace, as described and depicted in Attachment 1, between the hours of 0600 to 2200 (local time) daily. (4) With prior coordination, enroute aircraft may be routed through Chicago TRACON's delegated airspace outside of the times in paragraph 4.a.3 (5) Under normal circumstances, C90 shall notify ZAU prior to holding. ZAU will advise preference of the hold. (6) When holding is in progress, ZAU will determine the time and sequence of holding fixes. (7) When feasible, ZAU will notify C90 when holding at other than the primary arrival fixes. (8) When feasible, C90 will notify ZAU when placing adjacent Approach Control on hold. 5. APPROVAL: /Matthew Campbell/ /Jackson Gilliam/ /Chris Hadden/ Air Traffic Manager Deputy Air Traffic Manager Training Administrator

6. ARRIVALS: a.) ZAU shall: (1) Provide in-trail radar separation between successive arrivals crossing the fix at an interval and speed as coordinated through the receiving controller. (2) Where the LOA indicates a second altitude (e.g, 4,000/5,000 feet), the first altitude shall be the primary altitude. The second altitude may be used to resolve overtakes. (3) Release control for speed increase. (4) Arrival Routes which indicate (RNAV) are for aircraft capable of RNAV STAR procedures. Arrival Routes which indicate (NON-RNAV) are for aircraft unable to fly RNAV STAR procedures. (5) When handing off directly to C90, ZAU must advise C90 when a pilot advises that they are unable to participate in Precision Runway Monitor (PRM) Approaches. ZAU may disregard notification when ZAU TMU is advised by C90 that PRM approaches are not in use. (1) SOUTHEAST: (BEARZ Sector) (a) C90 Arrival will assume 11,000 12,000 within AREA F with the first coordinated WATSN arrival and revert to C90 Departure following the last WATSN Arrival. (b) C90 shall assume control from ZAU for descent north of HULLS. (c) BEARZ sector releases control on all ORD arrivals, provided the aircraft has crossed the southern and eastern boundary of Area E. (d) BEARZ sector releases control on all ORD arrivals, provided the aircraft has crossed the southern and eastern boundary of Area E. (e) BEARZ Sector shall route MDW arrivals and ORD prop arrivals through SBN Approach if online. (2) SOUTHWEST: (PLANO Sector) (a) Chicago TRACON shall advise the PLANO Sector when initiating any airspace configuration changes that affect Chicago TRACON Sectors 1, 2 or 4. (b) PLANO Sector shall route MDW arrivals and ORD prop arrivals through SBN Approach or Streator Sector. (c) The PLANO Sector releases control for descent and turns up to 30 to Chicago TRACON. (d) C90 will ensure AREA G is transferred to C90 prior to the first coordinated SHAIN arrival and revert to RFD following the last SHAIN Arrival. (e) ZAU shall assign runway transitions to aircraft routed via the ENDEE STAR. ZAU shall issue a clearance for ENDEE STAR arrivals to descend via the ENDEE STAR except maintain 6,000 feet when MDW is landing 4R.

(3) NORTHEAST: (KUBBS Sector) a.) When ORD is on East Flow RNAV capable aircraft must be assigned the WYNDE STAR. b.) The Satellite airport arrival route is-direct WURKO or FIYER.OBK.destination. Chicago ARTCC releases control for descent and turns. WURKO/FIYER is considered one route and must be in-trail. (4) NORTHWEST: (FARMM Sector) a.) FARMM Sector must transfer communications to C90 by FYTTE. b.) FARMM Sector releases control for turns from FYTTE 060, clockwise to FYTTE 180. Chicago TRACON assumes separation responsibility with known ORD Arrival traffic. c.) The FARMM Sector is authorized to descend ARR, DPA, Milwaukee Metropolitan Area and Rockford arrivals to 11,000 feet in an area on or north of the centerline of V100 and on or west of the JOT 360 degree radial. Chicago TRACON must point out to the FARMM Sector aircraft either entering or within 3 miles of this airspace with the exception of aircraft handed off to C90 TRACON by the FARMM Sector. Arrival Airport(s) ORD Qualifier Routed Via FIYER/WYNDE STAR (ORD E) Altitude Jets Props 11,000 8,000 KUBBS FIYER/WYNDE STAR (ORD W) 9,000 8,000 North Satellite OBK 30 DME 4,000/3,000 Sector 3 4,000 HULLS/WATSN STAR 12,000 No Props ORD ESSPO/ESSPO STAR 12,000 8,000 HALIE/OXI STAR 12,000 8,000 BEARZ BOONE/VEECK STAR 11,000 8,000 North Sat 6,000 Sector 3 6,000/7,000 MDW ENDEE/ENDEE STAR 6,000/7,000 JOT, 1C5, LOT 5,000 Sector 2/3/North Sat 4,000 TRIDE/SHAIN STAR 12,000 8,000 ORD BENKY/BENKY STAR 12,000 8,000 TRTLL/TRTLL STAR 11,000 8,000 PLANO BENKY/BDF STAR 12,000 8,000 North Sat 6,000 Sector 3 6,000/7,000 MDW ENDEE/ENDEE STAR 6,000/7,000 JOT, 1C5, LOT 5,000 Sector 2/3/North Sat 4,000 ORD FARMM FYTTE/FYTTE STAR 11,000 8,000

7. DEPARTURES: a.) General Procedures. (1) Chicago TRACON must ensure all departures are cleared via the C90 departure tracks. Jet departures shall be assigned 250 knots. (2) Chicago TRACON must assign departure aircraft the flight plan requested altitude unless another lower altitude is specified in the area departure procedures (See Attachment 1). (3) Known traffic is defined as an aircraft that ZAU has accepted the handoff. (1) EAST (KUBBS Sector) a.) Chicago TRACON shall advise the KUBBS Sector when initiating any airspace configuration change that affects Chicago TRACON Area F. When C90 is using the WATSN STAR, 11,000 12,000 feet within Area F is delegated to C90 Arrivals. b.) Departures on NON-RNAV routes shall be established on a 090 heading underlying the appropriate sector. c.) When vectoring MOBLE/LEWKE departures past MOBLE/LEWKE to avoid the WATSN STAR, aircraft shall be cleared to the next fix, ADIME or GIJ as appropriate. d.) C90 releases control to the KUBBS Sector on all east departure aircraft at or above 11,000 feet except when the WATSN STAR is in use. When WATSN is in use, then C90 releases control to the KUBBS Sector on the EBAKE/DUFEE departures at or above 11,000 feet and on the MOBLE/LEWKE departures at or above 13,000 feet. The KUBBS Sector assumes separation responsibility with known traffic. (2) SOUTH (BEARZ Sector) a.) C90 may enter the C90 Climb Corridor as depicted in Attachment 1 without a point out to the BEARZ Sector. The BEARZ Sector, as appropriate, shall point out to C90 traffic traversing the C90 Climb Corridor between 11,000 and 15,000 feet. b.) North Satellite aircraft that have been transferred to the Newtt Sector (West of ORD) north of ORD shall be assigned direct JORJO (departures on non-rnav routes shall be assigned direct RBS). c.) North Satellite aircraft that have been transferred to the Peotone Sector (East of ORD) north of ORD shall be assigned direct MONKZ (departures on non-rnav routes shall be assigned direct EON). d.) BEARZ Sector (Newtt and Peotone Sectors Combined) shall have control to climb, increase speed and turns up to 30, on Chicago Metropolitan departures.

(3) WEST (FARMM Sector) a.) Chicago TRACON shall advise the FARMM Sector when WEST Departure splits/combines with KANE departure. b.) Chicago TRACON releases control of west departures to the FARMM Sector to climb, increase speed, and turns up to 30 degrees provided: (1) MYKIE/NOONY/OLINN/PLL/NSAT departures remain north of the Kane sector boundary. (2) PEKUE /IOW/Sec 1, 2, 3, and 4 departures remain south of the West sector boundary. (3) The departure aircraft is at or above 10,000 and west of a north/south line through the JORJO waypoint. (4) FARMM assumes separation responsibility with known traffic. c.) Chicago Center Malta Sector will accept aircraft under the provisions of FAAO 7110.65, paragraph 5-5-4, b.4., 3 miles separation increasing to 5 miles. (1) PLL Aircraft shall be established on a 270 heading between the MYKIE and NOONY tracks. IOW Aircraft shall be established on a 270 heading South of the OLINN intersection and North of the ARR Airport. (2) Aircraft shall be established on a 270 heading between the MYKIE and NOONY tracks. (3) Aircraft shall be established on a 270 heading South of the OLINN intersection and North of the ARR Airport. All South Satellite aircraft must be in-trail. (3) NORTH (FARMM Sector) a.) C90 releases control for speed increase at or above 14,000 feet. b.) C90 releases control for turns at or above 13,000 feet. c.) C90 releases control for climb on prop aircraft reference known traffic. (d) C90 delegates to ZAU the use of ACCRA/UECKR SIDs through C90 airspace. Departures must be established on the appropriate SID, and must cross KAJJY or MAULT at or above 13,000 feet and cross LVENS or UECKR at or above 16,000 feet. (e) Aircraft must be established on course by NEATO/BRTMN. Exception: UGN departures must be established on course by DLLAN/DNIKA.

Departure Airport(s) Qualifier Routed Via Altitude Jets Props ORD/ North Sat. KUBBS (EAST) EBAKE 15,000 13,000 DUFEE 15,000 13,000 MOBLE 15,000 13,000 Sectors 1/2/3/4 LEWKE 15,000 13,000 ACITO 15,000 11,000 BACEN 15,000 11,000 ORD/ North Sat. CMKSY 15,000 11,000 DENNT 15,000 11,000 BEARZ (SOUTH) EARND 15,000 11,000 ACITO 12,000 N/A BACEN 12,000 N/A MDW/Sectors 1/2/3/4 CMSKY 12,000 N/A DENNT 12,000 N/A EARND 12,000 N/A MYKIE 15,000 N/A NOONY 15,000 N/A ORD/North Sat OLINN 15,000 N/A PLL 15,000 N/A FARMM (NORTH/WEST) IOW 15,000 N/A PEKUE 15,000 N/A Sectors 1 and 4 13,000 N/A Sectors 2 and 3 Any 270 heading 13,000 N/A ALL RNAV PMPKN/RAYNR 15,000 14,000 Non-RNAV BAE/PETTY 15,000 14,000

Attachment 1

8. CHANGE LOG: Change # Date Description Author CHG 1 1/16/19 Write & Approval ZAU Staff