OR22
Airport
Roppair
Albany, Oregon

FAA NFDC Information Effective 56-day cycle 03/21/2024 - 5/16/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:OR22 (Oscar-Romeo-Two-Two)
Lat/Lng:44.6192888889, -123.031759722
44-37-09.4400N, 123-01-54.3350W
Estimated
Elevation:247 feet Estimated
Magnetic Variation:19E,(1985), [14E (2024)]
Sectional:SEATTLE
From City:2nm SE of Albany

Operations

Use:Private
Airspace Analysis:OBJECTIONABLE
E111 Advrsly Affects Safe & Efficient Use of Airspace Because Traffic Pats Cannot be Made Compatible W Airport 4200' N.
Ownership:Privately owned
Activation:07/1971
Control Tower:no
ARTCC:Seattle(ZSE)Seattle Center
FSS:Mc Minnville FSS(MMV)
Wind Indicator:Unlighted
Landing Fee:no

Communications

Services

Airframe Repair:None
Powerplant Repair:None

Based Aircraft

Single Engine GA:1
Multi Engine GA:1
Total:2

Annual Operations

Total:0

Ownership

Owner:J E Ropp
35711 SE Kennel Rd
Albany, or 97321
503-928-3094
Manager:J E Ropp
35711 SE Kennel Rd
Albany, or 97321
503-928-3094

Runways

Runways:16/34

Runway 16/34

Length:1700 feet
Width:60 feet
Surface:Grass / Sod
Surface Treatment:NONE
End 16 End 34
Objects: Powerline

Procedures

NOTAMs

Additional Remarks

for Cd Contact Cascade Approach at 541-607-4674/4675, When Approach Closed Contact Seattle ARTCC at 253-351-3694.

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.