Central Cascades Fire And Ems
Cresent Lake, Oregon

FAA NFDC Information Effective 56-day cycle 04/30/2015 - 6/25/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:OR33 (Oscar-Romeo-Three-Three)
Lat/Lng: 43.5267777778, -121.948083333
43-31-36.4000N, 121-56-53.1000W
Elevation: 4750 feet Estimated
Magnetic Variation: 18E, (1995), [15E (2015)]
From City: 3nm N of Cresent Lake


Use: Private
Medical Use.
Ownership: Privately owned
Activation: 06/2000
Control Tower: no
ARTCC: Seattle Center (ZSE)
FSS: Mc Minnville FSS (MMV)
Wind Indicator: Lighted
Segmented Circle: yes
Lights: Sunset-Sunrise (local time)
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Central Cascades Fire & Ems
Po Box 1065, 20400 Crescent Lake Hwy
Crescent Lake, or 97425-1065
Manager: Tim Cramblit
Po Box 1065, 20400 Crescent Lake Hwy
Crescent Lake, or 97425-1065


Runways: H1

Runway H1

Length: 100 feet
Width: 100 feet
Surface: Asphalt / Bituminous Concrete
Runway Lights Edge Intensity: Perimeter



Additional Remarks

62' Tower 225' W of Heli.

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.