The Pentagon Filed a Request for British Support. The SAS Were Already Through the Target Building
The request was prepared in the correct format. An officer on the joint staff assembled the supporting intelligence, drafted the justification, attached the targeting package, and routed it through the three approval levels that a formal request for British military support required before it could be transmitted to the liaison desk.
The process was not cumbersome by the standards of the institution that designed it. It was designed to be efficient, and by those standards it was. The first signature took 11 minutes. The second took 26 minutes because the approving officer was in a meeting. The third took 4 minutes. The transmittal to the British liaison desk took another 8 minutes.
From the moment the request was initiated to the moment it reached the desk where it needed to land, 49 minutes. The operation it was requesting support for was, by the time the request arrived, already over. 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. The target was a senior facilitator in the AQI network operating in the Mosul area in 2005. A man whose role in the network was logistical, and whose compound, a structure in a mixed residential area on the city’s eastern side, had been under surveillance for 11 days.
The intelligence picture on the target was assessed as high confidence by the task force’s intelligence officer, meaning that the source reporting was corroborated, the imagery analysis was consistent across multiple collection passes, and the pattern of life assessment placed the target at the compound with high reliability during the hours relevant to the proposed operation.
The intelligence window was assessed at 48 to 72 hours before the target was likely to move based on what the source reporting suggested about his travel patterns. The operation needed to happen within that window or not at all. The compound fell within the British area of operational responsibility in the Mosul sector, which meant that under the coalition’s joint operating procedures, any direct action operation at the target location required either British execution or a formal American request for British support.
The American planning staff chose the formal request route because the target’s operational significance sat above the threshold that required higher level approval within the American chain, and the documentation that a formal request generated was necessary for that approval process. The intelligence officer who initiated the request did so with the understanding that the British would receive it, task it to the appropriate element, and begin planning within a timeline that would allow execution within the intelligence
window. This was a reasonable assumption based on the standard coordination processes the joint task force had established. The SAS had been looking at the same target for a different reason and through a different channel. Their human source network in the Mosul sector had been developing a reporting threat on the same AQI logistics operation for 3 months, and the reporting had identified the target’s compound as the primary node in the section of the network covering Eastern Mosul and the supply routes leading to the Syrian border. The SAS
intelligence picture was not identical to the American one. It had different source types, different observation periods, different analytical emphases, but it pointed at the same person, at the same location, for the same broad reasons. More importantly, it included a piece of source reporting that the American collection package did not have.
A human source report placing the target at his compound on a specific night with a specific purpose, a meeting with a logistics subordinate that would last long enough to constitute a reliable attendance window. The window was tonight. The SAS patrol commander reviewed the source report, assessed the intelligence, and made the decision to act within the window.
The formal American request for British support was in the routing process. It had not been received by the British liaison desk. The SAS were not aware that the formal request was being prepared because formal requests in routing are not visible to the operational elements. They will eventually task they are visible to the liaison and planning staff, not to the troop commander deciding whether to move.
The SAS decision to act on their own intelligence was made in isolation from the American process, not in knowledge of it. The two processes were running in parallel, in the same institutional space, in the same city, without either being aware of the others current status. The SAS moved at a time selected on the basis of the source report’s attendance window and the patrol commander’s assessment of the optimal approach conditions.
They moved with the minimal footprint that a small team direct action operation in a populated urban area required. Four operators, one support element, no heavy weapon systems, no close air support on station. The movement to the target took 16 minutes. The approach to the compound took another eight. The entry was through the ground floor at the rear of the structure using an access point that the source reporting had identified as being used by the compound’s legitimate occupants for informal entry and exit.
The entry took 40 seconds. The compound was cleared in the 4 minutes that followed. The target was in the compound’s main interior room with one other person. Both were detained. The one other person was, as the source report had suggested, a logistics subordinate whose identity the SAS operators did not fully know at the time, but who turned out, in the intelligence processing that followed, to be a more significant figure in the network than the source reporting had established.

The SAS had gone to the compound expecting to capture one valuable target. They captured two. The compound material devices, documents, ledger records was collected and removed. The team was exfiltrating when the British liaison desk received the formal American request for support. The AQI logistics network operating in Mosul in 2005 had been built by people who understood how institutional processes work and had organized their activities around the gaps those processes create.
The network’s primary vulnerability was the same as its primary strength. Its nodes were connected, which meant disrupting one node was less effective than disrupting multiple nodes simultaneously. But finding multiple nodes required the kind of intelligence, patience, and granularity that technical collection alone couldn’t always provide.
The facilitator, whose compound the American request was targeting, had managed his exposure well. He operated through intermediaries, used physical couriers for sensitive communications, and rotated his attendance at any given location to avoid the predictable patterns that technical collection could identify.
The human source network the SAS had been developing in the sector for 3 months, had gotten closer to his actual pattern than the technical collection had because human sources are not constrained by the physics of altitude and have access to the kind of specific, timely reporting that a determined target’s operational security is not designed to prevent entirely.
The SAS intelligence picture on the target was built around a specific source whose reliability had been established over multiple reporting cycles, each of which had been tested against other available information and found accurate. The source understood the target’s movements well enough to provide reporting that was specific rather than general, not where the target sometimes went, but where he was going to be tonight and why.
This kind of source reporting is the most valuable and the most perishable form of intelligence. It has a short validity window. It cannot be acted on cautiously because caution extends the response time past the window, and it requires the unit receiving it to be able to make a decision and move without the full coordination cycle that formal processes require.
The SAS patrol commander understood all of this without needing it explained. The source report said tonight, the window was tonight, and the patrol commander was already thinking about the entry when he finished reading it. The formal American request, processed correctly through its three approval levels, represented the standard method for managing operations in a complex, multinational coalition where conflicting timelines and overlapping areas of responsibility created regular coordination challenges. The method
worked well for operations where the intelligence window allowed the coordination process to complete before the window closed. It worked less well for operations where the window was measured in hours rather than days because the coordination process, however efficient, occupied a minimum time that was longer than the window.
This was not a flaw in the process. It was a structural characteristic of any formal coordination mechanism, and it was a characteristic that the SAS patrol commander had understood from the moment he received the source report. He was not circumventing the American process. He was simply operating in a different tempo, and the different tempo was what the intelligence window required.
The compound’s interior was configured in a way that the American targeting package had partially, but not fully captured. The imagery had established the building’s external dimensions and the general arrangement of windows and access points. What it hadn’t established was the interior room configuration, specifically whether the main meeting room used for the target’s network meetings was on the ground floor or the first floor, and whether the access point the SASR plan to use actually connected to that room’s level without passing through the
full building interior. The source reporting answered this question. The meeting room was on the ground floor, and the rear access point connected directly to a service corridor off which the ground floor rooms opened. The SAS entry plan was built around this specific piece of information, which meant the four operators entering the compound didn’t have to move through the full building to reach the room where the target would be.
They moved straight to it. The institutional asymmetry between the two processes was not a problem that could be fully resolved because the two processes served different purposes and operated within different command philosophies. The American formal request process served the purpose of ensuring that operations in a complex coalition environment were coordinated, documented, and conducted within a framework of mutual visibility and accountability.
These were legitimate purposes. The SAS operational tempo served the purpose of ensuring that time-sensitive intelligence windows were acted upon before they closed because intelligence about where a target will be tonight has no value after tonight has passed. These were also legitimate purposes. The two purposes were in structural tension, and the tension was not the fault of either institution.
It was the inherent friction of two systems designed to operate at different speeds trying to work together on problems that existed at the faster system’s tempo. The morning after the operation, the British liaison officer submitted his report to both the British and American chains. The report was factual and complete. It described the source reporting, the SAS patrol commander’s decision to act within the intelligence window, the operation’s conduct, and the result.
It noted the parallel American request process and the timeline relationship between the two. It did not editorialize. The liaison officer had been doing this work long enough to understand that the people who would read the report were professionals who could draw their own conclusions, and that the report’s job was to give them the accurate information from which to draw those conclusions rather than to guide them toward any particular finding.

He submitted it and moved on to the morning’s other business. The joint task force review, which would occupy several hours of several senior officers’ attention over the following 2 days, was the consequence. The operation itself was simply done. The bureaucratic process by which the Pentagon formally requested British special operations support had its own timeline, and that timeline was entirely disconnected from the operational timeline by which the SAS had been developing and preparing for the mission. The formal request moved
through the standard channels from the American operational commander to the relevant joint headquarters, from the joint headquarters through the liaison structure to the British military command, from the British command to the SAS’s theater headquarters, from the theater headquarters to the deployed element.
Each step in that chain involved a review, a concurrence, and a handover to the next link. The chain was efficient by the standards of interagency and international coordination, and inefficient by the standards of the operational window it was attempting to address. The SAS had been monitoring the intelligence on the target building since before the Pentagon’s request was initiated, and the assessment of the target that the SAS had developed through its own collection resources was substantially more current and more operationally
specific than the assessment that accompanied the formal request. The request was processed and transmitted while the SAS team that would respond to it was already working through the final phase of its mission preparation. The intelligence picture on the target building had developed through a collection process that reflected the SAS’s institutional understanding of how buildings are most usefully characterized for assault purposes.
The physical dimensions of the building, the floor plan, the room layout, the entry and exit points were the foundation of the picture, and they had been established early in the collection process with sufficient accuracy to allow detailed planning against them. The more analytically demanding elements of the picture were the elements that changed.
The locations of the building’s occupants at different times of day, the patterns of movement between floors and rooms, the positions of defensive personnel, and the timing cycles of their patrol routes. These elements required ongoing collection over a period of time sufficient to establish patterns, and the collection had been running long enough to produce pattern assessments with a confidence level that the planning cell considered adequate for the decision to proceed.
The confidence level was not certainty. Intelligence collection produces probability assessments, not certainties, and the planning cell’s decision to proceed was a decision that the probability assessment was reliable enough to justify accepting the residual uncertainty. The entry technique selected for the target building was a compromise between two approaches that the team had considered and both rejected in their pure forms.
The first approach, a hard, fast entry through the primary access point, minimized the time the team spent in the exposed approach phase, but maximized the noise signature at entry and sacrificed whatever element of surprise a quieter entry could preserve. The second approach, a covert approach and silent entry through a secondary access point, preserved more surprise, but required a longer approach phase through a more dangerous avenue.
The selected approach used a secondary entry point, but sacrificed some of the covert approach time in exchange for a faster breach on the assessment that the primary value of a secondary entry point was not the covert approach it enabled, but the defensive orientation it exploited.
The defenders would have their primary on the primary access points. A fast entry through a secondary point combined the partial surprise of an unexpected entry vector with the speed advantage of a forceful breach rather than a covert one. The weapons and equipment carried by each team member had been individually configured based on each member’s role in the clearance sequence.
The first through the breach operators carried configurations optimized for speed and close-range engagement, accepting limitations in terms of sustained firepower in exchange for the agility that fast room clearance requires. The operators who followed in the first wave carried complementary configurations that provided the sustained engagement capability the front operators lacked.
The communications operator carried primary and backup communications in a configuration that allowed them to maintain the link to the operation center while moving with the assault element through the building. The medical operator carried a kit configured for the most likely casualty types based on the expected contact, predominantly high-velocity projectile wounds at close range rather than a general-purpose trauma kit.
The individual configurations were the product of team discussions in which each member had contributed their assessment of the role requirements, and the discussions had produced configurations that reflected the team’s collective understanding of what the mission required. The decision sequence that led to the team entering the building while the Pentagon’s support request was still in transit through the liaison chain was not a decision by the SAS to act outside the alliance framework.
It was a decision by the SAS’s operational command that the intelligence window was closing, that the team was ready, and that waiting for the formal request to complete its bureaucratic journey would cost the operation the intelligence advantage that the collection effort had spent weeks developing. The SAS operational command had the authority to act on that assessment.
The formal request was a notification mechanism, not an authorization mechanism, and the distinction was understood by both the British and American elements who were involved in its processing. The Americans who were moving the request through their system understood that it was a formality acknowledging an operational reality rather than an approval initiating an operation.
The operation would happen when the SAS was ready. The paperwork would catch up. Chapter two. The British liaison officer was a major with two previous Iraq deployments and a working familiarity with the pace and complexity of joint task force operations. He received the formal American request at 0130, read it, noted the target reference number, and checked the SAS operational log that sat on his desk as part of the routine coordination documentation he maintained.
The log showed an active SAS operation that had been transmitted to his duty log at 2212. The target reference number in the American request and the target reference number in the SAS operation log were different. The American process and the SAS process had each assigned their own internal identifiers to what was, as became clear in the next 15 minutes, the same compound.
He picked up the secure phone and called the SAS duty officer. He was told the team was exfilling. He put the request on his desk and began writing. The timeline, when it was reconstructed for the joint task force review the following morning, was precise and specific. The American targeting process had identified the compound and begun the formal request at 2141.
The request had cleared all three approval levels and been transmitted to the British liaison desk at 2230. The SAS had made entry at 2212 and had transmitted secure at 2234. The formal request had arrived at the liaison desk 18 minutes after the SAS entered the compound and had been formally received 4 minutes after the team transmitted secure.
In a narrow technical sense, the request was still within the processing window the American planning staff had assumed the British had not yet been formally tasked and an operation had not yet been formally committed on the basis of the request. The operation had simply already happened. The joint task force review was chaired by the American deputy commander and attended by the senior liaison officers from both national contingents and the task force intelligence officer.
The review’s purpose was not disciplinary. Both the American request process and the SAS operation were procedurally appropriate within their respective chains. The review’s purpose was to understand how the two processes had run in parallel without either being aware of the other and whether the coordination mechanisms in place were sufficient to prevent this kind of parallel action from producing a conflict rather than a coincidence.
The SAS operation had succeeded without incident. The parallel American process had produced no operational conflict. The question was what would have happened if the timing had been different. The SAS liaison officer at the review provided the SAS account. Their intelligence source had provided a time-sensitive window.
The patrol commander had assessed the window as actionable and the operation had been conducted within the SAS chain’s tasking authority for the sector. There had been no awareness that an American request was in routing because in routing requests are not visible to operational elements in the field. The American liaison officer provided the American account.
The formal request had been processed within the standard timeline for a request of its type. The target had been identified as British AOR, and the formal process had been followed correctly. Both accounts were accurate. Neither was a criticism of the other. The conflict, if there was one, was structural. The two systems for generating operations had no shared visibility until a request was formally received, and the period before formal receipt was a blind spot.
The practical intelligence yield from the operation exceeded what the American planning process had been targeting. The second detainee, the logistics subordinate, who turned out to be a figure of greater significance than the source reporting had established, provided information in subsequent interrogations that drove six additional operations over the following 3 months.
The material from the compound, processed by the task force’s exploitation cell, identified a supply route that had not previously been mapped, and three safe houses that were subsequently targeted. The British liaison officer’s summary note on the operation, filed with the joint review, estimated that the intelligence yield from the SAS operation was substantially greater than the yield that the American-led operation described in the formal request would have produced because the SAS had timed their entry around a source-reported attendance
window that the American targeting package had not had access to, and this timing had produced the capture of the second detainee, rather than allowing him to leave before any operation was mounted. This estimate was included in the joint review summary without comment and without endorsement. The review did not assess which process had been better.
It assessed how to ensure the two processes had visibility of each other before operations were committed. The recommendation was a shared real-time operational log accessible to both liaison desks at the appropriate classification level so that operations in routing and operations underway were visible to both parties simultaneously.
The recommendation was implemented within 2 weeks. It remained in use for the duration of the task force’s deployment. The operations officer who designed the shared log system noted in the implementation document that the system would not have prevented the specific situation it was designed for. The SAS operation had been generated by a time-sensitive source window that couldn’t wait for coordination, but it would at minimum have allowed both sides to see what was happening as it happened rather than discovering it afterward.
The American officer who had initiated the formal request reviewed the joint task force review summary and filed a brief note acknowledging the outcome. He noted that the intelligence the SAS had used to initiate the operation was superior to the intelligence available to the American request process. That the timing advantage the SAS held as a result was decisive and that the operation success was unambiguous.
He expressed no frustration about the 49-minutes his request had taken to route. He was a professional and he understood clearly that the institution he worked for and the institution the SAS worked for were different instruments designed to do different things at different speeds and that the right response to a time-sensitive intelligence window was the one the SAS had demonstrated.
He filed the note in the joint review folder and went back to work. The joint task force review that examined the parallel processes produced alongside its coordination recommendation a secondary finding that appeared as an annex rather than a main finding because its implications were structural rather than procedural and the review committee did not have the authority to act on structural recommendations.
The annex noted that the two intelligence processes, the American technical collection process and the SAS human source process, had each produced actionable information about the same target through different methodologies and within different operational time frames, and that the combination of the two information streams had produced in the outcome of the SAS operation a result substantially better than either process alone would have generated.
The second detainee, whose capture had depended on the source reports specific timing information, rather than the American targeting packages general location information, was the product of the SAS process. The subsequent operational exploitation of the compound material, which drove six operations over three months, was the product of both processes because the material in the compound was accessible only because the SAS had timed their entry around the source window, but the exploitation itself used the analytical capacity that the
American intelligence architecture provided. The annex recommended a formal mechanism for sharing in-progress intelligence between the SAS source network and the American technical collection architecture at the speed that time-sensitive operations required, rather than the speed that formal intelligence sharing protocols allowed.
The distinction was significant. Formal intelligence sharing moved through classification and releasability reviews that imposed a timeline incompatible with source-driven operations. The annex proposed a specific exception mechanism for source reporting with validity windows of less than six hours. It was reviewed by the appropriate legal and policy advisers, modified in several particulars, and eventually implemented in a form that was more limited than the original proposal but that provided meaningful improvement over the previous
process. The SAS source officer who had generated the original reporting for the Mosul operation was consulted during the implementation process and noted that the mechanism would have allowed the American planning process to receive the source window data in time to coordinate the operation before the window closed.
He also noted that the SAS would likely still have moved when they did because six hours is six hours and four operators can clear a building faster than a formal coordination cycle can complete. The policy staff noted this comment and did not include it in the implementation documentation. The target and the logistics subordinate who had been captured alongside him remained in detention for several months.
The interrogation process produced information that was assessed as significant by the intelligence analysts who reviewed it though the specific details of what they provided remain within the classification structure that applies to source protection requirements. What is known from the unclassified portions of the task force’s post-deployment assessment is that the capture of the second detainee, the one the American targeting package had not known would be present was described as a consequential outcome for the subsequent targeting sequence
and that the capture was directly attributable to the SAS’s timing advantage which was itself a product of the source reporting that the American collection had not accessed. The task force’s final assessment of the operation noted that the intelligence yield justified every aspect of the process that had produced it including the aspects that the coordination mechanism had not fully anticipated.
It was an honest assessment from a professional institution that had learned something from the night, and it acknowledged what it had learned without embarrassment. The second detainee’s significance became fully apparent over a period of several weeks as the intelligence analysts worked through the material from the compound exploitation and the interrogation records.
He occupied a position in the AQI logistics structure that was one level above where the SASR source reporting had placed him, not a subordinate of the primary target as the source had characterized him, but a parallel node in the network operating a separate but connected logistics thread. The mischaracterization was not a failure of source quality.
It reflected the deliberate compartmentalization the network applied to its own internal structure, which prevented people operating at any given level from having accurate knowledge of others’ true positions. The source had provided the best information available to them. The analysis of the captured material established the correction.
Both were valuable. The combination produced an understanding of the AQI logistics structure in eastern Mosul that the task force had not possessed before the operation and that drove a targeting sequence it could not have generated without it. The 49 minutes the formal request had taken to route was, in the final accounting, the difference between capturing one target and capturing two, between producing one intelligence thread and producing six operations.
The process that mattered most on that night was the one that moved fastest. The Americans understood this. They implemented the coordination improvement anyway because the next time might be different. The work continued. The network was smaller. The valley knew nothing of what had driven the change. The moment the SAS team moved through the final room of the target building and confirmed the objective secured, the transmission to the operation center was brief, to the point of appearing casual to anyone who did not know the
operational context. The team leader’s transmission used the standard confirmation format, objective secure, team strength at this time, ready for exfiltration instructions, without any of the commentary that a civilian observer might have expected from someone who had just accomplished something.
The formal bureaucratic process had not yet officially authorized them to attempt. The operation center received the transmission and responded with exfiltration instructions. The Pentagon’s request, still moving through the liaison chain, was overtaken by the reality that the operation it was requesting had already concluded. The after-action reporting that followed the operation addressed the timeline discrepancy directly, because the timeline discrepancy was a fact, and the reporting process was not designed to accommodate undisclosed fact. The SAS
operational command’s report to the relevant joint headquarters noted that the team had entered the building prior to the receipt of the formal support request, that this had been consistent with the SAS’s operational authority as understood by both the British and American commands, and that the operation had achieved its objective successfully.
The report did not apologize for the timeline, it documented it. The response from the American joint headquarters reflected a similar pragmatism. The report was received and the operational outcome was noted. The timeline discrepancy was not pursued as a procedural violation, because everyone who reviewed the timeline understood that the procedural framework had not been designed for the operational tempo the campaign required.
The framework would be reviewed. The operation had been correct. The building that that SAS team had cleared yielded intelligence that was immediately processed through the joint exploitation cell. The materials recovered, documents, electronic devices, communications equipment, were consistent with the operational purpose the intelligence picture had attributed to the building, and they added specific detail that extended the analytical picture in directions that generated new collection requirements and new targeting priorities. The exploitation process was
efficient because the team had been thorough and methodical in their collection during the clearance, tagging and bagging materials in the sequence prescribed by the exploitation protocol, rather than in the order they happened to encounter them. The systematic approach to exploitation during clearance was a learned skill, one that required the team to maintain the discipline of the exploitation protocol while simultaneously executing the tactical priorities of the clearance.
And that represented a genuine division of attention under pressure that not all assault teams managed consistently. The Pentagon’s reaction to receiving confirmation that the support it had requested had already been delivered before the request was processed was precisely as measured as the institutional context required it to be.
The officials who had initiated the request understood the operational reality. The outcome was favorable. The procedural anomaly was documented and noted. The lesson drawn from the timeline discrepancy was applied to the liaison frameworks that governed subsequent joint operations, specifically to the mechanisms by which American operational commands and British special operations forces communicated about developing intelligence and operational timelines in ways that allowed both sides to coordinate their actions without being constrained by bureaucratic processes that moved at a
speed incompatible with the operational environment. The change was modest in its bureaucratic form. Its operational significance was substantial.