Seaplane Base
The Pass
Mound, Minnesota

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:MN80 (Mike-November-Eight-Zero)
Lat/Lng: 44.9143680556, -93.6885336111
44-54-51.7250N, 093-41-18.7210W
Elevation: 930 feet Estimated
Magnetic Variation: 03E, (1990), [0W (2017)]
Sectional: TWIN CITIES
From City: 2nm S of Mound


Use: Private
Airspace Analysis: CONDITIONAL
Submit Signed Agreement Between Owners of Flobacks Spb & Self Showing Compatable Traffic Patterns Without Overlap.
Ownership: Privately owned
Activation: 08/1994
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: Kurt Opheim
3895 Co Rd 44
Minnetrista, Mn 55364
Manager: Kurt Opheim
3895 Co Rd 44
Minnetrista, Mn 55364


Runways: 06/24

Runway 06/24

Length: 5500 feet
Width: 750 feet
Surface: Water
End 06 End 24

Runway 16/34

Length: 7000 feet
Width: 750 feet
Surface: Water
End 16 End 34
Objects: Trees Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 100' AGL 150' AGL
Object Distance: 1070' Along centerline 1070' 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.