4MN3
Heliport
Lexington
Ham Lake, Minnesota

FAA NFDC Information Effective 56-day cycle 03/21/2024 - 5/16/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:4MN3
Lat/Lng:45.2771555556, -93.150625
45-16-37.7600N, 093-09-02.2500W
Estimated by Ado on 12/12/2019
Elevation:907 feet Estimated by Ado on 12/12/2019
Magnetic Variation:02E,(1995), [0W (2024)]
Sectional:TWIN CITIES
From City: in Ham Lake

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Provided All Approach/Departure from 030-045, the Area from 110-170 may be Used After Small Trees are Removed, Wind Indicatoe Maintained, Comply with Far 91.126(B)(2), Maintain Warning Signs Around Takeoff & Landing Area.
Ownership:Privately owned
Activation:05/2000
Attended:Continuous
Control Tower:no
ARTCC:Minneapolis(ZMP)Minneapolis Center
FSS:Princeton FSS(PNM)
Wind Indicator:Lighted
Landing Fee:no

Communications

Services

Based Aircraft

Helicopter GA:1
Total:1

Annual Operations

Total:0

Ownership

Owner:Steven M. Thul
4656 169Th Lane NE
Ham Lake, Mn 55304
612-434-6415
Manager:Steven M. Thul
4656 169Th Lane NE
Ham Lake, Mn 55304
612-434-6415

Runways

Runways:H1

Runway H1

Length:200 feet
Width:85 feet
Surface:Grass / Sod
Surface Treatment:NONE
Remarks:Tlof 15X15 ft; Fato 200X85 ft.

Procedures

NOTAMs

Additional Remarks

for Cd Contact Minneapolis ARTCC at 651-463-5588.

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.