The Pentagon Filed a Request for British Backup. The SAS Were Already Through the Building.
0 Oh, 230 hours. A target building in the Mosul corridor, Iraq. 16 operators from Task Force Black stacked on two entry points, charges set, ready on the word. The intelligence window opened 40 minutes ago. It was assessed as good for 45 minutes from the moment the signals intercept was confirmed.
Somewhere above this building on the chain of command that stretches from this street through Baghdad to the Pentagon. A formal request for coalition coordination has been filed. It is being routed. It is being reviewed. The watch officer has flagged it for expedited handling. Somewhere in that chain, a desk officer in Washington is seeing the first page of a document that will eventually reach a British liaison officer who will stamp it and send it back.
None of that is done. The window is almost gone. The first man goes through the door before the request clears the desk. The structure of coalition special operations in Iraq in 2004 and 2005 was built on a premise that was sensible in theory and increasingly unworkable in practice. The premise was that any direct action operation conducted by a non US special forces unit inside a US designated area of responsibility required formal intercoalition coordination.
A request submitted, reviewed, approved, and returned before the operation could be launched. The system was not designed to obstruct. It was designed to prevent friendly fire incidents, to ensure that two coalition units did not unknowingly converge on the same building from opposite directions in the same night, and to give the dominant partner in the coalition operational visibility over what was happening inside its area of responsibility.
These were legitimate requirements with legitimate origins. The problem was that the system built to meet them had a processing time calibrated for operations planned over days and weeks, not for operations driven by intelligence that expired in minutes. In Baghdad at the joint special operations task force headquarters that General Stanley Mcristel was actively restructuring throughout 2004 and 2005.
The approval timeline under standard procedure ran between 6 and 18 hours depending on the complexity of the request and the availability of the relevant approving authorities across the chain. for operations involving British units operating as Task Force Black under the 22 SAS designation. The chain required a formal request from the British unit transmitted through its own national chain of command.
Sign off from UK special forces headquarters in theater routing to the JSOC watch officer Pentagon liaison review for any operation inside a US designated area of responsibility and formal approval returned back through the reverse chain to the British unit before it could launch 6 to 18 hours on the standard track.
The expedited track which existed on paper and was occasionally invoked in theory had a minimum documented processing time of 45 minutes on a perfectly clean run. Meaning no desk added review time, no routing system had a queue, no watch officer had a competing priority and no secondary approval was triggered by the nature of the target.
45 minutes was the theoretical floor. In practice, it was nearly always longer because desks had cues and watch officers had competing demands and roing systems were not engineered for the speed that time-sensitive targeting required. The legitimacy of the systems purpose was exactly what made the friction difficult to resolve.
The approval chain existed partly to prevent friendly fire, and friendly fire in a dense urban environment with multiple coalition units operating simultaneously was a genuine risk that nobody dismissed. Brigadier Ed Butler, the UK special forces commander in theater during this period, understood the friction from both sides, the operational pressure that TF Black generated, and the command visibility that the US chain of command needed to maintain over operations in its area, the resolution was never purely procedural. It was always partly
personal, built on relationships between liaison officers who understood each other’s constraints and who found ways to move requests faster than the system was designed to move them. A US liaison officer working the TF black coordination desk at JSOC headquarters reportedly described the deconliction system as designed for operations that last longer than the intelligence.
He was not being critical of the systems designers. He was being accurate about the mismatch between the architecture of the approval process and the tempo of the intelligence environment it was supposed to serve. By 2005, Task Force Black was running direct action operations in Iraq at a pace that had no precedent among coalition SOF units in the theater.
On the highest tempo operational nights, the squadron was clearing multiple buildings in the hours between midnight and first light. The target packages were not sequential. They were parallel. Each driven by its own intelligence thread, each requiring its own request, its own routing, its own position in the approval queue.
The approval system was not built for that throughput. It had been designed on the assumption that operations arrived in manageable sequence, that each request could be processed before the next arrived, and that the intelligence supporting each request would remain valid long enough to survive the processing time.
All three assumptions failed simultaneously against TF Black’s tempo. A USJSOC officer working the British coordination desk kept a separate whiteboard beside his primary workstation to track which TF Black requests were pending, which had been approved, and which had become irrelevant because the intelligence window they were designed to support had closed before the paper were cleared.
He described it in a post-eployment briefing as the saddest whiteboard in Baghdad. Not because the work was unimportant, but because every entry on it represented a decision that had already been made by the time he was processing it. Either TF Black had launched without the approval and the entry was being marked retroactively or the target had moved and the entry was being closed as void.
Over the period from 2005 to 2008, TF Black conducted approximately 250 direct action operations in Iraq based on figures from published accounts by officers present. Mcrist later described TF Black in his memoir as among the most effective direct action units he worked alongside during his time commanding JSOC. That description and the approval systems visible inability to keep pace with TF Black’s tempo were both true at the same time about the same unit and the tension between them was never fully resolved procedurally. It was resolved
operationally by the development of the concurrent notification procedure and by the informal accommodation that senior officers on both sides reached through personal relationships and mutual respect for what TF Black was producing. The intelligence that drove the Mosul operation arrived through the JSOC fusion cell in Baghdad on a night in 2005 when the systems inherent lag was not a background administrative problem but an immediate operational one with a specific clock attached to it.
A signals intercept placed a high-V valueue individual, a name on the JSOC targeting list, a network node the fusion cell had been trying to fix for several months without success, at a specific address in the Mosul corridor. The intercept was assessed as reliable based on source history.
The individual was assessed as present at the address now in the sense that now meant within a narrow window that was already running from the moment the product was processed. The analyst who produced the targeting assessment underlined the word perishable twice in the summary field and added a note window 30 to 45 minutes from product time.
That notation was not bureaucratic caution. It was an accurate description of how long a man who understood his own exposure could reasonably be expected to remain stationary at a known address in a city where British and American special forces had been operating at high tempo for months. The individual on the list was not naive about the intelligence environment he was operating in. He moved.
He did not stay in one place overnight. The window was the interval between when the intercept was collected and when he would have assessed that staying any longer was survivable only by luck. The minimum documented processing time for a formally expedited intercoalition approval was 45 minutes on a clean run. The window was 30 to 45 minutes.
The two numbers occupied the same space on the timeline even under perfect conditions. The request filed the moment the intelligence was received. The watch officer processing it immediately without cue. Every desk in the chain handling it as the first priority. The formal approval would arrive at the exact moment the window was closing.
The target would be gone before the approval reached the British unit to authorize the launch. The system had an expedited track. It existed on paper and was documented in the intercoalition coordination procedures. It had simply never been designed for a situation where the window was no wider than the process’s own minimum throughput time.
The analysts underlined word sat in the summary field of the targeting report and the clock on the wall moved at the same rate it always moved and nobody in the approval chain could do anything about the gap between those two facts. At the task force black forward operating base, the commanding officer looked at the targeting product, looked at the clock on the operations room wall and made a decision that sat within his legal authority under British national command frameworks, but that was going to produce a radio call from a twostar
general inside the hour. The decision was to invoke the concurrent notification procedure and launch without waiting for formal JSOC approval. The concurrent notification procedure was documented in the UK- US special operations memorandum of understanding for Iraq agreed at command level in 2004.
It had been negotiated into theou specifically for situations where perishable intelligence made prior approval impractical in the practical sense rather than the theoretical one. Not situations where prior approval was administratively inconvenient, but situations where the time required to complete the prior approval procedure would consume the intelligence window that the approval was supposed to authorize an operation against.
The concurrent notification was not a request for permission. It was an informing. It transmitted to the JSOC watch officer the target coordinates, the route, the team composition, the estimated duration, and the expected timeline so that deconliction could occur in real time. Other coalition units could be checked against the target area.
The overhead surveillance picture could be adjusted and the operational picture at JSOC could reflect what British forces were doing. The deconliction purpose of the approval process was served by the concurrent notification. The prior authorization purpose was not. Theou was clear that the notification had to be filed before or simultaneously with the launch.
The OC had the notification prepared and told his sergeant major to transmit it while the team was mounting up. By the time the transmission was complete and the signal reached the JSOC watch officer’s terminal, the assault vehicles had been moving for approximately 2 minutes, technically late under theou language as written in 2004 by 90 seconds, perhaps 2 minutes.
The OC’s instruction, as captured in the post-operation debrief, was simple. Send the notification and we will debrief whatever needs debriefing when we get back. The notification went, the team went. At JSOC, the watch officer read the notification, understood what it meant in terms of theou’s simultaneous filing requirement and escalated to his twostar supervisor.
The twostar was going to call TF Black OC. That call was going to happen in roughly 40 minutes. The building would be cleared by then. Before we dive in, drop a comment and let us know where you are watching from. If you haven’t already, make sure you hit the subscribe button to not miss any story.
and check out our Patreon in the description. We post full uncensored stories there. Every graphic detail, every brutal moment, nothing redacted. Stories YouTube won’t allow. Now, let’s get into it. Chapter 2. The four vehicle package moved out of the FOB and covered the 6 km to the target address in under 12 minutes.
16 operators, a JTAC in the lead vehicle route pre-planned from the intelligence picture and rechecked against the current pattern of life data from the fusion cell local human intelligence source confirmation that the target was still inside the building as of 30 minutes prior to the launch order. The JTAC in the lead vehicle had the JSOC radio net running as a secondary feed alongside his primary communications and he was hearing the JSOC watch officer’s escalation traffic beginning to build.
The two stars duty officer making preliminary calls, the watch officer providing the concurrent notification details. The chain assembling itself. The call was routed to the FOB operations room where the OC was monitoring. It was not routed to the vehicles in movement. The OC in the operations room received the preliminary calls and acknowledged them without recalling the package.
The JTAC in the lead vehicle, listening to the traffic, turned the gain on his secondary net down enough to continue monitoring without the conversation occupying his primary attention. It emerged in the debrief that the JSOC senior duty officer generating the call traffic was not attempting to stop the operation. He was trying to add a surveillance drone to the package for overhead coverage and post exploitation support.
The complication was not opposition. It was addition and the addition arrived too late in the timeline to be integrated without stopping the vehicles to replan. The drone was not launched in time to matter. The target building was a two-floor structure set back from the road in a residential block indistinguishable from its neighbors in the darkness of the Mosul night.
Multi-room construction on both floors, a single internal staircase connecting them. The number of occupants beyond the primary target, unknown at the time of the approach. The assault team split on the final approach. Two breach pairs to the main entrance at the front of the building. Two to the rear door.
All four pairs moving simultaneously on the signal. Charges on both entry points. The detonation was simultaneous. Both access points open in the same fraction of a second. The clearance ran in the standard compound pattern. Ground floor first, then the staircase, then the upper floor. Rooms checked in sequence. The pairs moving fast and controlled through the building without hesitation or cross talk beyond what the task required.
Time from the first simultaneous detonation to the building clear call 3 [music] minutes and 50 seconds. The primary target was on the upper floor in the room that the intelligence assessment had indicated as his likely location exactly where the intercept had placed him. He was present. He had not moved in the 45 minutes since the window opened.
Three additional military age males were detained in two other rooms on the upper floor. Their relationship to the primary target not immediately clear, but assessed as network associated given the building’s contents. One weapon cache was found in a room off the lower landing. Three Kalashnikov rifles, one PKM generalpurpose machine gun, one chest rig with loaded magazines, and a quantity of loose documents mixed in with personal effects.
No shots were fired during the clearance. The intelligence operator attached to the assault package, a female member of the JSOC exploitation cell embedded with TF Black for the [music] operation, had entered behind the first breach pair and was working the upper floor before the formal building clear call was made. She found a hand-drawn document on the wall of the primary targets room.
Names connected by lines with dates, frequencies, and marginal annotations in a format that suggested a working network reference document rather than anything prepared for concealment. It was not in a drawer. It was not folded and hidden. It was pinned to the wall with a single push pin at eye level as if it had been consulted that morning and left where it was because whoever had used it expected to be using it again.
She described it in the post operation debrief as the cleanest piece of network mapping she had seen in the theater during that deployment. The site exploitation ran for 9 minutes. The intelligence operator and two assaulters worked the upper floor methodically and without wasted motion. The network schematic came off the wall and was sealed in a numbered evidence bag.
The documents from the table and the drawers were collected and packaged in the sequence they were found, preserving the spatial relationship between materials that might matter to the analysts who would process them. A laptop sitting on a low table in the far corner of the room was logged, tagged, and placed in a padded sleeve.
An encrypted communications device found in a drawer beside the low table was collected separately, packaged, and logged as a priority item. Encrypted devices on a targeting list required their own handling chain 9 minutes from the breach to the extraction call. The primary target and the three additional detainees were flexcuffed, identified against the targeting materials the operator carried, and moved downstairs.
The intelligence operator carried the laptop under her arm and the evidence bags and the encrypted device over her shoulder. She was down the stairs and at the rear vehicle before the last breach pair had made the corner. Loading time from the moment the first man reached the vehicles to the moment the last vehicle moved was under two minutes.
The package moved on the extraction route. The JTAC had the overhead picture and called the route clear. No contact on the return to the FOB. The building was empty of British personnel before the 45minute window from the original intelligence product had technically expired. The target was in flex cuffs in the second vehicle.
The encrypted device was in the exploitation bag in the third vehicle. The network schematic was in the evidence bag beside the operator in the third vehicle. The vehicles were back at the FOB gate and clearing the perimeter within 15 minutes of leaving the target address. Total time from launch to return, 40 minutes.
At [music] the TF Black Forward operating base operations room at approximately 0240 hours, the commanding officer received the call from the JSOC twostar general that had been building in the radio traffic since the concurrent notification was filed. The general told the OC that the operation in the Mosul corridor had not been formally approved under the intercoalition coordination procedures applicable to operations in that area of responsibility and requested [music] an immediate explanation.
The OC cited the concurrent notification procedure as documented in the 2004 UK- USS memorandum of understanding for Iraq operations. The general acknowledged the procedures existence in the MOU. He then noted that the concurrent notification had been filed approximately 2 minutes after the TF black assault vehicles had departed the FOB rather than before or simultaneously with that departure.
Technically late under theou’s language as it stood in 2004. The distinction mattered procedurally, even if it mattered less operationally. The OC’s response, as characterized in the post-operation debrief and referenced in the post campaign review produced in 2009, was three sentences in sequence. The notification was filed, the window was perishable, and the target was in custody.
All three were accurate statements of fact. The general did not file a formal complaint. He characterized the exchange as a process discussion for the record and did not escalate it beyond the operational level. The reasons for not escalating were not difficult to identify when the encrypted communications device recovered from the target building was processed by the JSOC intelligence fusion cell over the following 72 hours.
It yielded contact information, network timing data, partial organizational mapping, and communication protocols that drove three separate follow-on operations against related targets on the JSOC list. Two of those follow-on operations resulted in the capture of additional high-value individuals. One identified a network node, a logistics facilitator with connections to both a bomb-making cell and a financing network that had been entirely absent from the JSOC intelligence picture for approximately 6 months. None of those
outcomes would have existed without the operation. The general had called it a process discussion. The process discussion had produced a six-month intelligence gap closed and three follow-on capture operations. The joint afteraction review convened at 0800 hours the following morning at the JSOC headquarters in Baghdad with US and British officers present and the JSOC intelligence fusion cell chief providing the exploitation yield briefing.
The review had been called partly as a process discussion and arrived at its conclusion as a capability assessment. The process violation, the two-minute gap between vehicle departure and the filing of the concurrent notification was entered in the official minutes of the review as noted for future compliance and was not pursued further in the formal record.
The operational result was briefed in full to those present and transmitted up the US chain of command as a significant intelligence success with actionable follow-on implications. The JSOC intelligence fusion cell chief briefed the encrypted device product and the network schematic in [music] detail. Three follow-on operations, two additional HVI captures, one previously unknown network node identified and added to the targeting picture.
The room was quiet during the exploitation brief in the way that rooms are quiet when the numbers are good. At the conclusion of the review, the JSOC operations officer closed his notebook, looked across the table at the TF black liaison officer and said, “Next time, file the notification before you leave the FOB.
” He paused, “Even if it is by 30 seconds, the liaison officer noted it.” The concurrent notification protocol was subsequently revised with the language around simultaneously adjusted to accommodate notifications filed while vehicles were in motion provided the intent to launch and the target coordinates had been formally established and logged before departure from the FOB.
The revision was not a loosening of the standard. It was a recognition that the practical purpose of the notification, real time deconliction, was served by a concurrent filing that reflected genuine advanced preparation regardless of whether the signal had left the transmitter before or after the vehicles crossed the FOB gate.
The practical effect of the revision was to formalize what TF Black had already been doing. The tempo did not change. The formal request for support document that had been generated in parallel with the actual operation routed through standard intercoalition channels from JSOC headquarters toward Pentagon J3 toward British defense staff Washington toward MOD London and eventually back toward British Special Forces headquarters in theater arrived at the British liaison desk in the Pentagon approximately 90 minutes after the TF black assault package had
returned to the FOB. completed the debrief and transferred the target and detainees to the detention processing system. The document was correctly dated. It was correctly formatted. It bore the right classification markings and the right routing annotations and the right subject header for an intercoalition SOF support request.
It requested coordination and support for a direct action operation against a time-sensitive high-value target at a specific address in the Mosul corridor. The requesting unit was listed as a coalition special operations element. The anticipated start time for the operation was listed as 0230 hours, the time at which the assault had actually begun.
The document was a complete and properly prepared formal request for something that had already happened 90 minutes before the document arrived at the desk it was addressed to. It could not be approved retrospectively in any meaningful sense because the operation it was requesting approval for was over. The target was in the detention system.
The exploitation materials were in the intelligence pipeline. Three follow-on operations were already being planned against [music] the network nodes. the exploitation had identified. The British liaison officer at the Pentagon, a colonel whose name does not appear in any public account of the Iraq campaign, reviewed the routing slip, cross-referenced the concurrent notification already in the system, and wrote four words in the margin of the routing slip in his own handwriting, operation complete, NFA, no further
action. The document was administratively closed as superseded by the concurrent notification on file. It went into a folder. The folder went into a file. The file went into a cabinet. The cabinet is in a building that does not appear on any public map. The routing slip note, four words, a colonel’s handwriting, 90 minutes late is what the title literally means.
The Pentagon filed a request. The SAS were already through the building. The Mosul episode was not unique. Over the three years that Task Force Black operated in Iraq at sustained high tempo, variations of the same collision, perishable intelligence pressing against a coordination system calibrated for slower timelines, produced similar friction repeatedly and in various forms.
Mcristl had been watching TF Black’s operational tempo and its relationship to the approval system from the beginning of his command of JSOC. And his conclusion was not that TF Black needed to slow down or that the approval system needed to assert itself more firmly. His conclusion was that the institution needed to be rebuilt around the speed the intelligence environment demanded.
The fine fix finish exploit analyze cycle F3EA was Mcrist’s formalization of a process that high functioning special operations units TF Black prominently among them had been running informally since before the concept had a name or a doctrine document. The cycle was designed to operate at the speed of intelligence decay.
Instead of treating each phase as a sequential step completed before the next began, F3EA ran exploitation and analysis [music] as a continuous feedback into targeting while the current operation was still in execution. An operation was not finished when the team came home. It was finished when the intelligence from the exploitation had been processed and issued as the next targeting package, which might happen before the team that produced it had finished writing their post-operation notes.
After F3A was formally implemented at JSOC and the intelligence and operations pipelines were genuinely integrated at the organizational level, meaning the analysts were coll-located with the planners. The exploitation cell was feeding products directly into the next targeting cycle in real time rather than processing them on a separate schedule.
And the approval chain for time-sensitive targets had been shortened by direct command authority rather than by procedural workarounds. Approval times for perishable intelligence direct action operations dropped from hours to minutes in most cases. Mcristel documented the model and the transformation it represented in his memoir, Team of Teams, and cited it in addresses to US special operations communities as the organizational architecture that the Iraq campaign had compelled his command to build.
The construction was not purely his own design. It was partly built by watching what TF Black was already doing and understanding why it was working. Task Force Black had been running at something functionally close to F3A speed before the model existed as a named concept or a formalized doctrine. The SAS approach to direct action.
Decentralized decision authority. Commander’s intent issued as guidance rather than as prescriptive orders. Subordinate commanders authorized and expected to act within defined parameters without seeking approval for each individual tactical choice. was not an innovation that TF Black developed in the Mosul corridor in 2005.
It was the operating model of the regiment since its reformulation after the Malaya emergency. Refined through the Borneo confrontation, the Dofar campaign in Oman, the Faulland’s war, the Gulf War, and the Balkans operations of the 1990s. It had accumulated across decades of operating in small teams without immediate support against targets and in environments that did not pause for institutional processes to complete their cycles.
Mission command was the formal British military doctrine label for the underlying philosophy codified in doctrine documents since the 1980s defense reforms. Though the practice was decades older than any doctrine document that described it. The core assumption was direct. The commander on the ground present in the situation and in possession of current information makes better tactical decisions than the commander at a higher echelon who is receiving the same information secondhand on a time delay and reacting to a situation that is already moved
forward from the version he is seeing. For the SAS, this was not a philosophical position or a theoretical preference to be debated in doctrine seminars. It was the practical answer to the physical problem of operating in four-man patrols and 16-man assault teams in environments where conditions changed faster than orders could follow and where the gap between the decision and the execution had to be as close to zero as training could achieve.
The contrast with the US approval model was not a contrast between a right approach and a wrong one. Both models had legitimate foundations. The US hierarchical approval chain existed partly to prevent blueonblue incidents in [music] a dense multi-unit operating environment and partly to maintain command visibility over operations with political and diplomatic dimensions.
These were real requirements. The SAS mission command model existed because the regiment’s entire operational history was built around small teams making consequential decisions without the ability to seek higher authority in time. Neither model was wrong. They were built on different assumptions for different contexts and they collided in Iraq because the operating environment required both things simultaneously.
the visibility and deconliction that the US chain provided and the speed that the intelligence environment demanded. One SAS sergeant asked during a post-eployment briefing what he made of the JSOC approval chain said, “We are not disrespecting their system. We just built ours to be faster.” Mcristel at a JSOC planning conference during the middle period of the campaign reportedly said, “The British showed us what our own doctrine should look like.
” In 2009, a classified joint UK-US post campaign assessment reviewed the TF Black and JSOC coordination model across the full Iraq period. The review was produced by officers who had not been present for the specific operations they were assessing. Every factual detail in it came from debrief transcripts, liaison reports, concurrent notification records, afteraction review minutes, and the administrative trail that four years of sustained operations had accumulated.
The review examined 12 specific episodes in which task force black had launched on concurrent notification rather than formal prior approval. In all 12 cases, the operational result was assessed as sound. In eight of the 12, the intelligence window would have closed before formal prior approval could have been completed under the expedited procedure on a clean run.
In four cases, the formal approval had actually arrived while the team was still on the target, received after launch, but before extraction, delivered to a process that was already resolved by the time the paperwork cleared. The review’s recommendation was to adopt concurrent notification as the standard default mechanism for time-sensitive intercoalition direct action with a filing window defined as prior to movement.
This was the precise thing that TF Black had not achieved in the Mosul operation. The notification had been filed 2 minutes after the vehicles moved rather than before them. The gap between the recommended doctrine and what had actually worked in practice was narrowed in the revision of the concurrent notification language to the point of practical irrelevance.
The 2011 UK-SS cooperation framework incorporated the recommendation. The concurrent notification window in the new framework allowed for filing while vehicles were in motion, provided the intent to launch, and the target coordinates had been formally established and logged before departure.
The OC’s instruction, send the notification, we will debrief whatever needs debriefing when we get back, was retrospectively within the new definition, if not the 2004 one. The review’s concluding line on the TF Black coordination episodes read, “In all cases, the operational result was sound. The process can be improved.
The process was improved. The target was already in detention by the time the first draft of the improvement was written. The routing slip in the Pentagon file, four words in a colonel’s handwriting in the margin, sits in a cabinet in a building that does not appear on any public map. The network schematic that came off the wall in Mosul drove three operations and closed a six-month gap in the JSOC intelligence picture.
The encrypted device yielded the contact data that made two of those follow-on operations possible without needing a fresh intercept. The concurrent notification was filed 2 minutes after movement by a commanding officer who knew it was 2 minutes after movement and sent the team through the door anyway because the window was 45 minutes and the floor was 45 minutes and neither number was going to change by waiting.
The twoar called it a process discussion. The operations officer said 30 seconds would do. The doctrine was revised to accommodate the reality. The target was in custody before the request was stamped. Operation complete.
