K95D Runway 10/28 — Beulah Airport

Long-term wind statistics for runway 10/28 are not loaded yet. ATIS Alerts computes them from the 20-year ASOS archive for stations with continuous records; check back as coverage expands.

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

No published instrument approach procedures are listed for K95D in the current FAA d-TPP cycle. Visual approaches only.

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 K95D 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 4 min ago; usage rollups every 3 h; climatology through the archive end.