Swanson Field
Crown, Minnesota

FAA NFDC Information Effective 56-day cycle 09/14/2017 - 11/9/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:MY95
Lat/Lng: 45.4463888889, -93.3827777778
45-26-47.0000N, 093-22-58.0000W
Elevation: 935 feet Estimated
Magnetic Variation: 03E, (1990), [0W (2017)]
Sectional: TWIN CITIES
From City: 4nm E of Crown


Use: Private
Airspace Analysis: CONDITIONAL
Provided Obstruction in Runway Approach Sfcs be Lowered or Removed or Runway Thrs be Dspld & Marked to Provide a Min 20:1 Approach Clearance with Remaining Usable Runway Length to Permit Safe Landing/Takeoff; Ref to Ac 150/5300-4B; & 125 Ft Either Side of Runway Centerline Extnd 300 Ft Off Both Runway Ends be Clear of Obstns.
Ownership: Privately owned
Activation: 12/1992
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Princeton FSS (PNM)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0


Owner: David R. Swanson
4585 261St Ave., NW
Isanti, Mn 55040
Manager: David R. Swanson
4585 261St Ave., NW
Isanti, Mn 55040


Runways: 18/36

Runway 18/36

Length: 2600 feet
Width: 100 feet
Surface: Grass / Sod
End 18 End 36
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach



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.