Skip to content
Know before you taxi

All Products

Aviation Intelligence

Alerts & Airspace

Free Pilot Tools & Widgets

RC Aviation

Games & Learning

Weather Research & More

Pilot Resources

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

KHTS Runway 12/30 — Tri-State Airport / Milton J. Ferguson Field

7,017 × 150 ft asphalt · true headings 112° / 292° · field elevation 828 ft

Runway 12/30 at Tri-State Airport / Milton J. Ferguson Field (KHTS) in Huntington, WV is 7,017 ft long and 150 ft wide, asphalt, with true headings 112° and 292°. The FAA record lists ILS/DME (CAT I) and MALSR approach lights on runway 12. Over 2005–2025 the wind gave runway 12 the headwind 45.1% of the time and runway 30 54.9%, with a crosswind above 15 kt in 0.2% of wind hours. KHTS has no digital ATIS, so the active runway is not known; the wind-favored end and the ATIS Alerts prediction are estimates.

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

Runway 12/30 — 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.

STATUS UNKNOWN
  • 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.

NOTAMs for runway 12/30

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.

Navaid / approach equipment · 4
  • 10/061 · DOM · scheduled11/04 1400Z (9:00 AM EST) → 11/04 2200Z (5:00 PM EST)
    !HTS 10/061 HTS NAV ILS RWY 12 U/S 2611041400-2611042200
  • 10/062 · DOM · scheduled11/04 1400Z (9:00 AM EST) → 11/04 2200Z (5:00 PM EST)
    !HTS 10/062 HTS NAV ILS RWY 30 U/S 2611041400-2611042200
  • 10/059 · DOM · scheduled11/02 1300Z (8:00 AM EST) → 11/02 2030Z (3:30 PM EST)
    !HTS 10/059 HTS NAV ILS RWY 12 U/S 2611021300-2611022030
  • 10/060 · DOM · scheduled11/02 1300Z (8:00 AM EST) → 11/02 2030Z (3:30 PM EST)
    !HTS 10/060 HTS NAV ILS RWY 30 U/S 2611021300-2611022030
Other · 2
  • 10/050 · DOM10/20 1638Z (12:38 PM EDT) → 11/20 1900Z (2:00 PM EST)
    !HTS 10/050 HTS RWY 12/30 BTN TWY A AND TWY H SFC MARKING NOT STD 2610201638-2611201900
  • 09/036 · DOM09/30 1822Z (2:22 PM EDT) → 10/30 2100Z (5:00 PM EDT)
    !HTS 09/036 HTS RWY 12/30 SFC MARKINGS W SIDE NOT STD 2609301822-2610302100

Current runway assignment is not available from D-ATIS at KHTS. 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 12/30

Wind from the south (190°) at 6 kt

METAR 1551Z (11:51 AM EDT)
Runway 12
FAVORED BY WIND
Headwind
1 kt
Crosswind
6 ktfrom right
Runway 30
Tailwind
1 kt
Crosswind
6 ktfrom left
1230N190°/6 kt
  • arrivals
  • departures
  • LAHSO hold-short
  • closed

Layout from FAA NASR runway-end coordinates; the selected runway is highlighted and no active source exists here. Not for navigation. Official FAA diagram ↗

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

Runway 12/30 outlook

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

Time · runway 12/30 · airport-wide outlook · confidence · forecast wind · why

  1. Now1653Z · 12:53 PM EDT·12/30: 12 likely·airport-wide likely 12 then 30·1 kt headwind, 6 kt crosswind·Medium 65%·wind 190° at 6 kt·Why Current METAR wind 190° at 6 kt favors south-facing runway ends: 1 kt headwind and 6 kt crosswind on 12 versus -1 kt headwind on 30.|No known runway closure prevents this configuration.
  2. +1 h1753Z · 1:53 PM EDT·12/30: no runway favored·no runway favored airport-wide·no confidence·wind calm·Why TAF wind 000° at 0 kt: below 5 kt, wind does not decide the runway.|No recorded calm-wind preference yet, so no end is favored.
  3. +2 h1853Z · 2:53 PM EDT·12/30: no runway favored·no runway favored airport-wide·no confidence·wind calm·Why TAF wind 000° at 0 kt: below 5 kt, wind does not decide the runway.|No recorded calm-wind preference yet, so no end is favored.
  4. +3 h1953Z · 3:53 PM EDT·12/30: no runway favored·no runway favored airport-wide·no confidence·wind calm·Why TAF wind 000° at 0 kt: below 5 kt, wind does not decide the runway.|No recorded calm-wind preference yet, so no end is favored.
  5. +6 h2253Z · 6:53 PM EDT·12/30: no runway favored·no runway favored airport-wide·no confidence·wind calm·Why TAF wind 000° at 0 kt: below 5 kt, wind does not decide the runway.|No recorded calm-wind preference yet, so no end is favored.
  6. +12 h0453Z · 12:53 AM EDT·12/30: no runway favored·no runway favored airport-wide·no confidence·wind calm·Why TAF wind 000° at 0 kt: below 5 kt, wind does not decide the runway.|No recorded calm-wind preference yet, so no end is favored.

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 1120Z (7:20 AM EDT).

Runway 12/30 equipment and lighting

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

Runway 12
Approach lighting
MALSR
Visual glide slope
PAPI (4-box, left side)
Runway edge lighting
HIRL (high intensity)
Centerline lighting
Not available
Touchdown zone lighting
Not available
REIL
Not available
ILS
ILS/DME
I-HTS · 109.9 MHz · CAT I
Localizer
Available
Glideslope
Available
3°
DME
Available
channel 36X
Marker beacons
Not available
RVR
touchdown
Runway markings
Precision instrument
condition good
Arresting system
Not available
Runway 30
Approach lighting
Not available
Visual glide slope
PAPI (4-box, left side)
Runway edge lighting
HIRL (high intensity)
Centerline lighting
Not available
Touchdown zone lighting
Not available
REIL
Available
ILS
ILS/DME
I-TUU · 108.7 MHz · CAT I
Localizer
Available
Glideslope
Available
3°
DME
Available
channel 24X
Marker beacons
Not available
RVR
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 12

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

Runway 30

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 12/30

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

Frequencies serving runway 12/30 at KHTS
ServiceFrequencyApplies to
Tower118.5Airport-wide
Tower270.1Airport-wide
Ground121.9Airport-wide
Clearance delivery118.05Airport-wide
ATIS125.2Airport-wide
Show all frequencies (4 more: approach and departure sectors, secondary and other)
Frequencies serving runway 12/30 at KHTS
ServiceFrequencyApplies to
UNICOM122.95Airport-wide
Approach / departure119.75Sector: SOUTH
Approach / departure128.4Sector: NORTH
Approach / departure270.1Airport-wide

The FAA record does not sectorize KHTS'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 12/30 overview

Physical characteristics from the FAA-derived runway record.

Length
7,017 ft
Width
150 ft
Surface
Asphalt · Good condition
Surface treatment
Grooved
Weight bearing (lb)
S 120k · D 210k · 2D 394k
PCN
470
Runway lights
Lighted
Airport elevation
828 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 12
True heading
112°
Magnetic
118°
Published FAA baseline
Open
Threshold elevation
828 ft
TDZ elevation
828 ft
Displaced threshold
None on record
Threshold crossing height
56 ft
Visual glide path
3°
Traffic pattern
Left
Controlling obstruction
trees, 36 ft, 950 ft from threshold, 21:1 slope
Runway 30
True heading
292°
Magnetic
298°
Published FAA baseline
Open
Threshold elevation
828 ft
TDZ elevation
828 ft
Displaced threshold
501 ft
Threshold crossing height
49 ft
Visual glide path
3°
Traffic pattern
Left

Runway 12/30 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, 6.0°W (1995), 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 KHTS — last 30 days

Which runway end had the most headwind each hour, from ATIS Alerts' collected wind history — an estimate, not ATC use.

Wind-favored runway - past 30 days

Share of hours each runway had the most headwind. From wind reports, not ATC assignments.

12
54%
30
46%

Historical wind and crosswind on runway 12/30

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

From 174,676 hourly observations at KHTS (2005–2025), 124,588 with a steady wind direction (28.7% calm, variable or direction-less). One observation per clock hour; TRUE headings against TRUE wind.

Crosswind on runway 12/30 (either end)

Mean crosswind
4.2 kt
median 3.9 kt
90th / 95th percentile
7.7 / 9 kt
max 29.6 kt
Above 10 kt
3%
> 15 kt: 0.2% · > 20 kt: 0%
Gust crosswind > 15 kt
4.7%
90th pct gust 9.2 kt
0%40%81%70%0–5 kt27%5–10 kt2.8%10–15 kt0.2%15–20 kt0.0%20–25 kt0.0%25+ kt
Share of wind hours by crosswind band on runway 12/30 at KHTS, 2005–2025
Crosswind (kt)Share of wind hours
0–570.4%
5–1026.7%
10–152.8%
15–200.2%
20–250%
25+0%

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

Runway 12

Headwind
45.1%
of wind hours
Tailwind > 5 kt
17.2%
> 10 kt: 2.3%
Most wind-favored end
45.1%
of steady-wind hours, 12 had the most headwind of every end at KHTS

Runway 30

Headwind
54.9%
of wind hours
Tailwind > 5 kt
3.3%
> 10 kt: 0.1%
Most wind-favored end
54.9%
of steady-wind hours, 30 had the most headwind of every end at KHTS

“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 KHTS. 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 12 and 30 by wind sector, 2005–2025
Wind fromShare of wind hours12 favored30 favoredMean crosswindCrosswind > 15 kt
N 338–023°11%0%100%4.7 kt0%
NE 023–068°9%100%0%4.6 kt0%
E 068–113°12%100%0%1.6 kt0%
SE 113–158°5%100%0%1.6 kt0%
S 158–203°20%100%0%5.7 kt0.4%
SW 203–248°21%0%100%5.7 kt0.6%
W 248–293°15%0%100%3.5 kt0%
NW 293–338°9%0%100%2.4 kt0%

By time of day (airport-local)

morning
12 favored 46.2% · 30 53.8%
mean crosswind 4.4 kt · calm 28.8%
afternoon
12 favored 35.9% · 30 64.1%
mean crosswind 4.8 kt · calm 23%
evening
12 favored 46.7% · 30 53.3%
mean crosswind 3.6 kt · calm 24.1%
night
12 favored 51.4% · 30 48.6%
mean crosswind 3.7 kt · calm 35.2%

Seasonal runway conditions

035JanFebMarAprMayJunJulAugSepOctNovDec
Mean crosswind on runway 12/30 at KHTS by month, 2005–2025
MonthMean crosswind (kt)
Jan4.5 kt
Feb4.6 kt
Mar4.6 kt
Apr4.6 kt
May4.0 kt
Jun4.0 kt
Jul3.9 kt
Aug3.6 kt
Sep3.7 kt
Oct3.9 kt
Nov4.1 kt
Dec4.3 kt
Monthly wind and weather statistics for runway 12/30 at KHTS, 2005–2025
MonthPrevailingMean windGustyMean xwxw > 10xw > 15xw > 2012 tail > 530 tail > 5IFRTSFog
JanW5.5 kt14.8%4.5 kt3.7%0.2%0%26%2.6%9.3%0.03%11.4%
FebSW5.7 kt15.8%4.6 kt5.1%0.5%0%25.3%3.4%10.7%0.18%12%
MarS5.7 kt17.4%4.6 kt5.7%0.5%0%23.5%5.3%7.2%0.38%9.3%
AprSW5.5 kt17.3%4.6 kt5%0.4%0%22.4%5%4.4%0.85%6%
MaySW4.2 kt7.7%4 kt2.3%0.1%0%13.7%4.2%8.3%1.22%11.9%
JunSW3.9 kt5.1%4 kt1.3%0.1%0%11.6%2.1%6.5%1.84%11.4%
JulSW3.4 kt2.9%3.9 kt1%0.1%0%7.1%1.5%9.3%2.18%16.1%
AugSW3.1 kt2%3.6 kt0.6%0%0%6.8%2%9.5%1.46%16.5%
SepS3.2 kt2.9%3.7 kt1%0%0%6.6%3.6%11.7%0.49%17%
OctS4 kt7.6%3.9 kt1.9%0.1%0%14.8%3%7.7%0.22%10.5%
NovSW4.5 kt10.3%4.1 kt2.8%0.2%0%19.3%2.9%6.6%0.07%9%
DecS4.9 kt11.6%4.3 kt3.4%0.3%0%19.8%3.3%9.8%0.05%11.8%

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 12/30 closure history

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

KHTS has no D-ATIS, so there is no broadcast-observed closure record.

NOTAM observed · recorded since Sep 19, 2026 (no archive before that)
  • 09/037 · partial closure (partial) · runway 12/30effective 2026-10-01 11:30Z → 2026-10-01 21:00Z · first seen 2026-09-30 21:29Z · last seen 2026-09-30 21:29Z
    !HTS 09/037 HTS RWY 12/30 CLSD EXC SKED ACFT AND AIR CARRIERS 20MIN PPR 122.950/304-654-1712 2610011130-2610012100
  • 09/034 · partial closure (partial) · runway 12/30effective 2026-09-30 17:58Z → 2026-09-30 23:00Z · first seen 2026-09-30 17:58Z · last seen 2026-09-30 17:58Z
    !HTS 09/034 HTS RWY 12/30 CLSD EXC SKED ACFT AND AIR CARRIERS 20MIN PPR 122.950/304-453-6165 2609301758-2609302300
  • 09/031 · partial closure (partial) · runway 12/30effective 2026-09-30 11:00Z → 2026-09-30 21:00Z · first seen 2026-09-30 03:02Z · last seen 2026-09-30 17:58Z
    !HTS 09/031 HTS RWY 12/30 CLSD EXC SKED ACFT AND AIR CARRIERS 20MIN PPR 122.950/304-453-6165 2609301100-2609302100
Published FAA baseline (NASR record)

Runway 12/30: 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 12/30

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

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

Instrument approaches to runway 12/30

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

Runway 12

Runway 30

No departure procedures · FAA hot spots 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 KHTS 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 KHTS

We'll message you on Telegram the moment a new METAR changes the picture at KHTS (Tri-State Airport / Milton J. Ferguson Field): flight category, wind, or ceiling past your minimums.

Track KHTS on Telegram

Free • no app to install • unsubscribe anytime

Other runways at KHTS

← KHTS live weather, METAR, TAF

Tools for this runway

KHTS 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.