ZME-ZKC Letter of Agreement
General Procedures
Section titled “General Procedures”a. Each ARTCC should route/restrict aircraft in accordance with the route and altitude assignments below.
b. Either ARTCC may change the aircraft’s beacon code after receipt of radar handoff.
c. ZKC/ZME shall release control for 15° turns on aircraft 15 NM on either side of the ZKC/ZME boundary, and control for speed adjustment on contact.
d. Aircraft landing within 60 miles of the boundary must enter the receiving ARTCC’s airspace AOB FL230, and the receiving ARTCC must have control for descent and turns.
e. Data Block and Interim Altitude Procedures:
- Data blocks must reflect the aircraft’s assigned altitude at the time of handoff.
- Handoffs must be directed to the appropriate sector for the aircraft’s altitude assignment. Acceptance of a radar handoff constitutes approval for the aircraft to climb or descend to the displayed altitude.
- Interim altitudes are authorized and must represent valid altitude coordination. They must not be used to coordinate IAFDOF or supersede LOA altitude restrictions.
- When unable to approve the automated altitude, the receiving controller must coordinate with the transferring controller prior to acceptance.
f. Aircraft unable to comply with required routes or altitudes must be coordinated with the receiving ARTCC on an individual basis.
g. AIT for aircraft in level flight: Controller A initiates handoff to B before the aircraft enters B’s airspace. B accepts and initiates handoff to C. A transfers comms to C after observing C has accepted. A retains the option to transfer comms to B after handoff to B is complete.
Route & Altitude Assignments
Section titled “Route & Altitude Assignments”STL Turbojet Arrivals
| Qualifier | Route | Altitude |
|---|---|---|
| East of J180 (RNAV) | BOOSH STAR | AOB FL280 ¹ |
| East of J180 (Non-RNAV) | FAM direct KSTL | AOB FL240 |
| West of J180 (RNAV) | SGF.KAYLA STAR | |
| West of J180 (Non-RNAV) | SGF.KOOOP STAR |
¹ ZME shall release control for descent to FL240 15 NM from the ZKC/ZME boundary.
STL Turboprop Arrivals
| Qualifier | Route | Altitude |
|---|---|---|
| AOA 10,000 and East of J180 | MWA..KSTL or on a heading to overlie the BOOSH arrival track | AOB FL230 |
STL Area Departures
- STL area departures entering ZME east of J180 are released for climb 15 NM from the ZKC/ZME boundary.
STL Satellite Turbojet Arrivals (ALN, BLV, CPS, SUS)
| Airport | Qualifier | Route | Altitude |
|---|---|---|---|
| ALN, BLV, CPS, SUS | West of J180 | DELMA STAR or DELMA direct destination | AOB FL350 |
| ALN, BLV, CPS | East of J180 | AOB FL270 ¹ | |
| SUS | East of CGI | SLVER..KSUS | AOB FL270 |
| SUS | East of J180 | FAM.SLVER STAR | AOB FL270 |
¹ ZME shall release control for descent to FL240 15 NM from the ZKC/ZME boundary.
Kansas City (MCI, MKC) Arrivals
| Airport | Qualifier | Route |
|---|---|---|
| KMCI | RNAV | KRTNY or NELVY and MHOMS STAR |
| KMCI | NON-RNAV | SGF or KRAZO and TYGER STAR |
| KMKC | SGF or KRAZO and TYGER STAR |
Memphis (MEM) Arrivals
| Qualifier | Route | Altitude |
|---|---|---|
| RNAV | WHOLL/RZC/IGLOO.BRBQQ STAR | AOB FL340 ¹ |
| RNAV | LIT/FSM.LIT/HOBRK STAR | AOB FL340 ¹ |
| Non-RNAV | RZC/ARG.DAWGG STAR | AOB FL340 ¹ |
| Non-RNAV | LIT.UJM/UJM STAR | AOB FL340 ¹ |
¹ Only applicable for arrivals east of J41.
Nashville Area Arrivals (BNA, JWN, MQY, MBT)
Arrivals entering ZME from ZKC Sector 14 (FAM)/Sector 90 (BLUES) — assign the RYYMN/CHSNE STAR and route no further than RANTS on the RYYMN STAR. ZKC shall release control for lower on contact.
| Qualifier | Route | Altitude |
|---|---|---|
| On or East of J45 | RYYMN STAR | AOB FL310 |
| West of J45 | RYYMN STAR | AOB FL330 |
ORD Arrivals
- Aircraft entering the lateral boundaries of ZKC Sector 28: cleared via WELTS.TRTLL#/SHAIN#
- Aircraft entering the lateral boundaries of ZKC Sector 29: cleared via FTZ.TRTLL#/SHAIN#
DFW Arrivals
- ZKC shall clear DFW arrivals operating AOA FL240 no further than RRNET or LIT and the appropriate STAR. ZKC shall release control for turns direct FSM or RRNET on all aircraft, except those routed over LIT.
- ZKC shall clear DAL arrivals operating AOA FL240 via FSM or LIT and appropriate STAR.
Marion (MWA), Carbondale (MDH), and Cape Girardeau (CGI) Arrivals
- ZKC/ZME shall release control of these arrivals upon completion of radar handoff and transfer of communications.
Paducah (PAH) Arrivals
- Arrivals entering east of V9 are released for descent to 5,000 ft upon completion of radar handoff and transfer of communications.
Tulsa Area Arrivals
- ZME must clear arrivals to their destination airport (except high-altitude approach aircraft and aircraft at or below 6,000 ft) via the ATAs at the following altitudes:
- Arrival aircraft AOA 10,000 ft must cross the TUL 30 NM fix at 10,000 ft.
- Arrival aircraft between 9,000 and 6,000 ft must be assigned 6,000 ft.
- Arrival aircraft at 4,000 and/or 6,000 ft may be cleared direct destination or TUL VORTAC without regard to ATA.
- High-altitude instrument approach aircraft: clear to the appropriate IAF at 15,000 ft. Manual coordination required prior to entering tower airspace. Transfer of control point must be specified ZME.
- ZME releases arriving aircraft to the Tower for descent to 7,000 ft and turns up to 30° within 10 NM of the ZME/Tulsa boundary. Tower assumes responsibility for any point out. (Not applicable to high-altitude approach arrivals.)
Tulsa Departures
- Departures at 5,000 ft with a first fix outbound of FSM, HRO, LIT, or RZC must proceed via V140 or V74 (whichever appropriate).
- Tower must clear departing aircraft requesting 16,000 ft or above to maintain 15,000 ft and expect requested altitude 10 minutes after departure. All others assigned requested altitude.
- Tulsa ATCT releases control of departing aircraft AOA 11,000 ft to ZME for turns up to 30° either side of initial flight path. Center assumes responsibility for point outs.
- Tulsa ATCT must provide at least 5 NM separation (constant or increasing) between departures and/or enroute aircraft entering ZME airspace at the same altitude.
Tulsa Overflights
- Center must APREQ overflights AOB 5,000 ft through Tulsa ATCT airspace.
Springfield Area Arrivals from ZME (Except PLK/BBG)
- ZME must clear arrivals, operating east of the FSM ATCT delegated airspace, at or above 16,000 to 16,000 ft and direct their destination.
- ZME must clear arrivals below 16,000 to cross the common ZME/SGF boundary at an altitude correct for direction of flight.
- Within 10 NM of the common ZME/SGF boundary, ZME releases control for descent and turns.
Arrivals from FSM ATCT
- Aircraft landing at Monett (HFJ), Cassville (94K), Branson (BBG), Branson West (FWB), or Clark Downtown (PLK): assigned 5,000 ft prior to crossing the SGF/FSM common boundary.
- Aircraft landing at Bolivar (M17), Lebanon (LBO), Springfield (SGF), Aurora (2H2), Ava (AOV), or Stockton (M03):
- At or above 11,000: assigned 11,000 ft prior to crossing.
- At or below 10,000: assigned enroute altitude correct for direction of flight.
- FSM releases control of arrivals 10 NM from the common ZKC/ZME boundary.
- Overflights: cleared via routes and altitudes as filed or coordinated.
PLK Arrivals from ZME
- AOA 6,000: at or descending to 6,000 ft and direct PLK. All others verbally coordinated.
- ZME releases control for descent and turns within 10 NM of the ZME/SGF boundary.
BBG Arrivals from ZME
- Instrument approaches in use: route via CADAN direct BBG. Visual approaches: may route direct BBG.
- Assign 6,000 ft or as coordinated.
- ZME releases control for descent and turns within 10 NM of the ZME/SGF boundary.
Departures (except BBG) to ZME
- SGF clears departures to 15,000 ft or requested altitude (whichever lower); expect requested altitude 10 minutes after departure.
- SGF must provide at least 5 NM separation (constant or increasing) between departures and/or enroute aircraft entering ZME at the same altitude.
BBG Departures to ZME
SGF must coordinate the following on all BBG departures entering ZME:
- Callsign
- Departure Runway
- First Fix
HRO Approach Procedures
- ZME must receive approval from SGF ATCT for the procedure turn for the HRO GPS 18 approach.
- Coordination to “block for an approach into HRO” means SGF will block airspace parallel the east/west centerline of the GPS 18 FAC, extending 4 miles from the CAVEK, ADOKE, and FATGO fixes.
- When ZME advises the aircraft is ADKOE inbound, SGF discontinues blocking.
BBG Approach Procedures
- SGF ATCT must receive approval from ZME for the procedure turn for the BBG GPS/ILS 32 approach.
- Coordination to “block for an approach into BBG” means ZME will block airspace 5 NM west and 10 NM east of the FAC.
Arrivals from ZKC
Arrivals crossing the ZKC/ZME boundary west of T411: cross the boundary AOB FL230, descending to 16,000 ft. IAFDOF approved.
Arrivals east of T411 — cross the ZKC/FSM boundary at:
| Aircraft Altitude | Crossing Altitude |
|---|---|
| At or above 10,000 | 10,000 ft |
| Between 9,000 and 6,000 | 6,000 ft |
| Below 6,000 | Level at altitude appropriate for direction of flight |
Arrivals from SGF
| Destination | Requirement |
|---|---|
| Rogers (ROG) | 6,000 ft prior to crossing ZKC/ZME boundary |
| XNA, VBT, ASG, FYV, 5M5, SLG, 4M1, H34 (Huntsville) | AOA 10,000: assigned 10,000 prior to crossing boundary. AOB 9,000: assigned 6,000 prior to crossing. |
Departures to ZKC
- FSM clears departures to 15,000 ft or requested altitude (whichever lower); expect requested altitude 10 minutes after departure.
- ZKC has control for climb upon contact, for aircraft departing FSM ATCT terminal airspace, up to FL230.
- FSM must provide at least 5 NM separation (constant or increasing) between departures and/or enroute aircraft entering ZME at the same altitude.
- Overflights: cleared via routes and altitudes as filed or coordinated.
Sector Maps
Section titled “Sector Maps”
