| 8WT0
Heliport
|
Eastern State Hospital Ems
|
|
Medical Lake, Washington
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | 8WT0 (Eight-Whiskey-Tango-Zero) |
| Lat/Lng: |
47.5733333333, -117.704166667
47-34-24.0000N, 117-42-15.0000W
Estimated by OWNER on 10/04/2009
|
| Elevation: |
2500 feet
Estimated
by OWNER
on 10/04/2009
|
| Magnetic Variation: |
[15E (2013)]
|
| Sectional: |
SEATTLE
|
| From City: |
1nm
W of Medical Lake
|
| Use: |
Private
|
| Airspace Analysis: |
CONDITIONAL
Provided VFR Operations and Pvt Use only; Proponent Monitors the Geight of the Trees on the East Side of the Heli As Potential Obstns; Class C Rules Apply to All Departures and Arrs Because Heli is Within the Ska Class C Surface Area and Borders on a Military Hel Training Area.
|
| Ownership: |
Privately owned
|
| Activation: |
01/2010
|
| Attended: |
Continuous
|
| Control Tower: |
no
|
| ARTCC: |
Seattle
(ZSE)
Seattle Center
(ZSE)
|
| FSS: |
Seattle FSS
(SEA)
|
| Wind Indicator: |
Lighted
|
| Lights: |
Dawn-Dusk
|
| Landing Fee: |
no
|
|
|
| For year ending: |
06/30/2009
|
| Total: |
0
|
|
| Owner: |
State of Washington, Dshs
Po Box 800
Medical Lake, Wa 99022
509-565-4354
|
| Manager: |
Connie Wilmot
Po Box 800
Medical Lake, Wa 99022
509-565-4354
|
|
Runway H1
| Length: |
40 feet
by Owner on 10/04/2009
|
| Width: |
40 feet
|
| Surface: |
Porland Cement Concrete
|
| Runway Lights Edge Intensity: |
Perimeter
Perimeter and Flood Lights.
|
| • | Owner Desires Airport not be Charted. |
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.