Selby, South Dakota

FAA NFDC Information Effective 56-day cycle 06/22/2017 - 8/17/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:9SD7
Lat/Lng: 45.4749897222, -100.035121111
45-28-29.9630N, 100-02-06.4360W
Elevation: 1960 feet Estimated
Magnetic Variation: 09E, (1985), [5E (2017)]
Sectional: TWIN CITIES
From City: 2nm SE of Selby


Use: Private
Airspace Analysis: NOT ANALYZED
Estb Prior to 1959.
Ownership: Privately owned
Activation: 12/1946
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Huron FSS (HON)
Wind Indicator: Unlighted
Landing Fee: no



Airframe Repair: None
Powerplant Repair: None
Bottled Oxygen: None
Bulk Oxygen: None
Transient Storage: Hanger

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Local GA (< 20 miles): 400
Non-local GA: 400
Total: 800


Owner: Dan Beaman
Rr 1, Box 69
Selby, Sd 57472
Manager: Dan Beaman
Rr 1, Box 69
Selby, Sd 57472


Runways: 13/31

Runway 13/31

Length: 1500 feet
Width: 40 feet
Surface: Grass / Sod
End 13 End 31
Objects: Road  
Object Clearance Slope: 14:1 50:1
Object Distance: 300' Along centerline  

Runway 17/35

Length: 3000 feet
Width: 40 feet
Surface: Grass / Sod
End 17 End 35
Objects: Road  
Object Clearance Slope: 18:1
Approach Ratio Runways 17 & 13 Includes Vehicle Clearance.
Object Distance: 270' Along centerline  



Additional Remarks

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.