Stargazer Field
Sandy, Oregon

FAA NFDC Information Effective 56-day cycle 06/22/2017 - 8/17/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:4OR6 (Four-Oscar-Romeo-Six)
Lat/Lng: 45.4498427778, -122.254255833
45-26-59.4340N, 122-15-15.3210W
Elevation: 510 feet Estimated
Magnetic Variation: 19E, (1990), [15E (2017)]
Sectional: SEATTLE
From City: 4nm N of Sandy


Use: Private
Airspace Analysis: CONDITIONAL
Provided Traffic Patterns are Est for N Side.
Ownership: Privately owned
Activation: 01/1992
Control Tower: no
ARTCC: Seattle Center (ZSE)
FSS: Mc Minnville FSS (MMV)
Wind Indicator: Unlighted
Landing Fee: no


UNICOM: 122.800


Based Aircraft

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

Annual Operations

Total: 0


Owner: Stargazer Llc
39391 S.E. Lusted Road
Sandy, or 97055
Manager: William Tosheff
39391 S.E. Lusted Road
Sandy, or 97055


Runways: 09/27

Runway 09/27

Length: 1850 feet
Width: 50 feet
Surface: Grass / Sod
End 09 End 27
Objects: Trees Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 100' AGL  
Object Distance: 50' Along centerline  



Additional Remarks

A30-09/27-Winds Permitting Land Runway 27 Takeoff Runway 09.
Watch for Birds; Animals; Workers & Farm Equipment on 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.