NV30
Airport
Dixie Valley
Fallon, Nevada

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:NV30 (November-Victor-Three-Zero)
Lat/Lng: 39.9665816667, -117.827625
39-57-59.6940N, 117-49-39.4500W
Estimated
Elevation: 3443 feet Estimated
Magnetic Variation: 15E, (1985), [13E (2014)]
Sectional: LAS VEGAS
From City: 50nm NE of Fallon

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Pvt Use VFR.
Ownership: Privately owned
Activation: 02/1991
Control Tower: no
ARTCC: Oakland Center (ZOA)
FSS: Reno FSS (RNO)
Wind Indicator: Lighted
Lights: Activate HIRL Runway 16/34 - 122.9.
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Bureau of Land Management
850 Harvard Way
Reno, Nv
775-423-6535
Manager: Terra-Gen Dixie Valley, Llc
Other Contact: Missy Miller C/O Terra-Gen Operating Co. 9590 Prototype Ct. #200 Reno, Nv 89521 775-850-2266
Po Box 1270, Dixie Valley Rd
Fallon, Nv 89407
775-423-6535

Runways

Runways: 16/34

Runway 16/34

Length: 6000 feet
4000 Ft Paved 1000 Ft Each End Grvl.
Width: 60 feet
50 Ft Paved 5 Ft Each Side Grvl.
Surface: Asphalt / Bituminous Concrete, Gravel
Runway Lights Edge Intensity: High Intensity
End 16 End 34

Procedures

NOTAMs

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.