62ND
Airport
|
Morten
|
Larimore, North Dakota
|
|
|
|
FAA NFDC Information Effective 56-day cycle 12/26/2024 - 2/20/2025
FAA Identifier: | 62ND |
---|
Lat/Lng: | 47.7791572222, -97.7595319444 47-46-44.9660N, 097-45-34.3150W Estimated |
---|
Elevation: | 1340 feet Estimated |
---|
Magnetic Variation: | 07E,(1985), [3E (2024)] |
---|
Sectional: | TWIN CITIES |
---|
From City: | 10nm SW of Larimore |
---|
Use: | Private |
---|
Airspace Analysis: | NOT ANALYZED Filed for Record Purposes only. |
---|
Ownership: | Privately owned |
---|
Activation: | 04/1981 |
---|
Control Tower: | no |
---|
ARTCC: | Minneapolis(ZMP)Minneapolis Center |
---|
FSS: | Grand Forks FSS(GFK) |
---|
Wind Indicator: | None |
---|
Landing Fee: | no |
---|
|
|
Owner: | John E Morten Box 513 Larimore, Nd 58251 701-343-2065 |
---|
Manager: | John E Morten Box 513 Larimore, Nd 58251 701-343-2065 |
---|
|
Runway 08/26
Length: | 1700 feet |
---|
Width: | 80 feet |
---|
Surface: | Grass / Sod |
---|
Surface Treatment: | NONE |
---|
|
End 08 |
End 26 |
---|
Objects: | | Road |
---|
Object Distance: | | 50' Along centerline |
---|
Runway 17/35
Length: | 2600 feet |
---|
Width: | 100 feet |
---|
Surface: | Grass / Sod |
---|
Surface Treatment: | NONE |
---|
|
End 17 |
End 35 |
---|
Objects: | | Road |
---|
Object Distance: | | 50' Along centerline |
---|
• | 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.