Operational Requirement
Open-knowledge reference entry
An Operational Requirement, commonly abbreviated OR, was a United Kingdom (UK) Air Ministry document setting out the required characteristics for a future (i.e., as-yet unbuilt) military aircraft or weapon system.
The numbered OR would describe what intended role the aircraft would be used for, e.g., bomber, fighter, etc., or what type of weapon was required, e.g., gun, armament, bomb type, etc.
In conjunction with any official specification, prospective manufacturers would then choose whether to design an aircraft or weapon for this particular requirement.
Operational Requirements were carried over with the dissolution of the Air Ministry and the creation of the Ministry of Defence (MoD).
Other requirements
An Experimental Requirement (ER) was for an aircraft for research purposes; e.g., ER.100 in support of development of the English Electric Lightning.
See also
List of Operational Requirements for nuclear weapons
List of Air Ministry specifications
Notes
Further reading
Moore, Richard (2010). Nuclear Illusion, Nuclear Reality: Britain, the United States, and Nuclear Weapons, 1958-64. Nuclear Weapons and International Security since 1945. Basingstoke, Hampshire: Palgrave Macmillan. pp.
This brief starts where responsible research should: with the source description of “Operational Requirement” as open-knowledge reference entry. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as open-knowledge reference entry. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Feb 16, 2025. The linked authority identifier is Q7097749. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2010, 1958 and 1945.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Operational Requirement”, its source revision and the description used here.
- Expand the search: follow Operational Requirement primary sources, Operational Requirement archive and Operational 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 “Operational Requirement”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Operational Requirement” 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.