Oregon City, Oregon

FAA NFDC Information Effective 56-day cycle 08/20/2015 - 10/15/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:OG30 (Oscar-Golf-Three-Zero)
Lat/Lng: 45.31651, -122.605368889
45-18-59.4360N, 122-36-19.3280W
Elevation: 420 feet Estimated
Magnetic Variation: 19E, (1985), [15E (2015)]
Sectional: SEATTLE
From City: 3nm S of Oregon City


Use: Private
Airspace Analysis: NOT ANALYZED
Non-Compliance with Far 157.
Ownership: Privately owned
Activation: 08/1970
Control Tower: no
ARTCC: Seattle Center (ZSE)
FSS: Mc Minnville FSS (MMV)
Wind Indicator: Unlighted
Landing Fee: no



Airframe Repair: Major
Powerplant Repair: Major
Bottled Oxygen: None
Bulk Oxygen: None
Transient Storage: Hanger

Based Aircraft

Single Engine GA: 3
Total: 3

Annual Operations

Total: 0


Owner: Henry Pflegl
20001 S Leland Road 2001
Oregon City, or 97045
Manager: Henry Pflegl
20001 S Leland Road 2001
Oregon City, or 97045


Runways: 04/22

Runway 04/22

Length: 1800 feet
Width: 250 feet
Surface: Grass / Sod
End 04 End 22
Objects: Powerline Road
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Clearance Slope: 20:1 1:1
Object Distance: 300' Along centerline 15' Along centerline



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.