CL39
Heliport
Napa County Fire Dept
St Helena, 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:CL39
Lat/Lng:38.5485, -122.510730556
38-32-54.6000N, 122-30-38.6300W
Estimated by Owner on 04/19/1999
Elevation:308 feet Surveyed by Owner on 04/19/1999
Magnetic Variation:16E,(2000), [13E (2024)]
Sectional:SAN FRANCISCO
From City:3nm N of St Helena

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Provided VFR Operations, Private Use and Ingress/Egress Routes Do not Conflict with TPA of Any Established Public-Use Landing Areas.
Ownership:Publicly owned
Activation:06/2000
Attended:Continuous
Control Tower:no
ARTCC:Oakland(ZOA)Oakland Center
FSS:Oakland FSS(OAK)
NOTAMs and Weather:FDC
Wind Indicator:Lighted
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:Napa County Fire Dept.
Owner Contact - Barry Biermann - Napa County Fire Chief
1199 Big Tree Road
St. Helena, Ca 94574
(707) 299-1460
Manager:Geoff Belyea
1199 Big Tree Road
St. Helena, Ca 94574
707-967-1400

Runways

Runways:H1

Runway H1

Length:100 feet
by Owner on 04/19/1999
Width:100 feet
Surface:Grass / Sod
Surface Treatment:NONE

Procedures

NOTAMs

Additional Remarks

for Cd Contact Oakland ARTCC at 510-745-3380.

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.