Kunar Province 2005: Complete Field Guide — Mountains, Pech Valley, Border War & Operation Red Wings // Log 045

Helmand and Kunar belong to the same war, but they do not look like the same battlefield. Kunar sits against Pakistan on Afghanistan’s eastern frontier: steep mountains divided by narrow river valleys, settlements strung along water and roads, and high ground that can dominate movement and communications.

My own Afghanistan service came later and elsewhere, not in Kunar in 2005. As a Royal Welsh mortarman, I cannot pretend this is a place I fought in. What I can do is read the ground through things I understand: observation, line of sight, the weight of ammunition, the difficulty of moving support weapons uphill and the dependence of isolated troops on communications and aviation. The history itself is grounded in the US Marine Corps, Army and Navy records cited below.

At a glance

• Location: eastern Afghanistan on the Pakistan frontier.
• Provincial capital: Asadabad, near the confluence of the Kunar and Pech rivers.
• Ground: steep mountains, narrow valleys, river corridors and limited road networks.
• 2005 campaign: US-led Operation Enduring Freedom, with Marine, Army, special-operations and Afghan partners operating against anti-government networks.
• Key conventional unit in Operation Red Wings: 2nd Battalion, 3rd Marines under Lieutenant Colonel Andrew R. MacMannis.
• Target network: Ahmad Shah’s anti-coalition militia cell in the Sawtalo Sar / Korengal-Shuryek area.
• Strategic timing: operations took place as coalition and Afghan authorities prepared for the 18 September 2005 parliamentary elections.

Where Kunar sits

Kunar’s eastern boundary touches Pakistan, while the Kunar River provides the province’s dominant north-south corridor. Side valleys including the Pech and Korengal cut westward into increasingly steep ground.

What immediately stands out to me is how badly a flat map hides the problem. Two positions that look close can be separated by a river, a deep valley and a ridge that takes hours to cross. Roads and landing zones therefore become disproportionately important.

Mountains, valleys and observation

High ground gives observation but demands effort to reach and sustain. Valleys channel roads, settlements and movement. A force on a valley floor can be watched from the slopes above it, while a small group on high ground may itself become isolated from resupply and reliable radio contact.

Looking at that as a mortarman, the questions come quickly: can the observer see the target area, can the fire unit communicate with him, can the ammunition actually be moved where it is needed, and can aircraft or vehicles reach the position when the situation changes?

In Kunar, the mountains often constrained the answer more than the theoretical range of the equipment.

2005: security before the parliamentary elections

Official Marine history describes 3rd Battalion, 3rd Marines operating in a wider area that included Kunar with the aim of increasing stability before Afghanistan’s parliamentary elections scheduled for 18 September 2005.

During the May–June relief in place and transfer of authority from 3/3 to 2/3, the outgoing battalion handed over the outline of an operation then called Operation Stars. The incoming 2/3 staff developed it further and renamed it Operation Red Wings.

Operation Red Wings was a Marine-led operation

This is the first thing I think needs correcting in the simplified popular version. Red Wings was not originally conceived as an isolated four-man SEAL mission. It was planned by 2nd Battalion, 3rd Marines as a multi-phase operation against anti-coalition activity in the Korengal region.

Marine intelligence identified a relatively small cell led by Ahmad Shah as the focus. The official Marine history describes the pre-operation assessment as fewer than 20 anti-coalition militia.

The Marine concept envisaged reconnaissance followed by a conventional direct-action phase and an outer cordon. Because the operation required aviation from the Army’s 160th Special Operations Aviation Regiment, special-operations ground personnel became central to the opening reconnaissance phase.

Operational structure

• 2nd Battalion, 3rd Marines: conventional force responsible for the wider Red Wings operation; commanded by Lt Col Andrew R. MacMannis.
• Naval Special Warfare reconnaissance element: four-man SEAL team led by Lieutenant Michael P. Murphy, tasked with locating Ahmad Shah.
• 160th Special Operations Aviation Regiment: provided MH-47 aviation support for the special-operations elements.
• Quick-reaction force: Navy SEALs and 160th SOAR soldiers dispatched after Murphy’s team came under attack.
• Opposition: Ahmad Shah and an anti-coalition militia network; US Army history describes Shah as affiliated with Hezb-e Islami Gulbuddin.

I am keeping this as an operational skeleton rather than pretending the public record gives us a perfect aircraft-by-aircraft, platoon-by-platoon picture.

27–28 June: reconnaissance

Murphy’s four-man SEAL team — Murphy, Danny Dietz, Matthew Axelson and Marcus Luttrell — inserted into mountainous terrain to locate Shah and his fighters.

The team was encountered by local herders. After the civilians were released, the SEAL position was compromised and the team was attacked on steep ground.

The enemy-number problem

Red Wings is a good example of why I do not want Field Notes repeating one dramatic number merely because it is familiar.

The official Marine planning history says 2/3 identified Shah’s cell before the operation as fewer than 20 fighters. Murphy’s official Medal of Honor citation later described his team being attacked by 30–40 enemy fighters. Other official Navy summaries have used still larger estimates.

Those figures come from different stages, sources and purposes: one is a pre-operation intelligence estimate of the target cell; another is an estimate of the force involved in a chaotic firefight. I would rather show the disagreement than pretend the evidence produces one undisputed number.

The communications crisis

As the four-man team fought downhill through difficult terrain, communications with higher headquarters were unreliable. Murphy moved from cover to obtain a satellite link and transmit the team’s position and request for immediate assistance.

His later Medal of Honor citation describes him maintaining that exposed position long enough to make the call despite being under fire and wounded.

From my own fire-support background, this is the central practical point of the action. You can have aircraft, reinforcements and enormous technological capacity somewhere in theatre and still be functionally alone if the ground prevents you telling anybody what is happening and where.

The quick-reaction force

An MH-47 Chinook carrying eight Navy SEALs and eight soldiers from the Army’s 160th Special Operations Aviation Regiment was sent toward the contact. The helicopter was struck by a rocket-propelled grenade and crashed, killing all 16 aboard.

Murphy, Dietz and Axelson were killed during the ground fight. Luttrell survived and was later recovered. The loss of the helicopter and three members of the original reconnaissance team made 28 June 2005 one of the deadliest days for US special operations forces up to that point in the Afghanistan war.

Chronology

May–June 2005: 3/3 hands the outline of Operation Stars to incoming 2/3 during the transfer of authority.

June: 2/3 develops the plan, renames it Operation Red Wings and focuses it on Ahmad Shah’s network in the mountainous Korengal region.

27–28 June: Murphy’s four-man SEAL reconnaissance element operates in the objective area.

28 June: local civilians compromise the team; the firefight develops; Murphy establishes contact and requests support.

28 June: the MH-47 carrying the quick-reaction force is shot down, killing all 16 aboard.

28 June: Murphy, Dietz and Axelson are killed during the ground action; Luttrell survives.

2 July: US forces recover Luttrell after he has been assisted and protected by local Afghans.

18 September: Afghanistan holds the parliamentary elections that formed part of the wider security context for Marine operations that summer.

What Red Wings tells me about Kunar

The operation is remembered for courage and loss, but I think its military value as a case study is broader. It shows a conventional battalion trying to shape a small insurgent network; special operations becoming integrated because aviation requirements changed the plan; reconnaissance isolated by terrain; communications becoming decisive; and a rescue force taking exceptional risk because people on the ground needed immediate help.

Above all, it shows why “Afghanistan” is too broad a description of terrain. Compare it with Log 042 — Helmand. Irrigation ditches and compounds there constrained movement horizontally; Kunar’s valleys and ridgelines add a vertical problem that changes observation, radio line of sight, resupply and casualty evacuation.

Beyond Red Wings

Kunar remained heavily contested after June 2005. The province’s border geography, valleys and local armed networks continued to draw US and Afghan forces into difficult operations for years.

I therefore see Red Wings as one episode within a much longer eastern Afghanistan campaign — important, costly and exceptionally well known, but not the whole history of Kunar.

Wear the history

I have linked this article to the Kunar Province 2005 Map T-Shirt — Afghanistan Military Heritage. The design uses the province as the subject rather than turning the Red Wings casualties into a graphic.

Sources & further research

• US Marine Corps History Division — U.S. Marines in Afghanistan anthology — 2/3 planning, Shah-cell estimate and the origins of Operation Red Wings.
• US Army Center of Military History — Operation Enduring Freedom, May 2005–January 2009 — Kunar and Red Wings campaign context.
• US Navy — Michael Murphy biography and Medal of Honor citation.
• Wikimedia Commons — Kunar district map, public domain.
• Wikimedia Commons — Kunar locator map, public domain.

I distinguish the Marine-led Operation Red Wings from the SEAL reconnaissance action inside it, show the discrepancy between pre-operation and firefight estimates of enemy strength, and avoid treating disputed popular retellings as settled fact.