Archive for the 'Aviation' Category
I began writing this during the 11th hour of Joint Warfighter, feeling like I had something of an information hangover. Coffee was having no effect. Concepts and ideas were jumbled into an atemporal mess in my mind–it has been a long couple of conferences.
After the last session a woman walked past me and remarked that the panel was uninformative. I’ve now heard this sentiment twice in the last two days. In terms of this, I can agree that perhaps the actual information given by panelists might not be new, novel, or insightful. But, at best such a reality is decided on a case-by-case basis, since those in the audience have each been privy to different types, amounts, and quality of data. What was not profound to you, could have very well been profound to someone else. In short, the fact that you might not have found anything new in the discussion is irrelevant. But, it does point my thinking towards a new paradigm for conferences is needed.
There is little information that will be given to you in person that could not have been read elsewhere. The volume of data and information availed online is huge–you want to know about the Navy, you can learn most everything online. You can be given nuance from blogs and context from history. However, it is in person is where you learn about what people are thinking, and what they haven’t decided on. You see the person and all those subconscious things that denote what they’re really thinking.
That is the power of panels, that is why it is worth traveling so very far and spending so much: Experience. My Boss says that nothing supplants meeting someone in person, and he’s right. You can share emotion via the Internet, but you cannot truly experience emotion with someone, not even the subtle emotion felt when one is posed with a difficult question–as is often done in panels.
The division between audience and panel needs to be broken down. I struggle to articulate how to do this short of some hippie-esq ‘let’s-circle-our-chairs-and-hold-hands’ nonsense. But, the answer must be in there somewhere between the connectivity enabled by the Internet and being there in person.
AirSea Battle is in trouble. I don’t really know what it is, and even with engaging with the panel today, I still don’t think there is anyone out there who has the whole story. But. What truly troubles me, is that from the question I asked today.
I asked how AirSea Battle Strategy (anyone know what the word ‘battle’ is doing in a strategy?) would affect the tactical level. From what I remember of the answer, almost nothing will change except that there will be more jointness (termed ‘interoperability’ if I remember correctly) and tactical units will be smaller and enabled to mass quickly if a concentration of forces are needed.
Additionally, the design for AirSea is such that it will be layered over the tactical and operational COCOM level. This is where I really get lost–and I need your help to make sense of.
Wasn’t one of the greatest critiques of COIN that it wasn’t a true strategy, but rather a collection of tactics jumbled together and called strategy? If we are overlaying this strategy on top our existing operational and tactical paradigms, aren’t we doing the same thing COIN is accused of? What I understand of strategy is that it is the larger goals and combination of ends, ways and means towards reaching those goals. In attempting to draft a strategy that does not perturb current tactical paradigms, are we creating a strategy that changes nothing?
I really hope we aren’t, but I will need to be convinced we aren’t.
Another thing is that the crowd drawn to such Conferences are more industry than strategist. The questions routinely posed to the panels concerned acquisition more than they did anything else. There’s nothing wrong with this, but I’m not a contractor and so I am more I am more interested in strategy and tactics. What’s more is that because of the majority of the questions it is now hard for me to separate the future tools for implementing AirSea from the strategy itself.
Is AirSea a collection of new capabilities rather than a strategy in its own right?
While I was told that AirSea was not to have any major impact on the tactical level, there is one area in which I do see it having a major impact. AirSea seems to support the notion of acquiring 5+ generation fighters, new comms gear, and making everything stealth. The fielding of such gear will necessarily drive the need for new tactics, and operational models. From what I understand of the F-22, the logistics and maintenance requirement are quite different from having 15s, 16s and 18s downrange. In addition, if the services are to specialize further in niche but vital capabilities, interoperability is going to demand another round of relocating units CONUS for training purposes. If the Army has an Electronic Warfare requirement for a mission the Navy will have to fill that role. But, odds are that EW Squadron is in Northern Virginia, but the Combat Brigade is located in North Carolina or Georgia. For these two units to train together to be fully interoperable, they will need to train together almost constantly. I struggle to see how this will be cost effective, in the age of austerity with sequestration looming.
There is way too much that has gone unsaid regarding AirSea. I appreciate OPSEC needs as much as the next guy. But, AirSea is starting to be discussed widely across strategy and military focused blogs. The Chief of Staff of the Air Force and the Chief of Naval Operations are appearing together to present this strategy to the American People, and the message is thus far garbled. As we’re in the opening stages of the messaging campaign, I can appreciate that there is tweaking that will be done to it towards answering the myriad of questions we all have regarding AirSea. But, it will be a struggle. My sense is that many bloggers, strategists, and journalists are suspect of AirSea. After nearly ten years of coin being vigorously debated, any new strategy will have an uphill battle.
I saw a lot of GOFO’s over the course of Joint Warfighter. Just about as many as are at SHAPE. But, what is important is that I got to listen to them, at some length. General Allen, COMISAF, VTC’d in for an hour (and it was roughly 2100L AFG). Despite weather delays GEN Dempsey was present for an hour. I don’t know how much experience everyone has will trying to get on a GOFO’s schedule. But, average availability is around 15 minutes. An hour is an insane amount of time.
GENs Cartwright, Allen, and Dempsey all spoke without the use of PowerPoint or notes. They were able to navigate through multiple topics, ensuring that key messages were hit and came across as relaxed. They were all polished and impressive. GEN Cartwright had the luxury of no longer being in uniform and so his candor was particularly poignant.
I asked a lot of questions, and the way I worded a lot of questions was not readily understood. I’m pretty sure I had to rephrase every question I asked. It sucks when you’ve got a minute or seven standing behind the mic, listening to the other questions being asked, answers that touch upon the one you’re about to ask, and you’re thinking of a myriad of permutations of how you could ask your question. It’s like roulette, you don’t know when the moderator is going to call on you, and where ever your mind is at when you’re asked is the question that comes out.
*Remember, identify your self and your affiliation.*
One question got me asked if I wanted to work on the Joint Staff, and the answer to that is still an emphatic yes (if you want to see how that went down, watch the video. I won’t elaborate further).
During one such evening, at the USNI Member Event, I turned a corner, and Mary stopped me and introduced me to John Nagl. Yes, that John Nagl. Amazing, right? I love the Naval Institute… For more than just this one instance.
In 2007 I attended my first conference. It was Joint Warfighter, and the day I attended ADM Stavridis gave the keynote at Lunch.
I became aware of the conference while I was underway, and emailed the Institute asking how I could pay for the lunches. I was told that the Institute saves a few tickets for Enlisted members, and that I needn’t worry about paying to attend the luncheon keynote. Because of this, I became aware of ADM Stavridis, and sought out everything I could find of his writing. Eventually I found him on facebook as well, and in 2010 this all came together in enabling me to come work for him at SHAPE. It is directly because of the Naval Institute that I am who I am today.
The last keynote of the Conference was from Google’s Chief Technology Advocate. He presented a number of fascinating things Google does as “hobbies”. Google is all about gathering real world information and organizing and availing that information through the internet. I consider this a noble and laudable goal. What’s more is that they are doing an exceptional job at all of it.
However, such a goal is fraught with challenges and disturbing implications. Arthur C. Clark has some very good words to this point
The Information Age offers much to mankind, and I would like to think that we will rise to the challenges it presents. But it is vital to remember that information — in the sense of raw data — is not knowledge, that knowledge is not wisdom, and that wisdom is not foresight. But information is the first essential step to all of these.
Google gets this, and they are actively engaged in finding the right answers to such dilemmas. They seek out expert advice from guys like GEN Colin Powell. They seek to understand the implications of the capabilities and technologies they develop–they seek to build wisdom as much as they compile information.
I think it is important for this conversation to take place, as well as for it to be transparent and done in public. If Google can develop technologies that have significant security implications, it does us no good to bury this fact, as it denies us the ability to develop the wisdom required to understand our new abilities. Further more, if Google can do it, then eventually anyone could do it, being quiet about it won’t prevent this from happening.
All Around It was an excellent conference, I was especially pleased to see so many of our Allies stationed at Allied Command Transformation in attendance. Seeing French, British, German, and Spanish uniforms in the crowd made me feel a little bit like I was back home at SHAPE. Going forward, I think it would be a good thing to try to engage with our Allies more in such conferences. With more focus on Asia being demanded, deepening engagement and ties with our European Allies in other ways is important. An easy, and smart way to do this is with conferences like Joint Warfighter. Plus, JCWC has a nice ring to it (Joint-Combined Warfighter Conference).
The May 2012 Proceedings reached me while I was on some active duty facilitating some war games at NDU. It is my second-favorite Proceedings issue of the year. It is the Naval Review issue. Contained therein is every Navy Flag Officer currently serving. Three hundred thirty one in total, according to USNI.
There has been discussion aplenty here and elsewhere regarding the absurdity and wastefulness of having 1.17 Admirals for EACH SHIP in the United States Navy. While the profligate growth of stars in the Navy’s senior ranks may have seemed like a good idea at the time, it is unconscionable in the current environment of extreme fiscal constraint, especially as the Sea Service is hemorrhaging highly qualified E-6 Sailors one hitch short of retirement eligibility. It is well past time to cull the Flag herd. And here’s one way forward (Hint: Simply shouting “you CAN’T!” and “we NEED!” does not constitute a counter-argument).
Among Rear Admirals, and Rear Admirals, Lower Half, there are 62 positions that are Deputy, Vice, or Assistant positions. Fill each with a Captain, breveted temporarily one or two ranks while serving in those billets. A successful tour in one of those positions would be a career enhancer for a Captain, increasing chances for permanent promotion.
Among Vice Admirals, there are ten positions that are Deputy or Assistant positions. Reduce those positions to two star rank. Reduce the billet of VCNO from four stars to three. Ditto Fleet Forces Command. Next time NDU is a Navy fill, do so with a Rear Admiral instead of a Vice Admiral. The Naval War College gets a Rear Admiral, Lower Half.
And have a long look at the Joint Billets that swell the Navy’s senior officer structure. Pursuant to meaningfully re-evaluating Goldwater-Nichols, which is now in its 27th year.
Implement this concept, and you have at least a 20% reduction of Navy Flag Officers. Between 65 and 70, depending on which path one takes regarding force structure tied up in Joint assignments. It’s a start. The path we are on gives this nation a Navy of 200 ships and 400 Admirals before the end of the next decade. That ain’t no way to run a railroad. Or win a war at sea.
Yes, I will have a similar look at the Marine Corps in the near future.
This is my first post, so I want to start off with a decent hook. Something interesting. How about this:
All three of my kids have flight time in Marine Corps aircraft. My oldest daughter, almost 7 years old, has 110.9 total hours, all in a Cobra. 36.4 of those are from night vision goggle flights (22.6 of them under low light conditions, thank you very much), and she was along for the ride on my Night Systems Instructor (NSI) check flight, since I was 4 months pregnant when I completed the qualification. She used to kick like crazy in there when we’d shoot the 20mm. Liked the sound the 2.75-inch rockets made coming off, too.
My second daughter, now 3 years old, has fewer hours. She only has 25.4 hours in the Cobra, 4.5 of them on NVGs (but all 4.5 under low light conditions), since by then we knew that Cobra pilots definitely were not allowed to fly pregnant (OPNAV was not clear, and as there had never been a pregnant Cobra pilot before, we made our best guess the first time). I waited until the end of my first trimester to ground myself, since that’s the traditionally “safer” time to tell people that you are pregnant.
My son, now 18 months, didn’t get to fly in a Cobra (poor dude), but he does have 30.7 hours in a King Air (UC-12B). None on goggles, since they don’t do that stuff. And he never seemed particularly impressed by the aircraft, since he didn’t do extra kicking or shifting to let me know.
But I digress. This is my first post as a USNI blogger-person, so maybe I should back up a bit. Chronologically speaking. While looking through some of the USNI blog entries a few months ago, I noticed something interesting. Or rather, I noticed—in an interested way—that something was lacking. There’s an amazing breadth of experience and knowledge available there, and the subjects addressed are broad and relevant. But I didn’t see anything out there remotely reminiscent of my experiences in the Marine Corps or at USNA. And considering it’s been 14 years since I graduated and got commissioned this month (plus the 4 years by the bay), that is…interesting. I know, in some eyes having only 14 years in makes me a baby. Which is wonderful, because these days I’m feeling pretty old. But at the same time, young women and men are signing up for the Navy or Marine Corps today, and they could have similar decisions to make. My choices and my story could help them. And with greater numbers of women joining the military, experiences like mine will become more common. Which makes this stuff…relevant.
In case the bio didn’t show up, here’s my story:
I’m a USNA grad, class of 1998. Graduated, got a commission in the Marine Corps, and set off for TBS and flight school. Winged in February 2001, selecting West Coast Cobras, since East Coast (New River) skid squadrons weren’t accepting women yet (I was quite happy to go to Camp Pendleton anyway, but found the restriction interesting. As in, “Really? You’re going to force me to go to Southern California, and keep me out of Jacksonville, NC? OK, twist my arm…”). Went through SERE school and the Cobra FRS, and—after my checkride from the FRS got delayed, since it was originally scheduled for September 11, 2001—checked into HMLA-369.
I was the third female Marine to fly the Cobra (I think) and the first in my squadron (the only one for most of my time there). This led to some great stories—mostly funny ones, a few disgusting ones, and one or two downright wrong ones. It was a familiar role after USNA and TBS. And to be honest, men are just as catty as women, only they are less honest about their cattiness. I went to an all-girls Catholic high school for all four years, and the only real difference between my four years there and my four years at USNA was the smell in the hallways.
At 369, I deployed three times (SE Asia/31st MEU, then Iraq, and another Thirty-worst MEU again), went on a bunch of dets, made some lifelong, amazing friends, served under two fascinating and inspiring commanding officers, and worked in Operations for the majority of my time there. Loved it, loved it, loved it. I miss it terribly (especially these days as I fly a desk in the Pentagon part-time and run around with three little kids the rest of the time).
Pre-flight school, back in 1999, I married my husband, a USMC infantry officer. We did NOT want kids. Of the first 9 years of our marriage, we lived in the same state for about 3 of them. In my mind, kids = wasted career. We were happy being childless and laughed at the idea of having kids, and how it would “ruin” things. Why would we ever want to have kids, right? Anyone with kids is laughing at us and the stupidity of that comment.
But…as it turned out, we had three kids, who are now aged almost 7, 3, and 18 months. And instead of still flying, still deploying, and staying on active duty for 20 or more years, I find myself a Reservist with three little kids, not flying at all, and driving myself crazy. This was NOT the original plan. It took me three years to accept the fact that life had changed (in what was a wonderful way, of course, but I didn’t see it like that at first). And I don’t know that I’ve really accepted it yet.
I don’t regret the choice to leave active duty for the Reserves (when my oldest was 2 ½ years old), but it shouldn’t have been the only viable option. I had nearly ten years in at the time, advanced qualifications in the aircraft, and the desire to keep doing it all. For a long, long time. But single-parenting through most of my oldest daughter’s first two years of life showed that I could not do it all, at least not without something coming off of the track. I went kicking and screaming from active duty, but did not see any other way, since I was failing at parenting and failing at being a Marine Corps officer/pilot. And that is one big reason that the services lose experienced women and men at a certain point in their lives and careers. But is it necessary?
This seems like a good forum to encourage dialogue and a sharing of ideas and experiences. Professionally. In this vein, I want to tell my story, as a pilot, a mother, a veteran, a Reservist, and also a Marine spouse (which is also growing more and more common these days). I want to ask a bunch of questions, maybe get a couple good ideas, and try to focus some attention on what will be a growing issue in the military.
Comments are encouraged. I can only tell my story, and hopefully that will encourage greater dialogue on the topic(s). But with women being allowed into more fields, the ongoing debate about women in combat (which I have some strong feelings and thoughts about), and about a million other things going on that are downright fascinating, these topics are relevant.
Plus, I can tell some good stories.
Lots of traffic over at Salamander’s Place, and at POGO, regarding continued problems with the Littoral Combat Ship program. I have commented on this struggling and costly program several times, and will refrain from doing so here, with the exception of a paraphrase of a comment that Sid made at Sal’s:
The Littoral Combat Ship is not built to survive combat in the littorals.
LCS was constructed to house weapons “modules” that do not exist, and in fact, consist largely of the theoretical.
Speed was going to be the capability which allowed LCS to avoid trouble. And now that single capability is negated by the fragility of the design that was required to reach those speeds.
Summed up thus:
IT (IS A) COMBAT SEAFRAME THAT CANNOT PERFORM ITS MISSION IN COMBAT THAT IT CANNOT BE EMPLOYED IN while RELYING ON SPEED THAT IT CANNOT MAKE, (THAT) WILL COMPRISE THE MAJORITY OF THE SURFACE COMBATANT FLEET OF THE US NAVY…
Someone, ANYONE, with a wide stripe on a sleeve tell us that he is wrong. And WHY he is wrong.
Here and elsewhere much has been written of the Doolittle raid, from the bookstand to Hollywood and the curriculum of War Colleges the world over. Coming fast on the heels of the stunning blows barely four months prior a malevolent arc of destruction and defeat stretching from Pearl Harbor back across the Pacific to the Philippines and the rest of Asia, the raid was, no, is emblematic of the American fighting spirit and ability to improvise on the fly and conduct improbable operations on the field of battle. From John Paul Jones’ raid on the English port of Whitehaven to putting a man on the moon barely a decade after the first tentative attempts to launch a satellite, our history has been replete with no small number of audacious operations. Of all these though, the Doolittle Raid is probably the best known and yet, there are aspects that still remain shadowed. To be successful required meticulous, but rapid planning. In short order an idea, germinated in Washington had to be planned, practiced, logistically provided for and executed in an air of ironclad secrecy. This in an age where “netcentric” and “JOPES” weren’t even a mirage on the horizon. As always, it was having the right people in place to do the heavy lifting behind the scenes that laid the groundwork for success. In the case of the Doolittle raid, there were four naval officers, one you have heard of, but two or three others you just as likely haven’t, who played key roles in the planning of the raid.
CAPT Francis S. Lowe: A member of the USNA class of 1915, a 1926 Naval War College graduate, a submariner, then-CAPT Low was assigned as Operations Officer on ADM King’s staff at CINCLANTFLT, and later followed him to Washington when King became CINC, US Fleet and CNO. Among his duties as Operations Officer was overseeing the ASW operations of the fleet, and it was in this capacity that he flew to Norfolk, VA in January 1942 to review the status of the USS Hornet CV-8. Chambers Field (the original, now part of the heliport today) had the outline of an aircraft carrier painted on it for FCLP (Field Carrier Landing Practice) which is used to maintain some of the skills necessary to conduct flight operations off an aircraft carrier – to include launching with a minimum of deck space available. It was during this trip that he observed some B-25s making passes at that outline in a mock attack and realized that twin-engine aircraft would fit on the deck of a carrier and wondered if the B-25s would be able to take off from a carrier. Upon his return to Washington, he mentioned his idea to the Admiral who thought it had merit as did General “Hap” Arnold (USAAF).
CAPT Donald Duncan: A 1917 graduate of the USNA, and holder of a MS in Radio Engineering from Harvard as well as a Naval Postgraduate school grad, then CAPT Duncan, a naval aviator with extensive carrier experience, was King’s Air Operations Officer and the one to whom it fell to evaluate the possible use of the B-25 from a carrier. In 30 handwritten pages, he outlined all the necessary details and precepts for a successful strike in a feasibility study forwarded to King and Arnold recommending the use of B-25s and oversaw the proof of concept flight that showed the Mitchell bombers could indeed, launch from a carrier deck. Subsequently he also oversaw the necessary logistical and administrative details needed to get the bombers to and onboard the Hornet at Alameda Naval Station.
LT Henry L. Miller: A 1934 graduate from the Naval Academy and native of Fairbanks, Alaska, then-LT Miller was a designated Naval Aviator. A multi-engine pilot and graduate of the Bombardier course at Sandia base and the All Weather course at Corpus Christi, he was serving as a flight instructor and Personnel Officer at Ellyson Field, FLA when tasked to train Doolittle’s pilots on takeoff techniques from the limited deck of a carrier. Shifting operations to Pierce Field (one of the outlying fields at Eglin AB – literally out in the sticks) LT Miller not only trained the raiders on take off techniques, but was also principle in teaching the finer points of shipboard life in general and accompanied them as operations shifted to Sacramento, CA and all the way to launch from the Hornet, 700 nm from Tokyo.
LT Stephen Jurika: Born in Los Angeles while his parents were visiting there, then LT Jurika grew up in the Philippines where his dad owned a number of plantations. He graduated from the Naval Academy in 1933 and served as a naval attache at the American Embassy in Tokyo before World War II. As the USS Hornet Association’s website notes, the plot thickens from there:
Being fluent in the Japanese language, he was able to collect significant information about the Japanese military and industrial capabilities, even photographing many of their sensitive sites. From August 1941 until October 1941, he reported to the Director of Naval Intelligence, providing a great deal of information about the Japanese threat, including specific information about the new “Zero” high performance fighter. In October 1941, he was involved with the commissioning of USS Hornet (CV-8), initially serving as the Flight Deck and Intelligence Officer. In mid-January 1942, he consulted to Captain Donald Duncan who was then conducting a feasibility study about launching a bombing raid against Tokyo. Lt Jurika provided a great deal of information about the types and locations of high priority industrial and military targets. Two months later, when the Hornet was carrying the Doolittle Raiders to their launch point, Lt Jurika spent many hours briefing them on the locations of the high value targets and optimum flight routes.
He also had a personal contribution to make to the raid:
One bomb was decorated with Japanese medals, donated by Navy Lieutenant Stephen Jurika, who had received them during pre-war naval attaché service and now wished to pointedly return them to a hostile government. (NHHC)
Each officer would go on to serve with distinction in the war and afterwards. CAPT Low took command of the cruiser Wichita and saw action from Africa to the Pacific. Returning to the US he was Chief of Staff for Tenth Fleet, running ASW operations in the Atlantic theater of operations and finished the war as Cruiser Division SIXTEEN supporting the invasion at Okinawa and strikes against the Japanese homeland. After the war he was in charge of the surrender and neutralization of all Japanese Naval installations in Korea and reported in November as Commander Destroyers Pacific Fleet, serving until March 1947, when, upon his advancement to Vice Admiral, he was given command of the Service Force, US Pacific Fleet. In November 1949 he returned to the Navy Department to conduct a special survey of the Navy’s anti-submarine program, and in February 1950 was designated Deputy Chief of Naval Operations (Logistics). He continued duty in that capacity until May 1953, when he became Commander, Western Sea Frontier, and Commander Pacific Reserve Fleet. He served as such until relieved of all active duty pending his retirement, effective 1 July 1956. He was advanced to Admiral on the basis of combat awards.
CAPT Duncan would become the first CO of the lead ship of the Essex class CV and see action in the Marcus Islands and Wake. From here he would serve as CARDIV commander, CINCPACFLT Chief of Staff, DCN(Air) and finally DCNO before retiring in 1957. Following the Doolittle raid, LT Miller commanded an Air Group on board USS Princeton (CVL-23), and during the remainder of the war he had command of Air Group SIX stationed on board USS Hancock (CV-19). Following the war he served in the Navy Department until July 1948, first assigned to writing Air Operations Instructions, later serving as Executive Officer, Air Branch, Office of Naval Research. For two years he served as Public Information Officer on the Staff of Commander in Chief, Atlantic Fleet, and from June 1950 to August 1952 served successively as Executive Officer of Composite Squadron SEVEN, and of USS Leyte (CV-32). Graduating from the Industrial College of the Armed Forces in 1953 and, he reported for duty in the Strategic Plans Division at the Office of the Chief of Naval Operation. Subsequent assignments saw him in command of USS Hancock, commander of CARDIV 15, and later, off Vietnam, CARDIV 3/Task Force 77/7th Fleet Carrier Strike Force. On July 22, 1959 Miller was commissioned a Rear Admiral, and was appointed Chief of Staff and Aide to the Commander Naval Air Force, Pacific. Rear Admiral Henry Louis Miller commanded Carrier Division FIFTEEN, which is the Anti-Submarine Hunter-Killer Task Group from May 1961 to June 1962. Admiral Miller also served as Assistant Chief of Staff for Plans, Joint Staff, Commander in Chief, Pacific, during the time when the turmoil in South East Asia escalated. He then assumed command of Carrier Division THREE, a Heavy Attack Carrier Task Group, and at the same time he took command of Task Force, SEVENTY-SEVEN, and the Carrier Striking Force of the SEVENTH FLEET and in this capacity, took the first nuclear power Task Force into combat with the enemy in Vietnam.
LT Jurika followed the Doolittle raid with an assignment to COMAIRSOLS on Guadalcanal as Air Ops officer, a tour which included a special operation that earned him a Legion of Merit. Returning briefly Stateside as a torpedo instructor, he returned to sea as navigator on the USS Franklin (CV-13) and in this capacity, was awarded the Navy Cross for his actions on the bridge in the wake of the attack and devastating explosions and damage that almost sank Franklin. After the war and a variety of foreign service tours, retired and began a career as a professor at Stanford University and the Naval Postgraduate School.
Note: The oral histories of several of the principals involved with the Doolittle raid and battle of Midway – including that of Stephen Jurika, are available through the Naval Institute via the ‘print-on-demand’ program. I think the advent of the 70th anniversary of the Doolittle Raid and the upcoming Battle of Midway observances would be a great time for the Naval Institue Press, in line with the Strategic Plan released at last week’s Annual Membership meeting, to announce it was making e-book versions available of these histories. w/r, SJS
Let’s get this list going.
As an observation and a nod, not a criticism (of course) of our Vice President Joe Biden – who observed that, “You can go back 500 years. You cannot find a more audacious plan. Never knowing for certain. We never had more than a 48 percent probability that he was there.”
Because this will be a list, compiled into one blog post, whatever you put in the comments (respectfully and to the point of the post) we will incorporate into the post – then delete. Please submit your comments to us here or via firstname.lastname@example.org or give us your submissions via Twitter or Facebook . And when the first 500 hits it, [UPDATE]: WE WILL MAKE A BRACKET COMPETITION.
Give us your best of the best who were audacious – winners or losers – those who dared. We will update the list daily, no repeats – so dig deep when your favorite has already been mentioned.
Listed in order of submission and raw commentary (and without attribution and to protect the innocent):
500. SEAL mission per Vice President Joe Biden: Audacious on the part of our Commander in Chief, President Obama.
499. Japanese attack on Pearl was an Orange/Blue war-gamer exercise 6 or 7 years before 1941.
498. Entebbe, anyone? Or one might even argue that the raid on Bin Laden’s compound would not have been possible without the lessons learned from the even more audacious (if ultimately unsuccessful) plan of Operation Eagle Claw.
497. Lets start early. 1519 Hernan Cortez landed 600 Spaniards and about a dozen horses at Cozumel. He BURNED HIS SHIPS so there was no way to escape, and he and his men had to fight to the death. He led his men to destroy the entire Aztec Empire something that no invader had done in over 6 centuries. In the process he actually convinced the Aztecs that he was THEIR GOD.
496. Henry V at Agincourt – Nope, too early.
496. (Do-over) ”Kedging“- How USS Constitution Sailors evaded 170 guns of HMS Africa, Shannon, Belvidera & Aeolus!
Dare I say George Washington before the Battle of Trenton? Christmas Day 1776.
George Washington Crosses the Delaware in the dark of night to attack the British in Trenton.
For me there is one and only one #1. Without it an army driffs away, an idea dies, a piece of paper signed at the greatest personal risk becomes meaningless. General George Washington’s decision to attack Trenton on the morning after Christmas 1776 with a night march of impossible proportions couples not only audaciousness, but the greatest risk. For me it is the single most important moment without even a close second in American history, and for the idea of freedom as the world knows it today, possibly. My own telling here: http://
494, Eben Emael and the raid to free Mussolini
493. CDR “Red” Ramage, USS Parche, Pacific, 1944: as commanding officer of the U.S.S. Parche http://
492. Col Robin Olds, Operation BOLO Mig Sweep, North Vietnam, 1967 http://user.icx.net/
491. Doolittle Raid Doolittle Raid, 1942…(while a japanese radio broadcast stated, almost to the moment of the attack, how Japan would never be attacked, with air raid sirens suddenly going off-a “baghdad bob” moment)…which in turn, caused grave consternation, and thus triggered rash action by the Imperial Japanese Navy, resulting in catastrophic loss at Midway, with which they would lose their offensive initiative for the remainder of the war…despite efforts to regain it at Guadalcanal and others.
490. Admiral David Farragut leads his ships into Mobile Bay, 1864. Approaching the mine field laid by the Confederates the USS Tecumseh (first in the battle line) hit a mine and exploded, shocking the entire fleet. The USS Brooklyn stopped dead in the water, and the Captain asked the Admiral for instructions. Farragut ordered his ship, the Hartford, to steam around the Brooklyn and take the lead, signaling his forces “Damn the Torpedoes…Full speed ahead!” The entire column of 14 ships passed safely through the mine field and took Mobile.
489. April 22, 1778. At 11 p.m. on this day in 1778, Commander John Paul Jones leads a small detachment of two boats from his ship, the USS Ranger, to raid the shallow port at Whitehaven, England, where, by his own account, 400 British merchant ships are anchored.
488. Captain Charles Stewart of USS Constitution taking on two warships simultaneously in February 1815.
487. Though unsuccessful, Desert One was audacious.
486. How USS Constitution Sailors evaded 170 guns of HMS Africa, Shannon, Belvidera & Aeolus!
485. Berlin Airlift
482. Market Garden (for a not-so-successful example)
481.Camp Century Greenland, 1959-1966.http://
480. Manstein Plan, France 1940 (replaced the original von Schlieffen plan), bait the allies into the low countries, cut them in half, and take the entire region in 6 weeks.
479. 1588, english channel, England vs Spain. English ships, more maneuverable, chipped away at the snds of the Spanish Armada’s ships (arranged in an arcing format) instead of taking them head-on. Forced the Spanish ships into disorder, and over a few days, whittled them down to near-insignificance…forc
Audacious to say the least.
478. 1970, USAF and Army Special operations crash land an HH-3 helicopter in the middle of the Son Tay prison complex in North Vietnam in an attempt to rescue 65 American POWs. The operation is carried out perfectly, but the prisoners were moved a few months earlier to different accommodations.
477. Operation Dynamo, the “miracle of Dunkirk” in WW2
476. Battle of the River Plate, 1939. One of the greatest psyche-outs in naval annals. Spee literally pulverized UK’s Ajax, Achillies(NZ), and Exeter. One’s fire control was out, another’s main gunnery was out, the third was mauled but intact. GS was also damaged, and thinking the UKs 3 were still coming after him (most would’ve broke off by then), he made for Montevideo…where he was told to leave within 72hours. GS was relatively intact, despite some damage, and could have re-engaged. Thinking there were more heavies coming (via the radio traffic of the 3, who remained, even though they would have been cut to pieces had the GS came out to face them), Capt Langsdorf scuttled the Graf Spee without a battle. 3 days later he shot himself. Sheer audacity, and well executed…using nothing but guile.(the truly genius strategist finds ways to war without battle-Sun Tzu)
475. The bayonet charge of Joshua Chamberlain on July 2, 1863 at Little Round Top during the Gettysburg battle.
474. Bridge at Dong Ha
473. 1918 Battle of Belleau Wood
472. June 1995 rescue of Scott O’Grady
471. Battle of the Bulge, with the Germans scraping up enough armor, soldiers and fuel to give the US and Allied Armies a real good scare
470. USS ENGLAND taking the bull by the horns, and sinking 6 Japanese subs in less than 2 weeks.
Secretary Mabus, CNO Admiral Greenert, and Marine Commandant General Amos,
Suggest you read an effective, efficient explanation of the ramifications of a really bad idea over at Tom Ricks’ Foreign Policy blog.
I wonder if the enhancement in personal readiness occasioned by breathalyzers will be worth the trade-off in flagging morale, professional insult, and perceptions of detached, out of touch senior leadership…
This is among the most paternalistic, professionally insulting concepts I’ve seen in all my years of service, and I’m not sure I will submit. Yes, I know my options, and I just may exercise them and go right over the side the first time the duty blowmeister shoves a plastic tube in my face and treats me like a drunk driver for daring to report for duty. To the CNO, CMC, CMC of the Navy, and SgtMaj of the Marine Corps, here’s my question: At what point will one of you four exercise your duty to tell the Secretary of the Navy, “Hey, Boss, WTF, over?” and that he really ought to fire whichever clown came up with this idea (?)
And, an additional observation:
Leaders exercising their solemn duty to junior sailors and Marines, who have even a modicum of intuition about their charges, can figure out who is sucking the worm out of the bottle every night without resorting to the extraordinary insulting and distrustful measure of breathalyzing every shipmate who steps across the brow and every Marine who marches into a gun park.
Please read the rest. There are some additional and very cogent points about the damage this exceedingly unwise little contrivance will cause.
Trust, like loyalty, is very much a two-way street. Trust is also a funny thing. Like an ornate hand-painted vase, it takes great dedication and hard work, and not a little inspiration, to create; yet just one instance of careless handling can shatter it into a thousand pieces. Even if one was so inclined to spend the time required to glue all of those pieces back together, the result is never quite nearly the same.
These Sailors and Marines have stood watch and fought two wars in the last decade. They have sacrificed, fought, bled, and died doing their duty. They are magnificent. They have given you, all of you, far more reasons for you to trust them than you have for them to trust you. The stars on the collar, the wide stripes on the sleeve, the nameplate on the big desk, those things are purely ornamental if you don’t earn the trust and respect of those you lead each day anew. Just as every Second Lieutenant and Ensign, every Chief Petty Officer and Gunnery Sergeant must do. Every day.
You are marching quick-time toward shattering that trust and breaching the loyalty of those you lead. The reasons that make this entire course of action seem like a good idea are inconsequential compared to the negative consequences of implementing this professionally insulting and terribly misguided policy. Your junior leaders, commissioned and non-commissioned, are telling you so, and loudly, even if the Generals and Admirals haven’t the courage to do so.
Good leaders listen, instead of ignoring sage advice. Now is just such a time.
h/t to LtCol P and to “John Paul Lejeune”
Tomorrow, 11 March 2012, the storied USS Enterprise (CVN-65) will leave home port to ply the world’s oceans for the 22nd, and last time. As she is about to head toward Middle Eastern waters, the Associated Press published a nice piece about her, and the challenges that her crew of 4,000 face in keeping a ship that is older than most of their parents operating and ready.
Since SWMBO reminded me how expensive picture books were to print, I figured I would take advantage of this newfangled internet thing to post some pictures of the Big E, and relate some things about her 52 years in service. A good deal of these pictures will come from familiar places, such as NavSource.org, and DANFS, as well as some others included from various spots.
It is staggering to think of a ship 52 years in commission. How long is that? Here are some facts about Enterprise and her history:
The sitting Secretary of the Navy, William B. Franke, whose wife christened CVAN-65, had been born in 1894. He lived to be 85, and still died 33 years ago.
Enterprise’s first CO, Captain Vincent P. de Poix, Annapolis ’39, had been a World War II aviator, and is still with us at 95!
In February of 1962, Enterprise stood by to assist with the recovery of the first American to orbit the Earth, LtCol John Glenn, USMC, in Mercury 6.
Enterprise was a part of the Second Fleet force that established the “Naval quarantine” of Cuba during the Cuban Missile Crisis, October, 1962.
Enterprise was the first nuclear powered warship ever to operate in a combat zone, off Vietnam, December, 1965.
Enterprise remains the longest warship ever to put to sea at 1,102 feet, 2 inches.
On May 24th, 2011, a Navy F/A-18F Super Hornet of VFA-11 made arrested landing number 400,000 on Enterprise.
When Enterprise joined the fleet in October of 1961, she was one of 24 carriers, and the only nuclear-powered carrier, in a Navy of 870 ships. Today she is one of 11 nuclear-powered carriers in a Navy of 285 ships.
Enterprise deployed to Vietnam six times, Operation SOUTHERN WATCH three times, Operation ENDURING FREEDOM four times (about to be five), and Operation IRAQI FREEDOM three times. Her CO, Captain William Hamilton, was not yet three years old when Enterprise was commissioned, her XO would not be born for another five years.
Best of luck to all the Officers and Sailors who crew this venerable old warship. She carries a glorious name proudly. One day you can tell your grandchildren you sailed on her. When you return, she will pass from the Navy list and into history.
But perhaps her name can live on with CVN-80. There always should be an Enterprise in the US Navy.
Many of the decision points in our lives can be sorted into four specific guiding questions. They provide an excellent means of evaluating our decision, our choices, and most effectively melding what we need with what we can afford. The questions can correspondingly apply to selecting a college, or to prospective employment. They work well when designing and building a house, or buying a car. Purchasing insurance. Even when deciding on marriage. What are these four questions?
- What can I live with?
- What can I live without?
- What can’t I live with?
- What can’t I live without?
Simple questions, really. But their answers require a good deal of thought.
They are also questions that should be asked when developing National Security Strategy, and its subcomponent, National Military Strategy. Those questions need to be asked as we determine the size, posture, and capability of our military and its supporting industrial base. Those four straightforward questions must eventually be asked of our Navy at a number of different levels.
The first is to address the size and capabilities/capacity of our Navy. What can we reasonably expect our Navy to do? For how long? In how many places at once? Hard questions that demand realistic and informed discussion. Currently, we have a Cooperative Strategy that cannot be executed under any but the most benign conditions on the world’s oceans. How long are we going to continue to make promises to ourselves and our allies that we cannot keep? What are we willing to have the courage to say openly that we cannot do with current capabilities?
Related to the above queries, but not identical, is to ask how big will our Navy be. Numbers tossed around in the previous decade and a half range anywhere from 340 down to the current 285-ish. (The disparity of 55 ships is equivalent to the strength of two Royal Navies, so it isn’t trivial.) Yet, the budget realities and the cuts made to shipbuilding projections point to a number closer to 260, if not lower, by the end of the decade. While it is true that 260 modern warships have tremendous combat power, it is also axiomatic that they cannot have the same global forward presence that 340 warships, some with somewhat less capability perhaps, can have.
The next level at which the four guiding questions need to be asked is the level of ship design and shipbuilding. This cannot be done in isolation, but must be informed by serious and exhaustive discussion regarding what Admiral Zumwalt called the “high-low mix”. How many capital ships of extensive capability are required for our missions, and how many of lesser but more appropriate capabilities does the Navy need? It is this level in particular that the Navy seems unable, in fact abjectly refuses, to answer. Not every ship needs every capability. When we believe it does, we end up with multi-BILLION dollar platforms chasing skiffs off the Horn of Africa, and a fleet so expensive that the risking of a single unit for a dangerous but necessary mission becomes all but unacceptable.
There has been much discussion of those issues in the pages of Proceedings, and among Naval Officers and strategic thinkers, Naval enthusiasts, and the legions of the Great Unwashed who blog the intertubes. One of the more interesting remarks in this regard was an assertion, perhaps rightly, that with its current philosophy and unwillingness to address the high-low question, the Navy is incapable of building a platform in between the under-gunned and unsurvivable LCS and an Aegis-capable Arleigh Burke.
So the question of the mix is not new. Captain Jerry Hendrix wrote of it with his Buy Fords, not Ferraris in the April 2009 Proceedings. Discussion at the last three USNI/AFCEA West conferences was rich with commentary. In this month’s Proceedings, Norman Polmar evokes Plan URR with his A Paradigm Shift, asking whether a much larger number of STOVL carriers would be more effective than a small and likely shrinking number of $15 billion dollar CVNs. (A hat-tip woulda been nice!) When I asked the question of high-low mix at this year’s Shipbuilding Panel in San Diego, the panelists all but admitted that there hadn’t been much discussion on the subject, and that the goal was still 313 ships.
The final level at which those four questions above need to be asked is in the experimentation with “Optimal Manning”. Anyone who even occasionally glances at this site knows my aversion to reducing crews of ANY equipment or weapon platform below what is required to drive, fight, fix, and maintain. The biggest decision for the Navy has to be defining “optimal”, and to whom the term applies. Is it “optimal” for the Navy leadership to show reduced manpower costs to our Congresscritters while our warships continue to experience serious maintenance issues and are not mission capable? Do we want crews so thin that there is only time for eating, sleeping, and operating? No time for training in the myriad skills and requirements of basic seamanship, damage control, or weapons proficiency? Do we want crews that have no ability to absorb any casualties without compromise of mission?
Again, difficult questions. Senior Navy leadership, and senior Defense Department officials, are going to have to make some hard calls. The answer is not to exhort our Sailors to do “more with less”. That bit of self-delusional platitude is the path to a head-on collision with the realities of combat, with usually catastrophic results.
The discussions must be informed, serious, and realistic. And they need to be soon. In May, USNI/AFCEA will be holding the Joint Warfighting Conference in Virginia Beach. The theme is “Joint and Coalition Forces; The Inflection Point. What to Hold and What to Fold?” Without these discussions, commentary will again be nearly blind speculation, akin to a hand of five-card stud, but deciding which cards to keep and which to discard without looking at them. If we continue to insist on playing our cards in such a way, we ought not to be surprised if the betting patterns of our potential adversaries change accordingly.
I mourn the passing of a great naval aviator, a professional analyst of all things naval, and a soulful and compelling writer of poetry and prose.
Ray Mabus, SecNav