61MN
Airport
Traverse Air
Wheaton, Minnesota

FAA NFDC Information Effective 56-day cycle 11/13/2014 - 1/8/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:61MN (Six-One-Mike-November)
Lat/Lng: 45.9535711111, -96.4008986111
45-57-12.8560N, 096-24-03.2350W
Estimated
Elevation: 1002 feet Surveyed
Magnetic Variation: 06E, (1985), [3E (2014)]
Sectional: TWIN CITIES
From City: 10nm NE of Wheaton

Operations

Use: Private
Airspace Analysis: NOT ANALYZED
Non-Compliance with Far Part 157.
Ownership: Privately owned
Activation: 11/1972
Attended: Apr-Oct Every day 24 hrs
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Princeton FSS (PNM)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Airframe Repair: Minor
Powerplant Repair: None
Bottled Oxygen: None
Bulk Oxygen: None
Transient Storage: Hanger

Based Aircraft

Single Engine GA: 1
Multi Engine GA: 1
Total: 2

Annual Operations

Total: 0

Ownership

Owner: George Ahlsten
7542 710 Avenue
Wheaton, Mn 56296
320-760-2131
Manager: George Ahlsten
7542 710 Avenue
Wheaton, Mn 56296
320-760-2131

Runways

Runways: E/W

Runway E/W

Length: 3000 feet
Width: 80 feet
Surface: Grass / Sod
End E End W
Objects: Powerline  
Object Height: 25' AGL  
Object Distance: 900' Along centerline  

Procedures

NOTAMs

Additional Remarks

Airport Closed Winter Months.

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.