Rooster Field
Shelbyville, Kentucky

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:40KY (Four-Zero-Kilo-Yankee)
Lat/Lng: 38.2934030556, -85.2049552778
38-17-36.2510N, 085-12-17.8390W
Elevation: 840 feet Estimated
Magnetic Variation: 02W, (1985), [-5W (2017)]
Sectional: ST LOUIS
From City: 4nm N of Shelbyville


Use: Private
Airspace Analysis: CONDITIONAL
E111: VFR; Private Use only.
Ownership: Privately owned
Activation: 11/1979
Control Tower: no
ARTCC: Indianapolis Center (ZID)
FSS: Louisville FSS (LOU)
Wind Indicator: Unlighted
Segmented Circle: yes
Landing Fee: no



Based Aircraft

Single Engine GA: 4
Total: 4

Annual Operations

Total: 0


Owner: Bill & Nydia Bors
5750 Eminence Pike
Shelbyville, Ky 40065
(502) 500-7258
Manager: Bill Bors
Additional Contact: Chuck Reed - 502-235-4262
5750 Eminence Pike
Shelbyville, Ky 40065
Addl Phone 502-235-4262.


Runways: 11/29

Runway 11/29

Length: 2000 feet
by Owner on 10/07/2002
Width: 40 feet
Surface: Grass / Sod
End 11 End 29
Runway Markings: Runway 11/29 Thlds Marked with Flat White Rocks Flush with the Ground.  
Objects: Trees Powerline
Object Marking:   Marked
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 50' AGL 35' AGL
Object Distance: 1000' Along centerline 150' Along centerline



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.