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 04/18/2024 - 6/13/2024
Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
FAA Identifier: | Y93 |
---|---|
Lat/Lng: | 44.9968948889, -84.1272343611 44-59-48.8216N, 084-07-38.0437W Estimated by Faa Oe/Aaa on 08/23/2016 |
Elevation: | 880 feet Estimated by Faa Oe/Aaa on 08/23/2016 |
Magnetic Variation: | 06W,(1985), [-7W (2024)] |
Sectional: | LAKE HURON |
From City: | 1nm SE of Atlanta |
Use: | Open to the public |
---|---|
Airspace Analysis: | NOT ANALYZED Non-Compliance with Far 157. |
Ownership: | Publicly owned |
Activation: | 04/1940 |
Attended: | All year Every day ON CALL (local) for Service Call Airport Manager. |
Control Tower: | no |
ARTCC: | Minneapolis(ZMP)Minneapolis Center |
FSS: | Lansing FSS(LAN) |
NOTAMs and Weather: | LANNOTAM-D service at airport |
Wind Indicator: | Lighted |
Segmented Circle: | yes |
Lights: | Activate PAPI Runway 23; LIRL Runway 05/23 & 13/31 - CTAF. |
Landing Fee: | no |
CTAF: | 122.900 |
---|
Transient Storage: | Tie-Down |
---|
Based Aircraft
|
Annual Operations
|
Ownership
|
Runways: | 05/23 13/31 |
---|
Length: | 3000 feet |
---|---|
Width: | 60 feet |
Surface: | Asphalt / Bituminous Concrete, Fair Condition |
Surface Treatment: | NONE |
Runway Lights Edge Intensity: | Low Intensity |
End 05 | End 23 | |
---|---|---|
True Alignment: | 047,(040 Magnetic) | 227,(220 Magnetic) |
Runway Markings: | Basic,Faded.,Poor Condition | Basic,Faded.,Poor Condition |
Displaced Threshold Distance: | 1494' | 370' |
Elevation at End: | 880.0' MSL | 872.0' MSL |
Threshold Crossing Glide Path Height: | 22' AGL | |
Visual Glide Path Angle: | 4.00° | |
Visual Glide Slope Indicator: | 2-light PAPI on left side of runway | |
Objects: | Trees | Road |
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
Object Clearance Slope: | 4:1 Approach Ratio 20:1 to Dthr. | 12:1 Approach Ratio 20:1 to Dthr. |
Object Height: | 54' AGL | 15' AGL |
Object Distance: | 442' Along centerline 93' Left of centerline | 393' Along centerline 125'Left and Right of centerline |
Length: | 3223 feet |
---|---|
Width: | 100 feet |
Surface: | Grass / Sod, Fair Condition |
Surface Treatment: | NONE |
Runway Lights Edge Intensity: | Low Intensity LIRL Oprs Jun-Sep. |
End 13 | End 31 | |
---|---|---|
True Alignment: | 127,(120 Magnetic) | 307,(300 Magnetic) |
Runway Markings: | Yellow Cones. | Yellow Cones. |
Displaced Threshold Distance: | 758' | 569' |
Elevation at End: | 876.0' MSL | 872.8' MSL |
Objects: | Trees | Trees |
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
Object Clearance Slope: | 1:1 Approach Ratio 20:1 to Dthr. | 3:1 Approach Ratio 12:1 to Dthr Ovr +62 ft Tree, 789 ft Dist, 112 ft R. |
Object Height: | 61' AGL | 55' AGL |
Object Distance: | 10' Along centerline 124' Left of centerline | 208' Along centerline 57' Right of centerline |
• | A30-13/31-Closed Nov-Apr & When Snow Covd. No Snow Removal. |
---|---|
• | A30-05/23-Cfm Winter Conds & Snow Removal Prior to Use - Call Airport Manager or Asst Airport Manager. |
• | for Cd Contact Minneapolis ARTCC at 651-463-5588. |
• | Deer & Lrg Birds on & in Vicinity of Airport. |
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.