27MO
Airport
Route 66 Airfield
Carthage, Missouri

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:27MO (Two-Seven-Mike-Oscar)
Lat/Lng: 37.1938888889, -94.2241666667
37-11-38.0000N, 094-13-27.0000W
Estimated
Elevation: 1055 feet Estimated
Magnetic Variation: 04E, (1995), [2E (2014)]
Sectional: KANSAS CITY
From City: 4nm E of Carthage

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Maintain a Clear 20:1 Approach Surface and 7:1 Transitional Surface.
Ownership: Privately owned
Activation: 06/1996
Control Tower: no
ARTCC: Kansas City Center (ZKC)
FSS: Columbia FSS (COU)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 3
Total: 3

Annual Operations

Total: 0

Ownership

Owner: Route 66 Airfield Partnership
Po Box 561
Carthage, Mo 64836
417-358-3035
Manager: David Waller
Harlan Block 9575 Cr 90 Carthage, Mo 64836 417-358-6427
Po Box 561
Carthage, Mo 64836
417-358-3035

Runways

Runways: 18/36

Runway 18/36

Length: 2500 feet
Width: 100 feet
Surface: Grass / Sod
End 18 End 36
Displaced Threshold Distance: 495' 550'
Objects: Powerline Powerline
Object Marking: Marked Marked
Object Height: 31' AGL 28' AGL
Object Distance: 125' Along centerline 0' 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.