46KY
Heliport
St Elizabeth-Ft Thomas Hospital
Fort Thomas, Kentucky

FAA NFDC Information Effective 56-day cycle 04/18/2024 - 6/13/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:46KY
Lat/Lng:39.0778380556, -84.4646636111
39-04-40.2170N, 084-27-52.7890W
Estimated by Faa-Est Imagery on 10/09/2015
Elevation:814 feet Estimated
Magnetic Variation:03W,(1985), [-6W (2024)]
Sectional:CINCINNATI
From City: in Fort Thomas

Operations

Use:Private
Airspace Analysis:CONDITIONAL
VFR, Pvt Use; Coord Use of Heli with Louisville Gado; Coord Com Procs with Cincinnati-Lunken Field Air Traffic Control Tower.
Ownership:Privately owned
Activation:09/1980
Attended:Continuous
Control Tower:no
ARTCC:Indianapolis(ZID)Indianapolis Center
FSS:Louisville FSS(LOU)
Wind Indicator:Unlighted
Beacon:for Rotating Beacon Call 859-572-3100.
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:St Elizabeth - ft Thomas Hospital
85 N Grand Avenue
Fort Thomas, Ky 41075
859-301-2000
Manager:John Mitchell
Dave Guethlein 859-572-3529.
85 N Grand Avenue
Fort Thomas, Ky 41075
859-301-2000

Runways

Runways:H1

Runway H1

Length:20 feet
Width:20 feet
Surface:Porland Cement Concrete
Surface Treatment:NONE

Procedures

NOTAMs

Additional Remarks

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 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.