Battle of Kirkuk (2016)
2016 battle between Iraqi Kurdish forces and ISIL in Iraq

The Battle of Kirkuk took place in the city of Kirkuk in northern Iraq between Kurdistan and allies and the Islamic State of Iraq and the Levant. The battle occurred less than a week after the beginning of the Battle of Mosul launched by Iraqi security forces and allies.
The battle
On 21 October 2016, dozens of ISIL militants and suicide bombers, supported by local sleeper cells, entered Kirkuk and stormed a power station and police stations in the city, killing 18 members of security forces and power station workers, including 2–5 Iranian workers. The ISIL militants captured a mosque and an abandoned hotel and barricaded themselves inside. Hours later, ISIL captured 2 more hotels and holed themselves in. Over 20 ISIL militants were killed, as security forces recaptured most of the buildings.
By the next day, ISIL forces still held parts of the Aruba District and a hotel, though these were retaken later on. Government forces then began a mop-up operation to clear the city of remaining militants, with some of the latter blowing themselves as they were cornered. Many local civilians had also taken up arms, hunting, capturing and killing ISIL fighters.
On the third day of the battle, several remaining ISIL militants attempted to flee the city, with five being killed and the ISIL operations leader captured by security forces.
The public source identifies “Battle of Kirkuk (2016)” as 2016 battle between Iraqi Kurdish forces and ISIL in Iraq. This brief keeps that definition visible, then builds a research path around Battle, Kirkuk and battle.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Battle of Kirkuk (2016)”, the useful work is to connect “2016 battle between Iraqi Kurdish forces and ISIL in Iraq” 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 Aug 21, 2026. The linked authority identifier is Q27502384. Authority coordinates are 35.470, 44.396. None of the 1 selected statements returned an explicit reference. The first chronological checks are 2016.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. 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
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 “Battle of Kirkuk (2016)”, its source revision and the description used here.
- Expand the search: follow Battle of Kirkuk (2016) primary sources, Battle of Kirkuk (2016) archive and Battle 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 “Battle of Kirkuk (2016)”?
- Which voices are present, absent or mediated by the institution?
- What chronology connects this entry to wider political or social change?
Search terms from this dossier
This entry incorporates text from “Battle of Kirkuk (2016)” 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.