Y93
Airport
Atlanta Municipal
Atlanta, Michigan

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:Y93
Lat/Lng: 44.9984271944, -84.1304597222
44-59-54.3379N, 084-07-49.6550W
Estimated
Elevation: 875 feet Estimated
Magnetic Variation: 06W, (1985), [-7W (2014)]
Sectional: LAKE HURON
From City: 1nm SE of Atlanta

Operations

Use: Open to the public
Airspace Analysis: NOT ANALYZED
E111 Non-Compliance with Far 157.
Ownership: Publicly owned
Activation: 04/1940
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Lansing FSS (LAN)
NOTAMs and Weather: LAN NOTAM-D service at airport
Pattern Altitude: 1875 MSL (1000 AGL)
Wind Indicator: Lighted
Segmented Circle: yes
Lights: Activate LIRL Runway 13/31 & LIRL Runway 05/23, PAPI Runway 23 - CTAF.
Landing Fee: no

Communications

CTAF: 122.900

Services

Fuel: Grade 100LL Gasoline (low lead blue)
Fuel by Prior Arrangement Call 989-306-0926.
Transient Storage: Tie-Down

Based Aircraft

Single Engine GA: 9
Total: 9

Annual Operations

For year ending: 12/31/2011
Local GA (< 20 miles): 700
Non-local GA: 700
Total: 1400

Ownership

Owner: Briley & Avery Twps
P.O. Box 322, 7570 M-52
Atlanta, Mi 49709
989-785-4050
Briley Twp Ofc.
Manager: Tom Weber
10298 Hammond Rd, 7570 M-32
Atlanta, Mi 49719
989-306-0926
John Vick, Asst. Mgr 989-370-5334.

Runways

Runways: 05/23
13/31

Runway 05/23

Length: 3000 feet
Width: 60 feet
Surface: Asphalt / Bituminous Concrete, Good Condition
Runway Lights Edge Intensity: Low Intensity
End 05 End 23
True Alignment: 046, (039 Magnetic) 226, (219 Magnetic)
Runway Markings: Basic, Good Condition Basic, Good Condition
Displaced Threshold Distance: 1230' 370'
Elevation at End: 875.0' MSL 875.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 Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Clearance Slope: 3:1
Approach Ratio 20:1 at Displaced Threshold.
6:1
Approach Ratio 12:1 at Displaced Threshold.Ovr +65 Ft Trees, 780 Ft from Displaced Threshold, 175 Ft R; 25:1 Based on Straight out Ovr 70 Ft Trees 2380 Ft Dstc.
Object Height: 80' AGL 20' AGL
Object Distance: 392' Along centerline
135' Left of centerline
320' Along centerline
125' Left of centerline

Runway 13/31

Length: 3223 feet
Width: 100 feet
Surface: Grass / Sod, Fair Condition
Runway Lights Edge Intensity: Low Intensity
LIRL Operates Jun Thru Sep.
End 13 End 31
Runway Markings: 13/31 Marked with 3 Ft Yellow Cones.  
Displaced Threshold Distance: 758' 569'
Elevation at End: 875.0' MSL 875.0' 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: 0:1
Approach Ratio 20:1 at Displaced Threshold.
0:1
Approach Ratio 20:1 at Displaced Threshold Ovr 42 Ft Trees, 840 Ft from Displaced Threshold, 0 B.
Object Height: 50' AGL 30' AGL
Object Distance: 50' Along centerline
120' Left of centerline
0' Along centerline
110' Right of centerline

Procedures

NOTAMs

Additional Remarks

for Winter Condition/Snow Removal Runway 05/23 Confirm Prior to Use; Call 989-306-0926; No Snow Removal Runway 13/31.
Runway 13/31 Closed Nov-Apr & When Snow Covered.

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.