SUBJECT: Kansas City (KC) TRACON - Standard Operating ... TRACON SOP_1565643055.pdf · For VFR operations, each TRACON sector is delegated VFR altitudes from the base of the overlying

VIRTUAL AIR TRAFFIC SIMULATION NETWORK ZKC ORDER 01.120A NORTH AMERICA REGION - USA DIVISION

vZKC – KANSAS CITY ARTCC Effective Date: February 1, 2013

SUBJECT: Kansas City (KC) TRACON - Standard Operating Procedures

This order prescribes standard operating procedures for use by individuals providing ATC services on the VATSIM network within the Kansas City TRACON boundary. Any controller providing such services- whether assigned to the Kansas City ARTCC or with visiting status- must be familiar and comply with the provisions of this order that pertain to their operational responsibilities, and use their best judgment when encountering situations not covered by it.

Please note, this order is intended for use on the VATSIM network and only applies in a virtual environment simulated on the VATSIM network. Although this order contains real-world procedures, it is not applicable for live operations in the National Airspace System.

The procedures contained within this order prescribe how the ATC facilities/positions are to be operated and-- in conjunction with FAA Orders 7110.10, 7110.65, 7210.3 and various ZKC Orders-- will be the basis for performance evaluation, training and certifications.

Wes Miles Air Traffic Manager Kansas City ARTCC

Jason Helkenberg Deputy Air Traffic Manager Kansas City ARTCC

Distribution: vZKC, VATUSA Initiated By: vZKC

2/28/12 ZKC 01.120A

Page | 2

RECORD OF CHANGES

CHANGE EFFECTIVE DATE DESCRIPTION

2/28/12 ZKC 01.120A

Page | 3

Table of Contents

RECORD OF CHANGES .......................................................................................................................... 2

Table of Contents ........................................................................................................................................ 3

Chapter 1. Introduction ............................................................................................................................. 6

1-1. Purpose of this Order ............................................................................................................ 6

1-2. Audience ............................................................................................................................... 6

1-3. Where Can I Find This Order? .............................................................................................. 6

1-4. What This Order Cancels ...................................................................................................... 6

1-5. Explanation of Changes ........................................................................................................ 6

1-6. Managing Agent .................................................................................................................... 6

1-7. Annotations ........................................................................................................................... 7

1-8. Word Meanings ..................................................................................................................... 7

1-9. Abbreviations and References .............................................................................................. 7

1-10. Delegated Airspace ............................................................................................................... 8

Chapter 2. General ..................................................................................................................................... 9

2-1. Calm Wind Runways ............................................................................................................ 9

2-2. Heavy Aircraft....................................................................................................................... 9

2-3. Crosswind Operations ........................................................................................................... 9

2-4. Noise Abatement ................................................................................................................... 9

2-5. Scratchpad Entries............................................................................................................... 10

2-6. Use of Temporary Altitude Field ........................................................................................ 12

Chapter 3. Airspace ................................................................................................................................. 13

3-1. KC TRACON ...................................................................................................................... 13

3-2. East/West Approach ............................................................................................................ 13

3-3. Final Approach .................................................................................................................... 14

3-4. Low ..................................................................................................................................... 14

3-5. Departure ............................................................................................................................. 14

3-6. MCI Tower (East/West) ...................................................................................................... 14

3-7. Satellite Airport Class D ..................................................................................................... 15 3-8. Minimum Vectoring Altitude .............................................................................................. 15

Chapter 4. Arrivals .................................................................................................................................. 16

4-1. Arrival Information ............................................................................................................. 16

4-2. Arrival Floors ...................................................................................................................... 16

4-3. MCI In-Trail Separation ...................................................................................................... 16

2/28/12 ZKC 01.120A

Page | 4

4-4. Simultaneous Approaches ................................................................................................... 17

4-5. North Flow .......................................................................................................................... 17

4-6. South Flow .......................................................................................................................... 17

4-7. East Flow ............................................................................................................................ 18

4-8. West Flow ........................................................................................................................... 18

Chapter 5. Departures ............................................................................................................................. 19

5-1. Initial Headings ................................................................................................................... 19

5-2. Initial Altitudes ................................................................................................................... 19

5-3. North Flow .......................................................................................................................... 19

5-4. South Flow .......................................................................................................................... 19

5-5. East Flow ............................................................................................................................ 19

5-6. West Flow ........................................................................................................................... 19

5-7. Missed Approaches ............................................................................................................. 19

Chapter 6. Satellite Airport Operations ................................................................................................ 20

6-1. Sector Responsibilities ........................................................................................................ 20

6-2. Arrivals ............................................................................................................................... 20

6-3. Departures ........................................................................................................................... 20 Appendix

2/28/12 ZKC 01.120A

Page | 5

THIS PAGE INTENTIONALLY LEFT BLANK

2/28/12 ZKC 01.120A

Page | 6

Chapter 1. Introduction 1-1. Purpose of this Order

This order establishes standard operating procedures for the VATSIM Kansas City TRACON-- referenced both as the ATC facility and as the terminal area-- and supplements FAA 7110.65, Air Traffic Control; ZKC 01.100, Air Traffic Control.

1-2. Audience

All VATSIM Kansas City ARTCC personnel, as well as those with a visiting status. Anyone providing ATC services within the KC TRACON boundary and STJ TRACON boundary must be familiar and comply with the provisions of this order.

1-3. Where Can I Find This Order?

This order is stored electronically on the vZKC website: www.kcartcc.com

1-4. What This Order Cancels

The following Orders/Notices are cancelled and superseded; their content has been added to this Order:

a. Kansas City TRACON SOP, dated 12/28/08.

1-5. Explanation of Changes

a. Initial altitude assignments of all MCI IFR departures have been changed to better reflect real-world procedure and provide better flow.

b. Arrival Floors have been established for IFR arrivals into MCI to avoid satellite airport traffic.

c. New sectors have been created: Final Approach, Low and Departure.

1-6. Managing Agent

a. This Order shall be managed, updated, issued and cancelled by the Air Traffic Manager (ATM), his designee or any entity that supersedes, replaces or assumes the ATM responsibilities. Any suggestions for modification/amendment to this Order should be sent to the ATM and/or his designee.

b. The following are identified as designee(s) for managing this Order with their respective permissions:

• Deputy Air Traffic Manager - draft changes

2/28/12 ZKC 01.120A

Page | 7

1-7. Annotations

Revised, new, or reprinted pages will be marked as follows:

a. The change number and the effective date are printed on each revised or additional page.

b. A reprinted page not requiring a change is reprinted in its original form with original effective date.

c. Bold vertical lines in the margin of the text mark the location of substantive changes; e.g., when material affecting the performance of duty is added, revised, or deleted.

d. Statements of fact of a prefatory or explanatory nature relating to directive material are set forth as notes.

1-8. Word Meanings

As used in this Order:

a. Must, or an action verb in the imperative sense, means mandatory.

b. Should means recommended

c. May and need not mean optional

d. Will indicates futurity

1-9. Abbreviations and References

This Order uses abbreviations and refers to words/phrases as defined in the following tables:

TBL 1-9-1 TRACON Sector/Position Identifiers Used In This Order

IDENTIFIER SECTOR/POSITION

KC_CTR Kansas City ARTCC (may be accompanied with a sector ID)

KC_APP Approach Combined

KC_E_APP East Approach

KC_W_APP West Approach

KC_F_APP Final Approach

KC_L_APP Low (Approach/Departure for satellite airports)

KC_DEP Departure

MCI_TWR Kansas City International Tower Combined

MCI_E_TWR Kansas City International Tower (East)

MCI_W_TWR Kansas City International Tower (West)

MKC_TWR Wheeler Downtown Tower

STJ_TWR St. Joseph Tower

IXD_TWR New Century Tower

2/28/12 ZKC 01.120A

Page | 8

OJC_TWR Executive Tower

TBL 1-9-2

Abbreviations

ABBR / REFERENCE DESCRIPTION

ATM Air Traffic Manager

DATM Deputy Air Traffic Manager

IAW in accordance with

m. - KC TRACON - the TRACON

- the ATC function (Approach Control / Departure Control) or - the terminal airspace

CTR En-route Control / Center (Kansas City Center may be assumed unless otherwise indicated)

APP Approach Control (may include a sector identifier ie: KC_E_APP)

DEP Departure Control

TWR Tower (Cab)

GND Ground Control

DEL Clearance Delivery

RWY Runway

TBL 1-9-3

Word/Phrase References

WORD/PHRASE DESCRIPTION

Departure Airspace Delegated airspace for vectoring departures to the appropriate Center sector

Arrival Corridors Areas depicted on the radar client as a single line which follows the STAR routes. The corridor lateral dimensions are 4NM either side of the depicted line to the Descent Zone.

Arrival Floors Areas along arrival corridors with an at-or-above altitude restriction. These "floors" are used to de-conflict MCI arrival traffic with satellite and over-flight traffic-- as well as keep arrival flow out of adjacent/bordering sector airspace.

Descent Zone An area associated with final descent and maneuvering area for the arrival runway(s). This typically consists of the area 5NM on either side of an active arrival runway's final approach course within 15NM of the threshold.

the website http://www.kcartcc.com and any/all associated features/programs

1-10. Delegated Airspace

Delegated airspace is defined throughout this Order and depicted in Appendix.

a. MCI Tower airspace (depicted in Appendix 1-A) supersedes KC TRACON airspace.

b. Delegated airspace diagrams depict IFR altitudes unless otherwise indicated

2/28/12 ZKC 01.120A

Page | 9

c. For VFR operations, each TRACON sector is delegated VFR altitudes from the base of the overlying airspace and down to 500 feet above any tower's airspace.

Chapter 2. General 2-1. Calm Wind Runways

Kansas City International favors a North (Runway 1L and 1R) flow under calm wind conditions. Calm wind runways are usually used when the wind is less than 5 knots at smaller airports. At KMCI, this is when the wind is less than 10kts.

2-2. Heavy Aircraft

All HEAVY aircraft are to use runway (19R/1L), this includes noise abatement hours.

2-3. Crosswind Operations

The use of RWY 9/27 is authorized under the following criteria:

a. When wind favors the runway by 15 knots or greater.

b. When pilot requests. The controller is responsible for approving pilot requests to use the runway based on traffic and other factors.

NOTE-- VATSIM controllers are not authorized to deny a pilot’s request for a runway. Refer to ZKC 01.100, Air Traffic Control, for further guidance/information.

2-4. Noise Abatement

Noise abatement procedures are in effect each day from 2200L – 0600L. Refer to table 3-4-1 for runway usage.

TBL 2-4-1 MCI Noise Abatement Runway Usage

FLOW DEPARTURE RUNWAY ARRIVAL RUNWAY

North 1R 1L

South 19R 19L

2/28/12 ZKC 01.120A

Page | 10

2-5. Scratchpad Entries

a.

1. Aircraft should be scratched with the approach procedure the aircraft has been assigned by the first APP controller who handles the aircraft as soon as practical.

ARRIVALS

2. Approach procedure codes for scratchpad entries are as follows:

i. “X” shall be the procedure type:

X # Y

• V = Visual

• I = ILS

• R = RNAV

• G = GPS

• O = VOR

• N = NDB

• L = LOC

• D = LDA

ii. “#” shall be the assigned runway using the second digit of the runway number:

• RWY 19R = "9"

• RWY 27 = "7"

• RWY 1L or 1R = "1"

iii. "Y" shall be the Left / Right identifier when applicable:

• RWY 1L = "L"

TBL 2-5-1

KC TRACON Arrival Scratchpad Entry Examples

SCRATCHPAD MEANING

V1R Visual Approach, RWY 1R

I9L ILS Approach, RWY 19L

I9 ILS Approach, RWY 9 (no left/right identifier)

V7 Visual Approach, RWY 27

V9R Visual Approach, RWY 19R

2/28/12 ZKC 01.120A

Page | 11

b.

1. Clearance Delivery-- or the controller performing the clearance delivery function-- shall insert the scratchpad entries for IFR aircraft as described below, only when KC_DEP is staffed, or another controller performing the Departure Control function.

DEPARTURES

NOTE-- All members of the tower cab (Delivery, Ground, and Tower) are responsible for ensuring that the scratchpad block is correct prior to departure.

2. KC_DEP-- or the controller performing the Departure Control function-- must clear all scratchpad entries prior to initiating the handoff to CTR.

TABLE 2-5-2

KC TRACON Departure Scratchpad Entries

DEPARTURE TRANSITION SCRATCHPAD ENTRY

CHIEF STJ CS

CATTS CC

LAKES COU LC

TWAIN LT

SPI LS

RACER BUM RB

SGF RS

DOSOA RD

ROYAL JTHRO YJ

TONCE YT

TIFTO TIFTO TT

WLDCT KENTN WK

SLN WS

ICT WI

NOT ON SID First 3 letters of first waypoint XXX (Ex: FRI, DOA)

DIRECT Destination ID XXX (Ex: MEM, DEC)

c.

1. Any position in the Kansas City TRACON should also use the following codes in an aircraft scratchpad only when there is more than one ATC function staffed within the TRACON.

GENERAL

2/28/12 ZKC 01.120A

Page | 12

TABLE 2-5-3 KC TRACON General Scratchpad Entries

DESCRIPTION SCRATCHPAD ENTRY

VFR Traffic Pattern PTN

Just Flying Around JFA

Missed Approach (and going back to APP for radar vectors)

MA

Go Around GA

VFR Flight Following VFF

VOR ID XXX (Example: ANX)

Heading HXX (Example: H23 – heading 230)

Fix ID (first 3 characters) XXX (Example: COU)

2-6. Use of Temporary Altitude Field

a. The ‘Temp Altitude’ field should not be used to coordinate altitudes at time of handoff – as all aircraft should be handed off descending to the altitudes defined in the SOP’s with which both CTR and APP controllers are required to be familiar with.

b. If other-than-standard altitudes are required due to traffic circumstances, this should be communicated directly with the receiving controller via landline, chat box or Teamspeak. This helps ensure that the unusual altitude will be noticed.

NOTE-- IAW ZKC 01.100, Air Traffic Control, the temporary altitude field is never used for coordination in ZKC. Controllers should use active coordination methods when handoffs will not occur at prescribed altitudes.

2/28/12 ZKC 01.120A

Page | 13

Chapter 3. Airspace 3-1. KC TRACON

a. KC TRACON

b.

owns the airspace designated within the TRACON boundary from the surface up to and including 15,000 MSL.

SOUTH SHELF

NOTE-- CTR will be responsible for the airspace from the surface up to and including 5,000 MSL including KLWC (Lawrence) which lies below.

– KC TRACON shall control the south shelf from the surface up to and including 5,000 MSL. Appendix: 1-B

c. NORTH SHELF

• STJ_APP Open:

– The inner-most shelf to the northwest which overlies KSTJ and within the KC TRACON boundary. Appendix: 1-B

St. Joseph Approach will control the North Shelf overlying the KSTJ Airport from the surface up to and including 6,000 MSL.

NOTE--

1. A section of the MCI Class BRAVO enters the North Shelf. This section floor is 5,000 MSL, which is the top of the North Shelf. This section of the Class BRAVO is unused for IFR aircraft between 4,000 and 5,000 MSL to provide 1,000 foot separation for possible traffic in the neighboring TRACONs.

2. VFR aircraft in this section of the Class BRAVO above 4,000 MSL will be handled by STJ_APP at the appropriate VFR altitude of 4,500.

• STJ_APP Closed:

KC TRACON will control the St. Joseph North Shelf from the surface up to and including 15,000 MSL and be responsible for KSTJ operations.

3-2. East/West Approach

a. Delegated airspace for East Approach (KC_E_APP) and West Approach (KC_ W_APP) is depicted in Appendix 1-C, 1-D and varies depending on flow.

b. The airspace is typically divided by an imaginary line drawn parallel to the midpoint between runways 1L/19R and 1R/19L and extending to the TRACON border, but doesn't match this layout during east/west flow.

c. Aircraft destined for a satellite airport in the adjacent sector will remain with the controller who's sector they are in until:

1. an appropriate time when a handoff can be completed to the East/West Approach controller, prior to entering their airspace (unless prior coordination has been conducted)

2. the aircraft has descended—or is cleared— to the sector floor, at which time a handoff can be conducted to Low Approach (when staffed)

2/28/12 ZKC 01.120A

Page | 14

3. If Final Approach (KC_F_APP) is closed, aircraft destined to an MCI runway which coincides with an adjacent sector will remain with the controller who's sector they are in until an appropriate time when a handoff can be completed to the appropriate East/West Approach controller (usually in the radar downwind or approaching the Descent Zone) unless prior coordination has been conducted.

3-3. Final Approach

a. The Final Approach (KC_F_APP) delegated airspace is depicted in Appendix 1-E, 1-F, 1-G and 1-H and varies depending on flow.

b. The airspace generally matches the Descent Zone for the active arrival runway in use, excluding MCI_TWR airspace.

3-4. Low

a. Low (KC_L_APP) airspace is depicted in Appendix 1-I, 1-J, 1-K and 1-L and varies depending on flow direction.

b. The airspace generally includes all airspace within the TRACON and shelves from the surface up to and including 6,000 MSL, excluding designated airspace for all TWRs, KC_F_APP, KC_DEP and STJ_APP (when staffed).

c. ARRIVALS

• IFR Arrivals to MCI within Low airspace shall be handed off to the appropriate East/West Approach as soon as practical

– Low shall handle arrivals into satellite airports after cleared to—or at—the overlying airspace floor and after all coordination has been completed (ie handoffs).

d. DEPARTURES

• Handoffs should be accomplished as required/appropriate as soon as practical to KC_DEP, or the next overlying radar position, and shall include notification if the aircraft was not cleared on course.

– Low shall handle initial departures from satellite airports, vectoring as needed, with the purpose of getting aircraft on course, and no higher than the Low airspace ceiling (unless otherwise coordinated).

• It shall be assumed KC_L_APP will clear satellite IFR departures on course if no notification is made otherwise during handoff coordination.

3-5. Departure

Departure (KC_DEP) generally includes all airspace within the KC TRACON from the surface up to and including 15,000 MSL, excluding all designated airspace belonging to TWRs and other APP sectors. Airspace for RW9 departures are depicted in Appendix 1-M.

3-6. MCI Tower (East/West)

a. Delegated airspace for East Tower (KC_E_TWR) and West Tower (KC_W_TWR) is depicted in Appendix 1-A and varies depending on flow.

2/28/12 ZKC 01.120A

Page | 15

b. The airspace matches the inner ring of the MCI Class B Airspace from the surface up to and including 3,000 MSL.

c. The East/West split is typically divided by an imaginary line drawn parallel to the midpoint between runways 1L/19R and 1R/19L, but doesn't match this layout during east/west flow.

3-7. Satellite Airport Class D

a. The lateral boundary of most satellite Class D airspaces includes a 4NM radius from the center of the airport.

1. MKC_TWR – vertical limits extend from the surface up to and including 3,000 MSL.

2. OJC_TWR – vertical limits extend from the surface up to and including 3,600 MSL.

3. IXD_TWR – vertical limits extend from the surface up to and including 3,600 MSL.

NOTE-- There are two sections of the IXD Class D Airspace where "cutouts" are made. One is to the east, where OJC's Class D overrides, the other is to the west to allow for Gardner airport.

4. STJ_TWR – vertical limits extend from the surface up to and including 3,300 MSL.

3-8. Minimum Vectoring Altitude

a. The MVA as shown in Appendix 1-N shows the minimum vectoring altitude for the KC TRACON. In vSTARS a LA alert will be given if an aircraft descends below a MVA Altitude.

2/28/12 ZKC 01.120A

Page | 16

Chapter 4. Arrivals 4-1. Arrival Information

a. IFR aircraft (and VFR aircraft receiving radar services) destined to an airport within the TRACON boundary without the current weather/ATIS must be issued the following by the first APP/DEP controller who handles them:

1. surface wind for the destination airport

2. ceiling and visibility if the reported ceiling at the destination airport is below 1,000 AGL, or the visibility is less than 3 miles

3. altimeter setting for the destination airport

b. IFR aircraft destined to a controlled airport within the TRACON boundary shall be issued the following as soon as practical:

1. Type of approach to be expected (unless ATIS broadcasts one arrival runway and approach in use, and the pilot has the latest ATIS code)

2. Runway if different from that to which the approach is being made

c. KC_L_APP-- or, when unstaffed, the appropriate sector with radar jurisdiction over the destination airport-- shall obtain the approach/runway request of IFR aircraft destined to an uncontrolled airport within the TRACON boundary.

“N121BK, SAY APPROACH REQUEST”

4-2. Arrival Floors

a. IFR Aircraft arriving KMCI

4-3. MCI In-Trail Separation

must not be descended below 7,000 MSL before reaching a midfield radar downwind.

Unless wake turbulence application would require a larger in-trail separation, IFR MCI arrivals may use the minimum in-trail separation standard of 2.5NM once established on the final approach course within 10NM of the runway. REFERENCE-- FAA 7110.65 5-5-4, Minima

NOTE-- Heavy aircraft and B757s are only permitted to participate in this reduced separation as the trailing aircraft.

2/28/12 ZKC 01.120A

Page | 17

4-4. Simultaneous Approaches

a.

1. Simultaneous visual approaches into MCI may be initiated IAW FAA 7110.65 7-4. Simultaneous visual approaches must be handled differently depending upon the distance between parallel runways, which at KMCI are separated by 6,620 feet.

VISUAL

2. The following rule summarizes FAA 7110.65 7-4 as it pertains to MCI. When vectoring for the visual approach for runways separated by 4,300 feet or more:

b.

1. Simultaneous ILS approaches are authorized between RWYS 19L/R, or RWYS 1L/R. Technically, simultaneous ILS approaches are only authorized when the "final approach monitor" positions are manned. For the purposes of VATSIM, we always consider these two positions manned, even if they are not.

ILS

4-5. North Flow

a. ROBINSON ARRIVALS

b.

are received from CTR with instructions to cross PEGGI at and maintain 12,000 MSL. The STAR then instructs aircraft to cross HUGGY at 210 knots, and depart HUGGY heading 190, then expect vectors to the final approach course.

JHAWK ARRIVALS

c.

are received from CTR with instructions to cross JHAWK at and maintain 12,000 MSL. The STAR then instructs aircraft to depart HOOZE heading 060 for vectors to the final approach course.

BRAYMER ARRIVALS

d.

are received from CTR with instructions to cross MATTZ at and maintain 12,000 MSL. The STAR then instructs aircraft to cross BYGEC at 210 knots, and depart BYGEC heading 190, then expect vectors to the final approach course.

TYGER ARRIVALS

4-6. South Flow

are received from CTR with instructions to cross TYGER at and maintain 12,000 MSL. The STAR then instructs aircraft to depart TRIKE heading 290 for vectors to the final approach course.

a) When aircraft flight paths do not intersect, visual approaches may be conducted simultaneously, provided standard separation is maintained until one of the aircraft has been issued and the pilot has acknowledged receipt of the visual approach clearance.

b) Visual approaches may be conducted to one runway while visual or instrument approaches are conducted simultaneously to the other runway, provided the conditions of sub paraphrase (a) are met.

c) Provided the aircraft flight paths do not intersect, when the provision of sub paraphrase (a and b) are met, it is not necessary to apply any other type of separation with aircraft on the adjacent final approach course.

2/28/12 ZKC 01.120A

Page | 18


b.

are received from CTR with instructions to cross RBA at and maintain 12,000 MSL. The STAR then instructs aircraft to depart JUDAA heading 110 for vectors to the final approach course.

JHAWK ARRIVALS

c.

are received from CTR with instructions to cross RUGBB at and maintain 12,000 MSL. The STAR then instructs aircraft to cross NOAHS at 210 knots, and depart NOAHS heading 010 for vectors to the final approach course.

BRAYMER ARRIVALS

d.

are received from CTR with instructions to cross BQS at and maintain 12,000 MSL. The STAR then instructs aircraft to depart DONNS heading 255 for vectors to the final approach course.

TYGER ARRIVALS

4-7. East Flow

are received from CTR with instructions to cross MORAY at and maintain 12,000 MSL. The STAR then instructs aircraft to cross SLABB at 210 knots, and depart SLABB heading 010 for vectors to the final approach course.


b.

are received from CTR with instructions to cross JUDAA at and maintain 12,000 MSL. After JUDAA, aircraft will receive vectors to the final approach course.

JHAWK ARRIVALS

c.

are received from CTR with instructions to cross HOOZE at and maintain 12,000 MSL. After HOOZE, aircraft will receive vectors to the final approach course.

BRAYMER ARRIVALS

d.

are received from CTR with instructions to cross DONNS at and maintain 15,000 MSL. After DONNS, aircraft will receive vectors to the final approach course.

TYGER ARRIVALS

4-8. West Flow

are received from CTR with instructions to cross TRIKE at and maintain 15,000 MSL. After TRIKE, aircraft will receive vectors to the final approach course.

e. ROBINSON ARRIVALS

f.

are received from CTR with instructions to cross JUDAA at and maintain 15,000 MSL. After JUDAA, aircraft will receive vectors to the final approach course.

JHAWK ARRIVALS

g.

are received from CTR with instructions to cross HOOZE at and maintain 15,000 MSL. After HOOZE, aircraft will receive vectors to the final approach course.

BRAYMER ARRIVALS

h.

are received from CTR with instructions to cross DONNS at and maintain 12,000 MSL. After DONNS, aircraft will receive vectors to the final approach course.

TYGER ARRIVALS are received from CTR with instructions to cross TRIKE at and maintain 12,000 MSL. After TRIKE, aircraft will receive vectors to the final approach course.

2/28/12 ZKC 01.120A

Page | 19

Chapter 5. Departures 5-1. Initial Headings

Unless otherwise needed for course divergence (see below), all IFR departures will be issued runway heading.

5-2. Initial Altitudes

a. IFR PROP

b.

aircraft must be assigned an initial altitude 4,000 MSL or lower requested altitude.

IFR TURBOJET

NOTE-- IFR departures must never be assigned an altitude lower than 3,000 MSL.

aircraft must be assigned an initial altitude of 10,000 MSL or lower requested altitude.

5-3. North Flow

a. EAST DEPARTURES

b.

may be issued a heading of 030

WEST DEPARTURES

5-4. South Flow

may be issued a heading of 350 (and 330 for props)

a. EAST DEPARTURES

b.


WEST DEPARTURES

5-5. East Flow


a. EAST DEPARTURES

b.


WEST DEPARTURES

5-6. West Flow


a. EAST DEPARTURES

b.


WEST DEPARTURES

5-7. Missed Approaches


a. IFR aircraft who conduct a missed-approach or go-around will be assigned an initial heading by MCI_TWR which will keep the aircraft within the departure parameters for the runway in use.

b. MCI_TWR must assign the aircraft 3,000 MSL and notify, then change the aircraft to the KC_DEP frequency (or appropriate RADAR controller).

2/28/12 ZKC 01.120A

Page | 20

Chapter 6. Satellite Airport Operations 6-1. Sector Responsibilities

a. Kansas City Approach (KC_APP) will have the responsibility of separating and sequencing all IFR arrivals to all controlled and uncontrolled satellite airports within the Kansas City TRACON.

b. KC_L_APP, when staffed, is the sector directly responsible for approach clearances, departure releases, and final sequencing. If unstaffed, this responsibility is assumed by the next staffed sector directly overhead each airport.

c. KC_APP will provide traffic advisories and, if necessary, separation and sequencing of all VFR aircraft receiving RADAR services within the Kansas City TRACON boundaries.

6-2. Arrivals

a. KC_APP will route all IFR arrivals into satellite airports along the appropriate STARS, or arrival routes when applicable.

b. Satellite towers in operation will inform KC_L_APP (or the appropriate staffed sector) of the current ATIS, runway(s) and approach(es) in use.

c. KC_L_APP (or the appropriate staffed sector) shall complete handoffs to satellite towers in operation when:

1. IFR arrivals are being vectored for an approach, or as soon as possible after clearing aircraft for an approach

2. VFR aircraft receiving RADAR services report the airport in sight

3. or otherwise before an aircraft is 10 miles-to-fly from the airport

NOTE-- vZKC simulates all Class D towers within the Kansas City TRACON boundary having tower RADAR displays. This allows for automated handoffs using a RADAR client to satellite towers. This does not prevent controllers from performing manual handoffs/inbound calls if they choose do to so.

6-3. Departures

a. Satellite airport TWR, GND and/or DEL (when staffed) will provide all IFR clearances to aircraft departing their airports.

b. Satellite airport TWR, GND, and/or DEL (when staffed) will issue the appropriate SID or TRACON departure gate to aircraft who are capable of navigating such routes, which is closest to their filed route of flight. Aircraft that are not capable of accepting these routes may be vectored over a departure gate by the appropriate RADAR sector if traffic conditions warrant this action.

c. All IFR departures from satellite airports will receive RADAR vectors on departure, to join their filed route of flight via the most direct route possible. EXAMPLE: “On departure, expect RADAR vectors.”

d. Initial Altitudes are assigned in accordance with table 6-3-1.

2/28/12 ZKC 01.120A

Page | 21

TABLE 6-3-1 Satellite IFR Departure Initial Altitudes

AIRPORT ALTITUDE

KMKC 3,000

KOJC, KIXD, KSTJ 5,000

e. Satellite airport Towers, when staffed, must request and receive an IFR release from KC_L_APP (or the appropriate staffed sector) prior to allowing any IFR departure to takeoff. As a standard, this release will usually be an initial heading. When traffic conditions/airspace configurations permit, an “On Course” release may be issued. This allows the aircraft to proceed on course instead of flying an assigned heading. EXAMPLE: “On departure, proceed on course. Runway 1 cleared for takeoff.”

NOTE-- Clearance to “proceed on course” does not require the aircraft to be RNAV equipped. Pilots without GPS/RNAV equipment may still navigate their aircraft on course without assistance from ATC. However, the pilot may request lateral guidance to his/her first fix, in which case an initial heading must be provided.

f. Go-arounds and missed-approaches that do not wish to cancel IFR and enter VFR traffic patterns, or cannot execute an appropriate published missed approach procedure, will be assigned the initial departure altitude (Table 6-3-1). Satellite Towers must notify KC_L_APP (or the appropriate staffed sector) who may issue a heading, then switch the aircraft to the approach frequency for re-sequence.

2/28/12 ZKC 01.120A

Page | 22

Appendix

1-A.

2/28/12 ZKC 01.120A

Page | 23

1-B.

2/28/12 ZKC 01.120A

Page | 24

1-C.

2/28/12 ZKC 01.120A

Page | 25

1-D.

2/28/12 ZKC 01.120A

Page | 26

1-E

2/28/12 ZKC 01.120A

Page | 27

1-F.

2/28/12 ZKC 01.120A

Page | 28

1-G.

2/28/12 ZKC 01.120A

Page | 29

1-H.

2/28/12 ZKC 01.120A

Page | 30

1-I.

2/28/12 ZKC 01.120A

Page | 31

1-J.

2/28/12 ZKC 01.120A

Page | 32

1-K.

2/28/12 ZKC 01.120A

Page | 33

1-L.

2/28/12 ZKC 01.120A

Page | 34

1-M.

2/28/12 ZKC 01.120A

Page | 35

1-N.

Documents

SUBJECT: Kansas City (KC) TRACON - Standard Operating ... TRACON SOP_1565643055.pdf · For VFR operations, each TRACON sector is delegated VFR altitudes from the base of the overlying