Fayette County Memorial Hospital
Washington Court House, Ohio

FAA NFDC Information Effective 56-day cycle 01/05/2017 - 3/2/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:11OH (One-One-Oscar-Hotel)
Lat/Lng: 39.5477555556, -83.4279583333
39-32-51.9200N, 083-25-40.6500W
Estimated by OWNER on 03/21/2013
Elevation: 981 feet Estimated by OWNER on 03/21/2013
Magnetic Variation: 05W, (2000), [-7W (2017)]
From City: 3nm NE of Washington Court House


Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only; Due to Close Prxmty of Fayette County Airport (I23), Operators Using the Fayette County Memorial Hospital Heli Should Monitor and Provide Traffic Reports on the Fayette County Airport Common Traffic Advisory Frequency (122.80); Takeoff/Landing Area Marked.
Ownership: Privately owned
Activation: 07/2013
Control Tower: no
ARTCC: Indianapolis Center (ZID)
FSS: Dayton FSS (DAY)
NOTAMs and Weather: FDC
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Fayette County Memorial Hospital
1430 Columbus Ave
Washington Court House, Oh 43160
Manager: Rodger Smith
1430 Columbus Ave
Washington Court House, Oh 43160


Runways: H1

Runway H1

Length: 62 feet
by Owner on 03/21/2013
Width: 60 feet
Surface: Asphalt / Bituminous Concrete



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.