VG17
Heliport
Defense Supply Center Richmond
Richmond, 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:VG17 (Victor-Golf-One-Seven)
Lat/Lng: 37.4236111111, -77.4505555556
37-25-25.0000N, 077-27-02.0000W
Estimated
Elevation: 115 feet Estimated
Magnetic Variation: 09W, (1995), [-10W (2014)]
Sectional: WASHINGTON
From City: 10nm N of Richmond

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Accurate Ingress/Egress Route, Clear 8:1 Slope, Appropriate Ingress/Egress Mkgs, Lgtd Windsock for Night Operations, Control Vehicular Traffic During Helicopter Operations, Red Obstruction Light Fence at South Edge of Pad.
Ownership: Army owned
Activation: 02/2000
Control Tower: no
ARTCC: Washington Center (ZDC)
FSS: Leesburg FSS (DCA)
Wind Indicator: Unlighted
Lights: Sunset-Sunrise (local time)
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: U.S. Army
8000 Jeff Davis Hwy
Richmond, Va 23297-5201
804-279-4888
Manager: Dennis B. Lacey
8000 Jeff Davis Hwy
Richmond, Va 23297-5201
804-279-4888

Runways

Runways: H1

Runway H1

Length: 98 feet
Width: 98 feet
Surface: Asphalt / Bituminous Concrete, Good Condition
Runway Lights Edge Intensity: Perimeter

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.