8OR2
Airport
Kingston Airpark
Stayton, Oregon

FAA NFDC Information Effective 56-day cycle 04/03/2014 - 5/29/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:8OR2 (Eight-Oscar-Romeo-Two)
Lat/Lng: 44.7784552778, -122.730087222
44-46-42.4390N, 122-43-48.3140W
Estimated
Elevation: 871 feet Surveyed
Magnetic Variation: 19E, (1985), [16E (2014)]
Sectional: KLAMATH FALLS
From City: 3nm SE of Stayton

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Traffic Pats are Estabd E of Airport to Avoid Traffic Pats of Lone Oaks Airport; Kingston Airport Users are Adzd of Lone Oaks Airport Lctn Aprxly 1.3 NW.
Ownership: Privately owned
Control Tower: no
ARTCC: Seattle Center (ZSE)
FSS: Mc Minnville FSS (MMV)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 5
Ultralights: 1
Total: 6

Annual Operations

Total: 0

Ownership

Owner: Kenneth H Horn
42156 Kingston Lyons Dr
Stayton, or 97383
503-769-6287
Manager: Kenneth H Horn
42156 Kingston Lyons Dr
Stayton, or 97383
503-769-6287

Runways

Runways: 14/32

Runway 14/32

Length: 3000 feet
Width: 50 feet
Surface: Grass / Sod
End 14 End 32
Right Hand Pattern:   Yes
Objects: Trees Powerline
Object Height: 50' AGL  
Object Distance: 400' Along centerline 300' Along centerline

Procedures

NOTAMs

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.