Bloxom, 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:VG56
Lat/Lng: 37.8083333333, -75.6027777778
37-48-30.0000N, 075-36-10.0000W
Estimated by OWNER on 08/06/2004
Elevation: 50 feet Estimated
Magnetic Variation: [-11W (2017)]
From City: 2nm NW of Bloxom


Use: Private
Airspace Analysis: CONDITIONAL
Provided Daylgt Operations; IFR Operations not Conducted; Powerlines Opposite End of Roadway Removed; and a Clear 7:1 Approach for Each Approach/Departure Path.
Ownership: Privately owned
Activation: 01/2005
Control Tower: no
ARTCC: Washington Center (ZDC)
FSS: Leesburg FSS (DCA)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 3
Total: 3

Annual Operations

Total: 0


Owner: Wayne Johnson & Bobby Flowers
P. O. Box 90
Bloxom, Va 23308
Manager: Bobby Flowers
22224 Foxgrove Rd
Parksley, Va 23421


Runways: 15/33

Runway 15/33

Length: 2000 feet
by Owner on 08/06/2004
Width: 200 feet
Surface: Grass / Sod, Good Condition
End 15 End 33
Objects: Powerline  
Object Marking: Marked
with Red Balls
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 60' AGL  
Object Distance: 800' Along centerline  



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.