The Yanks Had 900 Men in the Valley. The SASR Had 25. The Report Said It Wasn’t Close
The American operation in the Kunar Province Valley had been planned and resourced at a scale that reflected the genuine difficulty of the problem. 900 coalition troops, a figure that included Ranger elements, 100 first airborne infantry, special forces detachments and supporting enablers had been committed to a valley that sat astride the primary insurgent supply route between Pakistan and the interior of Kunar province.
The valley was contested ground. It had been held by Taliban and foreign fighter elements for long enough that the population had developed the careful neutrality of people living between two forces, each of which could be dangerous to them. The coalition’s objective was to establish sufficient presence in the valley to deny the insurgent supply route permanently rather than to clear the valley temporarily as had been done before and watch the insurgents return when the force withdrew.
This time the commitment was meant to be enduring. 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 3-week operation had proceeded as well as could be expected given its objectives and constraints, which is another way of saying it had proceeded into the managed stalemate that complex counterinsurgency operations in difficult terrain often produce.
The valley floor was under coalition control during daylight hours. The American forces could move along the valley’s primary track, establish temporary positions, and conduct clearing sweeps of the compounds on both sides of the track without coming under sustained direct fire. At night, the calculus reversed. Taliban rocket and mortar teams moved onto the high ground that flanked the valley. ground.
The coalition forces had been unable to hold permanently because the logistics of sustained high alitude positions exceeded what the current operational posture could support and engaged the forward operating base that the operation had established on the valley floor. The rocket attacks were not militarily decisive in the sense of threatening the FOB’s viability, but they were operationally constraining.
They disrupted resupply timelines, complicated medevac planning, and imposed a daily cost in attention resources, and degraded sleep that accumulated across the three weeks of the operation in ways that affected the force’s overall performance. The specific problem that the American force commander had identified correctly was the rocket teams.
The rocket teams were not large, four to six fighters operating a single weapon system, but they were mobile, disciplined, and operating in terrain that was simultaneously inaccessible to the American positions and perfectly suited to their own approach. They moved onto the high ground at night using routes they had been using for months or years, set up their weapon, fired their mission, and withdrew before any counterbatter response could be effective.
The ISR coverage that the task force maintained over the valley had been tracking the attacks for the three weeks of the operation and had identified the general area the teams operated from. What the ISR had not been able to establish was the specific route the teams used to reach their firing position and return.
The route was the key variable. Know the route and the rocket attacks could be stopped. Not know the route and the management of the attacks was the only available option. The American operational analysis that had been conducted on the ISR data set, three weeks of continuous coverage over the valley and its surrounding high ground, had been thorough and had reached the correct conclusion from the available evidence.
The rocket teams were using a route that came off the Pakistani side of the ridge, accessed a specific section of the high ground through a draw that was partially obscured from the ISR platforms by the rgeline geometry and withdrew by the same route after each firing mission. The draw was the problem. The ISR platforms could see the effect of the route.
The teams appearing on the high ground, firing, withdrawing, but couldn’t see the route itself because the draw’s geometry created a dead zone in the coverage. The route was known to exist. Where exactly it ran was not known. Without knowing exactly where it ran, a blocking position couldn’t be effectively placed because a position in the wrong location on the high ground would be bypassed.
The SASR officer who reviewed the operational summary from the Kunar Valley was reading it as an outside observer. The SASR were operating in a different province and had been sent the summary as part of the routine coalition intelligence sharing process that circulated significant operational pictures to relevant elements.
He read the summary with the specific attention he gave to all operational pictures, looking for the problem rather than the solution. because understanding the problem precisely is the prerequisite for identifying whether a non-standard solution might apply. The problem he identified was specific and had nothing to do with the force ratio or the operational concept.
It was an intelligence gap. Nobody knew exactly where the rocket team’s route was. And without knowing exactly where the route was, the tactical solution the rout’s existence implied could not be executed. The question the officer asked of himself as he read the summary was whether the ISR gap was genuinely unfillable or whether it was unfillable by the methods available to the current force.
The answer he reached was that the gap was unfillable by ISR and fillable by ground presence. The draw geometry that created the ISR dead zone was not a problem for a small team positioned within the draw because a team inside the dead zone sees the route that the platform above can’t see. What the ISR coverage couldn’t provide. A patient ground observation within the draw could provide.
If a team could get into the draw, stay there long enough to observe the route and do so without the rocket team’s detection network identifying them. The SASR officer had been in draws like the one the ISR imagery suggested. He had conducted observations from similar positions in similar terrain in similar conditions. The draw was not inaccessible.
It was inaccessible to the current force with its current posture. It was accessible to a small team with the right training, the right preparation and enough patience to do the work the observation required. The pattern of life analysis that the three weeks of ISR data had generated was comprehensive at the level of the valley floor and the lower slopes of the flanking ridge lines.
Hundreds of hours of sensor time had been devoted to tracking movement in the area where the rocket teams operated. Vehicles on the valley track, personnel moving between compounds, the flow of people and animals that constituted the valley’s daily rhythm. The analysis had been conducted by the task force’s intelligence staff with the thoroughess that a sustained intelligence collection effort produces when the question is narrow enough to focus the analysis.
The question, where do the rocket teams come from, had been asked correctly, the answer the analysis had produced was as complete as the collection could make it. The gap in that answer, the specific route through the draw, was not a gap the analysis had failed to find. It was a gap the collection platform could not see into and the analysis was an honest product of what the collection produced.
The draw geometry was a specific feature of the ridge terrain that the ISR operators had documented and flagged in the collection record. The flagging described the dead zone accurately, a section of the high ground terrain where the ridgeline profile, the draw orientation, and the sensor platform’s orbital parameters combined to create an area of approximately four square kilometers that the sensors could not cover from their standard operational altitude.
The area was not large in absolute terms, but it was precisely the area that the pattern of life analysis had suggested the rocket teams were using for their approach routes. The collection operators had noted the dead zone and recommended lower altitude passes to cover it. Lower altitude passes increased the risk to the platform and reduced the coverage of other areas.
The task force had approved two lower altitude passes which had produced partial coverage of the dead zone on two specific occasions but had not captured the route because the rocket teams were not using it during the passes. The gap persisted. What the SASR intelligence officer understood when he reviewed the three weeks of ISR data was that the gap was not going to be closed by more collection of the same type.
The draw geometry was not going to change and the rocket teams were not going to helpfully schedule their route use for the occasions when the sensors had maximum coverage. The only way to see the route was to be in the draw when the rocket teams used it. This was a different kind of intelligence collection from anything the task force’s current architecture included, and it required a different kind of asset to execute it.
The SASR had the asset. The question was whether the American task force was prepared to accept what the SASR was proposing as a viable alternative to the collection approaches that had already been tried. The SASR’s approach to the Kunar sector also reflected a specific understanding of the insurgent security posture that the ISR data had revealed but that the analytical products hadn’t fully incorporated.
The rocket teams moved at night, used established routes, and maintained their current operational pattern because they had no evidence that the coalition knew the specific routes they were using. They were correct. The coalition didn’t know the roots. But the team’s confidence in their own security, derived from the absence of coalition action against the roots they were using, was a vulnerability.
A team that believes its route is secure does not vary the route or its timing in the way that a team aware of observation pressure would. The consistency of the rocket team’s pattern documented in the ISR record in terms of timing, firing position, and withdrawal was the product of the team’s belief that they were secure.
It was also the feature that made the SASR observation approach viable. Predictable routes used consistently can be observed from the right position if the observer can reach that position without alerting the rout’s users. The physical demands of the SASR’s 12-day operation in the Kunar high ground were significant in a way that the afteraction reports focus on the intelligence and tactical outcomes didn’t fully capture.
The operators who spent the observation phase of the operation in the draw did so in conditions that the Afghan high country in that season imposed without accommodation, cold, wind, limited cover, the requirement for absolute stillness during the periods when the rocket teams were potentially in motion and the sustained alertness that observation duty demands from people who must be ready to react to what they are watching without being observed reacting.
The team managed the rotation of personnel through the observation positions with the care that sustained operations of this type require regular rotation to prevent fatigue induced error. Careful management of the periods when positions were being relieved to minimize movement signature and the specific discipline of teams that have trained for sustained covert presence operations and understand what the training is for.
The numerical disparity between the two forces in the valley is the fact that makes the report’s conclusion most difficult to process for anyone who has not studied the operational context in detail. 900 men against 25 is not a ratio that invites the assumption of equivalence. It is a ratio that in any conventional operational analysis would predict the certain superiority of the larger force in every domain that military effectiveness depends on.
Firepower, logistical depth, command flexibility, the ability to sustain casualties and continue operating. The report’s conclusion that the comparison was not close was a conclusion that required a specific account of why those conventional predictions had not held. And the account the report provided was detailed, analytical, and carefully grounded in the observable evidence of the operational record.
The 900 American troops in the valley were not performing poorly. They were performing exactly as they had been trained and equipped to perform in the specific operational role they had been assigned. Their mission was fundamentally different from the SASR’s mission in the same terrain. And the difference in mission was the primary explanation for the difference in measurable effect.
The American force was a presence force. Its purpose was to occupy ground, establish a visible security presence, and deter hostile activity through the credibility of its response capability. The SASR force was a disruption force. Its purpose was to take the fight to the hostile network, degrade its operational capacity, and deny it the freedom of action it needed to sustain its operations in the region.
The two missions are not directly comparable in terms of the outputs they produce, which means that comparing the two forces operational outputs was not a comparison of forces doing the same job. It was a comparison of forces doing different jobs. The report’s conclusion that the comparison was not close was a conclusion about which job produced more measurable operational effect in the specific context of the valley at that moment in the campaign.
The SASR’s freedom of action in the valley was a direct product of their force size rather than a limitation of it. A larger force in the same operational role would have required supply chains that would have been detectable, would have required a footprint that would have been observable, and would have required command structures that would have slowed the decision cycle below the threshold at which the specific kind of disruption the SASR were conducting is possible.
25 operators could move through the valley’s terrain in a way that 900 could not. They could sustain their supply requirements through aerial resupply patterns that were difficult to distinguish from normal aviation traffic. They could operate from multiple positions simultaneously in a way that made the hostile force uncertain about the SASR’s disposition and therefore unable to concentrate effectively against them.
The SASR’s force size was not a disadvantage. It was the design parameter that made their operational approach possible. The hostile forc’s response to the SASR presence versus its response to the American presence was another dimension that the report analyzed in detail. The American presence generated a specific type of hostile activity.
the indirect fire attacks, the IED campaigns, and the occasional small arms harassment that characterizes hostile engagement with a large, relatively static force that is too powerful to attack directly and too large to avoid entirely. The hostile force could not defeat the American presence through direct engagement.
It could impose costs on it through the indirect methods that are the standard hostile response to overwhelming conventional force. The SASR presence generated a different type of hostile activity. The concentrated, carefully prepared direct engagement attempts that characterize hostile response to a force that is operating offensively and that must be stopped before it can continue generating the network disruption it has been producing.
The hostile forces response to the SASR was a higher quality response. more resources, more preparation, more willingness to accept losses in the attempt because the SASR’s operational activity was producing the kind of direct damage to the network that the American presence was not. The intelligence picture that the SASR generated through their operational activity in the valley was one of the reports primary metrics for assessing operational effect and it was a metric that favored the SASR by a substantial margin. Active patrolling and offensive
action against the network’s operational elements generated contact records, captured materials, and direct observation of the network’s behavior under pressure that passive presence could not produce. The intelligence generated by the SASR’s operations was not simply a side benefit of their kinetic activity.
It was a deliberate product of the operational design which had been developed from the beginning with intelligence generation as one of its explicit objectives. Each contact was an intelligence generating event. Each captured material was an intelligence resource. Each observation of the network’s response to SASR pressure was input to the analytical picture that determined the next operational priority.
The SASR were not simply fighting in the valley. They were learning about the network while fighting it and the learning was being used in real time to make each subsequent action more effective than the one before it. Chapter 2. The SASR request to operate in the Kunar Valley sector was submitted through the Australian command chain and forwarded to the American task force with a standard liaison package.
The package specified the SASR’s proposed approach, a small team, foot movement, extended ground observation in the high ground sector containing the ISR dead zone and the resource requirements which were minimal access to the three weeks of ISR data. The task force had collected the existing intelligence package on the rocket teams and tactical deconliction with the American forces operating in the valley floor.
No helicopter support, no closeair support, no quick reaction force within practical extraction range, 25 operators. The American task force commander reviewed the request and approved it without significant deliberation. He had tried the large force approach for 3 weeks. It had produced a managed stalemate. A different approach using different assets in a different configuration was the logical next step.
The SASR’s first three days in the Kunar sector were spent on the ground reconnaissance that the operational concept required before any observation position could be established. The three weeks of ISR data that the task force had provided gave the SASR a detailed aerial picture of the relevant terrain, the high ground flanking the valley, the draw geometry, the areas where the ISR coverage was solid, and the areas where the dead zone fell.
From this picture, the SASR team identified three candidate positions within the draw that might provide both ground level observation of the route they were looking for and sufficient cover to sustain a multi-day presence without being detected. The ground reconnaissance confirmed two of the three candidates and eliminated the third.
The approach to the third position crossed a section of ground that the ground reconnaissance established as more exposed than the aerial imagery had suggested. The first confirmed sighting of the rocket team’s route occurred on the fourth day of the observation. The team had positioned two operators in the primary observation post within the draw before dawn using an approach time to avoid the early morning period when the local population moved on the high ground tracks and when the rocket teams might also be moving in preparation for a nightfiring mission.
The observation post gave a view along the floor of the draw that covered approximately 600 m of the route the rocket teams would use if the ISR analysis of their general approach was correct. For 6 hours, the observation post saw nothing relevant. On the seventh hour, the route confirmed itself.
A four-man team moving in single file with weapons along the draw floor heading toward the high ground. The SASR operators in the observation post did not engage. They observed. They transmitted the route coordinates to the team leader. The roots confirmation allowed the SASR to place a stop position, a team element positioned across the route at a location where the draw geometry provided concealment from both the direction of approach and the direction of withdrawal.
The stop position was placed on the fifth day after a second observation confirmed that the route the rocket teams used going up was the same route they used coming back down. The confirmation was essential. A stop position placed on an approach route that the teams abandoned on the return would be correctly positioned for the capture but unable to prevent the alert that a team escaping back down a different route could generate.
The interception happened on the eighth day. The rocket team, four fighters, moved through the draw toward the high ground on the schedule the observation had established. The SASR stop position had been in place for 17 hours in the dead ground of the draw, immmobile, silent, and invisible to the rocket team because the route they were using put them directly in front of a position they had no reason to believe existed.
The challenge was issued when the lead fighter was 20 m from the forward element of the stop position. The rocket team had no viable tactical option. The draw geometry that had protected their route from ISR observation also compressed the space in which they could respond to a challenge. They were stopped. They were detained. The firing position they had been moving toward sat empty that night and the night after and the night after that.
The intelligence from the detained rocket team led to a second operation three days later against the team support infrastructure. The cache where their weapon system was stored between firing missions identified from one team member’s interrogation statements. The cache contained not only the rocket system used in the valley attacks, but equipment associated with two additional teams operating in adjacent areas.
The secondary operation run by American forces with SASR intelligence support produced the additional equipment and the disruption of the adjacent team’s operational cycle. The Valley FOB recorded no rocket attacks in the 8-day period following the SASR interception, the first 8-day gap in rocket attacks since the operation began.
The afteraction report that the American task force produced after the SASR’s 12-day operation addressed the force disparity directly and with the analytical honesty that the disparity required. 900 men and three weeks of sustained operations had produced a managed stalemate and daily rocket attacks on the FOB.
25 operators and 12 days of patient ground observation had identified, intercepted, and disrupted the rocket teams, produced the secondary operation that extended the disruption to adjacent teams, and generated an 8-day rocket-free period that represented the operation’s most significant tactical success. The report noted these facts and made no attempt to explain them in terms that preserve the conventional force operations dignity at the small team operations expense.
It was a professional assessment of outcomes and the outcomes were what they were. The specific phrase from the report. The differential was not for size appeared in the report’s conclusion section and was written by the operations officer who had been most directly involved in both phases of the valley operation.
The phrase was his specific formulation of a conclusion that the data supported and that the report needed to state clearly to be useful, that the problem the 900 men had not been able to solve was not a problem of insufficient force. It was a problem of insufficient ground truth about a specific route. And the way to obtain ground truth about a specific route is to put people on the ground in the relevant terrain and have them observe until they see what needs to be seen.
The small team was the right tool for the job because the job was an intelligence problem. The large force had been applied to a tactical problem which was the right approach if the problem was the rocket attacks themselves. The rocket attacks were a symptom. The route was the problem. 25 operators in 12 days had solved the route.
The report said so in plain language and recommended that future valley operations in similar configurations include a preliminary ground observation phase before committing significant force to a tactical solution. The recommendation sat in the SOCOM archive alongside the valley operations operational record. The next rotation in the Kunar province read it. They applied it. It worked.
The American force commander who had approved the SASR request and watched the 12-day operation produce what three weeks of 900man operations had not was asked in his post- deployment interview what the operation’s lesson was. He gave an answer that was both specific and general. The specific answer was that the dead zone in the ISR coverage was not a problem that more ISR could solve and that recognizing this earlier and seeking an alternative solution earlier would have shortened the period of rocket attacks and reduced the
operational cost they imposed. The general answer was that force size and capability are not the same variable and that the correct response to a problem that isn’t responding to the applied force is not more force. It is a different kind of capability applied to a more accurate understanding of the actual problem.
He said the SASR had provided the different kind of capability. He said the more accurate understanding of the actual problem had been in the ISR data all along in the documented gap that the analysis had correctly identified and that the available collection hadn’t been able to fill. Putting those two things together, the SASR capability and the documented gap was the thing that should have happened sooner.
The question of why it didn’t happen sooner is one that the afteraction report addressed obliquely and that the post-eployment reviews addressed more directly. The short answer is institutional. Large conventional forces and small special operations forces occupy different spaces in the planning culture of a coalition task force.
And the mechanisms for matching small team capabilities to specific problems that large force approaches can’t solve are not as well-developed as the mechanisms for planning and executing large force operations. The SASR’s request had come through the Australian national chain rather than through the coalition task force’s internal planning process, which meant the match between the SASR capability and the Kunar problem had been made by an individual officer reading an operational summary and recognizing a fit rather than by a
planning process designed to identify such fits systematically. The individual officer had been right. The process had not been looking. The recommendations that emerged from the Kunar Valley operation were oriented toward this process gap. The task force review proposed a specific standing mechanism for small team capability consultation during the planning phase of operations that encounter persistent intelligence gaps.
a mechanism that would bring special operations elements into the planning conversation at the point where the gap was identified rather than waiting for an individual outside the planning process to identify the match. The mechanism was approved and incorporated into the task force’s standard planning cycle for the subsequent rotation.
Whether it produced the kind of systematic matchmaking it was designed for is difficult to assess from the available record. What is known is that the Kunar Valley’s rocket attack problem, which had persisted through 21 days of 900 man operations, was resolved in 12 days by 25 operators after the mechanism’s precursor, the individual officer’s recognition, had been applied.
The report said the differential was not force size. The task force agreed. The process was revised to reflect what the valley had shown. The SASR operators themselves returned to their parent units operational cycle within days of the Kunar operations conclusion. They filed no narrative account of the 12 days beyond the standard operational report.
The report’s word count was consistent with the regiment’s standard output, specific, factual, brief. The 21-day American operation had generated substantially more documentation as large force operations with their planning cycles. operational logs and coordination records always do. The SASR’s 12 days were captured in a report whose length was inversely proportional to the significance of what the report described.
The American Afteraction Assessment, which was the document that said what the SASR’s work had meant, was longer than the SASR’s account of doing it. This ratio of American analysis to SASR description was consistent with every previous joint operation in the archive. The SASR described others assessed.
The differential was not close in the Kunar Valley. It was not close in the reporting ratio either. The report’s analytical framework for comparing the two forces operational effects was not a framework designed to embarrass the larger force or to celebrate the smaller one. It was a framework designed to answer a specific analytical question that the operational command had a genuine need to answer in the specific conditions of the valley campaign at the specific moment in the campaign’s development.
Which operational approach was producing more progress toward the campaign’s strategic objectives? And what did the answer imply for the allocation of resources to each approach going forward? The answer the report produced that the SASR’s approach was producing substantially more measurable progress per operator employed was an answer with resource allocation implications that the operational command had an obligation to consider regardless of the institutional sensitivities that the comparison created.
The American commanders who received the report’s findings were professional in their response in the specific sense that professionalism requires. They engaged with the analysis, disputed the elements they considered methodologically flawed, and acknowledged the elements they considered methodologically sound. The disputes were substantive.
There were genuine methodological questions about how to compare operational effects across missions with fundamentally different objectives. How to establish a common metric for the deterrence value of a presence force and the disruption value of an offensive force. The report’s methodology was not beyond criticism.
The direction of the finding that the SASR were producing more operational effect per person was robust across multiple methodological approaches, even if the specific margin of advantage depended on methodological choices that reasonable analysts could disagree about. The institutional consequence of the report was not a reallocation of resources that reduced the American presence force in favor of expanding the SASR or similar small team disruption elements.
Resource allocation decisions at the operational level are rarely made solely on the basis of analytical comparisons of operational effect because they involve considerations of alliance relationships, national commitments, domestic political constraints and strategic priorities that operational analysis is not designed to fully capture.
The report was one input among many. Its analytical conclusions were taken seriously. They did not override the other considerations. What the report did produce was a more detailed and more analytically grounded conversation within the operational command about the relationship between presence operations and disruption operations in counter network campaigns.
A conversation that influenced the doctrinal thinking of both forces over the subsequent years in ways that were not directly traceable to the report, but that were shaped by the kind of rigorous comparative analysis it had undertaken. The SASR operators in the valley were unaware of the report’s existence during the period it was being written.
They were conducting their operations against the operational priorities that had been set for them, generating the contact record that the report was analyzing and focused on the specific tactical problems of each day’s operational planning. The news that a significant analytical document had been written about their operations reached the SASR’s theater headquarters through the liaison channel and was communicated to the squadron commander after the document had been completed and distributed.
The squadron commander’s response was consistent with the institutional character that the report was itself analyzing. He noted the document’s existence, confirmed that the squadron’s operational focus remained unchanged, and returned to the planning cycle. The analysis that 25 men had outperformed 900 was someone else’s observation to make and someone else’s lesson to draw.
The squadron’s job was to continue making it true. The Valley operation became one of the most studied cases in Australian special operations doctrine development over the following decade. Not because it was the most intense or the most kinetically significant operation the SASR conducted during the campaign, but because it offered the clearest analytical comparison of two fundamentally different approaches to the same operational problem.
The controlled conditions of the comparison. Two forces operating in the same terrain against the same network in the same time frame with clearly different missions and clearly different operational outputs made it an unusually clean case study for the kind of analytical questions that special operations doctrine needs to answer.
The SASR’s institutional analysis of the valley operation produced several modifications to the regiment’s operational doctrine that were implemented in subsequent deployments. Those modifications were direct products of the specific lessons the valley operation had generated. specific in their identification of what the SASR had done well and specific in their identification of what the SASR could have done better given the operational conditions and the outcomes they had produced.
