| VA12
Airport
|
Gravely
|
|
Martinsville, Virginia
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | VA12 (Victor-Alpha-One-Two) |
|---|
| Lat/Lng: |
36.6468041667, -79.7969805556
36-38-48.4950N, 079-47-49.1300W
Estimated
|
|---|
| Elevation: |
750 feet
Estimated
|
|---|
| Magnetic Variation: |
06W,
(1985),
[-9W (2013)]
|
|---|
| Sectional: |
CINCINNATI
|
|---|
| From City: |
4nm
SE of Martinsville
|
|---|
| Use: |
Private
|
|---|
| Airspace Analysis: |
CONDITIONAL
Runway 09 Displaced to Insure Clearance Over Fence; Trees North are Kept Topped.
|
|---|
| Ownership: |
Privately owned
|
|---|
| Activation: |
07/1988
|
|---|
| Control Tower: |
no
|
|---|
| ARTCC: |
Washington Center
(ZDC)
|
|---|
| FSS: |
Leesburg FSS
(DCA)
|
|---|
| Wind Indicator: |
Unlighted
|
|---|
| Landing Fee: |
no
|
|---|
| Single Engine GA: |
1
|
|---|
| Total: |
1
|
|---|
|
|
| Owner: |
Edward M. Gravely
Po Box 3762
Martinsville, Va 24115
276-638-1039
|
|---|
| Manager: |
Edward M. Gravely
Po Box 3762
Martinsville, Va 24115
276-638-1039
|
|---|
|
Runway 10/28
| Length: |
1500 feet
|
|---|
| Width: |
60 feet
|
|---|
| Surface: |
Grass / Sod
|
|---|
|
End 10 |
End 28 |
|---|
| Objects: |
Tree
|
|
|---|
| Object Height: |
40' AGL
|
|
|---|
| Object Distance: |
400' Along centerline
|
|
|---|
| • | Owner Requests Airport be Charted. |
|---|
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.
