MT03
Airport
Lakeside
Lakeside, Montana

FAA NFDC Information Effective 56-day cycle 04/03/2014 - 5/29/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:MT03 (Mike-Tango-Zero-Three)
Lat/Lng: 47.9934083333, -114.224305556
47-59-36.2700N, 114-13-27.5000W
Estimated
Elevation: 3440 feet Surveyed
Magnetic Variation: [14E (2014)]
From City: 2nm NW of Lakeside

Operations

Use: Private
Airspace Analysis: Provided VFR Use only.
Ownership: Privately owned
Activation: 09/2007
Control Tower: no
ARTCC: Salt Lake City Center (ZLC)
FSS: Great Falls FSS (GTF)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Fuel: Grade 100LL Gasoline (low lead blue)

Based Aircraft

Single Engine GA: 5
Multi Engine GA: 2
Total: 7

Annual Operations

Total: 0

Ownership

Owner: Montana Eagle Development Llc
7135 Hwy 93 South
Lakeside, Mt 59922
406-844-2091
Manager: Trevor Schaefer
Alternate Airport Manager is Mr. Robert Martyn.
Montana Eagle Development Llc
Lakeside, Mt 59922
406-844-2091

Runways

Runways: 01/19

Runway 01/19

Length: 3376 feet
Width: 60 feet
Surface: Asphalt / Bituminous Concrete, Good Condition
End 01 End 19
Runway Markings: Basic Basic
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach

Procedures

NOTAMs

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.