IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
FAA NFDC Information 28-day cycle
Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
FAA Identifier: | WA50 (Whiskey-Alpha-Five-Zero) |
---|---|
Lat/Lng: | 47.35221666666667, -122.62513055555554 47-21-07.9800N, 122-37-30.4700W Estimated by Faa-Est Imagery on 06/27/2016 |
Elevation: | 326 feet Estimated by Owner on 08/12/2011 |
Magnetic Variation: | [15E (2025)] |
Sectional: | SEATTLE |
From City: | 2nm NW of Gig Harbor |
Use: | Private Medical. |
---|---|
Ownership: | Privately owned |
Activation: | 03/2005 |
Control Tower: | no |
ARTCC: | Seattle(ZSE)Seattle Center |
FSS: | Seattle FSS(SEA) |
Wind Indicator: | Lighted |
Lights: | for Perimeter Lights Call 253-851-3111. |
Beacon: | None |
Landing Fee: | no |
Owner: | Pierce City Fire Dist. 5 10222 Bujacich Rd NW Gig Harbor, Wa 98332 253-851-3111 |
---|---|
Manager: | Chief John Burgess Addnl Contact Eric Watson Asst Chief 253-851-3111. 10222 Bujacich Rd NW Gig Harbor, Wa 98332 253-851-3111 |
Runways: | H1 |
---|
Length: | 36 feet |
---|---|
Width: | 36 feet |
Surface: | Asphalt / Bituminous Concrete |
Surface Treatment: | NONE |
Runway Lights Edge Intensity: | Perimeter |
• | Call Before Use: 253-851-3111 |
---|---|
• | for Cd Contact Seattle Approach at 206-214-4794. |
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 Chart Supplment (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.
rgrep