| WV30
Airport
|
Rainelle
|
|
Rainelle, West Virginia
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | WV30 (Whiskey-Victor-Three-Zero) |
| Lat/Lng: |
37.9487286111, -80.7164763889
37-56-55.4230N, 080-42-59.3150W
Estimated
|
| Elevation: |
3446 feet
Surveyed
|
| Magnetic Variation: |
06W,
(1985),
[-8W (2013)]
|
| Sectional: |
CINCINNATI
|
| From City: |
3nm
SE of Rainelle
|
| Use: |
Private
|
| Ownership: |
Privately owned
|
| Activation: |
12/1969
|
| Control Tower: |
no
|
| ARTCC: |
Washington Center
(ZDC)
|
| FSS: |
Elkins FSS
(EKN)
|
| Wind Indicator: |
Unlighted
|
| Landing Fee: |
no
|
| Airframe Repair: |
None
|
| Powerplant Repair: |
None
|
| Transient Storage: |
Hanger,Tie-Down
|
| Single Engine GA: |
1
|
| Total: |
1
|
|
| For year ending: |
08/19/1987
|
| Local GA (< 20 miles): |
20
|
| Non-local GA: |
50
|
| Military Operations: |
4
|
| Total: |
74
|
|
| Owner: |
Rainelle Arpk Inc.
209 3Rd St Lilly Park
Rainelle, Wv 25962
304-438-7221
|
| Manager: |
Ralph D. Williams
209 Thind Hill Park
Rainelle, Wv 25962
304-438-7221
|
|
Runway 17/35
| Length: |
3300 feet
|
| Width: |
75 feet
|
| Surface: |
Grass / Sod, Good Condition
|
|
End 17 |
End 35 |
| Objects: |
Trees
|
Tree
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
| Object Clearance Slope: |
1:1
|
1:1
|
| Object Height: |
25' AGL
|
20' AGL
|
| Object Distance: |
50' Right of centerline
|
65' Left of 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.