CO56 Runway 17/35 — Jjs Airport
4,280 × 40 ft dirt · true headings 181° / 000° · field elevation 5,075 ft
Runway 17/35 at Jjs Airport (CO56) in Keenesburg, CO is 4,280 ft long and 40 ft wide, dirt, with true headings 181° and 000°. CO56 has no digital ATIS, so the active runway is not known; the wind-favored end and the ATIS Alerts prediction are estimates.
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 received NOTAM closes or restricts this runway, but the NOTAM stream has no complete initial load and the airport has no tower or D-ATIS feed. No current closure information.
Sources: Published FAA baseline (OurAirports/NASR record) · FAA NOTAMs. 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 17/35 at CO56. 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 runway assignment is not available from D-ATIS at CO56. The wind components below show which end the wind favors; the section after it is an ATIS Alerts prediction. Neither is an ATC assignment.
Current wind on Runway 17/35
Wind from the east (090°) at 17 kt, gusting 24 kt · from KDEN, the nearest reporting station
- Headwind
- 0 kt
- Crosswind
- 17 ktfrom left
- Gust crosswind
- 24 kt
- Headwind
- 0 kt
- Crosswind
- 17 ktfrom right
- Gust crosswind
- 24 kt
Components use TRUE runway headings and TRUE METAR wind. “Favored by wind” is arithmetic, not an ATC assignment.
Runway 17/35 outlook
Where runway 17/35 stands now and which runway at CO56 is likely over the next 12 hours — an estimate, not an ATC assignment.
Time · runway 17/35 · airport-wide outlook · confidence · forecast wind · why
- Now2236Z · 4:36 PM MDT·17/35: 35 likely·airport-wide likely 35 then 17·North flow·0 kt headwind, 17 kt crosswind·Low 52%·wind 090° at 17 kt G24·Why Current METAR wind 090° at 17 kt gusting 24 favors east-facing runway ends: 0 kt headwind and 17 kt crosswind on 35 versus 0 kt headwind on 17.|No known runway closure prevents this configuration.
- +1 h2336Z · 5:36 PM MDT·17/35: 17 likely·airport-wide likely 17 then 35·South flow·2 kt headwind, 13 kt crosswind·Medium 68%·wind 100° at 13 kt G22·Why TAF forecast wind 100° at 13 kt gusting 22 favors east-facing runway ends: 2 kt headwind and 13 kt crosswind on 17 versus -2 kt headwind on 35.|No known runway closure prevents this configuration.|Gusts well above the steady wind (confidence lowered).|Confidence falls with forecast distance (+1 h).
- +2 h0036Z · 6:36 PM MDT·17/35: 17 likely·airport-wide likely 17 then 35·South flow·2 kt headwind, 10 kt crosswind·Medium 64%·wind 100° at 10 kt·Why TAF forecast wind 100° at 10 kt favors east-facing runway ends: 2 kt headwind and 10 kt crosswind on 17 versus -2 kt headwind on 35.|No known runway closure prevents this configuration.|Confidence falls with forecast distance (+2 h).
- +3 h0136Z · 7:36 PM MDT·17/35: 17 likely·airport-wide likely 17 then 35·South flow·2 kt headwind, 10 kt crosswind·Medium 61%·wind 100° at 10 kt·Why TAF forecast wind 100° at 10 kt favors east-facing runway ends: 2 kt headwind and 10 kt crosswind on 17 versus -2 kt headwind on 35.|No known runway closure prevents this configuration.|Confidence falls with forecast distance (+3 h).
- +6 h0436Z · 10:36 PM MDT·17/35: 17 likely·airport-wide likely 17 then 35·South flow·5 kt headwind, 5 kt crosswind·High 95%·wind 140° at 7 kt·Why TAF forecast wind 140° at 7 kt favors southeast-facing runway ends: 5 kt headwind and 5 kt crosswind on 17 versus -5 kt headwind on 35.|No known runway closure prevents this configuration.|Confidence falls with forecast distance (+6 h).
- +12 h1036Z · 4:36 AM MDT·17/35: 17 likely·airport-wide likely 17 then 35·South flow·10 kt headwind, 5 kt crosswind·High 95%·wind 210° at 11 kt·Why TAF forecast wind 210° at 11 kt favors southwest-facing runway ends: 10 kt headwind and 5 kt crosswind on 17 versus -10 kt headwind on 35.|No known runway closure prevents this configuration.|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. 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 2157Z (3:57 PM MDT).
Runway 17/35 equipment and lighting
What the FAA record lists for each end, annotated with current NOTAM and D-ATIS outages.
- 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.
No LAHSO hold-short point on the FAA record for this end.
No LAHSO hold-short point on the FAA record for this end.
This airport has no D-ATIS, so the current LAHSO state is not known here. 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.
No tower, ground, ATIS or approach frequencies are on the FAA NASR record for CO56.
Runway 17/35 overview
Physical characteristics from the FAA-derived runway record.
- Length
- 4,280 ft
- Width
- 40 ft
- Surface
- Dirt
- Runway lights
- Not lighted
- Airport elevation
- 5,075 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.
- True heading
- 181°
- Magnetic
- 170°
- Published FAA baseline
- Open
- Displaced threshold
- None on record
- Controlling obstruction
- plines, 22 ft, 440 ft from threshold
- True heading
- 000°
- Magnetic
- 349°
- Published FAA baseline
- Open
- Displaced threshold
- None on record
- Controlling obstruction
- plines, 28 ft, 560 ft from threshold
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, 11.0°E (1990), 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.
Wind-favored runway at CO56 — last 30 days
Which runway end had the most headwind each hour, from ATIS Alerts' collected wind history — an estimate, not ATC use.
Share of hours each runway had the most headwind. From wind reports, not ATC assignments.
- 17
- 70%
- 35
- 30%
Historical wind and crosswind on runway 17/35
20-year hourly climatology from the ASOS archive, computed per runway end.
Long-term wind statistics for runway 17/35 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 17/35 closure history
Kept per source with its provenance: D-ATIS-observed, NOTAM-observed and the FAA published baseline are never merged.
CO56 has no D-ATIS, so there is no broadcast-observed closure record.
No closure NOTAM naming runway 17/35 has been received since the stream went live.
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 CO56 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.
No published instrument approach procedures are listed for CO56 in the current FAA d-TPP cycle. Visual approaches only.
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 CO56 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 0 min ago; usage rollups every 3 h; climatology through the archive end.
Get free ATIS alerts for CO56
We'll message you on Telegram when a new report moves the picture near CO56 (Jjs Airport): alerts read from KDEN, the station this page uses.
Track CO56 on TelegramFree • no app to install • unsubscribe anytime
Other runways at CO56
CO56 has a single runway.
Tools for this runway
⚠️ 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.