Welcome to Minneapolis.

General Overview

As a general rule, all arrival procedures are filed with the route in an aircraft's flightplan. This cuts down on the number of transmissions and controller workload.

RNAV Optimized Profile Descent Procedures

As of AIRAC 1503, RNAV Optimzed Profile Descent profiles are the preferred arrival routes into MSP for turbojet aircraft only. These arrival routes are the MUSCL, KKILR, BAINY, TORGY, NITZR, and BLUEM. These types of arrival routes are designed to minimize or eliminate steps during descent, saving fuel and time. Please file these arrivals, if able, into MSP.

Depending on the direction of arrival, Minneapolis Center will instruct aircraft on these arrivals to "descend at pilot's discretion, maintain FL240" or "descend via". In both instances, pilots should plan a continuous descent path to meet the "hard" altitude fixes on the arrival. Pilots should not descend to meet the minimum altitude possible for an "at-or-above" fix.

Per the chart instructions for these procedures, pilots should descend via their cruise Mach number until reaching 280 knots, then descend at 280 knots until further slowed by the restrictions by the STAR.

Conventional Arrival Procedures

Pilots operating non-jet aircraft into MSP and all types of aircraft into MSP Satellite Airports (ANE, STP, FCM, etc.) should file and expect to fly "conventional" or "legacy" arrival procedures. These aircraft are typically issued "descend at pilot's discretion, maintain FL240". It is imperative that pilots do not descend immediately when issued this instruction, but rather descend at the computed top of descent in order to meet hard altitude restrictions.

Once reaching the low Minneapolis Center sector, aircraft will be issued a crossing restriction in line with the altitude restrictions published on the chart. If a speed restriction is assigned, aircraft are expected to meet the assigned speed by the crossing restriction.

If arriving into Minneapolis, be careful to fly the appropriate assigned headings on the chart. For example, the SKETR arrival specifies a heading of 120° after MONKY when landing 30L/R, and a heading of 170° after CHYMP when landing runway 35.

Initial Contact

When checking on with Minneapolis Approach, advise the controller of the current ATIS code at your destination airfield. The controller will usually respond with a runway assignment and any relevant information or control instructions. From entering M98's airspace to gate arrival, please give the controller your full attention, as frequencies will be busy and instructions will be issued in rapid succesion to multiple aircraft. Use of ACARS or TeamSpeak/Discord chat functions should be kept at a minimum once in the terminal environment.

By this point, you should have familiarized yourself with the arrival procedure and runway transition. Note the instructions on each of the arrivals, particularly on arrivals with a downwind portion (BLUEM landing 12R, e.g.) Note that these arrivals typically assign a heading to fly after the last fix (heading 300 after GREAK, e.g.), and pilots are expected to comply. Once on one of these assigned headings, pilots should expect vectors to the airport. At no point should a pilot execute a base turn or execute an RNAV approach unless cleared to do so.

Final Approach

Depending on the traffic levels, you may be issued another frequency change to the Final Approach controller. If you are landing at an M98 satellite airport, you will be handed off to the satellite controller (MSP_E_APP) who will sequence you onto your requested approach at your destination airport. When instructed, please check on with the controller as soon as possible. Not doing so will lead to delays.

When instructed to turn, it is imperative to initiate the turn upon receipt prior to or during your readback. Not doing so will lead to missed localizer captures. When cleared for the approach, the controller may assign a speed restriction to the final approach fix ("maintain 170 knots or greater until HAMML", e.g.) For sequencing purposes, do not reduce to final approach speed until inside of the final approach fix.

Gate Assignment

Before arriving at MSP, decide where you are parking. Either on approach or after landing, you will be asked for your gate number in order to facilitate taxi. Please have an airport diagram available for reference for your assigned taxi route.

Landing & Taxi

ZMP simulates ASDE-X. Please taxi with your transponder with altitude encoding on ("Mode C") while on all taxiways and runways. If unable, advise controllers as soon as practical.

Do not cross any runway without a clearance from a controller. This rule applies to all active, inactive, and closed runways.

There is no need to advise the controller that you have arrived or parked at the gate.

If you will be departing MSP, please obtain the most recent ATIS information and contact MSP_DEL (or MSP_GND if MSP_DEL is not online) to obtain your clearance. Be prepared to copy amendments, as routes may change due to weather or traffic volume.

Standard Instrument Departures

All Minneapolis SIDs are radar vector procedures. Departures from MSP are assigned a heading and are advised to "climb via SID". As such, on departure, pilots are required to fly the assigned heading and to comply with all altitude restrictions on the chart on the climb to their assigned top altitude.

Minneapolis has 14 published SIDs; 4 of which are RNAV. The 10 non-RNAV departures are COULT, DARWIN, KBREW, MEADOW LAKE, MINNEAPOLIS, ORSKY, ROCHESTER, SCHEP, WLSTN, and ZMBRO. The 4 RNAV departures are LEINY, HESTIN, SLAYER, and SMERF. The HESTIN, SLAYER, and MEADOW LAKE procedures are for MSP runway 17 departures only and are rarely used.

Pushback & Taxi

Pushback onto movement areas (e.g. taxiways) requires a clearance from MSP_GND. As such, a clearance to push must be obtained off of most gates at MSP, excluding those in the alley between Concourses E and F and at Concourse A.

Taxi instructions at MSP tend to be lengthy. Be sure to have an airport diagram for reference, and to copy down taxi instructions accurately. Pilots are reminded that in order to cross any runway, a clearance must be obtained.

Pre-Departure Clearance

MSP Clearance Delivery uses text-based Pre-Departure Clearances which simulate PDCs on ACARS-equipped aircraft. If your route of flight and other flightplan information is valid, exect to receive two private messages from the appropriate clearance delivery controller. The PDC formatting at KMSP is as follows:

**** PREDEPARTURE CLEARANCE **** | FLTS MORE THAN 2 HRS PAST SKED DEP TIME MUST VERIFY PDC IS STILL VALID WITH ATC. | < CALLSIGN > DEPARTING KMSP TRANSPONDER < CODE > SKED DEP TIME < TIME > EQUIP < EQUIP > FILED FLT LEVEL < CRZALT > | ROUTING -CLEARED AS FILED- < ROUTE >

CLIMB VIA SID TOP ALTITUDE < TOP ALT > | GND CTL FREQ < FREQ >/DPTR CTL FREQ < FREQ > | PLAN RWY < RWY > ATC MAY CHANGE ANY TIME

Ground Metering Procedures

During the busiest periods of an event, departure slot and ground metering procedures may be utilized in order to efficiently manage departure traffic from the airport. In the event that a flight booking system is used, priority will be given to pre-booked flights. If this procedure is used, the ATIS will be updated with the relevant NOTAM. It is very important that all airline traffic contact MSP_DEL prior to pushing back during metering procedures so that a proper departure sequence can be maintained. When contacting MSP_DEL for push, check on with the current ATIS information, gate, and assigned beacon code. (e.g. "Minneapolis Ground, Delta 589, gate C4.") Clearance Delivery will advise you monitor the appropriate MSP_GND controller, who will approve your push in sequence, and assign you a departure runway.