Lovingston, Virginia

FAA NFDC Information Effective 56-day cycle 06/22/2017 - 8/17/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:VA96
Lat/Lng: 37.8254194444, -78.7316847222
37-49-31.5100N, 078-43-54.0650W
Elevation: 640 feet Estimated
Magnetic Variation: 08W, (1985), [-10W (2017)]
From City: 8nm NE of Lovingston


Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR; Opers are Conducted As Submitted on 7480-1; All Landings/Departures to/from Runway 17.
Ownership: Privately owned
Activation: 03/1990
Attended: All year Sat-Sun 1300-DARK (local)
Control Tower: no
ARTCC: Washington Center (ZDC)
FSS: Leesburg FSS (DCA)
Wind Indicator: Unlighted
Landing Fee: no


UNICOM: 122.700


Based Aircraft

Single Engine GA: 2
Total: 2

Annual Operations

Total: 0


Owner: Joyce T. & Roger F. Wood
Rt 1, Box 23
Faber, Va 22938
(434) 263-4512
Manager: Roger Wood & James Tinder
Rt 1, Box 23
Faber, Va 22938
(434) 263-4512


Runways: 17/35

Runway 17/35

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



Additional Remarks

All Landings/Takeoffs on Runway 17.

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.