Carillion Giles Community Hospital
Pearisburg, Virginia

FAA NFDC Information Effective 56-day cycle 08/17/2017 - 10/12/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:VA67
Lat/Lng: 37.333875, -80.7126472222
37-20-01.9500N, 080-42-45.5300W
Estimated by FAA-EST IMAGERY on 09/16/2015
Elevation: 1984 feet Estimated by OWNER on 06/28/2010
Magnetic Variation: [-8W (2017)]
From City: 1nm W of Pearisburg


Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only; Takeoff/Landing Area Marked; Please Note That the Pad is Located Near a Military Training Rte Ip-80. Please Use Utmost Precaution.
Ownership: Privately owned
Activation: 05/2011
Attended: Continuous
Control Tower: no
ARTCC: Washington (ZDC) Washington Center (ZDC)
FSS: Leesburg FSS (DCA)
Wind Indicator: Unlighted
Lights: Sunset-Sunrise (local time)
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Carillion Health Systems
Po Box 13367
Roanoke, Va 24033
Manager: Alan Verling
Additional Contact: Don Mullins 159 Hartley Way Pearisburg, Va 24134 Dkmullins@Carillionclinic.Org
2900 Tyler Dr
Radford, Va 24141


Runways: H1

Runway H1

Length: 50 feet
by Owner on 06/28/2010
Width: 50 feet
Surface: Porland Cement Concrete, Good Condition
Runway Lights Edge Intensity: Perimeter



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.