42OR
Airport
Shotgun Ranch Airstrip
Post, 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:42OR (Four-Two-Oscar-Romeo)
Lat/Lng:44.1341666667, -120.323055556
44-08-03.0000N, 120-19-23.0000W
Estimated by Naco on 04/04/2006
Elevation:3430 feet Estimated by Naco on 04/04/2006
Magnetic Variation: [14E (2024)]
Sectional:SEATTLE
From City:8nm E of Postof Post, or.

Operations

Use:Private
Ownership:Privately owned
Activation:11/2005
Control Tower:no
ARTCC:Seattle(ZSE)Seattle Center
FSS:Mc Minnville FSS(MMV)
Wind Indicator:Lighted
Landing Fee:no

Communications

Services

Based Aircraft

Single Engine GA:1
Total:1

Annual Operations

Total:0

Ownership

Owner:Wayne Perry
3025 100Th St SW
Everett, Wa 98204
(425) 519-3988
Manager:Wayne Perry
Other Contact Jennifer Ross 425-519-3988; JENN@SHOTGUNCREEK.COM
3025 100Th St SW
Everett, Wa 98204
(425) 519-3988

Runways

Runways:01/19

Runway 01/19

Length:1650 feet
by Owner on 08/28/2006
Width:50 feet
Surface:Asphalt / Bituminous Concrete, Porland Cement Concrete
Surface Treatment:NONE
End 01 End 19
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach

Procedures

NOTAMs

Additional Remarks

for Cd 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.