SN13
Airport
Albers
Cheney, Kansas

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:SN13 (Sierra-November-One-Three)
Lat/Lng: 37.6583469444, -97.7744952778
37-39-30.0490N, 097-46-28.1830W
Estimated
Elevation: 1380 feet Estimated
Magnetic Variation: 07E, (1990), [4E (2014)]
Sectional: WICHITA
From City: 2nm S of Cheney

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Approach to Each Runway is a 20:1 Glide Slope; 7:1 Transitional Slope; & Loa with Combs Airstrip.
Ownership: Privately owned
Activation: 03/1993
Control Tower: no
ARTCC: Kansas City Center (ZKC)
FSS: Wichita FSS (ICT)
Wind Indicator: Lighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: Donald R. Albers
P.O. Box 730
Cheney, Ks 67025
316-540-3151
Manager: Donald R. Albers
P.O. Box 730
Cheney, Ks 67025
316-540-3151

Runways

Runways: 18/36

Runway 18/36

Length: 2623 feet
Width: 50 feet
Surface: Grass / Sod
End 18 End 36
Objects: Road  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 15' AGL  
Object Distance: 0' Along centerline  

Procedures

NOTAMs

Additional Remarks

Owner Desires Airport not be Charted.

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.