70CL
Airport
Amargosa
Death Valley Junction, California

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:70CL (Seven-Zero-Charlie-Lima)
Lat/Lng: 36.2957891667, -116.425874722
36-17-44.8410N, 116-25-33.1490W
Estimated
Elevation: 2037 feet Estimated
Magnetic Variation: 14E, (1985), [12E (2014)]
Sectional: LAS VEGAS
From City: 1nm W of Death Valley Junction

Operations

Use: Private
Airspace Analysis: NOT ANALYZED
Estabd Prior to 5/15/59.
Ownership: Privately owned
Control Tower: no
ARTCC: Los Angeles Center (ZLA)
FSS: Riverside FSS (RAL)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Airframe Repair: None
Powerplant Repair: None

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: Amargosa Opera House Inc.
P.O. Box 608
Death Valley Jct, Ca 92328
Manager: Richard Regnell
P.O. Box 608
Death Valley Jct, Ca 92328
760-852-4441
Cell - 562-841-5266

Runways

Runways: 17/35
H1

Runway 17/35

Length: 1625 feet
Width: 50 feet
Surface: Natural Soil
End 17 End 35
Objects: Powerline
60' Powerline East Side Runway.
 
Object Height: 60' AGL  
Object Distance: 440' Along centerline  

Runway H1

Length: 40 feet
Width: 40 feet
Surface: Porland Cement Concrete

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.