Weeze Airport
airport in Germany
Weeze Airport (IATA: NRN, ICAO: EDLV), less commonly known as Niederrhein Airport and sometimes marketed as Düsseldorf-Weeze, is a minor international airport in the Lower Rhine region of Germany. It is used by Ryanair. The airport is situated 3.7 km (2.3 mi) southwest of the municipality of Weeze (German pronunciation: [ˈveːtsə]) and 7 km (4.3 mi) northwest of Kevelaer, about 33 km (21 mi) southeast of the Dutch city of Nijmegen, and 48 km (30 mi) northwest of the German city of Duisburg.
History
Foundation and early years
The airport uses the facilities of the former military airbase RAF Laarbruch, and began operating as a civilian airport in 2003. There is also a large fire department training facility on the airport grounds. Its IATA code is NRN because of its official name Flughafen Niederrhein.
The airport has had several different names in its history as a civilian airport. The operators originally wanted to name it after the city of Düsseldorf, but the significant distance of 83 km (52 mi) to that city, which already had two closer international airports (Düsseldorf Airport as well as Cologne Bonn Airport), resulted in the name being blocked by a court ruling in 2016 that such a description would be likely to mislead passengers. However, Ryanair still refers to it as "Düsseldorf-Weeze". Compared to Düsseldorf, the airport is actually closer to the Dutch cities of Venlo, Nijmegen and Arnhem, the German cities of Duisburg and Essen, and the immediate Weeze area.
“Weeze Airport” enters the record as airport in Germany. Crown Archives preserves that source wording while asking what Weeze, Airport and airport can confirm, complicate or overturn.
Why this record matters
“Weeze Airport” is worth following because a concise public description often conceals a longer documentary argument. Here, Weeze, Airport and airport provides the most credible route into that argument.
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 10, 2026. The linked authority identifier is Q632410. VIAF identifies the subject as 236123184. Authority coordinates are 51.602, 6.142. 2 of 5 selected statements include explicit references; 3 carry qualifiers and 0 use preferred rank. The first chronological checks are 2003 and 2016.
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 “Weeze Airport”, its source revision and the description used here.
- Expand the search: follow Weeze Airport primary sources, Weeze Airport archive and Weeze 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 “Weeze Airport”?
- Which earlier names or jurisdictions may reveal additional records?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “Weeze 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.