Craddock Field
Licking, Missouri

FAA NFDC Information Effective 56-day cycle 06/22/2017 - 8/17/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:6MU9
Lat/Lng: 37.5347666667, -91.9651583333
37-32-05.1600N, 091-57-54.5700W
Estimated by OWNER on 04/30/2004
Elevation: 1199 feet Estimated by OWNER on 04/30/2004
Magnetic Variation: [0W (2017)]
Sectional: KANSAS CITY
From City: 6nm E of Licking


Use: Private
Airspace Analysis: CONDITIONAL
Provided Clear 20:1 Approaches & Clear 7:1 Transitional Sfcs.
Ownership: Privately owned
Activation: 07/2006
Control Tower: no
ARTCC: Kansas City Center (ZKC)
FSS: Columbia FSS (COU)
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Single Engine GA: 1
Gliders: 1
Ultralights: 1
Total: 3

Annual Operations

For year ending: 04/01/2003
Total: 0


Owner: Joseph Jagr
16165 Hwy Af
Licking, Mo 65542
Manager: Joseph Jagr
16165 Hwy Af
Licking, Mo 65542


Runways: 09/27

Runway 09/27

Length: 2000 feet
by Owner on 04/30/2004
Width: 60 feet
Surface: Grass / Sod
End 09 End 27
Displaced Threshold Distance:   1000'
Objects:   Powerline
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:   200' Along centerline



Additional Remarks

Ultralights & Gliders on & in Vicinity of Airport.

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.