00VA
Airport
Vaughan
Alton, Virginia

FAA NFDC Information Effective 56-day cycle 04/03/2014 - 5/29/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:00VA (Zero-Zero-Victor-Alpha)
Lat/Lng: 36.576, -78.9991666667
36-34-33.6000N, 078-59-57.0000W
Estimated by OWNER on 12/04/2007
Elevation: 551 feet Estimated by OWNER on 12/04/2007
Magnetic Variation: [-9W (2014)]
Sectional: WASHINGTON
From City: 12nm NE of Alton

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Pvt Use only, VFR Operation only.
Ownership: Privately owned
Activation: 10/2008
Control Tower: no
ARTCC: Washington (ZDC) 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

For year ending: 12/31/2007
Total: 0

Ownership

Owner: Ronnie D. & Jeremy L. Vaughan
1226 Blane Road
Alton, Va 24520
434-753-1260
Manager: Ronnie D. & Jeremy L. Vaughan
1226 Blane Road
Alton, Va 24520
434-753-1260

Runways

Runways: 01/19

Runway 01/19

Length: 1300 feet
by Owner on 12/04/2007
Width: 100 feet
Surface: Grass / Sod
End 01 End 19
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach

Procedures

NOTAMs

Additional Remarks

Bldgs 5 Mi SW of Runway 01/19.

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.