River Valley
Rhinelander, Wisconsin

FAA NFDC Information Effective 56-day cycle 06/22/2017 - 8/17/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:WS78
Lat/Lng: 45.5502777778, -89.4877777778
45-33-01.0000N, 089-29-16.0000W
Estimated by NACO on 08/04/2004
Elevation: 1525 feet Estimated by NACO on 08/04/2004
Magnetic Variation: 02W, (2000), [-3W (2017)]
Sectional: GREEN BAY
From City: 6nm SW of Rhinelander


Use: Private
Airspace Analysis: CONDITIONAL
Provided Clear 20:1 Approaches, Clear Obstacle Free Zone, and Clear Runway Safety Area.
Ownership: Privately owned
Activation: 11/2002
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Green Bay FSS (GRB)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0


Owner: Dennis J. Dalka
W1254 County a
Rhinelander, Within 54501
Manager: Dennis J. Dalka
W1254 County a
Rhinelander, Within 54501


Runways: 02/20

Runway 02/20

Length: 1610 feet
by Owner on 08/07/2001
Width: 120 feet
Surface: Grass / Sod
End 02 End 20
Displaced Threshold Distance: 288' 440'
Objects: Trees Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 20' AGL 30' AGL
Object Distance: 60' Along centerline 20' Along centerline



Additional Remarks

This information is current as of the date at the top of the page. These pages are valid for all US airports, based on information from FAA National Flight Data Center. Weather information is provided based on AvnWx Data Sources. NOTAM information is from FAA's NAIMES data portal.

As with most information on this website, this page is generated based on FAA data, with automatic translations done via computer. You can also directly read the A/FD via the green icon link at the top of the page, which is the FAA text, and sometimes provides a different translation of codes. Please email me (using link at top-right of this page) if you see information which is confusing, misleading, or wrong....Or have suggestions for additions/changes.

Comments from the user community are clearly noted as such this page, are for informational purposes only, may be wrong and/or out-of-date, and must not be used as a sole source for critical decision making. See Privacy Policy and Conditions of Use.