OR00
Airport
Flying K Ranch
Beaverton, Oregon

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:OR00 (Oscar-Romeo-Zero-Zero)
Lat/Lng: 45.4345277778, -122.88
45-26-04.3000N, 122-52-48.0000W
Estimated
Elevation: 350 feet Estimated
Magnetic Variation: 19E, (1995), [16E (2014)]
Sectional: SEATTLE
From City: 4nm NE of Beaverton

Operations

Use: Private
Ownership: Privately owned
Activation: 06/2000
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: 4
Total: 4

Annual Operations

Total: 0

Ownership

Owner: Kobbefarm, Llc
11795 Kobbe Drive
Beaverton, or 97007
503-649-3381
or Call 503-808-0440.
Manager: Keith Kobbe
4635 SW 180Th Ave
Beaverton, or 97078
503-808-0440

Runways

Runways: 07/25

Runway 07/25

Length: 1700 feet
Width: 20 feet
Surface: Grass / Sod, Gravel
End 07 End 25
Objects:   Bldg
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   20' AGL
Object Distance:   1000' Along centerline

Procedures

NOTAMs

Additional Remarks

A30-07/25-Calm Wind Land Runway 07, Depart Runway 25.
Runway 07/25 Soft After Heavy Rain.
Trees S of Centerline Runway 07/25.

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.