95VA
Airport
Buck Hollar
Danville, Virginia

FAA NFDC Information Effective 56-day cycle 11/13/2014 - 1/8/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:95VA
Lat/Lng: 36.6231936111, -79.3558552778
36-37-23.4970N, 079-21-21.0790W
Estimated
Elevation: 450 feet Estimated
Magnetic Variation: 07W, (1990), [-9W (2014)]
Sectional: CINCINNATI
From City: 3nm NE of Danville

Operations

Use: Private
Airspace Analysis: CONDITIONAL
VFR Daylight Use only; Coordination with Danville Muni Airport; Follow-on FAA Inspection.
Ownership: Privately owned
Activation: 11/1993
Control Tower: no
ARTCC: Washington Center (ZDC)
FSS: Leesburg FSS (DCA)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: H Dan Davis
3204 Old Richmond Rd
Danville, Va 24540
434-793-0410
Manager: H Dan Davis
3204 Old Richmond Rd
Danville, Va 24540
434-793-0410

Runways

Runways: 17/35

Runway 17/35

Length: 1200 feet
Width: 75 feet
Surface: Grass / Sod
End 17 End 35
Objects: Trees Hill
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 100' AGL 50' AGL
Object Distance: 200' Along centerline 200' Along centerline

Procedures

NOTAMs

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.