forty knots for ten minutes before the Peleliu’s hulking profile loomed in the haze. Coming alongside, we reversed the earlier process and climbed up a rope ladder into the cavernous hangar bay. The Peleliu’s flight deck stretched from bow to stern, like an aircraft carrier, and the MEU’s whole squadron was aboard. Inside the hangar bay, helicopters and Harrier jets crouched on their landing gear in the dim light, while maintenance crews scurried around and a group of Marines practiced semper fu on a blue rubber mat.

The Battalion Landing Team (BLT), composed mostly of infantry Marines from 1/1, planned its missions in a room the size of a Manhattan studio apartment. Computers lined one wall, and a huge map of Pakistan and Afghanistan covered the opposite bulkhead. Exposed pipes and fluorescent lights hung from the ceiling, and some wag had taped a drawing of Osama bin Laden to the door. Its caption read, “You can run, but you’ll only die tired.” Battalion officers and staff NCOs filled the scattered chairs.

When Captain Whitmer, Patrick, and I walked in, the battalion’s executive officer called the room to order. He freed up chairs by dismissing several Marines from the room. “We’re keeping details on this one close to our chest, gents. Sorry.”

They walked out, looking hurt, and the door was closed behind them. This was starting to sound interesting.

“Welcome, Bravo Company,” he said with a nod in our direction. “What I am about to say will not leave this room. You will do your planning, theorizing, and bullshitting within these four walls — not on the mess deck, not in the wardroom, and not in the gym. Is that clear?”

We all nodded as he continued. “As you know, the United States has been dropping bombs on Afghanistan for the past nine days.” He explained that there was a small CIA and Army Special Forces presence on the ground, mainly in the north. There was as yet no ground presence in the country’s south. The executive officer paused for effect. “That is about to change. On Friday evening, October 19, Task Force Sword will conduct a mission into southern Afghanistan to seize an airfield and attempt to capture a high-value leadership target.” Pause. “We have been tasked with providing a Bald Eagle for that mission.” Pause, and a slow turn to face Captain Whitmer, Patrick, and me. “Bravo Company, you’re it.”

The three of us glanced at one another. A Bald Eagle was a company-size reserve element, ready to help in case a raid force ran into trouble. The question on all our minds was “Why Bravo?”

Captain Whitmer was too self-effacing to say it, but I knew the answer. Among the battalion’s company commanders, he was the iconoclast, the outcast stepchild who trained his Marines to be good instead of look good. He pushed us hard, questioned authority, and couldn’t even feign obsequiousness. But when the first real mission called, the battalion turned to him.

“Task Force Sword is composed of SOF currently embarked on the Kitty Hawk,” the executive officer continued. The aircraft carrier Kitty Hawk was being used as a floating base for special operations forces working in and around Afghanistan.

“Here’s your mission statement.” He handed us a sheet of paper marked SECRET in bold red letters. I read, “On order, Task Force Bald Eagle launches from PEL in 4 x CH-53 to OBJ RHINO, links up with TF SWORD mobile reserve, and conducts relief in place. Defend RHINO with Bravo Company for up to twenty-four hours. O/o turn over OBJ RHINO to TF SWORD and withdraw to ARG shipping.” This prompted more questions than it answered.

After a more comprehensive brief, I thought I had a good idea of the plan. On Friday night around dusk, elements of Task Force Sword, mostly Army Rangers and Special Forces, would launch from the Kitty Hawk. They would fly into Pakistan, securing a small airfield near Dalbandin, code-named Honda, to use as a refueling and rearming point. From Dalbandin, part of the force would parachute into a desert airstrip in southern Afghanistan code-named Rhino, while the other part would raid Taliban leader Mullah Omar’s residential compound outside Kandahar. We would serve as a reserve in case something went wrong during any part of the mission. This sounded complex, I thought, and a lot could go wrong.

Bravo Company flew over from the Dubuque the next morning. While the NCOs settled the troops in their temporary berthing and began distributing ammunition and gear for the mission, Captain Whitmer, Patrick, and I continued with planning. Every MEU mission ran through three planning stages. First came a warning order from some higher command notifying the MEU to “be prepared to” execute a given task. That task may have been distributing food to the people of East Timor, evacuating the embassy in Islamabad, or serving as the quick reaction force for a mission into Afghanistan. Once the warning order was received, the MEU staff went into overdrive, developing a course of action for how the MEU would accomplish the mission.

It is a central tenet of the Marines’ war-fighting philosophy that each subordinate must provide options to his boss — tell him what you can do, rather than what you can’t. Depending on the situation, two or three or four courses of action would be developed and then roughed out into basic operational plans. For the Sword mission, helicopter pilots calculated distances and fuel burn, charting different paths through the mountains. Infantry officers studied maps to memorize the layouts of Rhino and Honda and decided how many men they’d need in different scenarios. All the hypothesizing came together in the final construction of three possible courses of action — put the Bald Eagle on the ground at Honda in case it was needed, keep it airborne over the ocean until called, or keep it on the Peleliu, ready to launch on a few minutes’ notice. The MEU commander reviewed the options and decided to keep the quick reaction force aboard the Peleliu. Its response time would be almost as fast and at greatly reduced risk. With a course of action chosen, the MEU fleshed out a detailed concept of operations for accomplishing the mission.

The wheels spun madly again. Numerous small planning cells, each focused on a different aspect of the mission, convened in coffee-fueled debate sessions. Pilots plotted their courses and picked the mix of Super Stallion transport helicopters and Cobra gunships. Grunts finalized their manifests, picking platoons and dividing them among the helicopters so that one crash wouldn’t wipe out all the machine gunners or all the officers. Other cells focused on communications, requesting dedicated satellite radio channels and preparing encryption codes to scramble the transmissions. Logisticians brought ammunition up from the ship’s magazine. Medical teams prepared the ship’s operating rooms and thawed blood for the Marines to take with them. All the details of the plan were then presented to the MEU commander in a concept of operations brief.

Preparing a concept of operations during training had always frustrated me. The briefs were PowerPoint presentations held in the Peleliu’s wardroom. Captains and majors fought over font size, background color, and whether to include cute graphics of moving helicopters. The purpose, though, was sound: to air the plan publicly, criticize it, test its assumptions, focus on the friction points where something was likely to go wrong, and strengthen it. Finally, after the appropriate changes and refinements were made, the plan was rehearsed from start to finish in a confirmation brief, with each key player explaining his role to the MEU commander. According to MEU (SOC) standards, the whole process, from warning order to confirmation, had to be done in less than six hours.

Only after the plan was approved did I feel comfortable briefing the Marines. I wanted to insulate them from the confusion of changing details in the mission.

“Weapons platoon, circle it up,” I said, standing in the hangar bay with my notebook and a photocopied map.

The Marines stopped loading ammo and programming radios, pressing close to hear the word. I quickly outlined the mission to low whistles and nods of approval.

“It’s important right now that we stick to our timeline. We have a lot to do. The rest of this evening is your time to prep individual and platoon gear. Get some rest tonight — tomorrow’s a busy day.” I tore a page from the notebook and taped it to the bulkhead above the platoon’s gear. “Here’s the schedule: 0600 breakfast; 0630 to 0800 draw weapons, issue ammo, and stage equipment; 0800 to 0900 helo drills; 0900 to 1000 formal platoon order issued; 1100 to 1200 final gear staging; 1200 to 1300 rules of engagement brief; 1300 to 1600 rehearsals; 1630 test fire; and 1700 call away and final load rehearsals. After 1730, Sword is airborne, and we’re on alert 10 — that’s ten minutes from notification to launch.”

I looked around at the crowd of faces. “You’re it, fellas. A hundred million American men would like to be in your shoes right now. We have the honor of fighting back.”

On Friday, I got my first look at the wartime military. While the platoons ran through the schedule, Patrick

Вы читаете One Bullet Away
Добавить отзыв
ВСЕ ОТЗЫВЫ О КНИГЕ В ИЗБРАННОЕ

0

Вы можете отметить интересные вам фрагменты текста, которые будут доступны по уникальной ссылке в адресной строке браузера.

Отметить Добавить цитату