KUZA Runway 02/20 — Rock Hill - York County Airport
5,500 × 100 ft asphalt · true headings 011° / 191° · field elevation 666 ft
Runway 02/20 at Rock Hill - York County Airport (KUZA) in Rock Hill, SC is 5,500 ft long and 100 ft wide, asphalt, with true headings 011° and 191°. The FAA record lists ILS/DME (CAT I) and MALSR approach lights on runway 02. Over 2005–2025 the wind gave runway 02 the headwind 39.6% of the time and runway 20 60.4%, with a crosswind above 15 kt in 0.1% of wind hours. KUZA has no digital ATIS, so the active runway is not known; the wind-favored end and the ATIS Alerts prediction are estimates.
Runway 02/20 — 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 02/20 at KUZA. 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 KUZA. 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 02/20
Wind from the north-northeast (020°) at 4 kt
- Headwind
- 4 kt
- Crosswind
- 1 ktfrom right
- Tailwind
- 4 kt
- Crosswind
- 1 ktfrom left
- 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.
Components use TRUE runway headings and TRUE METAR wind. “Favored by wind” is arithmetic, not an ATC assignment.
Runway 02/20 outlook
Where runway 02/20 stands now and which runway at KUZA is likely over the next 12 hours — an estimate, not an ATC assignment.
Time · runway 02/20 · airport-wide outlook · confidence · forecast wind · why
- Now1304Z · 9:04 AM EDT·02/20: no runway favored·no runway favored airport-wide·no confidence·wind 020° at 4 kt·Why METAR wind 020° at 4 kt: below 5 kt, wind does not decide the runway.|No recorded calm-wind preference yet, so no end is favored.
- +1 h1404Z · 10:04 AM EDT·02/20: no runway favored·no runway favored airport-wide·no confidence·wind not forecast·Why No TAF is published for this airport, so there is no forecast wind to score.
- +2 h1504Z · 11:04 AM EDT·02/20: no runway favored·no runway favored airport-wide·no confidence·wind not forecast·Why No TAF is published for this airport, so there is no forecast wind to score.
- +3 h1604Z · 12:04 PM EDT·02/20: no runway favored·no runway favored airport-wide·no confidence·wind not forecast·Why No TAF is published for this airport, so there is no forecast wind to score.
- +6 h1904Z · 3:04 PM EDT·02/20: no runway favored·no runway favored airport-wide·no confidence·wind not forecast·Why No TAF is published for this airport, so there is no forecast wind to score.
- +12 h0104Z · 9:04 PM EDT·02/20: no runway favored·no runway favored airport-wide·no confidence·wind not forecast·Why No TAF is published for this airport, so there is no forecast wind to score.
ATIS Alerts Predicted Runway is an estimate from the current wind (no TAF is published for this airport), 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.
Runway 02/20 equipment and lighting
What the FAA record lists for each end, annotated with current NOTAM and D-ATIS outages.
- Approach lighting
- MALSR
- Visual glide slope
- PAPI (2-box, left side)
- Runway edge lighting
- MIRL (medium intensity)
- Centerline lighting
- Not available
- Touchdown zone lighting
- Not available
- REIL
- Not available
- ILS
- ILS/DME
- Localizer
- Available
- Glideslope
- Available
- DME
- Available
- Marker beacons
- OM
- RVR
- Not available
- Runway markings
- Precision instrument
- Arresting system
- Not available
- Approach lighting
- Not available
- Visual glide slope
- PAPI (2-box, left side)
- Runway edge lighting
- MIRL (medium intensity)
- 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
- Precision instrument
- 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 02/20
Tower, ground, clearance, ATIS and approach frequencies from the FAA record, labelled by what they apply to.
| Service | Frequency | Applies to |
|---|---|---|
| CTAF | 123.05 | Airport-wideDUSK-2300. MIRL RWY 02/20 & MALSR RWY 02 PRESET MED INTST DUSK-2300; TO INCR INTST & ACTVT AFTER 2300 - CTAF. |
| UNICOM | 123.05 | Airport-wide |
Show all frequencies (2 more: approach and departure sectors, secondary and other)
| Service | Frequency | Applies to |
|---|---|---|
| Approach / departure | 120.05 | Airport-wide |
| Approach / departure | 307.8 | Airport-wide |
The FAA record does not sectorize KUZA'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 02/20 overview
Physical characteristics from the FAA-derived runway record.
- Length
- 5,500 ft
- Width
- 100 ft
- Surface
- Asphalt · Good condition
- Surface treatment
- Grooved
- Weight bearing (lb)
- S 78k · D 104k
- PCN
- 30
- Runway lights
- Lighted
- Airport elevation
- 666 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
- 011°
- Magnetic
- 016°
- Published FAA baseline
- Open
- Threshold elevation
- 666 ft
- TDZ elevation
- 666 ft
- Displaced threshold
- None on record
- Threshold crossing height
- 41 ft
- Visual glide path
- 3°
- Traffic pattern
- Left
- Controlling obstruction
- tree, 82 ft, 1,589 ft from threshold, 16:1 slope
- True heading
- 191°
- Magnetic
- 196°
- Published FAA baseline
- Open
- Threshold elevation
- 661 ft
- TDZ elevation
- 662 ft
- Displaced threshold
- None on record
- Threshold crossing height
- 40 ft
- Visual glide path
- 3°
- Traffic pattern
- Left
- Controlling obstruction
- tree, 87 ft, 1,825 ft from threshold, 18:1 slope
Runway 02/20 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, 5.0°W (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 KUZA — 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.
- 02
- 68%
- 20
- 32%
Historical wind and crosswind on runway 02/20
20-year hourly climatology from the ASOS archive, computed per runway end.
From 173,347 hourly observations at KUZA (2005–2025), 105,287 with a steady wind direction (39.3% calm, variable or direction-less). One observation per clock hour; TRUE headings against TRUE wind.
Crosswind on runway 02/20 (either end)
| Crosswind (kt) | Share of wind hours |
|---|---|
| 0–5 | 80.7% |
| 5–10 | 17.4% |
| 10–15 | 1.8% |
| 15–20 | 0.1% |
| 20–25 | 0% |
| 25+ | 0% |
Strongest-crosswind month on average: Feb; calmest: Sep. Percentiles are streaming approximations (t-digest), accurate to about 0.1 kt.
Runway 02
Runway 20
“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 KUZA. 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 from | Share of wind hours | 02 favored | 20 favored | Mean crosswind | Crosswind > 15 kt |
|---|---|---|---|---|---|
| N 338–023° | 15% | 100% | 0% | 1.3 kt | 0% |
| NE 023–068° | 13% | 100% | 0% | 2.5 kt | 0% |
| E 068–113° | 4% | 79.8% | 20.2% | 4.5 kt | 0% |
| SE 113–158° | 3% | 0% | 100% | 3.5 kt | 0% |
| S 158–203° | 16% | 0% | 100% | 0.8 kt | 0% |
| SW 203–248° | 30% | 0% | 100% | 3.5 kt | 0.1% |
| W 248–293° | 13% | 12.8% | 87.2% | 6.1 kt | 0.7% |
| NW 293–338° | 7% | 100% | 0% | 5.4 kt | 0.5% |
By time of day (airport-local)
Seasonal runway conditions
| Month | Mean crosswind (kt) |
|---|---|
| Jan | 3.4 kt |
| Feb | 3.6 kt |
| Mar | 3.5 kt |
| Apr | 3.6 kt |
| May | 3.2 kt |
| Jun | 3.1 kt |
| Jul | 2.8 kt |
| Aug | 2.5 kt |
| Sep | 2.4 kt |
| Oct | 2.9 kt |
| Nov | 2.8 kt |
| Dec | 3.2 kt |
| Month | Prevailing | Mean wind | Gusty | Mean xw | xw > 10 | xw > 15 | xw > 20 | 02 tail > 5 | 20 tail > 5 | IFR | TS | Fog |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Jan | SW | 4.7 kt | 8.2% | 3.4 kt | 2.8% | 0.2% | 0% | 23.2% | 16.6% | 14.3% | 0.11% | 15% |
| Feb | SW | 5 kt | 10.1% | 3.6 kt | 4.2% | 0.4% | 0% | 28.6% | 15.2% | 13.5% | 0.14% | 13.4% |
| Mar | SW | 5.3 kt | 12.1% | 3.5 kt | 3.3% | 0.3% | 0% | 27.4% | 19.2% | 10.7% | 0.31% | 11.2% |
| Apr | SW | 5.3 kt | 12.8% | 3.6 kt | 3.6% | 0.3% | 0% | 32.8% | 13.5% | 6.8% | 0.65% | 8.7% |
| May | SW | 4.5 kt | 6.7% | 3.2 kt | 1.5% | 0.1% | 0% | 24.5% | 12.6% | 7.8% | 1.3% | 10% |
| Jun | SW | 4.1 kt | 3.8% | 3.1 kt | 1% | 0% | 0% | 21.8% | 8.9% | 5.9% | 1.94% | 9.8% |
| Jul | SW | 3.8 kt | 2.8% | 2.8 kt | 0.5% | 0% | 0% | 21.4% | 6.7% | 5.9% | 2.52% | 10.6% |
| Aug | SW | 3.2 kt | 2.2% | 2.5 kt | 0.4% | 0% | 0% | 14.1% | 10.7% | 8% | 1.74% | 13.1% |
| Sep | NE | 3.4 kt | 4.2% | 2.4 kt | 0.3% | 0% | 0% | 10.2% | 21.4% | 9.4% | 0.59% | 14% |
| Oct | SW | 3.6 kt | 5.7% | 2.9 kt | 1.1% | 0% | 0% | 14% | 20.1% | 9.9% | 0.06% | 14.4% |
| Nov | SW | 3.8 kt | 6.2% | 2.8 kt | 1.1% | 0% | 0% | 15.1% | 21% | 11% | 0.04% | 13.7% |
| Dec | SW | 4 kt | 6% | 3.2 kt | 2% | 0.2% | 0% | 22.1% | 13.8% | 16.8% | 0.06% | 18.2% |
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 02/20 closure history
Kept per source with its provenance: D-ATIS-observed, NOTAM-observed and the FAA published baseline are never merged.
KUZA has no D-ATIS, so there is no broadcast-observed closure record.
No closure NOTAM naming runway 02/20 has been received since the stream went live.
Runway 02/20: 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 02/20
Official PIREPs that name this runway explicitly, past 6 hours.
No pilot report in the last 6 hours names runway 02/20 at KUZA explicitly. Reports near the airport that do not name a runway are on the airport page.
Instrument approaches to runway 02/20
From the FAA d-TPP, linked to the official plates.
Runway 02
- ILSILS OR LOC RWY 02 ↗precision
- RNAV (GPS)RNAV (GPS) RWY 02 ↗
Runway 20
- RNAV (GPS)RNAV (GPS) RWY 20 ↗
13 departure procedures · 4 STARs · 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 KUZA 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 2025-12-31.
Get free ATIS alerts for KUZA
We'll message you on Telegram the moment a new METAR changes the picture at KUZA (Rock Hill - York County Airport): flight category, wind, or ceiling past your minimums.
Track KUZA on TelegramFree • no app to install • unsubscribe anytime
Other runways at KUZA
KUZA 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.