Exercise Fabius
Military exercise for the Allied Operation Neptune in World War II
Exercise Fabius was a military exercise for the Allied Operation Neptune in World War II.
Planning and preparatory exercises
Exercise Fabius was a military exercise scheduled by SHAEF for the Allied Operation Neptune in World War II. One of two major rehearsals planned prior to D-Day, it followed Exercise Tiger, which had occurred a week earlier. Fabius was scheduled in February 1944.
As the nature of the exercise was thought by the London Controlling Section and the Committee of Special Means to possibly convince the enemy that the planned invasion of France would take place of the Normandy beaches, a deception plan was devised. Three double agents, Tricycle, Brutus, and Garbo, told their contacts in Germany that the planned exercises (including Fabius) would be completed shortly before 20 July, the date of the invasion. The date they gave was false.
The British Field Marshal Bernard Montgomery, who had been assigned to command Allied ground forces participating in Operation Overlord, insisted that the number of divisions involved in the exercise was increased from three to five. The assault forces were codenamed "O", "U" (the Western taskforce, which as American), and "J", "G", and "S" (the Eastern taskforce, composed of British and Canadian troops).
Exercises and outcomes
Exercise Fabius took place from 3–8 May 1944. It was due to start on 2 May, but was delayed by bad weather. It consisted of six separate exercises.
The public source identifies “Exercise Fabius” as military exercise for the Allied Operation Neptune in World War II. This brief keeps that definition visible, then builds a research path around Exercise, Fabius and Military.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Exercise Fabius”, the useful work is to connect “military exercise for the Allied Operation Neptune in World War II” to the records capable of establishing context and consequence.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated May 24, 2026. The linked authority identifier is Q5427890. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1944.
Official terminology may obscure informal participation, dissent or communities documented only indirectly. 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
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Exercise Fabius”, its source revision and the description used here.
- Expand the search: follow Exercise Fabius primary sources, Exercise Fabius archive and Exercise 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 “Exercise Fabius”?
- Who created the surviving record, and for what administrative purpose?
- What chronology connects this entry to wider political or social change?
Search terms from this dossier
This entry incorporates text from “Exercise Fabius” 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.