80VA
Airport
Holly Springs
Richmond, Virginia

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:80VA (Eight-Zero-Victor-Alpha)
Lat/Lng: 37.791255, -77.8247161111
37-47-28.5180N, 077-49-28.9780W
Estimated
Elevation: 250 feet Estimated
Magnetic Variation: 09W, (1990), [-10W (2014)]
Sectional: WASHINGTON
From City: 17nm N of Richmond

Operations

Use: Private
Ownership: Privately owned
Activation: 02/1994
Attended: All year Sat-Sun DAWN-DUSK (local)
Control Tower: no
ARTCC: Washington Center (ZDC)
FSS: Leesburg FSS (DCA)
Wind Indicator: Unlighted
Lights: for Strobe Light & LIRL Runway 06/24 Call (804) 883-5314.
Beacon: Flashing Strobe Light.
Landing Fee: no

Communications

Services

Fuel: Automotive Gasoline

Based Aircraft

Single Engine GA: 7
Total: 7

Annual Operations

Total: 0

Ownership

Owner: James Dunn Sr
Rt 1 Box 2270
Montpelier, Va 23192
804-883-5314
Manager: James Dunn Sr
Rt 1 Box 2270
Montpelier, Va 23193
804-883-5314

Runways

Runways: 06/24

Runway 06/24

Length: 2000 feet
Width: 90 feet
Surface: Grass / Sod
Runway Lights Edge Intensity: Low Intensity
End 06 End 24
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach

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.