|
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/ICAO Identifier: | ETH / KETH |
|---|---|
| Lat/Lng: | 45.780506083333336, -96.54379797222222 45-46-49.8219N, 096-32-37.6727W Estimated by Faa on 06/07/2011 |
| Elevation: | 1022 feet Surveyed by 3rd Party Survey on 10/25/2009 |
| Magnetic Variation: | 05E,(1995), [2E (2026)] |
| Sectional: | TWIN CITIES |
| From City: | 3nm SW of Wheaton |
| Use: | Open to the public |
|---|---|
| Ownership: | Publicly owned |
| Activation: | 04/1947 |
| Control Tower: | no |
| ARTCC: | Minneapolis(ZMP)Minneapolis Center |
| FSS: | Princeton FSS(PNM) |
| NOTAMs and Weather: | ETHNOTAM-D service at airport |
| Pattern Altitude: | 1998 MSL (976 AGL) |
| Wind Indicator: | Lighted |
| Lights: | Runway 16/34 MIRL Preset to Low Intensity. to Increase Intensity & Activate PAPI Runway 16/34 - CTAF. |
| Beacon: | Sunset-Sunrise White-Green (Lighted Land Airport) |
| Landing Fee: | no |
| CTAF: | 122.800 |
|---|---|
| UNICOM: | 122.800 |
| Weather: | AWOS-3 320-563-4975 118.775 |
| Airframe Repair: | None |
|---|---|
| Powerplant Repair: | None |
| Bottled Oxygen: | None |
| Bulk Oxygen: | None |
| Transient Storage: | Tie-Down |
| Other Services: | Crop Dusting, Aircraft Sales |
| Owner: | City of Wheaton Po Box 868, 104 9Th St N Wheaton, Mn 56296 320-563-4110 |
|---|---|
| Manager: | Amy Olson Po Box 868, 104 9Th St N Wheaton, Mn 56296 320-563-4110 |
| Runways: | 06/24 16/34 |
|---|
| Length: | 1953 feet by 3rd Party Survey on 10/25/2009 |
|---|---|
| Width: | 175 feet |
| Surface: | Grass / Sod, Good Condition |
| Surface Treatment: | NONE |
| End 06 | End 24 | |
|---|---|---|
| True Alignment: | 063,(061 Magnetic) | 243,(241 Magnetic) |
| Runway Markings: | Marked with Yellow Cones. | |
| Elevation at End: | 1016.0' MSL | 1017.4' MSL |
| Elevation at Touchdown Zone: | 1018.1' MSL | 1018.1' MSL |
| Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
| Object Clearance Slope: | 20:1 | 20:1 |
| Object Height: | 3' AGL | |
| Object Distance: | 100' Along centerline |
| Length: | 3298 feet by 3rd Party Survey on 10/25/2009 |
|---|---|
| Width: | 75 feet |
| Surface: | Asphalt / Bituminous Concrete, Fair Condition |
| Surface Treatment: | NONE |
| Runway Lights Edge Intensity: | Med Intensity |
| End 16 | End 34 | |
|---|---|---|
| True Alignment: | 164,(162 Magnetic) | 344,(342 Magnetic) |
| Runway Markings: | Nonprecision Instrument,Good Condition | Nonprecision Instrument,Good Condition |
| Elevation at End: | 1017.2' MSL | 1022.7' MSL |
| Elevation at Touchdown Zone: | 1022.7' MSL | 1022.7' MSL |
| Threshold Crossing Glide Path Height: | 25' AGL | 25' AGL |
| Visual Glide Path Angle: | 3.00° | 3.00° |
| Visual Glide Slope Indicator: | 2-light PAPI on left side of runway | 2-light PAPI on left side of runway PAPI 34 Unusable Beyond 8 Degree Left of Course. |
| Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a nonprecision approach | Utility runway with a nonprecision approach |
| Object Clearance Slope: | 20:1 | 20:1 |
| • | A30-06/24-not Plowed Winter Months. |
|---|---|
| • | for Cd Contact Minneapolis ARTCC at 651-463-5588. |
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.