Operation Red Wings: The Rescue Story Behind Lone Survivor

Operation Red Wings: The Rescue Story Behind Lone Survivor

3.3 18
by Peter Nealen
     
 

Marcus Luttrell's blockbuster bestseller, Lone Survivor—soon to be a major motion picturetells the story of Operation Red Wings, in which four U.S. Navy SEALs were inserted into the mountains of eastern Afghanistan with the task of collecting intelligence and finding—or killing—a top al Qaeda commander. The SEALs were ambushed

Overview

Marcus Luttrell's blockbuster bestseller, Lone Survivor—soon to be a major motion picturetells the story of Operation Red Wings, in which four U.S. Navy SEALs were inserted into the mountains of eastern Afghanistan with the task of collecting intelligence and finding—or killing—a top al Qaeda commander. The SEALs were ambushed by over one hundred Taliban fighters and a horrific battle ensued. The rescue helicopter carrying eight SEALs was shot down by a reported Rocket Propelled Grenade (RPG), killing them instantly and erasing any hope for the SEALs already on the ground. Luttrell was the only survivor.

OPERATION RED WINGS is an in-depth examination of the recovery mission to rescue Luttrell, filled with never-before-told details and shocking new revelations. Author Peter Nealen (former USMC Force Recon) and the team at SOFREP have an expansive network within the Special Operations community, providing them with access to exclusive interviews, after action reports, military intel and previously untold accounts of the rescue mission. Nealen and his team have uncovered eyewitness reports that put the "official" story into question as to how the initial rescue helicopter was shot down. If true, this potential coverup will have had severe consequences on subsequent helicopter insertion operations and put lives at risk.

Complete with a foreword by former Navy SEAL Brandon Webb, this is a must-have companion to the blockbuster book and upcoming film.

(12,000 words)

Product Details

ISBN-13:
9781466855533
Publisher:
St. Martin's Press
Publication date:
12/17/2013
Series:
SOFREP
Sold by:
Macmillan
Format:
NOOK Book
Pages:
60
Sales rank:
118,769
File size:
602 KB

Read an Excerpt

Operation Red Wings

The Untold Story Behind Lone Survivor


By Peter Nealen, SOFREP, First Edition: December 2013

St. Martin's Press

Copyright © 2013 SOFREP, INC.
All rights reserved.
ISBN: 978-1-4668-5553-3



CHAPTER 1

Day 1: June 28


It was about 1140Z. Two MH-47 Chinooks, call signs Turbine 32 and Turbine 33, were closing on the LZ (landing zone) near the base of Sawtalo Sar, the compromised team's last known position. Two UH-60 Black Hawks and two AH-64 Apaches were flying cover, and Grip 21, a flight of two A-10 Warthogs, was circling above. Lieutenant Commander Erik Kristensen, commanding SEAL Team 10 and the four-man Special Reconnaissance (SR) team, was aboard Turbine 33, determined to lead the effort to get his SEALs back, in one piece if at all possible.

The SEALs aboard both helos had been preparing to follow on the reporting from Murphy's team. They had been hunting a particular anti-Coalition militia leader, known as either Ahmad Shah or Sharmak, who had killed a number of the marines of 2/3 (2nd Battalion, 3rd Regiment), who were moving into Kunar Province in the Korengal and Pech valleys and had set up in an FOB (forward operating base) named Camp Blessing, after Jay Blessing, a Special Forces soldier killed by an IED (improvised explosive device) strike in the area in 2003. Initial intelligence had Shah leading between one hundred and three hundred fighters and boasting that he had a weapon that could bring down helicopters.

The men aboard the helos, SEALs from both SEAL Team 10 out of Virginia Beach and SEAL Delivery Vehicle Team 1 out of Pearl Harbor, had been preparing to go in the next night, clear the target villages where Ahmad Shah was believed to be, and then blow LZs for the marines of 2/3 to come in and do a more thorough sweep of the entire area. There were about five villages on their target list, most of them clinging to the steep sides of the mountains. Instead, they found themselves going in during daylight, trying to retrieve their teammates under fire on the mountain.

Sawtalo Sar is the highest point on a ridgeline running between the Korengal and Shuryek valleys, roughly in the center of Kunar Province, a mountainous province in the northeast of Afghanistan. The Pech River runs across the end of the ridge to the north, with the Korengal and Shuryek rivers running into it. The valleys are dotted with small stone villages, surrounded by terraced fields. The heights are rocky alpine slopes, cloaked in thick coniferous woods.

Turbine 33 took the lead, descending toward the chosen LZ, an open meadow surrounded by scrubby trees on the shoulder of Sawtalo Sar, about 650 meters from the summit of the mountain. In their haste to rescue the SR team, they pushed to the LZ ahead of their escort.

As the big Chinook prepared to settle on the LZ, a white smoke trail was seen streaking up from the trees near the zone. The projectile impacted the MH-47's exhaust duct and detonated.

The Chinook rolled over in midair at the impact. The pilot lost control, and the helicopter hit the side of the mountain and exploded. All sixteen men aboard — eight members of the 160th Special Operations Aviation Regiment (SOAR), the Night Stalkers, and eight SEALs from Team 10 and SEAL Delivery Vehicle Team 1 — were killed.

Under more ground fire, Turbine 32 turned away hard, throwing the men in the troop compartment to the deck, and pulled into an orbit above the mountain, searching for survivors. According to the official contact report, one of the AH-64s reported a possible survivor near the crash at around 1215Z, but the report was never corroborated. It is remotely possible that one of the men aboard the helicopter survived, only to succumb to his wounds before rescue forces could reach the LZ, but it is equally possible that what the Apache pilot saw was a Taliban combatant, investigating the wreck. No one will likely ever know.

The birds continued to orbit the mountain. A No Fire Area was established for a 500-meter radius around the downed helicopter, so as to avoid accidentally hitting any possible survivors. There would be no air support or artillery missions approved within 500 meters of the crash site.

While the SEALs desperately wanted to get on the ground to look for surviving SEALs and Night Stalkers from the downed bird, as well as retrieve the SR team that still had not been contacted, word came from CJSOTF (Commander, Joint Special Operations Task Force) to return to the airbase at Jalalabad. The risk of losing another helicopter on the mountain was considered too great. The aircraft turned southwest for Jalalabad, while the SEALs aboard Turbine 32 fumed at losing a chance to rescue their brothers.

* * *

It was later reported that Turbine 33 was struck by an RPG (rocket-propelled grenade) that went through the open ramp and impacted the main driveshaft, thus downing the bird. According to the SEALs who witnessed the shootdown, however, it is the consensus that it was not an RPG but something much more powerful, a MANPAD (man-portable air defense) device of some kind. RPGs, contrary to movies and video games, do not leave smoke trails. Missiles do. There had been rumors of Stingers still around from the Soviet-Afghan War, but those were just that — rumors. Stinger batteries don't last all that long; the missiles have a definite shelf life. Whether it will ever be discovered what exactly shot down Turbine 33 is unlikely, but the question of how many loose SA-7 Strela shoulder-launched surface-to-air missiles are still floating around has to be asked.

Given the operational impact of acknowledging an actual MANPAD threat in-theater, the reports were put down as an RPG shot down Turbine 33. Otherwise, it would have been necessary to completely alter air operations in the entire AO (area of operations). It did, however, put a substantial damper on air operations in support of the rescue effort. Having lost one bird already, the command became extremely skittish about risking another.

Had a suspected MANPAD been reported and verified, it's likely that loss of life in-theater linked to shot-down helicopters could have been prevented, including the controversial Extortion 17 crash that would happen years later.

* * *

The SEALs weren't going to sit still in Jalalabad. Now, not only were four SEALs missing on the mountain, but another eight, plus their Night Stalker brethren, had gone down on the same mountain. Getting off the MH-47, they pushed to get aboard new birds, this time UH-60 Black Hawks. They had to get back to the crash site as quickly as possible, in case the reports from the Apache pilots had been correct and anyone had survived. The birds took off and headed back northeast toward Sawtalo Sar, passing over the checkered fields of the Kunar River valley before heading up into the Hindu Kush as the sun began to go down.

It was only about a 65-kilometer flight from Jalalabad to Sawtalo Sar, but they only made it about halfway before the storms building up in the mountains made it too dangerous to fly. The pilots told the SEALs that they had to return to base and turned around for Jalalabad once more. Once again, the SEALs had to wait, knowing their comrades — those still alive — were in deadly jeopardy on the mountain slopes.

Shortly after returning to Jalalabad, the SEALs were ordered back to Bagram Airfield, to reconstitute a new rescue force. The effort would now be completely coordinated out of Bagram.

* * *

It was after the second attempt to rescue the downed SEALs and the SR team that CJSOTF called off the organic rescue effort and called for dedicated Air Force Rescue to come in and take over. The initial effort had been according to standard operating procedure, but with the situation getting more complex, especially with Turbine 33 down, the commander wanted expert rescue personnel involved. There were no Combat Rescue personnel or plans in that AO at the time.

The call was answered by U.S. Air Force Combat Rescue personnel of the 59th Expeditionary Rescue Squadron from Kandahar. The combat rescue officer, or CRO, had been in Kunar only a week before, working out of Camp Blessing to attempt to find and rescue a marine who had been lost in the Pech River. While on an evening patrol, marines in a Humvee had been moving down the road next to the river when the Humvee hit a washout and began to tip toward the water. Two marines were in the back of the vehicle, and when the truck started to slide, one went out to the left, the other to the right, into the water. The driver managed to right the vehicle, but the marine had been swept away by the current. The Combat Rescue personnel, along with more marines and their attached Afghan National Army counterparts, searched for several days, but the lost marine was never found. Neither was any of his equipment.

The CRO, six Pararescue Jumpers, or PJs, and three HH-60 Pave Hawk helicopters, two of which were from the 920th Rescue Wing, a reserve unit, flown by "Skinny" and "Spanky," flew from Kandahar to Bagram Airfield in the afternoon of June 28. The CRO went straight to the JOC to get a handle on the situation, while the other rescue personnel got ready to head out as soon as possible.

The 920th Rescue Wing pilots and crews were reservists, and as such encountered a fair amount of tension with the 160th SOAR personnel. The Night Stalkers had lost eight of their own and felt that it should be their responsibility to go rescue them. They didn't necessarily trust the training and expertise of reservists, who didn't train constantly for the job, as they saw it. In fact, the reserve pilots and crews did spend a great deal of their time either training or deployed; the 920th is the only Reserve Combat Rescue Wing in the U.S. Air Force, and with the Global War on Terror in full swing, they had quite a few operational commitments. Spanky had been flying Combat Rescue for ten years.

The 920th pilots and crews had actually been scheduled to return home within days; several of them already had plans for the Fourth of July. The disaster on Sawtalo Sar deferred those plans.

Getting up to speed and ready to go wasn't as easy as it might sound. The CRO was the only one cleared to enter the JOC in the first place, which put a crimp in getting the rest up to speed. They had to get clearance paperwork done and get the necessary briefs on what was going on. The concerns about possibly losing another helicopter on the mountain were still very fresh, which meant there was not a lot of hurry to send the HH-60s back up. There was required maintenance on the helicopters after the flight from Kandahar, as well as required crew rest before they could fly again.

In the JOC, the CRO sat down with the special tactics officer, the air force SOF officer on-site, and got the full briefing on what they knew had gone down. There were already Rangers, Special Forces, and some PJs heading for Turbine 33's crash site, so the primary effort became about finding the four-man SEAL team that had come under fire, then dropped off comms (slang for communications). They had to figure out what they would do next, where they would go, so that they could get rescue assets there to pick them up.

What the CRO found as soon as he started working was that there was very little coordination going on. Between the army, the air force, Naval Special Warfare, and the marines, there were lots of units and groups trying to get in to help, but very few were talking to each other. The communications channels between the different chains of command simply weren't there. Units in the field were setting up comms with their own headquarters, but all of the radio frequencies being utilized for the rescue effort were separate. So anything the Rangers found wasn't necessarily being passed to the Special Forces, and thus wasn't being passed to the air force personnel who were in charge of the overall effort. In fact, throughout the entire recovery operation, the Combat Rescue personnel were never entirely sure who was where on the ground, and when, due to the spotty nature of the communications channels.

He also found that, while the initial actions to launch the QRF on Turbine 32 and Turbine 33, and the follow-on attempt to get SEALs, PJs, and U.S. Air Force Combat Controllers to the crash site were the correct ones, there really wasn't any further contingency planning in place. There was no plan beyond the initial attempt. While the CRO will today stress that everything they did was the right thing to do, the JSOTF in Kunar was winging it. That was what the CRO was there to fix.

* * *

While all this was happening, in spite of the numbers of forces on the ground already, including elements of 2nd Ranger Battalion, Special Forces, and marines from 2/3 who were pushing into the Korengal and Merit valleys from Camp Blessing, more forces were deemed to be needed on the ground. To this end, elements of 3rd Ranger Battalion, still stateside in Georgia, were called in and told to get ready to deploy to Afghanistan. All the 3rd Battalion Rangers was told initially was that an MH-47 had gone down with sixteen men aboard, SEALs and Night Stalkers. They would not find out about the four-man SR team on the mountain until they arrived at Bagram.

The Rangers, most of whom were off duty, were simply paged to report to Battalion Headquarters. When they got to their company areas, they were told to pack their gear and get ready to go. Eighteen hours after receiving the first page, they were on the plane and heading for Afghanistan.

* * *

With forces already preparing to move to the Turbine 33 crash site, and the site being known already, the CRO's primary focus became finding the four-man SR team. While Turbine 33 was well localized, no one knew exactly where the team was, or whether they were alive or dead. The assumption, for the sake of the operation, was that they were alive; if they were alive, it made it all the more urgent to find them and get them out. They were alone, off comms, and in enemy territory, and quite likely one or more of them were wounded. The longer they stayed lost, the greater the likelihood that they would wind up dead. In fact, three of them already were dead, but the JOC didn't know that for certain.

The first priority, in addition to getting air assets up to search and attempt to make contact over the SAR (search and rescue) frequency, was to get inside the SEALs' heads and try to ascertain where they would go, assuming they were still alive. To that end, the CRO had to go through all of their operational plans and materials, as well as their personnel recovery materials, which would provide information that only they would know, in the event they were found and had to be identified on the ground.

What had to be determined was what direction the team would go, based on their E&E (escape and evasion) plan, what retrieval point they would make for, and what equipment they had with them they could signal with. What was their SAR frequency? What nonradio signaling devices did they have? Moreover, he had to get to know the men themselves. He had to get into their heads, figure out how they thought, to try to determine what each one of them would do when alone and cut off, with everything having gone to hell in a hand basket. A man in a team will react differently from a man alone. Even if they had a detailed team E&E plan, there was no guarantee that if cut off from each other, they would follow it exactly. Personality quirks became extremely important.

He immediately ran into some serious difficulty. The E&E plan the SR team had left was vague at best — in fact, there hardly was one. There was a possible retrieval area, but actual E&E routes, especially in the brutally steep terrain of Kunar, weren't there. The team might well have had a detailed E&E plan worked up before going out; they just didn't leave a copy of it with the JOC. This made the CRO's job considerably harder, as the "probability of area," the zone where the lost team might be found, couldn't be narrowed down without that E&E plan, unless they actually made contact with the team.

Determining how they might make contact was made even harder by the fact that the team had apparently not left behind an Equipment Density List, or the list of all serialized gear (including comms and other signaling devices), when they left on the mission. At least it couldn't be found when the CRO requested it at the JOC. Eventually, however, some photographs of the team, taken just before insertion, provided some idea of the equipment they'd taken with them.


(Continues...)

Excerpted from Operation Red Wings by Peter Nealen, SOFREP, First Edition: December 2013. Copyright © 2013 SOFREP, INC.. Excerpted by permission of St. Martin's Press.
All rights reserved. No part of this excerpt may be reproduced or reprinted without permission in writing from the publisher.
Excerpts are provided by Dial-A-Book Inc. solely for the personal use of visitors to this web site.

Meet the Author

PETER NEALEN stepped on the yellow footprints at MCRD San Diego in 2003. A year and a half later, he began training to be a Reconnaissance Marine. After graduating the Basic Reconnaissance Course, he deployed twice to Iraq as a Recon Marine with Bravo Co, 1st Recon Bn, before moving on to what was to become the reconstituted Force Recon Company, I MEF. By the time he finished his active service, he had qualified as a Combatant Diver, Navy/Marine Corps Parachutist, Marine Scout/Sniper, Scout/Sniper Team Leader, and Combat Tracker. He is now a Tactical Tracking Instructor, a freelance writer and contributor for SOFREP.com, and the author of the thrillers Task Force Desperate and Hunting in the Shadows.

BRANDON WEBB is a former U.S. Navy SEAL; his last assignment with the SEALs was Course Manager for the elite SEAL Sniper Course, where he trained some of the most accomplished snipers of the twenty-first century. Webb has received numerous distinguished service awards, including the Presidential Unit Citation and the Navy Commendation Medal with a "V" for "Valor."

SOFREP.com is the #1 site on the Internet for news and information as it relates to the Special Operations and Intelligence community. In a very short time, SOFREP has become a legitimate source of alternative non partisan news media. The editors of SOFREP are from the US military Special Operations and Intelligence communities, and most have over a decade of operational experience that sets them apart from typical journalists.


PETER NEALEN stepped on the yellow footprints at MCRD San Diego in 2003. A year and a half later, he began training to be a Reconnaissance Marine. After graduating the Basic Reconnaissance Course, he deployed twice to Iraq as a Recon Marine with Bravo Co, 1st Recon Bn, before moving on to what was to become the reconstituted Force Recon Company, I MEF. By the time he finished his active service, he had qualified as a Combatant Diver, Navy/Marine Corps Parachutist, Marine Scout/Sniper, Scout/Sniper Team Leader, and Combat Tracker. He is now a Tactical Tracking Instructor, a freelance writer and contributor for SOFREP.com, and the author of the thrillers Task Force Desperate and Hunting in the Shadows.
SOFREP.com is the #1 site on the Internet for news and information as it relates to the Special Operations and Intelligence community. In a very short time, SOFREP has become a legitimate source of alternative non partisan news media. The editors of SOFREP are from the US military Special Operations and Intelligence communities, and most have over a decade of operational experience that sets them apart from typical journalists.
Brandon Webb is a former U.S. Navy SEAL; his last assignment with the SEALs was Course Manager for the elite SEAL Sniper Course, where he was instrumental in developing new curricula that trained some of the most accomplished snipers of the twenty-first century. Webb has received numerous distinguished service awards, including the Presidential Unit Citation and the Navy Commendation Medal with a “V” for “Valor,” for his platoon’s deployment to Afghanistan following the September 11 attacks. He is editor for Military.com’s blog Kit Up, SOFREP’s Editor in Chief, and a frequent national media commentator on snipers and related Special Operations Forces military issues.

Customer Reviews

Average Review:

Write a Review

and post it to your social network

     

Most Helpful Customer Reviews

See all customer reviews >

Operation Red Wings: The Rescue Story Behind Lone Survivor 3.4 out of 5 based on 0 ratings. 19 reviews.
Anonymous More than 1 year ago
A quick read and the first book I've seen available that focuses on the recovery mission, rather than the sole survivor. I'm pleased that their story is being told in greater detail.
Anonymous More than 1 year ago
got this thinking it would be interesting or have anything new to say. nope nope nope. waste of money. it's like 40 pages long and is written at an 8th grade level. it tells nothing new. if you've read "lone survivor" and marcus luttrell's second book you already know everything about what happened. seriously, NOT worth it! ignore, move on, get a real book not this garbage.
Anonymous More than 1 year ago
Disappointed in how short this story was written. Could have been fleshed out 3-4 times more info 8 years after the event. Read it straight thru and left me wanting more.
Numa-1 More than 1 year ago
I was disappointed that this book was so short. Information was good. Thought it was going to be like other Navy Seal stories.
Anonymous More than 1 year ago
Great help with putting the finishing touch to Marcus's book!!!!!
Anonymous More than 1 year ago
Short did cover afew things and raises a few questions as to what the SEALS could have done diffrent.
Anonymous More than 1 year ago
Very disappointed.
Anonymous More than 1 year ago
WillyG127 More than 1 year ago
Short Informative Interesting reading.
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
Anonymous More than 1 year ago
The story from the ones that did the rescue
Anonymous More than 1 year ago
.
Anonymous More than 1 year ago
Somewhat interesting but you have had to read "Sole Survivor" to understand what was going on.
Anonymous More than 1 year ago
Beware, "book" is only 45 pages long. I was disappointed.
Anonymous More than 1 year ago
Kn
Anonymous More than 1 year ago
Hi
Anonymous More than 1 year ago
Hello.