Quail Field
Pendleton, Oregon

FAA NFDC Information Effective 56-day cycle 01/05/2017 - 3/2/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:OG42 (Oscar-Golf-Four-Two)
Lat/Lng: 45.6548527778, -118.589694444
45-39-17.4700N, 118-35-22.9000W
Estimated by OWNER on 10/15/2002
Elevation: 1610 feet Estimated by OWNER on 10/15/2002
Magnetic Variation: [14E (2017)]
Sectional: SEATTLE
From City: 9nm E of Pendleton


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



Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

For year ending: 10/15/2002
Total: 0


Owner: Leonard & Janna Quaile
290 Chalan Palayso Ste 3
Agana Heights, Gu 96910
Manager: Leonard & Janna Quaile
290 Chalan Palayso Ste 3
Agana Heights, Gu 96910


Runways: 16/34

Runway 16/34

Length: 1335 feet
by Owner on 10/15/2002
Width: 30 feet
Surface: Grass / Sod
End 16 End 34
Objects:   Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   15' AGL
Object Distance:   250' Along centerline



Additional Remarks

A30-16/34-Runway Slope 3 % Down to North
Birds and Deer on & in Vicinity of Airport.

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.