KORD Runway 18/36 — Chicago O'Hare International Airport
5,332 × 150 ft asphalt · true headings 180° / 360° · field elevation 680 ft
Runway 18/36 at Chicago O'Hare International Airport (KORD) in Chicago, IL is 5,332 ft long and 150 ft wide, asphalt, with true headings 180° and 360°. KORD publishes its tower configuration on FAA SWIM, 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.
Runway 18/36 — 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.
- The published FAA runway record lists this runway as closed.
Sources: Published FAA baseline (OurAirports/NASR record) · Tower TFDM 1404Z (8:04 AM CST) · D-ATIS 1351Z (7:51 AM CST). 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.
No received NOTAM currently names runway 18/36 at KORD. 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.
Current active runways at KORD
As stated by the tower — its TFDM surface system and its D-ATIS broadcast. Not an estimate.
Airport rates: 112 arrivals / 112 departures per hour. In effect since 2026-11-03 1332Z (7:32 AM CST).
Flow: West flow— the compass direction of the stated arrival ends
Runway 18/36 in this configuration: not listed for arrivals or departures (tower TFDM)
A bare number (09) means the broadcast did not say which parallel.
This D-ATIS configuration has been stated since 1251Z (6:51 AM CST).
Show the D-ATIS text
ORD ATIS INFO W 1351Z. 18017G28KT 10SM FEW015 FEW070 BKN250 19/15 A2991 (TWO NINER NINER ONE) RMK AO2 PK WND 18028/1350 SLP125 T01890150. ARR EXP VECTORS ILS RWY 28C APCH, VISUAL APCH RWY 27C, VISUAL APCH RWY 27R. SIMUL APCHS IN USE. LAND AND HOLD SHORT OPERATIONS ARE IN EFFECT. RWY 27C ARR PLAN TO H/S OF TWY V V, 9 THSD 7 HND 25 FT AVBL, RWY 28C ARR PLAN TO H/S OF TWY Z, 9 THSD 6 HND TEN FT AVBL. DEPS EXP RWYS 22L 28R FROM NOVEMBER 5 9750 FT AVL. RWY 4L, 22R CLSD. RWY 9L IM OTS, RWY 9C IM OTS, RWY 9R IM OTS, RWY 10L IM OTS, RWY 10C IM OTS, RWY 10R IM OTS, RWY 27L IM OTS, RWY 27C IM OTS, RWY 27R IM OTS, RWY 28L IM OTS, RWY 28C IM OTS, RWY 28R IM OTS. PILOTS USE CTN FOR BIRD ACTIVITY IN THE VICINITY OF THE ARPT. USE CTN FOR PERSONNEL AND EQUIP AT NUMEROUS SITES ON THE FIELD. AUTHORIZED DRONE ACTIVITY, OVER CONSTRUCTION AREAS WEST OF THE TERMINALS, , 300 FEET. READBACK ALL RWY HOLD SHORT INSTRUCTIONS. WHEN READY TO TAXI CONTACT GND METERING ON FREQ 121.67. ...ADVS YOU HAVE INFO W.
Current wind on Runway 18/36
Wind not reported
No steady wind direction — no components to compute.
No steady wind direction — no components to compute.
- arrivals
- departures
- LAHSO hold-short
- closed
Layout from FAA NASR runway-end coordinates; the selected runway is highlighted and the ends the tower TFDM states in use are marked at their own threshold. Not for navigation. Official FAA diagram ↗
Components use TRUE runway headings and TRUE METAR wind. “Favored by wind” is arithmetic, not an ATC assignment.
Today's runway configuration at KORD
Meaningful configuration changes recorded from the tower's TFDM feed — the facility's own statements, not estimates.
Nov 3, 2026 (airport-local day): 2 configuration changes since local midnight, from the tower's TFDM configuration 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.
- 06:05Z12:05 AM CST(in effect since before the day began)7.5 hArrivals28C27C27RDepartures28R22LWest flowLAHSO in effectIn effect at the start of the day
- 13:32Z7:32 AM CSTArrivals09L10C10RDepartures10L09CEast flowFlow changed: West → East · Arrivals +09L, 10C, 10R −28C, 27C, 27R · Departures +10L, 09C −28R, 22L
- 13:32Z7:32 AM CST0.5 h · currentArrivals28C27C27RDepartures28R22LWest flowLAHSO in effectFlow changed: East → West · Arrivals +28C, 27C, 27R −09L, 10C, 10R · Departures +28R, 22L −10L, 09C
Runway 18/36 outlook
Where runway 18/36 stands now and which runway at KORD is likely over the next 12 hours — an estimate, not an ATC assignment.
Time · runway 18/36 · airport-wide outlook · confidence · forecast wind · why
- Now1405Z · 8:05 AM CST·18/36: CLOSED·Current airport configuration (tower TFDM): arrivals 27R · 27C · 28C · departures 22L · 28R·stated·wind not forecast
- +1 h1505Z · 9:05 AM CST·18/36: CLOSED·airport-wide likely 22L then 28R·Southwest flow·16 kt headwind, 10 kt crosswind·High 95%·wind 190° at 19 kt G31·Why TAF forecast wind 190° at 19 kt gusting 31 favors south-facing runway ends: 16 kt headwind and 10 kt crosswind on 22L versus 3 kt headwind on 28R.|This would be a change from the current 27R, 27C and 28C configuration.|Runways 04L and 22R are excluded: stated closed.|Gusts well above the steady wind (confidence lowered).|Confidence falls with forecast distance (+1 h).
- +2 h1605Z · 10:05 AM CST·18/36: CLOSED·airport-wide likely 22L then 28R·Southwest flow·16 kt headwind, 10 kt crosswind·High 95%·wind 190° at 19 kt G31·Why TAF forecast wind 190° at 19 kt gusting 31 favors south-facing runway ends: 16 kt headwind and 10 kt crosswind on 22L versus 3 kt headwind on 28R.|This would be a change from the current 27R, 27C and 28C configuration.|Runways 04L and 22R are excluded: stated closed.|Gusts well above the steady wind (confidence lowered).|Confidence falls with forecast distance (+2 h).
- +3 h1705Z · 11:05 AM CST·18/36: CLOSED·airport-wide likely 22L then 28R·Southwest flow·16 kt headwind, 10 kt crosswind·High 95%·wind 190° at 19 kt G31·Why TAF forecast wind 190° at 19 kt gusting 31 favors south-facing runway ends: 16 kt headwind and 10 kt crosswind on 22L versus 3 kt headwind on 28R.|This would be a change from the current 27R, 27C and 28C configuration.|Runways 04L and 22R are excluded: stated closed.|Gusts well above the steady wind (confidence lowered).|Confidence falls with forecast distance (+3 h).
- +6 h2005Z · 2:05 PM CST·18/36: CLOSED·airport-wide likely 22L then 28R·Southwest flow·16 kt headwind, 10 kt crosswind·High 95%·wind 190° at 19 kt G31·Why TAF forecast wind 190° at 19 kt gusting 31 favors south-facing runway ends: 16 kt headwind and 10 kt crosswind on 22L versus 3 kt headwind on 28R.|This would be a change from the current 27R, 27C and 28C configuration.|Runways 04L and 22R are excluded: stated closed.|Gusts well above the steady wind (confidence lowered).|Confidence falls with forecast distance (+6 h).
- +12 h0205Z · 8:05 PM CST·18/36: CLOSED·airport-wide likely 22L then 10L·Southwest flow·7 kt headwind, 12 kt crosswind·Low 20%·wind 160° at 14 kt G24·Why TAF forecast wind 160° at 14 kt gusting 24 favors south-facing runway ends: 7 kt headwind and 12 kt crosswind on 22L versus 5 kt headwind on 10L.|This would be a change from the current 27R, 27C and 28C configuration.|Runways 04L and 22R are excluded: stated closed.|Gusts well above the steady wind (confidence lowered).|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 tower use since Sep 10, 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 1137Z (5:37 AM CST).
- APREQ → KDEN (25 programs) · since 11/03 1307Z · by ZDV — approval request — departures need a release time
- APREQ → KMEM (7 programs) · since 11/03 0301Z · until further notice · by ZME — approval request — departures need a release time
- APREQ → KDCA (6 programs) · since 11/03 1058Z · until further notice · by ZDC — approval request — departures need a release time
- APREQ → KARR/KDKB/KDPA/KGYY/KIGQ/KJOT/KMDW/KPWK/KUGN/C09/1C5/C81/LL10/LL22/06C/10C/3CK/68IS/82IS/KLOT/05C · since 10/14 1431Z · until further notice — approval request — departures need a release time
- APREQ → KGRB · since 10/23 0222Z · until further notice · by ZAU — approval request — departures need a release time
- APREQ → KLGA · since 11/03 1134Z · until further notice · by ZAU — approval request — departures need a release time
- APREQ → KDFW · since 11/03 1219Z · until further notice · by ZAU — approval request — departures need a release time
- MIT → KLGA · 20 MIT · 6 MINIT · since 10/16 1914Z · until further notice — miles-in-trail spacing
- SWAP → KASE/KEGE/KHDN/KGUC/KTEX/KMTJ/KJAC/KSUN/KBZN/KFCA/KMMH/KRNO/KSLC/KPVU/KDEN/KBJC · since 10/14 1424Z · until further notice
Restrictions on departures from KORDtoward the named airports or fixes, as recorded by the tower's surface system; they change the departure flow, not the runway in use. Not an FAA product.
Runway 18/36 equipment and lighting
What the FAA record lists for each end, annotated with current NOTAM and D-ATIS outages.
The FAA NASR runway record does not carry this airport, so no equipment can be listed. Nothing is inferred.
- Approach lighting
- Not available
- Visual glide slope
- Not available
- Runway edge lighting
- Not available
- Centerline lighting
- Not available
- Touchdown zone lighting
- Not available
- REIL
- Not available
- ILS
- Not available
- Localizer
- Not available
- Glideslope
- Not available
- DME
- Not available
- Marker beacons
- Not available
- RVR
- Not available
- Runway markings
- Not available
- Arresting system
- Not available
- Approach lighting
- Not available
- Visual glide slope
- Not available
- Runway edge lighting
- Not available
- Centerline lighting
- Not available
- Touchdown zone lighting
- Not available
- REIL
- Not available
- ILS
- Not available
- Localizer
- Not available
- Glideslope
- Not available
- DME
- Not available
- Marker beacons
- Not available
- RVR
- Not available
- Runway markings
- Not available
- 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.
LAHSO CURRENTLY REPORTED IN D-ATIS“LAND AND HOLD SHORT OPERATIONS ARE IN EFFECT”
No LAHSO hold-short point on the FAA record for this end.
No LAHSO hold-short point on the FAA record for this end.
Source: FAA NASR cycle 2026-10-01; D-ATIS text read by ATIS Alerts.
Frequencies for runway 18/36
Tower, ground, clearance, ATIS and approach frequencies from the FAA record, labelled by what they apply to.
| Service | Frequency | Applies to |
|---|---|---|
| Tower | 348.0 | Airport-wide |
| Ground | 118.05 | Sector: TWR SOUTH |
| Ground | 121.9 | Sector: TWR CENTER INBOUND |
| Ground | 121.75 | Sector: TWR CENTER OUTBOUND |
| Ground | 124.125 | Sector: TWR NORTH |
| Ground | 226.675 | Airport-wide |
| Clearance delivery | 121.6 | Airport-wide |
| D-ATIS | 135.4 | Airport-wide |
| D-ATIS | 282.225 | Airport-wide |
Show all frequencies (16 more: approach and departure sectors, secondary and other)
| Service | Frequency | Applies to |
|---|---|---|
| UNICOM | 122.95 | Airport-wide |
| Ground (secondary) | 134.15 | Sector: TWR CENTER |
| Clearance delivery (secondary) | 119.25 | Airport-wide |
| Approach / departure | 119.0 | Sector: 360-179 |
| Approach / departure | 124.35 | Airport-wide |
| Approach / departure | 125.7 | Sector: 180-359 |
| Approach / departure | 126.625 | Sector: 220-319 WEST |
| Approach / departure | 126.625 | Sector: 150-219 SOUTH |
| Approach / departure | 128.575 | Sector: 320-149 EAST/NORTH |
| Approach / departure | 133.625 | Sector: 180-359 |
| Approach / departure | 292.125 | Sector: 360-179 |
| Approach / departure | 327.075 | Sector: 150-219 SOUTH |
| Approach / departure | 327.075 | Sector: 220-319 WEST |
| Approach / departure | 350.325 | Sector: 180-359 |
| Approach / departure | 351.675 | Sector: 320-149 EAST/NORTH |
| Approach / departure | 377.15 | Airport-wide |
The FAA record does not sectorize KORD's frequencies by runway; every row applies airport-wide. Source: FAA NASR FRQ, cycle 2026-10-01. Verify on the current chart supplement before use.
Runway 18/36 overview
Physical characteristics from the FAA-derived runway record.
- Length
- 5,332 ft
- Width
- 150 ft
- Surface
- Asphalt
- Runway lights
- Lighted
- Airport elevation
- 680 ft
- Published FAA baseline
- Closed
- Published NASR record; does not reflect temporary closures or restrictions. Current operational status is the card at the top of the page.
- True heading
- 180°
- Magnetic
- 183°
- Published FAA baseline
- Closed
- True heading
- 360°
- Magnetic
- 003°
- Published FAA baseline
- Closed
Runway 18/36 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, 3.0°W (2010), the same value printed on the FAA airport diagram. This airport is not in the FAA NASR record, so surface condition, thresholds and traffic-pattern direction are omitted rather than guessed.
Configuration history at KORD
Observed runway usage: how often the tower's TFDM configuration listed each end, by window, flow, wind and time of day (the tower's own statement, via FAA SWIM).
- 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%.
- Most-used arrival ends at the airport
- 27C (75%) · 27R (75%) · 28C (75%)
- Most-used departure ends
- 22L (80%) · 28R (75%) · 10L (20%)
Insufficient history for flow shares: 24 of the 48 hours of stated configuration needed have been recorded.
- Most-used arrival ends at the airport
- 10C (89%) · 10R (89%) · 09L (87%)
- Most-used departure ends
- 10L (89%) · 09C (87%) · 22L (11%)
- East flow89%(150 h)
- West flow11%(18 h)
- 87% · arrivals 09L · 10C · 10R · departures 09C · 10L(East flow)
- 11% · arrivals 27C · 27R · 28C · departures 22L · 28R(West flow)
- 2% · arrivals 09C · 10C · 10R · departures 04L · 10L(East flow)
- Most-used arrival ends at the airport
- 10C (81%) · 09L (80%) · 10R (77%)
- Most-used departure ends
- 04L (41%) · 10C (40%) · 09L (40%)
- East flow40%(291 h)
- Mixed configuration40%(290 h)
- West flow19%(140 h)
- 40% · arrivals 04L · 09L · 10C · 10R · departures 04L · 09L · 10C · 10R(Mixed configuration)
- 36% · arrivals 09L · 10C · 10R · departures 09C · 10L(East flow)
- 10% · arrivals 27R · 28C · 28L · departures 27L · 28R(West flow)
| Wind from | Hours | 18 arrivals | 36 arrivals | 18 departures | 36 departures |
|---|---|---|---|---|---|
| Calm / light (< 5 kt) | 720 | 0% | 0% | 0% | 0% |
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 tower TFDM runway configuration history collected · 9 distinct configurations observed · through Nov 3, 2026. Shares are the fraction of recorded hours in which the tower's TFDM configuration listed each end. Wind sectors use the wind reported when each configuration began. Nothing here is inferred from wind; the wind-favored analysis for KORD is a separate module. 90-day, 12-month and seasonal views appear once the record is long enough.
Historical wind and crosswind on runway 18/36
20-year hourly climatology from the ASOS archive, computed per runway end.
Long-term wind statistics for runway 18/36 are not loaded yet. ATIS Alerts computes them from the 20-year ASOS archive for stations with continuous records; check back as coverage expands.
Runway 18/36 closure history
Kept per source with its provenance: D-ATIS-observed, NOTAM-observed and the FAA published baseline are never merged.
- 18: no broadcast has reported it closed
- 36: no broadcast has reported it closed
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.
No closure NOTAM naming runway 18/36 has been received since the stream went live.
Runway 18/36: Closed on the published record — a baseline that does not reflect temporary closures or restrictions, not the current operational status.
Recent pilot reports involving runway 18/36
Official PIREPs that name this runway explicitly, past 6 hours.
No pilot report in the last 6 hours names runway 18/36 at KORD explicitly. Reports near the airport that do not name a runway are on the airport page.
Instrument approaches to runway 18/36
From the FAA d-TPP, linked to the official plates.
Runway 18
No straight-in instrument approach published to this end.
Runway 36
No straight-in instrument approach published to this end.
Circling / other approaches at KORD
- OTHERPRM AAUP ↗
2 departure procedures · 19 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 (KORD does); 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 KORD 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 5 min ago; the tower TFDM feed last delivered 1 min ago; usage rollups every 3 h; climatology through the archive end.
Get free ATIS alerts for KORD
We'll message you on Telegram the moment KORD (Chicago O'Hare International Airport)'s ATIS letter changes or it drops below VFR, so you check weather only when it actually matters.
Track KORD on TelegramFree • no app to install • unsubscribe anytime
Other runways at KORD
Tools for this runway
Active runway - past 30 days
Share of stated hours each end was named for arrivals at KORD. From the tower TFDM configuration, not wind. Shares are measured independently, so parallels active together can each read 100%.
- 10C81%dep 40%
- 09L80%dep 40%
- 10R77%dep 40%
- 04L40%dep 41%
- 27R19%dep 0%
- 28C19%dep 0%
- 28L10%dep 0%
- 27C9%dep 0%
- 09C4%dep 36%
- 10L0%dep 37%
- 28R0%dep 17%
- 27L0%dep 14%
30.0 days of stated configuration on record · 13 configuration changes · 9 distinct configurations.
KORD 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.