80WA
Airport
Sfs Airpark
Hadlock, Washington

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:80WA (Eight-Zero-Whiskey-Alpha)
Lat/Lng: 48.0358333333, -122.773611111
48-02-09.0000N, 122-46-25.0000W
Estimated
Elevation: 120 feet Estimated
Magnetic Variation: 20E, (1995), [16E (2014)]
Sectional: SEATTLE
From City: 1nm W of Hadlock

Operations

Use: Private
Ownership: Privately owned
Activation: 06/2000
Control Tower: no
ARTCC: Seattle Center (ZSE)
FSS: Seattle FSS (SEA)
Wind Indicator: Lighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 2
Ultralights: 1
Total: 3

Annual Operations

Total: 0

Ownership

Owner: Frary & Solomonson
2321 NE 160 Loop
Vancouver, Wa 98684
360-253-8605
or Call 360-253-8605
Manager: Jim Frary
2321 NE 160 Loop
Vancouver, Wa 98684
360-253-8605
or Call 360-253-8605

Runways

Runways: 08/26

Runway 08/26

Length: 1600 feet
Width: 75 feet
Surface: Grass / Sod
End 08 End 26
True Alignment: 106, (090 Magnetic) 286, (270 Magnetic)
Objects: Trees Bldg
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 40' AGL 40' AGL
Object Distance: 0' Along centerline 0' 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.