7KY1
Heliport
Nicholas County Hospital
Carlisle, Kentucky

FAA NFDC Information Effective 56-day cycle 04/03/2014 - 5/29/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:7KY1 (Seven-Kilo-Yankee-One)
Lat/Lng: 38.3161111111, -84.0519444444
38-18-58.0000N, 084-03-07.0000W
Estimated by OWNER on 03/01/2010
Elevation: 830 feet Estimated by OWNER on 03/01/2010
Magnetic Variation: [-6W (2014)]
Sectional: CINCINNATI
From City: 2nm W of Carlisle

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only; Takeoff/Landing Area Marked; All Approach/Departure Operations Conducted in a Area from 160 to 220 Deg Clkws and 330 to 020 Deg Clkws.
Ownership: Privately owned
Activation: 06/2010
Attended: Continuous
Control Tower: no
ARTCC: Indianapolis (ZID) Indianapolis Center (ZID)
FSS: Louisville FSS (LOU)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

For year ending: 10/30/1998
Total: 0

Ownership

Owner: Jmhc Dba Nicholas County Hospital
Po Box 232
Carlisle, Ky 40311
859-289-7181
Manager: Mark Hatton
P.O. Box 232
Carlisle, Ky 40311
859-289-3855

Runways

Runways: H1

Runway H1

Length: 40 feet
by Owner on 03/01/2010
Width: 40 feet
Surface: Porland Cement Concrete

Procedures

NOTAMs

Additional Remarks

Owner Desires Airport not be Charted.

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.