Bismark, North 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:ND96
Lat/Lng: 46.8007111111, -100.678644444
46-48-02.5600N, 100-40-43.1200W
Estimated by OWNER on 01/31/2014
Elevation: 1730 feet Estimated
Magnetic Variation: 09E, (1995), [6E (2017)]
Sectional: TWIN CITIES
From City: 4nm E of Bismark


Use: Private
Airspace Analysis: CONDITIONAL
Provided Obstns in Runway Approach Slope Removed/Lowered to Provide 20:1 Approach Clearance; 125 Ft Either Side of Centerline & 200 Ft Off Runway Ends Clear of Obstns; Clear & Grade 60 Ft Either Side of Runway & 240 Ft Off Runway Ends; Estab Opnl Letter with Bis ATC.
Ownership: Privately owned
Activation: 05/1998
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Grand Forks FSS (GFK)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 3
Total: 3

Annual Operations

Total: 0


Owner: Allen Sauter
501 66Th St SE
Bismarck, Nd 58501
(701) 471-9804


Runways: 08/26

Runway 08/26

Length: 3000 feet
Width: 100 feet
Surface: Grass / Sod
End 08 End 26
Objects: Powerline  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 50' AGL  
Object Distance: 300' 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.