Hay Acres
Akeley, 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:1MN2 (One-Mike-November-Two)
Lat/Lng: 46.9383333333, -94.7570333333
46-56-18.0000N, 094-45-25.3200W
Estimated by FAA-EST IMAGERY on 11/04/2013
Elevation: 1430 feet Estimated
Magnetic Variation: 04E, (1995), [1E (2017)]
Sectional: TWIN CITIES
From City: 4nm S of Akeley


Use: Private
Airspace Analysis: CONDITIONAL
Provided Obstns in Runway Approach be Lowered/Removed; 125 Ft Either Side of Runway Centerline & 200 Ft Off Runway Ends Clear; Area 60 Ft Either Side of Runway Centerline & 240 Ft Off Runway Ends Cleared & Graded.
Ownership: Privately owned
Activation: 05/1998
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Princeton FSS (PNM)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Joseph C. Penaz
8775 Airport Road
Waconia, Mn 55387
Manager: Joseph C. Penaz
8775 Airport Road
Waconia, Mn 55387


Runways: 16/34

Runway 16/34

Length: 1650 feet
Width: 75 feet
Surface: Grass / Sod, Good Condition
End 16 End 34
Runway Markings: 16/34 Thlds Marked with Triangular Orange Signs.  
Objects: 16/34 38 Ft Trees 800 Ft N; 50 Ft Trees 100 Ft W; 50 Ft Trees 200 Ft E.  



Additional Remarks

Do not Chart Per Minnesota Department of Transportation

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.