|
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: | GTG / KGTG |
|---|---|
| Lat/Lng: | 45.798377861111106, -92.66433091666667 45-47-54.1603N, 092-39-51.5913W Estimated by Faa on 09/06/2011 |
| Elevation: | 927 feet Surveyed by 3rd Party Survey on 06/25/2010 |
| Magnetic Variation: | 00E,(2015), [-1W (2026)] |
| Sectional: | GREEN BAY |
| From City: | 2nm NE of Grantsburg |
| Use: | Open to the public |
|---|---|
| Airspace Analysis: | NOT ANALYZED Existed Prior to 1959. |
| Ownership: | Publicly owned |
| Activation: | 10/1946 |
| Control Tower: | no |
| ARTCC: | Minneapolis(ZMP)Minneapolis Center |
| FSS: | Green Bay FSS(GRB) |
| NOTAMs and Weather: | GRBNOTAM-D service at airport |
| Wind Indicator: | Lighted |
| Segmented Circle: | yes |
| Lights: | Activate MIRL Runway 12/30 - CTAF. |
| Beacon: | Sunset-Sunrise White-Green (Lighted Land Airport) |
| Landing Fee: | no |
| CTAF: | 122.900 |
|---|
| Bottled Oxygen: | None |
|---|---|
| Bulk Oxygen: | None |
| Transient Storage: | Tie-Down |
| Owner: | Village of Grantsburg 316 S. Brad St Grantsburg, Within 54840 715-463-2405 |
|---|---|
| Manager: | Sheila Meyer 316 S. Brad St Email Address: Office@Villageofgrantsburg.Gov Grantsburg, Within 54840 715-463-2405 |
| Runways: | 05/23 12/30 |
|---|
| Length: | 3280 feet by 3rd Party Survey on 06/25/2010 |
|---|---|
| Width: | 120 feet |
| Surface: | Grass / Sod, Fair Condition |
| Surface Treatment: | NONE |
| End 05 | End 23 | |
|---|---|---|
| True Alignment: | 056,(055 Magnetic) | 236,(235 Magnetic) |
| Runway Markings: | Runway 05/23 Marked with Yellow Cones. | |
| Elevation at End: | 924.1' MSL | 924.2' MSL |
| Elevation at Touchdown Zone: | 927.1' MSL | 927.1' MSL |
| Objects: | Trees | |
| Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
| Object Clearance Slope: | 20:1 | 7:1 |
| Object Height: | 30' AGL | |
| Object Distance: | 225' Along centerline 125' Right of centerline |
| Length: | 2999 feet by 3rd Party Survey on 06/25/2010 |
|---|---|
| Width: | 60 feet |
| Surface: | Asphalt / Bituminous Concrete, Poor Condition Numerous Cracks and Vegetation in Pavement. |
| Surface Treatment: | NONE |
| Runway Lights Edge Intensity: | Med Intensity |
| End 12 | End 30 | |
|---|---|---|
| True Alignment: | 121,(120 Magnetic) | 301,(300 Magnetic) |
| Runway Markings: | Nonprecision Instrument,Markings Faded.,Poor Condition | Nonprecision Instrument,Markings Faded.,Poor Condition |
| Elevation at End: | 924.2' MSL | 923.6' MSL |
| Elevation at Touchdown Zone: | 926.7' MSL | 926.7' MSL |
| Objects: | Trees | Trees |
| Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a nonprecision approach | Utility runway with a nonprecision approach |
| Object Clearance Slope: | 6:1 | 10:1 |
| Object Height: | 20' AGL | 50' AGL |
| Object Distance: | 330' Along centerline 225' Left of centerline | 700' Along centerline 300' Left of centerline |
| • | A30-05/23-Closed Nov 1 - Apr 15. |
|---|---|
| • | Deer & Waterfowl on and in Vicinity of Airport. |
| • | 1100 ft MSL/182 ft AGL Water Tower Located 5060 ft SW Runway 05. |
| • | 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.