Skip to content
ZME Wiki

ZME-ZID Letter of Agreement

Definitions

Section titled “Definitions”
TermMeaning
BoundaryZME/ZID common boundary
CoordinatedPassed as the final requested or interim altitude, or last cleared route
↑Climbing to
↓Descending to
IAFDOFInappropriate Altitude For Direction Of Flight

Airspace Delegation

Section titled “Airspace Delegation”

ZME delegates to ZID the responsibility for control of aircraft within the area depicted in Attachment A (airspace delegation map) from the surface up to and including 13,000 ft.

General Procedures

Section titled “General Procedures”

a. Specific routes and altitudes must be assigned for arrivals and departures per Attachments B and C. Deviations must be coordinated between the appropriate sector controllers.

b. Except where otherwise specified, aircraft can climb/descend to the altitude displayed in the full data block without verbal coordination, provided the altitude is correct for direction of flight. The transferring facility must effect a handoff to the sector controlling the assigned altitude.

c. Either facility can change an aircraft’s beacon code after receipt of radar handoff and communications transfer.

d. When opening, de-combining, combining, or closing adjacent sectors, each facility must ensure that affected sectors/facilities are notified.

e. On handoff, the receiving controller has control for turns up to 15° within 15 NM of the boundary. Heading information forwarded via fourth line supersedes this authorization.

f. Aircraft not covered in Attachments B or C arriving at airports within 30 NM of the boundary shall cross the boundary AOB 11,000 ft at an appropriate altitude for direction of flight. ZID and ZME shall release control of these aircraft on contact.

AIT Procedures

Section titled “AIT Procedures”

a. EVV/OWB arrivals — For arrivals AOA 14,000 ft: PAH LO or BWG LO must clear aircraft to cross the boundary AOB FL230 descending to 14,000 and initiate a handoff to EVV LO.

  • If traffic is not a factor: EVV LO accepts and initiates handoff to EVV ATCT. PAH LO/BWG LO transfers comms to EVV ATCT at the boundary.
  • If traffic is a factor: EVV LO verbally coordinates with PAH LO/BWG LO prior to accepting.

b. HOP, CKV, 1M9, HVC, M21, 2M0 arrivals — For arrivals AOA 11,000 ft: EVV LO must clear aircraft to 11,000 and initiate a handoff to BWG LO.

  • If traffic is not a factor: BWG LO accepts and initiates handoff to HOP ARAC. EVV LO transfers comms to HOP ARAC at the boundary.
  • If traffic is a factor: BWG LO verbally coordinates with EVV LO prior to accepting.

Route & Altitude Restrictions

Section titled “Route & Altitude Restrictions”
AirportQualifierRouteAltitudeSpecial
CVGWest of FAPERTERGE.SARGO# or TERGE..HEREE..SARGOAOB FL310
CVGEast or over FAPERJRICO.SARGO#AOB FL230
CVG Satellites (LUK, HAO, I69, K62)PXV/IMP SectorsJRICO..HEREE..SARGO..JIMURAOB FL330
CVG Satellites (LUK, HAO, I69, K62)LOU/MYS SectorsMYS..SARGO..JIMURAOB FL270
EVV and SatellitesThru ZID 17/19AOB FL230, ↓ 14KAIT Procedures
IND and SatellitesFrom ZME 05/25/33, RNAVTERGE.SMUKE#AOB FL330
IND and SatellitesFrom ZME 05/25/33, Non-RNAVPXV.RACYR#AOB FL330
IND and SatellitesFrom ZME 40/41/63/61, RNAVHAGAL.GIBBS#AOB FL330
LEXEast of GUMMAIIU..FEDRA or ..UNCKLAOB FL270, ↓ FL240
SDF / LOU / JVYJetsMOOCH/BUMPY.MBELL#AOB FL290May clear direct PENBE
SDF / LOU / JVYProps, east of GUMMAAOB 13K
SDF / LOU / JVYProps, west of GUMMAAOB FL230
BNA Terminal AreaJetsSWAPP..DNUTS..ARUSH..COBBZ.LEDDL#AOB FL230

Sector Maps

Section titled “Sector Maps”

ZID HI Sectors