MU65
Airport
Lakeside
Farmington, Missouri

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:MU65
Lat/Lng: 37.7694955556, -90.4656788889
37-46-10.1840N, 090-27-56.4440W
Estimated
Elevation: 910 feet Estimated
Magnetic Variation: 02E, (1990), [-1W (2014)]
Sectional: ST LOUIS
From City: 2nm W of Farmington

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided a 2:1 Approach Slope is Maintained; 7:1 Transitional Slope is Maintained; Right Traffic is Established for Runway 20.
Ownership: Privately owned
Activation: 02/1994
Control Tower: no
ARTCC: Kansas City Center (ZKC)
FSS: Saint Louis FSS (STL)
Wind Indicator: Lighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: John G Hunt
Box 526
Farmington, Mo 63640
314-756-5826
Manager: John G Hunt
Box 526
Farmington, Mo 63640
573-756-5826

Runways

Runways: 02/20

Runway 02/20

Length: 1200 feet
Width: 250 feet
Surface: Grass / Sod
End 02 End 20
Right Hand Pattern:   Yes
Objects: Trees  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 20' AGL  
Object Distance: 50' Along centerline  

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.