A hard covered hardcopy of this briefing is available for purchase online, click here.

MILNET: U.S. Special Forces

See Additional Reading for Updates  |  Special Operations Aircraft  |  USSCOM
SOCOM's Capstone Concept for Special Operations, 2006 (PDF: 1.2MB)

"To quote Rush Limbaugh, "War is about killing people and breaking things." I have done it, war is not a lot of fun, and intellectually there is little to defend the practice. Notice, I did not say "nothing," I said "little," and it is a damn BIG little.

It is this simple, if they are willing to kill people and break things, and you are not, they win. One ugly fact about human nature is: If someone will not fight for what is theirs, they lose it. This book is about some of the men who choose to be ready to fight. Next to my wife and children, I am more proud of becoming a member of this group of men, then anything else I've done in my life.

Around fourth grade I saw a movie, it was "The Frogmen" with Richard Widmark. When I walked out of that theater, my life's ambition was firmly fixed in every cell of my body. You could have offered me GOD'S job, the presidency, anything, I would have turned it down. I was going to be a United States Navy Frogman.

This book is about the test to become a Frogman, the men I took it with, and the men who gave it to us. We were tested by the BEST, and I thank them. 5" - John Carl Roat, Class 29

So begins the forward for John Carl Roat's new book, CLASS-29 a gritty look at the U.S. Navy Seals training regime.

This section of MILNET is dedicated to the Special Warriors worldwide, whose job is usually hidden by politics, yet plays one of the most important roles in defense of a nation's people.

And while this section may seem a bit critical, realize that our purpose is to lay out the criticisms as they have been expressed, with a fervent hope they have been heeded, and every confidence that years from now we will finally hear more about the actual changes that while obscurred today, will be visible then.

"Under Change"

When the U.S. Special Operations Command began operation in April of 1987, it was clear that a lot of adjustments were needed to make the command an effective force in face of the needs of the rapidly changing world. And while U.S. operation in Kuwait, Saudi Arabia and Iraq proved the services could and did play well together in an all out effort to wage war, undercurrents during special operations conducted probably indicate that the military leaders have not been trained well enough on how to use the potent Special Forces weapon.

However, looking at the U.S. statements on the Special Forces place in the military have become increasingly more positive and rational. For instance, from the 1998 Annual Defense Report:

"SOF ROLES AND MISSIONS

Special operations forces have a dual heritage. They are one of the nation's key penetration and strike forces, able to respond to specialized contingencies across the conflict spectrum with stealth, speed, and precision. They are also warrior-diplomats capable of influencing, advising, training, and conducting operations with foreign forces, officials, and populations. These two distinct missions are complementary, allowing SOF personnel to gain regional expertise and access that enhances their ability to react to any contingency in any region of the world. One of these two generic SOF roles is at the heart of each of the following special operations core missions:

With this current framework in mind, let's look at some inside information on the makeup of the special forces community circa 1996.

Below we present a narrative describing the current U.S. Special Forces structure as relayed to us by a retired Army officer cognizant of the structure as reported in 1996.

USSOCOM is commanded by a 4 star general, ASOC and the other service components are commanded by 3 stars (Lt. General), and their subordinate commands (SF Command, USACAPOC, etc) by 2 stars (Major General). USSOCOM is one of the unified commands which rates a CINC, much like USEUCOM or CENTCOM. Commander USSOCOM is essentially commandless until forces are placed under him. What that means is that Army SF is commanded by Army SOC until they are placed under command of USSOCOM, as they were during Desert Storm. Until then there are regulations, mission, and other activities where the component commands work closely but it isn't real firm.

Under USSOCOM there are component commands. Army Special Operations Command, NAVSPECWAR, etc. These elements exercise direct command and control under normal conditions. They write regs, handle training standards, do strength evaluations, and all the other stuff a command would do. These are normally run by a 3 star (Lt. General).

Under these are various smaller commands. I will discuss the Army as that is what I am most familiar with, but the AF and Navy are similar. SF Command (formerly 1st SOCOM) has command of all SF assets in the continental US. This is a 2 star (Major General) billet. SF Cmd has recently been gutted and all the control passed to ASOC (Army Special Operations Command). There is also US Army Civil Affairs and Psychological Operations Command or USACAPOC. This is considered SOF but no one really believes it. They, along with SF CMD and ASOC are located at Ft. Bragg. Rangers are placed under ASOC but their string is a little different as they are subject to direct tasking by other elements. But they are listed under ASOC.

All of these command relationships are discussed in Joint PUB 3-05, which is unclassified. You can also get it through various books and magazine articles and on the internet under XVIII Corps and Ft. Bragg. There is an ASOC page which has many regs and such to look at.



The Structure

Obviously then there are still separate units within USSOCOM, units that have their origins in the individual services, and should be quite familar to those with interest in special forces:

We, so far, have not been able to discern the disposition of the U.S. Marines Force Recon.

In his book COMMANDOS, Douglas C. Waller describes the makeup of USSOCOM circa 1994:

Today the Special Operations Command, which is headquartered at McDill Air Force base in Tampa, Florida, oversees more than 46,000 soldiers. The Army portion of the command is the largest, with about 30,000 members, and is made up of the famed Green Berets Special Forces teams, the Army Rangers who are crack assault troops, the 160th Special Operations Aviation Regiment, pyschological warfare groups, and civil affairs battalions that repair villages or restore order after a war.

The Navy's contribution to the command are some 5,500 SEALS, and their support forces, which specialize in amphibious commando raids and waterborne operations.

The Air Force allocates 9,500 Air Commandos who provide special infiltration helicopters, transport planes, aerial refueling tankers, and gunships.

Then there are the 1,300 members of the most secret part of the command - the Joint Special Operations Command. The Pentagon refuse to acknowledge that most of its forces even exist; the Army's Delta Force, and the Navy's Seal Team-6 which specialize in counter-terrorism and special commando missions, a Ranger unit for surgical combat assaults and a secret Army and Air Force helicopter force and intelligence unit. 2

It's all quite confusing, so here is a diagram to illustrate the SOCOM and other special ops groups in the U.S.

Lessons to be Learned and Acted Upon

Note: We are not experts on Special Forces thus we are at the mercy of those who have researched the special forces subject. We have tried to confirm much of what we say with others in the special forces community, however, we are not always able to get straight answers...the community is rightfully close mouthed. We invite those in the know to correct any misconceptions we have or indicate that changes in the areas we discuss HAVE indeed been made since the events which highlighted their deficiency. We ARE fans of Special Operations, and feel these folks deserve much better than they have gotten, and hope fervently that their mission capabilities are increasing daily. It is our opinion that times will force a larger dependence on these unique capabilities.

With that, on with the discussion.

The rationale for better supporting the Special Forces capability is the effectiveness of your initial warfighting capability (i.e. in taking out discrete elements of command and control such as key "inbound route" radar sites) as well as supply missions for small units in need of resupply, pathfinders, or other such groups on the ground or leading from the front in the air.

Kelly talks about an opportunity that General Schwartzkopf availed himself of during Desert Storm, a pathfinder mission of Air Commando Pave Low helicopters that lead Apaches to radar sites on the route F-15E Strike Eagles needed to use to lead the attack on Baghdad. While the General's agreement to use the pathfinder method proved to be adequate, it is clear that a lower profile, and perhaps less risky mission (both in terms of assets and time) would have been better served by a typical Air Commando supported Special Forces raid, making use of sabotage ground forces ferried in by Pave Low helicopters.

The General 's reluctance is no indication of any less a capable commander (We really love ya' General), but indicates a high level (i.e. not just one but most higher ranking military leaders) lack of education or perhaps lack of understanding of the nature and capabilities of our special forces units.

Note: Late in 1997, General Hugh Shelton was named the new Chief of the Joint Chiefs of Staff. General Shelton is well versed in the arts of the special warrior having been in Command of U.S. Special Operations. One would assume he brings a new attitude to the Joint Chiefs which should be reflected in any operations that may occur during his tenure. We also hope that his leadership will further the integration of the special operations forces into the overall U.S. Military capability. Congratulations, General!

To illustrate some the changes that seemed necessary as late as 1996, we present the following opinion expressed by a retired Army officer (in an email interview, in 1996):

"My problem with ASOC taking the lions share of C2 over SF is due to the fact that it is NOT an SF-heavy headquarters. Therefore it has no base of expertise to draw on. SF Command has guys and gals with primarily SF experience who have been in groups and worked their way up to the head shed. For instance, at one point, the DCSINT at ASOC had never been in an airborne unit in his entire career. He didn't understand the constraints or requirements an SF unit had in the intel field.

It was primarily a Ranger-oriented (which is to say light infantry) political arrangement. Bad blood. Also, the arrangements in place at that point were not "official" but just done as a favor. No way to do business and highly unprofessional." 1

Note: We have taken some liberty with the direct quote to ensure anonimity of the source.

In looking at the warrior's statements above, as well as noting statements made by Kelly and Waller (see below), it is apparent that the Special Forces command structure must learn from lessons in Grenada, Panama, and Desert Storm. To be specific without going into too much detail (which is better handled by the two authors) the problems are essentially unintentional mission segregation...that is, planning as a unit rather then as part of an overall multi-service, multi-role team. We'll cite one example from Kelly's book that was confirmed in part by Waller.

In Panama, during Operation Just Cause...

"SEALS attacked the Patilla airfield to prevent Noriega from escaping in a jet parked there...one of the SEAL platoons advanced up the field toward the hanger where the jet was kept.

"Suddenly, the SEALS came under murderous fire from a small group of Panamanians hiding in the darkened hanger. Four SEALS fell mortally wounded, and nine others were injured..."

"...Looking back on the incident later, Gary Weikel, commander of the 20th Special Operations Squadron, a Pave Low helicopter unit from Hulbert, was frustrated that he had not been able to have one of his Pave Lows accompany the SEALs, peering ahead and telling them exactly what kind of resistance they could expect to encounter as they approached the hanger." 3

Here's a case of "all someone had to do was ask." Or let the appropriate commander know about that particular mission, and he'd have sent the needed assets along on his own nickel.

However, this particular lesson should have been learned quite awhile ago. Let us hope the command structure within USSOCOM has implemented changes to fix this one.

According to our research, there are a number of things that have needed correction in the last few special operations missions:


Additional Reading
  1. Protected Source, retired U.S. Army officer email communiqu e, Fall of 1995/1996, Copyright 1996, 1997, 1998, Michael G. Crawford and MILNET , all rights reserved.
  2. COMMANDOS, Douglas C. Waller, Copyright 1994, Dell Publishing division of Bantam Doubleday Dell Publishing Group, Inc., 1540 Broadway, New Yo rk, N.Y., 10036, ISBN 0-0440-22046-7.
  3. From a Dark Sky, Orr Kelly, Copyright 1996, published by the Presidio Press, 505 b, San Marin Drive, Suite 300, Novato, CA, 94945-1340, ISBN 0-89141-520-3 (hardcover).
  4. Annual Defense Report, The U.S. Department of State, Chapter 4, "SOF Roles and Missions", (actual document title is "The Annual Report to the President and the Congress, attributed to the Secretary of Defense William S. Cohen, dated 1998).
  5. CLASS-29, Copyright, 1997, 1998, John Carl Roat, forward and sections selected by the author, used with permission.
  6. Special  Operations Forces (SOF) and CIA Paramilitary Operations, Congressional Research Service, 1/5/2005 (PDF 23KB)
  7. All Necessary Mean:  -- Employing CIA Operatives in a Warfighting Role Alongside Special Operations Forces, Colonel Kathryn Stone, U.S. Army War College 4/7/2003 (PDF 137 KB
  8. From Bosnia to Baghdad: The Evolution of U.S. Army Special Forces from 1995-2004 by Armando J. Ramirez, Navy Postgraduate School, September 2004 (PDF 381KB)
  9. Special Operations Glossary - MILNET, 1/8/2005
  10. Capstone Concept for Special Operations, SOCOM, 2006 (MILNET Mirror)




milnet@milnet.com