| 3VG3
Airport
|
Serenity Farm
|
|
Burgess, Virginia
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | 3VG3 |
| Lat/Lng: |
37.9361083333, -76.3486083333
37-56-09.9900N, 076-20-54.9900W
Estimated by OWNER on 10/30/1999
|
| Elevation: |
10 feet
Surveyed
by OWNER
|
| Magnetic Variation: |
11W,
(2000),
[-11W (2013)]
|
| Sectional: |
WASHINGTON
|
| From City: |
4nm
SW of Burgess
|
| Use: |
Private
|
| Airspace Analysis: |
CONDITIONAL
Provided VFR only Clear 20:1 Approach Path, C00-Ord Flgt Pattern with 2 Pvt Arpts in Close Proximity.
|
| Ownership: |
Privately owned
|
| Activation: |
12/2001
|
| Control Tower: |
no
|
| ARTCC: |
Washington Center
(ZDC)
|
| FSS: |
Leesburg FSS
(DCA)
|
| Wind Indicator: |
Unlighted
|
| Landing Fee: |
no
|
| Single Engine GA: |
1
|
| Total: |
1
|
|
|
| Owner: |
Serenity Farm
2109 Mob Neck Rd
Northumberland County, Va 22039
804-580-4431
|
| Manager: |
Don Watrous
2115 Mob Neck Rd
Heathsville, Va 22473
804-580-1889
|
|
Runway 14/32
| Length: |
2200 feet
by Owner on 02/18/2009
|
| Width: |
75 feet
|
| Surface: |
Grass / Sod
|
|
End 14 |
End 32 |
| Objects: |
Trees
|
Trees
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
| Object Height: |
50' AGL
|
50' AGL
|
| Object Distance: |
200' Along centerline
|
50' Along centerline
|
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.