8LL4
Heliport
Richland Meml Hospital
Olney, Illinois

FAA NFDC Information Effective 56-day cycle 03/21/2024 - 5/16/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:8LL4
Lat/Lng:38.7358638889, -88.0770333333
38-44-09.1100N, 088-04-37.3200W
Estimated by Faa-Est Imagery on 04/12/2016
Elevation:485 feet Surveyed
Magnetic Variation:00E,(1985), [-4W (2024)]
Sectional:ST LOUIS
From City:1nm N of Olney

Operations

Use:Private
Medical Use.
Airspace Analysis:CONDITIONAL
All Ingress/Egress Routes are to be to the North and/or West.
Ownership:Privately owned
Activation:11/1972
Attended:Continuous
Control Tower:no
ARTCC:Indianapolis(ZID)Indianapolis Center
FSS:Columbia FSS(COU)
Wind Indicator:Unlighted
Beacon:for Rotating Beacon Call 618-395-2131.
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:Richland Meml Hospital Inc
800 East Locust St
Olney, Il 62450-2598
618-395-7340
Manager:Gina Thomas
Additional Contact: Les Harrison 800 E Locust, Olney, Il 62450 Phone 618-395-6080 Email LES.HARRISON@CARLERMH.COM
800 E.Locust
Olney, Il 62450
618-395-2131

Runways

Runways:H1

Runway H1

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

Procedures

NOTAMs

Additional Remarks

Fire Extinguishers Available for Landings.
for Cd Contact Evansville Approach at 812-436-4690, When Approach Closed Contact Indianapolis ARTCC at 317-247-2411.

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.