22nd Attack Squadron
military unit
See 46th Bomb Squadron for the Strategic Air Command squadron
The 22nd Attack Squadron is a United States Air Force unit assigned to the 432d Wing Air Combat Command at Creech Air Force Base near Indian Springs, Nevada. It operates Unmanned aerial vehicles, including the General Atomics MQ-9 Reaper, and provides combat support, surveillance, and reconnaissance. The squadron has been activated on five occasions since its formation in World War II, and has seen combat service in both the early years of the war and during the Vietnam War. The unit has also undergone multiple reactivations and redesignations throughout its history.
History
World War II
The squadron was first activated at March Field, California in January 1941 as the 46th Bombardment Squadron, one of the three original squadrons of the 41st Bombardment Group. The squadron moved to Davis-Monthan Field, Arizona and trained there with Douglas B-18 Bolos. Following the attack on Pearl Harbor, the squadron moved to Muroc Bombing Range and conducted antisubmarine patrols off the Pacific Coast from bases in California until the summer of 1942.
The squadron moved to the Atlantic Coast in July 1942 and its air echelon was attached to Army Air Forces Antisubmarine Command in October and continued its patrols in this area. The squadron formally joined Antisubmarine Command in March 1943, when it became the 22d Antisubmarine Squadron (Heavy) equipped with B-24. In June, 1943 the air echelon moved to England, conducting operations over the Bay of Biscay.
The public source identifies “22nd Attack Squadron” as military unit. This brief keeps that definition visible, then builds a research path around 22nd, Attack and Squadron.
Why this record matters
A short description can identify a subject without explaining its stakes. For “22nd Attack Squadron”, the useful work is to connect “military unit” to the records capable of establishing context and consequence.
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 Aug 31, 2026. The linked authority identifier is Q4631342. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1941, 1942 and 1943.
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 “22nd Attack Squadron”, its source revision and the description used here.
- Expand the search: follow 22nd Attack Squadron primary sources, 22nd Attack Squadron archive and 22nd 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 “22nd Attack Squadron”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “22nd Attack Squadron” 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.