Dickinson Theodore Roosevelt Regional Airport
airport in North Dakota, United States of America

Dickinson Theodore Roosevelt Regional Airport (IATA: DIK, ICAO: KDIK, FAA LID: DIK), formerly Dickinson Municipal Airport, is six miles south of Dickinson, in Stark County, North Dakota. It is owned by the Dickinson Airport Authority.
The airport serves western North Dakota, eastern Montana and northwest South Dakota, home to Theodore Roosevelt National Park. The airport sees one airline, SkyWest Airlines operating on behalf of United Express, flying an Bombardier CRJ200 to Denver; Delta Connection flew to Minneapolis-St. Paul until November 30, 2015. The first airline flights were Frontier DC-3s in 1959.
Federal Aviation Administration records say the airport had 9,164 passenger boardings (enplanements) in calendar year 2008, 8,924 in 2009 and 10,383 in 2010.
The Federal Aviation Administration (FAA) National Plan of Integrated Airport Systems for 2021–2025 categorized it as a non-hub primary commercial service facility.
The airport is named for Theodore Roosevelt, Jr., the 26th President of the United States.
Facilities
The airport covers 626 acres (253 ha) at an elevation of 2,592 feet (790 m).
The public source identifies “Dickinson Theodore Roosevelt Regional Airport” as airport in North Dakota, United States of America. This brief keeps that definition visible, then builds a research path around Dickinson, Theodore and Roosevelt.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Dickinson Theodore Roosevelt Regional Airport”, the useful work is to connect “airport in North Dakota, United States of America” to the records capable of establishing context and consequence.
The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated Sep 19, 2026. The linked authority identifier is Q1656886. Authority coordinates are 46.797, -102.802. 2 of 2 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 2015, 1959, 2008 and 2009.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Dickinson Theodore Roosevelt Regional Airport”, its source revision and the description used here.
- Expand the search: follow Dickinson Theodore Roosevelt Regional Airport primary sources, Dickinson Theodore Roosevelt Regional Airport archive and Dickinson research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Dickinson Theodore Roosevelt Regional Airport”?
- Which authority defined the place, boundary or structure at the relevant date?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Dickinson Theodore Roosevelt Regional Airport” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.