Skip to content
Know before you taxi

All Products

My Airports

Your shortcuts, saved on this device. Search to add an airport.

No airports saved yet. Add the fields you visit most.

Ask ATIS

KMSP Runway 17/35 — Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field

8,000 × 150 ft concrete · true headings 170° / 350° · field elevation 842 ft

Runway 17/35 at Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (KMSP) in Minneapolis, MN is 8,000 ft long and 150 ft wide, concrete, with true headings 170° and 350°. The FAA record lists Localizer/DME (no glideslope) on runway 17. Over 2005–2025 the wind gave runway 17 the headwind 51.6% of the time and runway 35 48.4%, with a crosswind above 15 kt in 1.8% of wind hours. KMSP publishes a digital ATIS, so this page shows the runway the tower is actually using right now, today's configuration changes, and a growing record of how often each end is assigned.

Ask ATIS AIAsk anything about KMSP's weather, runways or delays, or search another airport.

Runway 17/35 — current operational status

What the D-ATIS, the tower and current NOTAMs state now. The published FAA baseline (NASR) is a separate line in the overview below and does not reflect temporary closures.

NO CLOSURE REPORTED
  • The current D-ATIS names no closure, restriction or outage for it. No received NOTAM closes or restricts this runway, but the NOTAM stream has no complete initial load yet — verify NOTAMs before flight.

Sources: Published FAA baseline (OurAirports/NASR record) · FAA NOTAMs · D-ATIS · D-ATIS 0253Z (9:53 PM CDT). Runway NOTAMs stream live from the FAA NOTAM Management Service (SWIM); the official text is shown verbatim below the card. Always confirm with a current briefing.

NOTAMs for runway 17/35

Official text as issued; grouped for reading only. “Scheduled” means not yet in effect. NOTAMs are received live from the FAA NOTAM Management Service through SWIM and recorded since Sep 19, 2026; a NOTAM issued before that and not re-issued since may be missing. Get a full briefing before flight.

Obstruction · 2
  • 09/622 · DOM09/30 1300Z (8:00 AM CDT) → 10/31 2200Z (5:00 PM CDT)
    !MSP 09/622 MSP OBST CRANE (ASN UNKNOWN) 445153N0931349W (.27NM E APCH END RWY 35) UNKNOWN (150FT AGL) FLAGGED AND LGTD 2609301300-2610312200
  • 09/397 · INTL09/21 0816Z (3:16 AM CDT) → 12/31 1400Z (8:00 AM CST)
    !MSP 09/397 MSP OBST CRANE (ASN UNKNOWN) 445121N0931436W (0.67NM SW APCH END RWY 35) 
    UNKNOWN (124FT AGL) FLAGGED AND LGTD 2609210816-2612311400
Taxiway · 4
  • 09/538 · DOM09/26 2100Z (4:00 PM CDT) → 12/26 1200Z (6:00 AM CST)
    !MSP 09/538 MSP TWY N SFC PAINTED HLDG PSN SIGNS AT RWY 17/35 REMOVED 2609262100-2612261200
  • 09/461 · DOM09/23 2055Z (3:55 PM CDT) → 12/31 2359Z (5:59 PM CST)
    !MSP 09/461 MSP TWY N SFC PAINTED HLDG PSN SIGNS BTN RWY 17/35 AND TWY K REMOVED 2609232055-2612312359
  • 09/460 · DOM09/23 2046Z (3:46 PM CDT) → 12/31 2359Z (5:59 PM CST)
    !MSP 09/460 MSP TWY N HLDG PSN MARKINGS BTN RWY 17/35 AND TWY K REMOVED 2609232046-2612312359
  • 09/459 · DOM09/23 2040Z (3:40 PM CDT) → 12/31 2359Z (5:59 PM CST)
    !MSP 09/459 MSP TWY N CL MARKINGS BTN RWY 17/35 AND TWY K REMOVED 2609232040-2612312359
Runway visual rangeSTDDS 0315Z (10:15 PM CDT)
17 TDZ 6000+ ↑ · MID 6000+ ↑ · RO 6000+ ↑ · lights edge 1 / CL 1
35 TDZ 6000+ ↑ · MID 6000+ ↑ · RO 6000+ ↑ · lights edge 1 / CL 1

Feet, touchdown / midpoint / rollout; 6000+ is the reportable maximum and “off” means the sensor is not reporting (runway not in use). Light settings 0 (off) to 5. Runway lights are on. Not an FAA product; verify with the current METAR and ATIS.

Current active runways at KMSP

As stated by the airport’s D-ATIS — the facility’s own broadcast, not an estimate.

Information Hotel · 0253Z (9:53 PM CDT)

Flow: Northwest flow— the compass direction of the stated arrival ends

Runway 17/35 in this configuration: not listed for arrivals or departures (D-ATIS)

Arrivals
30L30R
Departures
30L30R

This D-ATIS configuration has been stated since 0953Z (4:53 AM CDT).

Show the D-ATIS text
MSP ARR INFO H 0253Z. 02006KT 10SM FEW130 08/03 A3027 (THREE ZERO TWO SEVEN) RMK AO2 SLP254 T00780028 50009. VISUAL RWY 30L APCH IN USE, VISUAL RWY 30R APCH IN USE. NOTICE TO AIRMEN. RWYS 4, 22 CLSD. RWYS 12R AND 12L INNER MARKER OTS. CTN, BIRDS NEAR MSP. READ BACK HS AND ALT. ALL ACFT TAXI WITH TRANSPONDER AND ALTITUDE ENCODING ON. ...ADVS YOU HAVE INFO H.
MSP DEP INFO U 0253Z. 02006KT 10SM FEW130 08/03 A3027 (THREE ZERO TWO SEVEN) RMK AO2 SLP254 T00780028 50009. DEPARTING RWY 30L, RWY 30R. NOTICE TO AIRMEN. RWYS 4, 22 CLSD. ALL ACFT CTC METERING ON ONE THREE THREE POINT FIVE SEVEN WHEN READY TO PUSHBACK OR TAXI. CTN, BIRDS NEAR MSP. READ BACK HS AND ALT. ALL ACFT TAXI WITH TRANSPONDER AND ALTITUDE ENCODING ON. ...ADVS YOU HAVE INFO U.

Current wind on Runway 17/35

Wind from the north-northeast (020°) at 6 kt

METAR 0253Z (9:53 PM CDT)
Runway 17
Tailwind
5 kt
Crosswind
3 ktfrom left
Runway 35
FAVORED BY WIND
Headwind
5 kt
Crosswind
3 ktfrom right
042212L30R12R30L1735N020°/6 kt
  • arrivals
  • departures
  • LAHSO hold-short
  • closed

Layout from FAA NASR runway-end coordinates; the selected runway is highlighted and the ends the D-ATIS states in use are marked at their own threshold. Not for navigation. Official FAA diagram ↗

Wind-favored runway at KMSP right now: 04 (5 kt headwind) — a different runway than this one.

Components use TRUE runway headings and TRUE METAR wind. “Favored by wind” is arithmetic, not an ATC assignment.

Today's runway configuration at KMSP

Meaningful configuration changes recorded from the D-ATIS — the facility's own statements, not estimates.

Oct 29, 2026 (airport-local day): 1 configuration change since local midnight, from the D-ATIS broadcasts ATIS Alerts recorded. A change is a different arrival or departure set; a new ATIS letter with the same runways is folded into the row it belongs to. The history section below counts the same way over rolling windows.

  1. 05:02Z12:02 AM CDT(in effect since before the day began)
    4.8 h
    Arrivals
    30L
    Departures
    30L
    ATIS: Golf → Hotel → Uniform → India → Victor → Juliett → Whiskey → Kilo → X-ray → Lima → Oscar → Mike → PapaNorthwest flowIn effect at the start of the day
  2. 09:53Z4:53 AM CDT
    17.4 h · current
    Arrivals
    30L30R
    Departures
    30L30R
    ATIS: Alfa → Quebec → Bravo → Romeo → Charlie → Sierra → Delta → Tango → Echo → Uniform → Foxtrot → Oscar → Golf → Papa → Hotel → Quebec → India → Romeo → Juliett → Sierra → Kilo → Tango → Lima → Uniform → Mike → Victor → Alfa → November → Bravo → Oscar → Charlie → Papa → Delta → Quebec → Echo → Romeo → Foxtrot → Sierra → Golf → Tango → Hotel → UniformNorthwest flowArrivals +30R · Departures +30R

Runway 17/35 outlook

Where runway 17/35 stands now and which runway at KMSP is likely over the next 12 hours — an estimate, not an ATC assignment.

Time · runway 17/35 · airport-wide outlook · confidence · forecast wind · why

  1. Now0317Z · 10:17 PM CDT·17/35: not in the stated configuration·Current airport configuration (D-ATIS): arrivals 30L · 30R · departures 30L · 30R·stated·wind 020° at 6 kt
  2. +1 h0417Z · 11:17 PM CDT·17/35: 35 likely·airport-wide likely 35 then 30L·North flow·4 kt headwind, 3 kt crosswind·Medium 68%·wind 020° at 5 kt·Why TAF forecast wind 020° at 5 kt favors north-facing runway ends: 4 kt headwind and 3 kt crosswind on 35 versus 1 kt headwind on 30L.|This would be a change from the current 30L and 30R configuration.|Runways 04 and 22 are excluded: stated closed.|Recorded use with wind from the north: 30R named for arrivals 61% of 70 h (D-ATIS).|Confidence falls with forecast distance (+1 h).
  3. +2 h0517Z · 12:17 AM CDT·17/35: not favored·airport-wide likely 30R·Northwest flow·Low 55%·wind VRB at 3 kt·Why TAF wind variable at 3 kt: no steady direction, so wind does not decide the runway.|In recorded use, 30R is the end this airport most often named for arrivals in calm wind (D-ATIS).|The airport is already using 30L and 30R.|Runways 04 and 22 are excluded: stated closed.
  4. +3 h0617Z · 1:17 AM CDT·17/35: not favored·airport-wide likely 30R·Northwest flow·Low 55%·wind VRB at 3 kt·Why TAF wind variable at 3 kt: no steady direction, so wind does not decide the runway.|In recorded use, 30R is the end this airport most often named for arrivals in calm wind (D-ATIS).|The airport is already using 30L and 30R.|Runways 04 and 22 are excluded: stated closed.
  5. +6 h0917Z · 4:17 AM CDT·17/35: not favored·airport-wide likely 30R·Northwest flow·Low 55%·wind VRB at 3 kt·Why TAF wind variable at 3 kt: no steady direction, so wind does not decide the runway.|In recorded use, 30R is the end this airport most often named for arrivals in calm wind (D-ATIS).|The airport is already using 30L and 30R.|Runways 04 and 22 are excluded: stated closed.
  6. +12 h1517Z · 10:17 AM CDT·17/35: not favored·airport-wide likely 12R then 12L·Southeast flow·8 kt headwind, 3 kt crosswind·Low 22%·wind 100° at 9 kt·Why TAF forecast wind 100° at 9 kt favors east-facing runway ends: 8 kt headwind and 3 kt crosswind on 12R versus 8 kt headwind on 12L.|This would be a change from the current 30L and 30R configuration.|Runways 04 and 22 are excluded: stated closed.|Recorded use with wind from the east: 12L was named for arrivals 100% of 24 h (D-ATIS).|Confidence falls with forecast distance (+12 h).

ATIS Alerts Predicted Runway is an estimate from the TAF wind forecast, runway geometry (most headwind, crosswind penalised, tailwind over 5 kt avoided, longest runway breaks ties), the current stated configuration and any stated closures; recorded D-ATIS use since Sep 18, 2026 (720 h) is an input wherever a wind sector has 24 h on record. Each row lists its reasons; “no runway favored” is a genuine answer under variable or light wind, never replaced by a guess. It is not an ATC assignment and does not know about noise abatement or traffic flow unless the recorded history shows them. TAF issued 0251Z (9:51 PM CDT).

Runway 17/35 equipment and lighting

What the FAA record lists for each end, annotated with current NOTAM and D-ATIS outages.

Runway 17
Approach lighting
Not available
Visual glide slope
PAPI (4-box, right side)
Runway edge lighting
HIRL (high intensity)
Centerline lighting
Available
Touchdown zone lighting
Not available
REIL
Available
ILS
Localizer/DME (no glideslope)
I-TJZ · 110.95 MHz
Localizer
Available
Glideslope
Not available
DME
Available
channel 46Y
Marker beacons
Not available
RVR
touchdown, midpoint, rollout
Runway markings
Non-precision instrument
condition good
Arresting system
Not available
Runway 35
Approach lighting
ALSF-2
Visual glide slope
PAPI (4-box, left side)
Runway edge lighting
HIRL (high intensity)
Centerline lighting
Available
Touchdown zone lighting
Available
REIL
Not available
ILS
ILS/DME
I-BMA · 110.95 MHz · CAT III
Localizer
Available
Glideslope
Available
3°
DME
Available
channel 46Y
Marker beacons
IM
RVR
touchdown, midpoint, rollout
Runway markings
Precision instrument
condition good
Arresting system
Not available

Source: FAA NASR 28-day subscription, cycle effective 2026-10-01 (equipment on record) · FAA NOTAMs via SWIM (live)and the current D-ATIS (outages). “Not available” means the FAA record lists no such equipment for the end; nothing here is inferred. An outage annotation is only ever a reading of the official text shown with it. Declared distances are not shown in this phase.

Land and hold short operations

LAHSO hold-short points and available landing distances on the FAA record, and whether the current D-ATIS reports LAHSO in effect.

Runway 17

No LAHSO hold-short point on the FAA record for this end.

Runway 35

No LAHSO hold-short point on the FAA record for this end.

The current D-ATIS does not state LAHSO in effect. Source: FAA NASR cycle 2026-10-01; D-ATIS text read by ATIS Alerts.

Frequencies for runway 17/35

Tower, ground, clearance, ATIS and approach frequencies from the FAA record, labelled by what they apply to.

Frequencies serving runway 17/35 at KMSP
ServiceFrequencyApplies to
Tower123.675Runway 17/35
Tower273.55Airport-wide
Ground121.8Sector: N
Ground121.9Sector: S
Ground127.925Sector: W
Ground348.6Airport-wide
D-ATIS120.8Departure
D-ATIS135.35Arrival
D-ATIS239.275Arrival
Show all frequencies (9 more: approach and departure sectors, secondary and other)
Frequencies serving runway 17/35 at KMSP
ServiceFrequencyApplies to
UNICOM122.95Airport-wide
Approach / departure118.725Runway 17/35
Approach / departure119.3Runway 17/35
Approach / departure124.7Sector: SOUTH OR EAST OF ARR RWY
Approach / departure125.75Sector: NORTH OR WEST OF ARR RWY
Approach / departure132.975Sector: E OF DEP RWY 17
Approach / departure284.7Airport-wide
Approach / departure335.5Airport-wide
Approach / departure335.65Airport-wide

Rows marked “Runway 17/35” are sectorized to this runway complex in the FAA record; “Airport-wide” rows serve every runway. Source: FAA NASR FRQ, cycle 2026-10-01. Verify on the current chart supplement before use.

Runway 17/35 overview

Physical characteristics from the FAA-derived runway record.

Length
8,000 ft
Width
150 ft
Surface
Concrete · Good condition
Surface treatment
Grooved
Weight bearing (lb)
S 100k · D 200k · 2D 400k · 2D/2D2 850k
PCN
1840
Runway lights
Lighted
Airport elevation
842 ft
Published FAA baseline
Open
Published NASR record; does not reflect temporary closures or restrictions. Current operational status is the card at the top of the page.
Runway 17
True heading
170°
Magnetic
170°
Published FAA baseline
Open
Threshold elevation
840 ft
TDZ elevation
840 ft
Displaced threshold
None on record
Threshold crossing height
60 ft
Visual glide path
3°
Controlling obstruction
tree, 52 ft, 1,990 ft from threshold, 34:1 slope
Runway 35
True heading
350°
Magnetic
350°
Published FAA baseline
Open
Threshold elevation
833 ft
TDZ elevation
834 ft
Displaced threshold
None on record
Threshold crossing height
71 ft
Visual glide path
3°

Runway 17/35 numbers are magnetic; the stored geometry and every wind calculation on this page are TRUE north, so they never need a variation correction. Magnetic headings use the FAA's published variation for this airport, 0.0°E (2015), the same value printed on the FAA airport diagram. Surface condition, treatment, weight bearing, thresholds and traffic pattern are from the FAA NASR record (cycle 2026-10-01); lighting, ILS and LAHSO are in their own sections above. Declared distances are not shown in this phase.

Configuration history at KMSP

Observed runway usage: how often the D-ATIS named each end, by window, flow, wind and time of day (the facility's own statement).

D-ATIS runway history at KMSP
720 hours collected since Sep 18, 2026
  • 7-day analysis: Ready
  • 30-day analysis: Ready
  • 90-day analysis: Collecting · 30 / 90 days
  • 12-month analysis: Collecting · 30 / 365 days

Runway percentages are measured independently. Multiple runways can be active simultaneously, so totals may exceed 100%.

Last 24 hours
2 configuration changes · 2 distinct configurations · 24 h recorded
Most-used arrival ends at the airport
30L (100%) · 30R (75%)
Most-used departure ends
30L (100%) · 30R (75%)
Runway 17
Arrivals0%
Departures0%
Runway 35
Arrivals0%
Departures0%

Insufficient history for flow shares: 24 of the 48 hours of stated configuration needed have been recorded.

Last 7 days
27 configuration changes (≈ 3.9 per day) · 11 distinct configurations · 7 days recorded
Most-used arrival ends at the airport
12L (56%) · 12R (50%) · 30L (40%)
Most-used departure ends
12L (56%) · 17 (56%) · 12R (50%)
Runway 17
Arrivals0%
Departures56%
Runway 35
Arrivals1%
Departures0%
Flow
  • Southeast flow56%(94 h)
  • Northwest flow43%(73 h)
  • Mixed configuration1%(1 h)
Most common configurations
  • 39% · arrivals 12L · 12R · departures 12L · 12R · 17(Southeast flow)
  • 30% · arrivals 30L · 30R · departures 30L · 30R(Northwest flow)
  • 8% · arrivals 12L · 12R · departures 12L · 12R(Southeast flow)
Last 30 days
74 configuration changes (≈ 2.5 per day) · 21 distinct configurations · 30 days recorded
Most-used arrival ends at the airport
12L (52%) · 12R (51%) · 30R (43%)
Most-used departure ends
12L (51%) · 12R (49%) · 30R (43%)
Runway 17
Arrivals0%
Departures29%
Runway 35
Arrivals1%
Departures0%
Flow
  • Southeast flow54%(390 h)
  • Northwest flow45%(324 h)
  • North flow1%(5 h)
  • Mixed configuration0%(1 h)
Most common configurations
  • 39% · arrivals 30L · 30R · departures 30L · 30R(Northwest flow)
  • 22% · arrivals 12L · 12R · departures 12L · 12R · 17(Southeast flow)
  • 22% · arrivals 12L · 12R · departures 12L · 12R(Southeast flow)
How the facility used runways by wind
Wind fromHours17 arrivals35 arrivals17 departures35 departures
N (338–023°)700%9%6%0%
E (068–113°)240%0%100%0%
SE (113–158°)1260%0%46%0%
S (158–203°)520%0%54%0%
SW (203–248°)1020%0%28%0%
W (248–293°)300%0%0%0%
Calm / light (< 5 kt)2970%0%22%0%
Use by time of day (airport-local)
night (239 h)
17 arr 0%35 arr 0%
morning (180 h)
17 arr 0%35 arr 3%
afternoon (181 h)
17 arr 0%35 arr 1%
evening (120 h)
17 arr 0%35 arr 0%
0003060912151821

Bars: share of each local hour in which an end of this runway was named for arrivals. Patterns are described, not explained.

Observed runway usage — 720 hours of D-ATIS runway configuration history collected · 21 distinct configurations observed · 1,803 D-ATIS broadcasts recorded · through Oct 30, 2026. Shares are the fraction of recorded hours in which the D-ATIS named each end. Wind sectors use the wind reported when each configuration began. Nothing here is inferred from wind; the wind-favored analysis for KMSP is a separate module. 90-day, 12-month and seasonal views appear once the record is long enough.

Historical wind and crosswind on runway 17/35

20-year hourly climatology from the ASOS archive, computed per runway end.

From 175,075 hourly observations at KMSP (2005–2025), 157,373 with a steady wind direction (10.1% calm, variable or direction-less). One observation per clock hour; TRUE headings against TRUE wind.

Crosswind on runway 17/35 (either end)

Mean crosswind
5.1 kt
median 4.3 kt
90th / 95th percentile
10.2 / 12.3 kt
max 31.6 kt
Above 10 kt
10.3%
> 15 kt: 1.8% · > 20 kt: 0.2%
Gust crosswind > 15 kt
7.8%
90th pct gust 13.2 kt
0%33%67%58%0–5 kt32%5–10 kt8.5%10–15 kt1.5%15–20 kt0.2%20–25 kt0.0%25+ kt
Share of wind hours by crosswind band on runway 17/35 at KMSP, 2005–2025
Crosswind (kt)Share of wind hours
0–558%
5–1031.7%
10–158.5%
15–201.5%
20–250.2%
25+0%

Strongest-crosswind month on average: Apr; calmest: Aug. Percentiles are streaming approximations (t-digest), accurate to about 0.1 kt.

Runway 17

Headwind
51.6%
of wind hours
Tailwind > 5 kt
26.6%
> 10 kt: 8.5%
Most wind-favored end
16.2%
of steady-wind hours, 17 had the most headwind of every end at KMSP

Runway 35

Headwind
48.4%
of wind hours
Tailwind > 5 kt
25.6%
> 10 kt: 6.5%
Most wind-favored end
14%
of steady-wind hours, 35 had the most headwind of every end at KMSP

“Most wind-favored end” is meteorological analysis: the share of steady-wind hours (2005–2025) in which this end had the most headwind of every open runway end at KMSP. It does not mean ATC selected the runway that often (parallel ends with the same heading share the credit equally). Observed runway use, where available, is the configuration-history section above.

By wind direction

Wind-favored share of runway 17 and 35 by wind sector, 2005–2025
Wind fromShare of wind hours17 favored35 favoredMean crosswindCrosswind > 15 kt
N 338–023°13%0%83.6%1.9 kt0%
NE 023–068°6%0%0%6.3 kt1.2%
E 068–113°9%0%0%8.2 kt3.9%
SE 113–158°17%24.7%0%4.3 kt0.2%
S 158–203°14%83.9%0%1.7 kt0%
SW 203–248°10%0%0%5.7 kt1.3%
W 248–293°14%0%0%8.5 kt7.4%
NW 293–338°17%0%20.9%5.6 kt0.8%

By time of day (airport-local)

morning
17 favored 16.3% · 35 14.9%
mean crosswind 5 kt · calm 10.8%
afternoon
17 favored 17.9% · 35 13.3%
mean crosswind 6 kt · calm 7.7%
evening
17 favored 16.4% · 35 13.1%
mean crosswind 4.9 kt · calm 6.3%
night
17 favored 14.7% · 35 14.5%
mean crosswind 4.4 kt · calm 13.3%

Seasonal runway conditions

037JanFebMarAprMayJunJulAugSepOctNovDec
Mean crosswind on runway 17/35 at KMSP by month, 2005–2025
MonthMean crosswind (kt)
Jan5.0 kt
Feb5.3 kt
Mar5.4 kt
Apr6.1 kt
May5.3 kt
Jun5.2 kt
Jul4.4 kt
Aug4.3 kt
Sep4.5 kt
Oct5.3 kt
Nov5.0 kt
Dec5.1 kt
Monthly wind and weather statistics for runway 17/35 at KMSP, 2005–2025
MonthPrevailingMean windGustyMean xwxw > 10xw > 15xw > 2017 tail > 535 tail > 5IFRTSFog
JanNW7.6 kt12%5 kt8.5%1%0.1%31.1%18.4%11.7%0%12.9%
FebNW7.9 kt14.7%5.3 kt11.2%1.9%0.2%34%17%8.4%0%9.9%
MarSE8.4 kt18.6%5.4 kt12.6%2.5%0.4%31.3%24.7%8.4%0.09%9.7%
AprN9.3 kt26.6%6.1 kt18%3.8%0.6%34.5%23.5%5.6%0.5%7.2%
MaySE8.2 kt21.8%5.3 kt12.9%2.2%0.3%25.9%28.8%3.5%1.09%4.7%
JunSE7.7 kt19.5%5.2 kt10.4%1.6%0.2%21.6%29%2.5%1.93%3.1%
JulS6.9 kt15.4%4.4 kt6.2%0.9%0.1%20.7%29.6%1.4%1.77%2.1%
AugSE6.7 kt12.1%4.3 kt5.3%0.5%0.1%18.5%29.1%3.3%1.52%3.3%
SepSE7.4 kt15.4%4.5 kt6.7%0.9%0.1%19.5%34.7%3.1%0.92%3.6%
OctNW8 kt19.6%5.3 kt12.2%2.5%0.4%26.7%26.3%5.3%0.29%6.2%
NovNW8.1 kt17.5%5 kt10.1%1.7%0.3%28.6%26.2%7.2%0.12%8.7%
DecW7.6 kt11.8%5.1 kt9.3%1.7%0.2%25.8%20.6%16%0.02%18.1%

IFR, thunderstorm (TS) and fog columns are airport-wide shares of hours; the crosswind and tailwind columns are specific to this runway. Prevailing = most common 45° wind sector among wind hours.

Runway 17/35 closure history

Kept per source with its provenance: D-ATIS-observed, NOTAM-observed and the FAA published baseline are never merged.

D-ATIS observed · since tracking began Sep 18, 2026 · coverage 30 / 30 days
  • 17 reported closed on 17 calendar days (904 broadcasts; first seen 2026-09-30 03:20Z, last seen 2026-10-23 09:35Z)
  • 35 reported closed on 17 calendar days (904 broadcasts; first seen 2026-09-30 03:20Z, last seen 2026-10-23 09:35Z)

Normalised status: closed on those days as stated in the broadcast text (shown verbatim in the live band above). History is incomplete until 30 days of coverage exist.

NOTAM observed · recorded since Sep 19, 2026 (no archive before that)
  • 10/669 · partial closure (partial) · runway 17/35effective 2026-10-29 17:15Z → 2026-10-29 17:55Z · first seen 2026-10-29 12:21Z · last seen 2026-10-29 12:21Z
    !MSP 10/669 MSP RWY 17/35 CLSD EXC XNG 2610291715-2610291755
  • 10/639 · partial closure (partial) · runway 17/35effective 2026-10-28 21:30Z → 2026-10-28 22:30Z · first seen 2026-10-28 12:42Z · last seen 2026-10-28 20:54Z · cancelled 2026-10-28 20:54Z
    !MSP 10/639 MSP RWY 17/35 CLSD EXC XNG 2610282130-2610282230
  • 10/635 · closure (full) · runway 17/35effective 2026-10-28 21:30Z → 2026-10-28 22:30Z · first seen 2026-10-28 12:42Z · last seen 2026-10-28 12:42Z
    RWY 17/35 CLSD
  • 10/635 · closure (full) · runway 17/35effective 2026-10-28 21:30Z → 2026-10-28 22:30Z · first seen 2026-10-28 12:20Z · last seen 2026-10-28 12:40Z · cancelled 2026-10-28 12:40Z
    !MSP 10/635 MSP RWY 17/35 CLSD 2610282130-2610282230
  • 10/639 · partial closure (partial) · runway 17/35effective 2026-10-28 21:30Z → 2026-10-28 22:30Z · first seen 2026-10-28 20:55Z · last seen 2026-10-28 20:55Z
    RWY 17/35 CLSD EXC XNG
  • 10/634 · closure (full) · runway 17/35effective 2026-10-28 20:00Z → 2026-10-28 21:00Z · first seen 2026-10-28 12:20Z · last seen 2026-10-28 12:40Z · cancelled 2026-10-28 12:40Z
    !MSP 10/634 MSP RWY 17/35 CLSD 2610282000-2610282100
  • 10/638 · partial closure (partial) · runway 17/35effective 2026-10-28 20:00Z → 2026-10-28 21:00Z · first seen 2026-10-28 12:42Z · last seen 2026-10-28 20:55Z · cancelled 2026-10-28 20:55Z
    !MSP 10/638 MSP RWY 17/35 CLSD EXC XNG 2610282000-2610282100
  • 10/603 · closure (full) · runway 17/35effective 2026-10-27 13:30Z → 2026-10-27 13:50Z · first seen 2026-10-27 12:21Z · last seen 2026-10-27 13:26Z · cancelled 2026-10-27 13:27Z
    !MSP 10/603 MSP RWY 17/35 CLSD 2610271330-2610271350
  • 10/603 · closure (full) · runway 17/35effective 2026-10-27 13:30Z → 2026-10-27 13:50Z · first seen 2026-10-27 13:28Z · last seen 2026-10-27 13:28Z
    RWY 17/35 CLSD
  • 10/606 · closure (full) · runway 17/35effective 2026-10-27 13:26Z → 2026-10-27 13:50Z · first seen 2026-10-27 13:41Z · last seen 2026-10-27 13:41Z
    RWY 17/35 CLSD
  • 10/606 · closure (full) · runway 17/35effective 2026-10-27 13:26Z → 2026-10-27 13:50Z · first seen 2026-10-27 13:28Z · last seen 2026-10-27 13:39Z · cancelled 2026-10-27 13:39Z
    !MSP 10/606 MSP RWY 17/35 CLSD 2610271326-2610271350
  • 10/569 · partial closure (partial) · runway 17/35effective 2026-10-26 17:15Z → 2026-10-26 17:35Z · first seen 2026-10-26 12:07Z · last seen 2026-10-26 12:07Z · cancelled 2026-10-26 12:07Z
    !MSP 10/569 MSP RWY 17/35 CLSD EXC XNG 2610261715-2610261735
Published FAA baseline (NASR record)

Runway 17/35: Open on the published record — a baseline that does not reflect temporary closures or restrictions, not the current operational status.

Recent pilot reports involving runway 17/35

Official PIREPs that name this runway explicitly, past 6 hours.

No pilot report in the last 6 hours names runway 17/35 at KMSP explicitly. Reports near the airport that do not name a runway are on the airport page.

Instrument approaches to runway 17/35

From the FAA d-TPP, linked to the official plates.

13 departure procedures · 15 STARs · FAA hot spots page ↗ · LAHSO page ↗ · FAA d-TPP cycle 2611. Plates open on aeronav.faa.gov (public domain); ATIS Alerts does not reproduce charts or minimums.

Methodology and sources

Short version below; the full write-up is at Runway Intelligence methodology, and every launched airport is listed on the Runway Intelligence hub.

  • Active runwayscome first from the tower's TFDM (Terminal Flight Data Manager) airport configuration, received as structured data through the FAA SWIM Cloud Distribution Service at towers that have it; otherwise from the airport's D-ATIS text (community relay of the FAA broadcast) with an open, tested parser, and the broadcast text is always shown. Every change is recorded, so “recorded use” is what the facility stated, never an inference. ATIS Alerts is not an FAA product and this is not FAA data; SWIM content is for non-operational use.
  • Flowis the compass direction of the stated arrival ends (eight sectors, named only when every arrival end points within 30° of the others and clear of a sector edge); a tower's own configuration name is used when it carries a direction word. Stored separately from the runway sets.
  • Equipment, LAHSO and frequencies come from the FAA NASR 28-day subscription (cycle 2026-10-01): approach lights, visual glide slope, edge / centerline / touchdown-zone lights, REIL, ILS components with FAA status, RVR, markings, LAHSO hold-short points and available landing distances, and facility frequencies with their published sectorization. Outage annotations are readings of the NOTAM or D-ATIS text shown beside them. Blank FAA fields read “Not available”.
  • Wind components use the current METAR (aviationweather.gov) against TRUE runway headings from the OurAirports/FAA runway record.
  • Runway visual range, tower demand and traffic-management restrictions come from FAA SWIM: STDDS Airport Data (RVR and light settings, about 130 airports) and TFDM (15-minute runway demand, APREQ/MIT restrictions). Each block is stamped with its own time; none of it is an FAA product or a clearance.
  • Predicted runway scores each open end from the TAF wind (headwind, crosswind penalty, tailwind avoidance, longest-runway tie-break), excludes stated closures, and — once a wind sector has 24 h of recorded use — adjusts confidence by what the facility did under similar wind; every row lists its reasons. It does not model noise abatement or flow programs beyond what the record shows.
  • History thresholds: usage shares need 12 / 48 / 168 recorded hours for the 24-hour / 7-day / 30-day windows; a wind sector needs 24 h and 5 days; time-of-day needs 7 days and 20 h per daypart; flow shares need 48 h. Below a bar the module says so instead of showing a percentage.
  • Climatology: Iowa Environmental Mesonet ASOS archive, one observation per hour, 45° wind sectors, percentiles via t-digest; runway geometry is today's record applied to all years. Methodology v1.
  • PIREPs: official reports from aviationweather.gov are attached only when the text names this runway and the report is tied to KMSP by identifier or by position within 15 NM. Approaches: FAA d-TPP metafile, current charting cycle; plates link to aeronav.faa.gov. No minimums are reproduced.
  • Data freshness: METAR and D-ATIS refresh every minute on this page; the D-ATIS recorder ran 2 min ago; usage rollups every 3 h; climatology through 2025-12-31.

Get free ATIS alerts for KMSP

We'll message you on Telegram the moment KMSP (Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field)'s ATIS letter changes or it drops below VFR, so you check weather only when it actually matters.

Track KMSP on Telegram

Free • no app to install • unsubscribe anytime

Other runways at KMSP

← KMSP live weather, METAR, TAF & D-ATIS

Tools for this runway

Active runway - past 30 days

Share of stated hours each end was named for arrivals at KMSP. From the D-ATIS, not wind. Shares are measured independently, so parallels active together can each read 100%.

  • 12L52%dep 51%
  • 12R51%dep 49%
  • 30R43%dep 43%
  • 30L42%dep 42%
  • 351%dep 0%
  • 170%dep 29%
  • 040%dep 1%

30.0 days of stated configuration on record · 74 configuration changes · 21 distinct configurations.

KMSP airport diagram

Official FAA taxiway and runway layout. Tap to zoom.

Official FAA airport diagram · d-TPP cycle 2611 · Not for navigation. Download the official FAA PDF ↗

⚠️ ATIS Alerts provides informational runway analysis based on available weather, the tower's TFDM configuration and NOTAMs received through FAA SWIM, D-ATIS text, FAA data and historical observations. Active runways shown here are what the tower or its D-ATIS stated and may lag or be misread; NOTAM coverage is not complete; predicted runways are an ATIS Alerts estimate, not an ATC assignment; equipment states are readings of the official text shown with them. Not an FAA product. Not for operational use. Always verify with official FAA-approved preflight weather sources before flight.