Not a Good Day to Die

Home > Other > Not a Good Day to Die > Page 15
Not a Good Day to Die Page 15

by Sean Naylor


  But it was the Ranger Regiment that provided the largest set of shared experiences that connected the leaders gathering at Bagram. The regiment falls under U.S. Special Operations Command but is really an elite airborne infantry force that links the light infantry and special ops communities. Unlike Delta or Special Forces, into which troops tend to disappear for the rest of their careers, soldiers often rotate between the Ranger Regiment and the Army’s light infantry divisions. So it was that many Mountain and Rakkasan officers and senior NCOs had served together in the Rangers. This was a massive slice of good fortune. The 75th Ranger Regiment is a tight community of warriors whose ethos is summed up in the Ranger Creed. There are 241 words in the Ranger Creed, and every Ranger is required to learn them all by heart. But the Creed’s essence is encapsulated in six of them: “Never shall I fail my comrades.”

  If the Ranger Regiment Association had opened a Bagram chapter, Wiercinski, Larsen, LaCamera, Grippe, and Nielsen would all have been members. Of these, only Nielsen had not fought with the Rangers in Panama. Other Ranger alumni included Blaber, Jimmy, and Rosengard, as well as Lieutenant Colonel Chip Preysler, who commanded 2-187 Infantry. Blaber and Grippe had served together in 1997 as the operations officer and B Company first sergeant of 2nd Ranger Battalion. When Grippe left the battalion, he bid farewell to Blaber with the prophetic words, “I’ll see you on a distant battlefield.”

  Walking out of one of the many briefings held at Bagram in the prelude to Anaconda, another soldier whispered to Wiercinski, “Holy smokes! Look at everybody’s right shoulder!” In the U.S. Army, soldiers wear their unit patch on their left shoulder. The space on their right shoulder is reserved for the insignia of a unit in which they have served in a combat zone. As Wiercinski glanced around, on right shoulder after right shoulder he saw the small black scroll-shaped patches of the Ranger battalions. It told him these were men who lived the values of the Ranger Creed, men who would not let him down.

  For Wiercinski, still smarting from the refusal of generals far above his level to allow his third battalion to join him in Afghanistan, there was some solace to be gained from knowing that its place would be taken by a unit led by LaCamera, who had been the operations officer of the Ranger Regiment’s 1st Battalion when Wiercinski had been the regiment’s deputy commander. “I knew him very well—superb reputation, great soldier,” Wiercinski said. “I know we all train to the same standards, but that would have been a little bit different, had I not known Paul LaCamera and served with Paul LaCamera before, and understood exactly how he trained and the kind of leader that he was.”

  Then Hagenbeck made an inspired decision. A division commander is normally supported by a pair of one-star generals who serve as his assistant division commanders, one for operations and the other for support (i.e., logistics). But neither of Hagenbeck’s assistant division commanders was in Afghanistan. One was in Kosovo, where about half the division was stationed. The other had fully expected to deploy to K2 with Hagenbeck. But Forces Command ordered Hagenbeck to leave a general behind at Fort Drum, even though there were few troops left to command there, because the four-star headquarters felt more comfortable with a general available to handle any tasks assigned to the post as part of Operation Noble Eagle, the mission to secure key facilities in the United States after September 11. So Hagenbeck had to deploy to a war zone without either of his right-hand men. Once he got to Bagram, the Mountain commander realized he could use some general officer help, both to organize the various components of his new command into a cohesive whole and then to help him run the battle. There weren’t many generals in Afghanistan to choose from, but the two Hagenbeck had in mind were perfect for the job. One was Gary Harrell. The other was Brigadier General Mike Jones, a six-foot-four Special Forces officer who was in Kabul as the military’s liaison to the CIA. Both brought impeccable credentials as warriors with contacts throughout the special ops and intelligence communities. When asked by Hagenbeck, the two readily agreed to serve as his deputy commanding generals. Hagenbeck then got Franks to approve their assignments in that capacity. Harrell began working with Hagenbeck around February 22. Jones came on board several days later. Now Hagenbeck had two seasoned special ops generals—officers well known to many of the other leaders in Bagram—at his side. These weren’t just experienced special ops officers, they were generals willing to use their rank to break bureaucratic logjams at CENTCOM and other higher headquarters. In the days and weeks ahead they would prove invaluable.

  Harrell and Jones were also useful intermediaries between Hagenbeck and the two elements of U.S. force in Afghanistan over which he exercised no control: Task Force 11 and the CIA. That the CIA was beyond the control of the military commander in country was to be expected. But CENTCOM’s decision to retain control of TF 11 in Tampa caused concern in Bagram, even though that too was par for the course in large military operations. Because of the covert nature of their specialized missions, the sensitive intelligence on which those missions were often based and the equally highly classified methods used to conduct them, black special ops units were rarely placed under conventional two or three-star commanders. But this didn’t mean such circumstances met with the approval of the generals cut out of the command chain. Hagenbeck and his staff were preparing to fight the largest set-piece battle the U.S. military had waged since the 1991 war with Iraq, and yet American units over whom they exerted no control would be running around on the same battlefield. This was a clear violation of the military principle of unity of command—the idea that a single commander should control all forces involved in an operation. U.S. officials like to say that in circumstances in which unity of command is impossible, “unity of effort” is the goal. But this doctrinal sleight of hand only papers over the cracks left when two generals at the same base each command forces operating over the same patch of ground, yet neither is answerable to the other, or to another commander in the theater of operations. In the Mountain TOC, the situation made officers uneasy. “There’s definitely some concern any time you’ve got two forces working in the same location, and there’s so little known about what one of them is doing,” Wille said.

  To reduce the risk of friendly fire and to share situational awareness, Task Force Blue permitted a single liaison officer from Mountain to hang out in their TOC, located at the other end of the airfield from Hagenbeck’s headquarters. But there was only one other exception to TF 11’s “never the twain shall meet” policy regarding conventional forces: Pete Blaber’s AFO. In keeping with his belief in “the power of combinations,” Blaber had begun to work closely with the conventional troops soon after the basement meeting in Kabul. Although friction persisted between Blaber and some JSOC leaders, Blaber persuaded the TF 11 staff to support Anaconda and his participation in it. “Pete’s arguments, and why we ended up going into Shahikot, is if you go to the places they have fought before, where the caches were, where they had a historical pattern, that’s where the leaders will be, and that’s what some of the signals [intelligence] supported,” said a TF 11 staffer. “We were watching and supporting their operation because we believed that would flush the pheasants.”

  (Despite the lack of hard evidence that any of the “big three” HVTs were in the Shahikot, the very presence of a large number of enemy fighters in one place, combined with a spike in Arabic cell phone traffic and a concentration of SUVs, suggested that one or more of them might be wintering there, protected by a large cadre of guards. This added to the widespread view among U.S. officers that Anaconda would prove to be the decisive operation in the Afghanistan. “It’s safe to say that the intel community thought that there were some significant leaders potentially in the Shahikot Valley,” Harrell said.)

  Blaber installed Jimmy and his small command and control element in the Mountain TOC as soon as it was established in Bagram. The AFO officers decided there was no point in gaining knowledge only to keep it from the commanders whose troops would be at the tip of the spear, so Blaber fed Hagenbeck inte
l from Gardez and Jimmy ensured the AFO teams’ locations were marked on Mountain’s maps of the Shahikot and the surrounding area. Jimmy, who by now had about half a dozen operators working for him in Bagram, also attended every important rock drill and briefing that Mountain held. In the Mountain TOC Jimmy ran his operation from a table just five feet away from the table at which the three generals sat. Sitting on the AFO desk were enough radios, satellite phones, and secure laptops to keep a small electronics store in business. But the gadgetry and the proximity had a purpose. If Jimmy learned something important, he could immediately pass it on to the generals without even raising his voice.

  THE first Mountain staffers to arrive in Bagram—Bentley, Gray, Wille, Ziemba, and Captain Shawn Prickett, an air operations officer—threw themselves into their work. February 14, the day after their arrival, marked the start of a two-day planning conference held by Rosengard in Dagger’s AOB building. Mulholland and Rosengard gave the newcomers another detailed overview of the intelligence regarding the Shahikot, and how they proposed to attack the valley. The Mountain planners liked what they heard, and applied themselves to the painstaking staff work required to give such a complex military operation any chance of success. The work Wille and Ziemba had done sketching out a concept of operations for the Shahikot now paid dividends, drastically shortening the time the Mountain planners needed to get smart on the operation. By the time Hagenbeck arrived February 17, his advance party had a detailed concept of operation ready to brief to him. The nascent plan still clung to Rosengard’s vision of attacking the valley from the west with Zia’s troops and the two A-teams (a force now collectively known as Task Force Hammer) while air-assaulting TF Rakkasan—including LaCamera’s battalion—to occupy blocking positions astride the escape routes out of the valley. Many i’s remained to be dotted and t’s to be crossed, but the basic elements were there. With D-Day set for February 25, the planners needed the commanding generals at every level to sign off on the work that had been done so far. Those crucial briefings occurred February 17.

  Hagenbeck was briefed first, by Gray and Smith, and gave his thumbs-up. Then Mikolashek flew in from Kuwait. His approval was vital for Anaconda to proceed, and represented the highest hurdle so far for the work into which Rosengard, Wille, and the other planners had been pouring themselves. All the assorted task force commanders—Hagenbeck, Harrell, Mulholland, Wiercinski, Harward, and even Trebon—gathered to hear Gray and Rosengard brief the CFLCC commander. Rich, the CIA chief of station, also came up to Bagram for the occasion. Gray outlined the conventional forces’ role in each phase of the plan to Mikolashek, Rosengard described what Dagger would contribute. Mikolashek raised two issues. He was concerned that the operation was scheduled to begin on the last day of Eid ul Adha, the three-day Feast of Sacrifice that commemorates Abraham’s willingness to sacrifice his son Ishmael to Allah. During the holiday Moslems around the world sacrifice a lamb or other animal and distribute the meat to relatives or the needy. Mikolashek told Hagenbeck and the others that they should not ignore the holiday: Either they should take advantage of it and attack during the festivities to catch the enemy by surprise—he cited Washington’s Christmas 1776 crossing of the Delaware and attack on Trenton to illustrate what he meant—or they should delay the attack until the holiday had passed. Worried that some of their Afghan allies wouldn’t show up for the fight unless the date changed, the Americans decided there and then to move D-Day from February 25 to February 28.

  Mikolashek was also concerned that too many conventional forces were being committed to the fight, according to officers who heard him speak. Larsen, the Rakkasan executive officer, who was present at the briefing, said Mikolashek reflected CENTCOM’s view that “the more targets we present to the enemy, the more he will kill.” This was a curious approach to take to an operation in which the objective was to trap and kill the enemy. Wiercinski countered that “he didn’t think we had enough force, because the enemy situation was too vague, and there were a lot of escape routes,” Larsen said. There was, of course, no chance of CENTCOM providing more forces for the operation. Just getting eight Apaches into the country had taken a momentous bureaucratic struggle. But Wiercinski’s argument at least persuaded Mikolashek not to tamper with the force already set aside for Anaconda. (Mikolashek took strong exception to this account. “I don’t remember saying anything about ‘too many conventional forces,’” he said.)

  Finally, the leaders in Bagram held a video-teleconference with Franks and his principal staff in Tampa. The CENTCOM commander liked Rosengard’s concept of forcing the enemy in the valley to flee toward Pakistan, which the Dagger operations officer referred to as “convincing the enemy to do what he already wants to do.” Franks approved the concept of operations, but told Hagenbeck to give his task force a new name. “Don’t call yourself ‘Afghanistan,’” he said. “Call it anything else, but that has geopolitical implications.” With CENTCOM apparently still gripped by the fear of appearing like an army of occupation, Hagenbeck renamed his organization Coalition and Joint Task Force (CJTF) Mountain.

  Having gotten a green light, the planners redoubled their efforts. What Mikolashek and Franks had approved was a concept of operations—the broad brush outline of who would do what in Anaconda. There was still much work to be done to determine the hows, wheres, and whens of the operation. As C-130s and C-17s landed night after night on the airstrip and scores of tents went up to shelter the army gathering at Bagram, Gray, Wille, Rosengard, and Larsen toiled long caffeine-and nicotine-fueled hours refining the plan. There were plenty of devils left in the details.

  17.

  PETE Blaber had a rapt audience.

  It was February 14. The B Squadron recce guys had arrived earlier that day, only forty-eight hours after Blaber had requested them in the tense video-teleconference with Dailey. (They had actually been warned several days earlier by others in Delta that Blaber wanted them in Afghanistan, forcing them to cut short a training exercise in Europe to return to Bragg less than a week before their arrival in Gardez.)

  Blaber gathered the new men—the operators he planned to send on the reconnaissance missions—and explained why they had been called forward. The meeting, held in the big work room, was also attended by the Special Forces and CIA folks. Their mission was to reconnoiter the approaches to and—eventually—the interior of the Shahikot Valley, Blaber said. He repeated his guiding principles for operating in the enemy’s backyard. First was the need to understand the enemy. Blaber told the new arrivals they should read everything about the Shahikot, talk to Zia’s troops about the enemy, and ask themselves, “If I were the enemy, how would I defend this area?” Locking eyes with each man in turn, he told them, not for the last time, that the key to success was to follow Patton’s three principles of war: “Audacity, audacity, and audacity.”

  Blaber had handpicked these men because he knew they were some of the very few in the U.S. military—in anyone’s military—who could attempt the missions he had in mind with any hope of success.

  The next day the reconnaissance effort began in earnest. The new guys got up to speed quickly, reading all the same books and intel papers the other guys had read, and familiarizing themselves with the surrounding area using maps and overhead photos. Helped by Glenn P., the AFO intel analyst, they looked for avenues of approach into and escape from the Shahikot, potential enemy lines of communication, evidence of enemy activity, and, crucially, places in and around the valley where they might be able to establish observation posts. It was busy, as they war-gamed numerous options for infiltrating teams into the valley.

  The AFO operators were imbued with their commander’s audacious spirit, but neither they—nor he—were blind to the dangers of operating in that environment. They were particularly concerned about the threat of mines, which had been strewn about the Afghan countryside liberally over the previous twenty-five years. These haphazardly marked minefields had cost many civilians their legs or worse. The maps and other intelligenc
e documents identifying the area’s minefields left a lot to be desired. The AFO troops turned for help to Hoskheyar’s fighters, who, as locals in the pay of the Americans, were the best sources of intel on the mine threat. Prompted by the AFO operators, the Dagger troops at the safe house asked their Afghan allies a series of seemingly innocuous questions designed to elicit information about minefield locations without letting on that a big operation in the Shahikot was in the offing. The militiamen knew there were Al Qaida troops in and around the Shahikot, and the Americans were clearly building up the force in the safe house and paying, training, and equipping the Afghans for something, so whether the local fighters failed to put two and two together is open to question. However, they did give the U.S. troops valuable information about “thousands” of mines that lay along routes the AFO patrols might otherwise have taken.

  Blaber envisioned an initial recon mission divided into two phases. The first would be a “vehicle recce,” driving along and off the roads southwest and southeast of Gardez in order to determine the feasibility of moving deeper into the mountains on foot. Providing such penetration seemed possible, the second phase would be the true environmental recon, with two teams approaching, but not entering, the Shahikot Valley—one from the north, one from the south—and establishing observation posts, before returning to Gardez to prepare for a mission into the valley just prior to D-Day.

  The troops who would take the lead were the recce experts newly arrived from Bragg. The B Squadron operators were divided into two teams: India and Juliet. A Delta recce team usually consisted of four men, divided into two sniper-spotter duos, with the spotter being the senior man of each pair, but these teams had only five operators between them.

 

‹ Prev