IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
FAA NFDC Information 28-day cycle
Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
FAA Identifier: | 19KY (One-Nine-Kilo-Yankee) |
---|---|
Lat/Lng: | 38.706456111111116, -84.5999425 38-42-23.2420N, 084-35-59.7930W Estimated |
Elevation: | 940 feet Estimated |
Magnetic Variation: | 03W,(1985), [-6W (2025)] |
Sectional: | CINCINNATI |
From City: | 2nm N of Dry Ridge |
Use: | Private |
---|---|
Airspace Analysis: | CONDITIONAL Provided VFR/Personal Use. |
Ownership: | Privately owned |
Activation: | 08/1988 |
Control Tower: | no |
ARTCC: | Indianapolis(ZID)Indianapolis Center |
FSS: | Louisville FSS(LOU) |
Wind Indicator: | Unlighted |
Beacon: | None |
Landing Fee: | no |
Owner: | Chase Bentley 660 Bannister Pike Dry Ridge, Ky 41035 760-828-2211 |
---|---|
Manager: | Chase Bentley 660 Bannister Pike Dry Ridge, Ky 41035 760-828-2211 |
Runways: | 18/36 |
---|
Length: | 2200 feet |
---|---|
Width: | 60 feet |
Surface: | Grass / Sod |
Surface Treatment: | NONE |
End 18 | End 36 | |
---|---|---|
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
• | Tower 1/2 NM S of Airport. |
---|---|
• | for Cd Contact Cincinnati Approach at 859-372-6440 |
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 Chart Supplment (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.
rgrep