Vesper, Wisconsin

FAA NFDC Information Effective 56-day cycle 01/05/2017 - 3/2/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:4WN2
Lat/Lng: 44.4169913611, -89.9863794167
44-25-01.1689N, 089-59-10.9659W
Estimated by OWNER on 12/04/2003
Elevation: 1055 feet Estimated by NACO on 03/31/2010
Magnetic Variation: [-3W (2017)]
Sectional: GREEN BAY
From City: 4nm S of Vesper


Use: Private
Airspace Analysis: CONDITIONAL
Provided Clear 20:1 Approaches, Clear Obstacle Free Zone, Clear Runway Safety Area, and Cll Approach Runway 18, All Departure Runway 36, and You Must Personally Brief Other Users.
Ownership: Privately owned
Activation: 06/2004
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Green Bay FSS (GRB)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Ultralights: 1
Total: 1

Annual Operations

Total: 0


Owner: Ronald C. Swensen
4874 Matthies Rd
Vesper, Within 54489
Manager: Ronald C. Swensen
4874 Matthies Rd
Vesper, Within 54489


Runways: 09/27

Runway 09/27

Length: 1200 feet
Width: 60 feet
Surface: Grass / Sod
End 09 End 27
Objects: Powerline Powerline
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 40' AGL 40' AGL
Object Distance: 10' Along centerline 30' Along centerline



Additional Remarks

Departure Runway 36 Approach Runway 18.

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.