Yucca Airstrip
Mercury, Nevada

FAA NFDC Information Effective 56-day cycle 09/14/2017 - 11/9/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:NV11 (November-Victor-One-One)
Lat/Lng: 36.9457861111, -116.037811667
36-56-44.8300N, 116-02-16.1220W
Elevation: 3919 feet Surveyed
Magnetic Variation: 14E, (1985), [12E (2017)]
Sectional: LAS VEGAS
From City: 17nm N of Mercury


Use: Private
Airspace Analysis: NOT ANALYZED
Formal Evaluation not Rqrd, Date Estabd not Known.
Ownership: Publicly owned
Control Tower: no
ARTCC: Los Angeles Center (ZLA)
Wind Indicator: Unlighted
Landing Fee: no



Airframe Repair: None
Powerplant Repair: None

Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Nevada Dept of Energy
Box 98518
Las Vegas, Nv 89193-8518
Manager: Michael Childers
Other Contcact: Joseph M. Ginanni 702-295-0209
Nevada Dept of Energy, Box 98518
Las Vegas, Nv 89193-8518


Runways: 14/32

Runway 14/32

Length: 9000 feet
Width: 200 feet
Surface: Natural Soil
End 14 End 32
Right Hand Pattern: Yes Yes
Runway Markings: 14/32 Has Reflectors.  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach



Additional Remarks

Airstrip Within R-4808.
Official Business only. Prior Permission Rqrd from Dept of Energy for All Flights.
Owner Desires Airport not 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.