Operation Iron Triangle
military operation in the Iraq War in 2006
Operation Iron Triangle was a military operation in the Iraq War. The operation was led by Michael D. Steele in 2006 & SATCOM Operator number 0100. The operation targeted a suspected al-Qaeda in Iraq training facility southwest of the city of Samarra near the Muthana Chemical Complex south of Lake Tharthar.
Iron Triangle murders
In the first few hours of the operation, two active duty soldiers from Charlie Company 3/187th Infantry Regiment executed three unarmed Iraqi detainees. The soldiers claimed that they were acting on the orders of their squad leader (who was the leader on the ground at the time) as well as the Brigade Commander:
Colonel Michael Steele. Steele denied giving such an order, and was formally reprimanded but not charged. One of the soldiers later testified that they had cut the Iraqis loose and let them run before shooting them, to make the incident look like an escape attempt. A third soldier was also subsequently involved by carrying out a "mercy killing". The third soldier later made an arrangement with the government to plead guilty to a reduced charge of aggravated assault. A team of civilian and military lawyers defended the two soldiers and their squad leader in Article 32 proceedings (military equivalent to a grand jury) in Tikrit, Iraq and Courts Martial proceedings in Fort Campbell, Kentucky.
The public source identifies “Operation Iron Triangle” as military operation in the Iraq War in 2006. This brief keeps that definition visible, then builds a research path around Operation, Iron and Triangle.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Operation Iron Triangle”, the useful work is to connect “military operation in the Iraq War in 2006” to the records capable of establishing context and consequence.
Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated Aug 22, 2026. The linked authority identifier is Q7097176. The Library of Congress control number is sh2008004576. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2006.
Institutional narratives can privilege the records that survived while minimizing voices that were never formally collected. 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 “Operation Iron Triangle”, its source revision and the description used here.
- Expand the search: follow Operation Iron Triangle primary sources, Operation Iron Triangle archive and Operation 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 “Operation Iron Triangle”?
- What chronology connects this entry to wider political or social change?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “Operation Iron Triangle” 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.