|
IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
| FAA Identifier: | 8AN6 |
|---|---|
| Lat/Lng: |
47.6591666667, -117.681666667 47-39-33.0000N, 117-40-54.0000W Estimated by OWNER on 03/25/2002 |
| Elevation: | 2410 feet Surveyed by OWNER on 03/25/2002 |
| Magnetic Variation: | 18E, (2000), [15E (2013)] |
| Sectional: | SEATTLE |
| From City: | 9nm S of Medical Lake |
| Use: | Private |
|---|---|
| Airspace Analysis: |
CONDITIONAL Provided Loa with Spokane Int'L Airport and Fairchild AFB Due to Class C Airspace. |
| Ownership: | Privately owned |
| Activation: | 11/2002 |
| Control Tower: | no |
| ARTCC: | Seattle Center (ZSE) |
| FSS: | Seattle FSS (SEA) |
| Wind Indicator: | Lighted |
| Landing Fee: | no |
Based Aircraft
|
Annual Operations
|
Ownership
|
| Runways: | 05/23 |
|---|
| Length: |
750 feet by Owner on 03/25/2002 |
|---|---|
| Width: | 28 feet |
| Surface: | Grass / Sod |
| End 05 | End 23 | |
|---|---|---|
| Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
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.