CL28
Heliport
Moronga Basin Chp
Joshua Tree, California

FAA NFDC Information Effective 56-day cycle 02/22/2024 - 4/18/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:CL28
Lat/Lng:34.1341555556, -116.273905556
34-08-02.9600N, 116-16-26.0600W
Estimated by Faa-Est Imagery on 07/14/2016
Elevation:2485 feet Estimated
Magnetic Variation:14E,(1985), [11E (2024)]
Sectional:LOS ANGELES
From City:2nm E of Joshua Tree

Operations

Use:Private
Airspace Analysis:CONDITIONAL
VFR, Private Use only.
Ownership:Publicly owned
Activation:10/1984
Control Tower:no
ARTCC:Los Angeles(ZLA)Los Angeles Center
FSS:Riverside FSS(RAL)
Wind Indicator:Unlighted
Lights:Activate Perimeter Lights - 122.750.
Landing Fee:no

Communications

Services

Fuel:Jet A - Kerosene, freeze point -40C

Based Aircraft

Single Engine GA:1
Helicopter GA:1
Total:2

Annual Operations

Total:0

Ownership

Owner:State of California
California Highway Patrol.
63683 29 Palms Highway
Joshua Tree, Ca 92252
760-366-3707
Manager:Facilities Section
Contact: Sgt. Randy O'Brien
Hcr 1, Box 61
Joshua Tree, Ca 92252
760-366-3707

Runways

Runways:H1

Runway H1

Length:15 feet
Width:15 feet
Surface:Porland Cement Concrete
Surface Treatment:NONE
Runway Lights Edge Intensity:Perimeter

Procedures

NOTAMs

Additional Remarks

for Cd Contact Los Angeles ARTCC at 661-575-2079.

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.