Archive for the 'Aviation' Category
Earlier this spring, the former commanding officer of the Blue Angels was relieved of his duties as Executive Officer of Naval Base Coronado, CA, after he was found guilty at mast of “condoning crude practices on the F/A-18 flight team that led to a sexually hostile command climate.” I don’t know exactly what happened during CAPT McWherter’s second (or first, for that matter) tour as the commanding officer of the Blue Angels. Having read the Command Investigation from start to finish (available on multiple sources, but CDR Salamander has it posted on his site and it’s also available here), I am still unsure of the sequence of events and whether or not this is cause for alarm or celebration. I tried to read between the lines of the Command Investigation and failed at that too. Much of what is described sounds distinctly like regular squadron life, albeit on a more high-profile scale due to the nature of the Blue Angels.
Media reports and discussions focus on the pornography (or porn-lite as it may be), whether or not what happened was offensive, and the actions of the female members of the Blue Angels relative to the rest of the team. But those discussions miss the point, as does most of the ongoing commentary.
Having spent the majority of my Marine Corps time in a skid squadron, I think I have an idea for what gets said and done in such an environment. Skid pilots are not Blue Angels, but they are no shrinking violets either. Let’s just say my learning curve on such matters was steep. I was not offended by porn, nor was I bothered by dirty jokes, and there were plenty of both to go around. Luckily, however, I had a strong and close peer group with several amazing commanding officers. If something had felt wrong, I think that I could have spoken up with few repercussions. There were guys who were bothered by pornographic material, off-color humor, and similar things; out of respect for them others toned it down. That wasn’t the important part of squadron life, anyway, nor did it take up much of our time. What was important was whether or not you knew your job.
Pornography, sexual innuendo, et cetera, while raucously funny to some and at the right time, do not bring about unit cohesion. People don’t need porn to bond, or dirty jokes to trust each other. Humor is needed; smut, not really. Common interests and shared goals and standards, yes. Strong leaders to offer guidance versus camaraderie, yes. Giant phallic symbols on the roof? Not required. Those things are just not that important, but trust, mutual respect, and the understanding that we all have a job to do are. Creating and encouraging that kind of environment among a bunch of type-A, strong-willed pilots—or anyone, for that matter—does not require heavy doses of testosterone, porn, or raunchy humor. I belonged to some great squadrons, led by great COs, who led by example and were strong enough to stand up and do the right thing at tough times. That makes a cohesive Ready Room.
The point—regardless of the outcome of the investigation or the actual events in questions—is not that pornography, dirty jokes, and painted phalluses run rampant throughout naval aviation. It is that when a member of a unit asks others for some respect, a CO needs to take charge of the situation and lead. According to the investigation, CAPT McWherter inherited a broken, “fractured” Ready Room, and to fix it he allowed the pilots to follow the “will of the majority,” “failed to set limits,” and “returned the Ready Room to a more democratic style of leadership.” That sounds like putting the cart before the horse, and the ensuing mess suggests that it was. If people don’t trust each other, don’t respect each other, and cohesion is low, relaxing the rules and fostering overly familial relationships seems like a misstep, not leadership. Maybe that’s not really what happened, but the fact that none of the postmortem discussions note this bothers me.
How did the United States Navy achieve victory at Midway and turn the tide in the Pacific so early in World War II? An anthology from the Naval Institute Press shows the answer: Sailor ingenuity, science and skill blended with Nimitz’s wisdom and determination — along with some luck.
Other factors contributed, including miscalculations and overconfidence of Imperial Japan, whose military leaders were set on taking out “Hawaii’s sentry,” Midway Atoll. But fortune favored many of the U.S. carrier aviators who fatally damaged three enemy carriers, writes John B. Lundstrom in historian Thomas C. Hone’s “The Battle of Midway: The Naval Institute Guide to the U.S. Navy’s Greatest Victory.” Imperial Japan would lose four carriers that attacked Pearl Harbor and more than 100 of its aviators.
Lundstrom notes, “The actual sequence of events was stranger than anyone could have imagined; as [Rear Adm. Murr] Arnold wrote in 1965, it was ‘the most god-awful luckiest coordinated attack.'”
In “The Battle of Midway” editor Hone brings together a gifted roster of writers and leaders including Craig L. Symonds, E.B. Potter, James Schlesinger, Adm. Raymond A. Spruance, Rear Adm. Edwin T. Layton, Elliot Carlson, Mitsuo Fuchida, Masatake Okumiya, Lundstrom and Mark R. Peattie, among others.
Throughout this book of mostly essays written over a span of seven decades, Hone adds context and analysis. In his introduction to Chapter 9, “Prelude to Midway,” he explains Imperial Japan’s motive for the attack.
“The Midway operation had two central objectives. The first and more limited one was the seizure of Midway as an advance air base to facilitate early detection of enemy carrier forces operating toward the homeland from Hawaii, with the attack on the Aleutians as a diversion … The second, much broader objective was to draw out what was left of the United States Pacific Fleet so that it could be engaged and destroyed in decisive battle. Were these objectives achieved, the invasion of Hawaii itself would become possible, if not easy.”
Hone’s “The Battle of Midway” opens with Part I, which explores Nagumo’s kido butai (air fleet), presents Admiral Yamamoto from a Japanese perspective, and shows why Imperial Japan’s carrier pilots were so skilled in the first year of the war with the U.S. Navy; it was because they had already gained experience in the previous decade in China. Part II is titled “Approach to Midway” and includes a brief but powerful piece from Proceedings, “Lest We Forget: Civilian Yard Workers,” by Lt. Cmdr. Thomas J. Cutler, USN (ret.). Cutler is author of “Bluejacket’s Manual,” “A Sailor’s History of the U.S. Navy” and numerous other books.
Part III, “The Battle,” recounts the battle Kurosawa-like, from different angles and viewpoints including several from an Imperial Japanese perspective. “I Sank the Yorktown at Midway,” by Yahachi Tanabe and Joseph D. Harrington, is one provocative title. Parts IV and V deal with the aftermath of the battle, its finale and the official report by Commander-in-Chief, U.S. Pacific Fleet.
Part VI of “The Battle of Midway” explores the personalities, strategies and relationships of the commanders: Nimitz, Spruance, Nagumo, Yamato, Fletcher and Mitscher. Part VII shows how code-breaking helped provide some of the “god-awful luck” that gave U.S. Navy the edge against the enemy fleet. Editor Hone leads with an analysis of the complicated state of affairs with regard to code-breaking, and he includes an excerpt from Elliot Carlson’s excellent “Joe Rochefort’s War: The Odyssey of the Codebraker Who Outwitted Yamamoto at Midway.”
Hone’s book concludes with Part VIII “Assessments of the Battle” and appendixes, including the USS Enterprise Action Report and Spruance’s Letter to Fletcher of June 8, 1942.
The source materials, oral histories, chronologies and analysis in “The Battle of Midway” make this book a compelling overview of the heroic battle while leaving some mysteries, fog-of-war questions, and the impact of luck as still part of the story and lessons of Midway.
An extended version of this post appears on Doughty’s Navy Reads blog, along with a recent review of Robert D. Kaplan’s “Revenge of Geography.”
Her email address was nowhining@…, a symbol of her outlook on life. Married to Paul since the early 1960s, Phyllis Galanti endured six years as a wife of a prisoner-of-war (POW) in Vietnam. But she never complained. Instead, she got busy. The “shy, retiring housewife,” as she was described by Paul at the time he left for Vietnam, later became a national advocate for the release of all our American servicemen who were held as POWs in Vietnam, as well as those service members who were missing-in-action (MIA).
Warned by the military that speaking out publicly about their husbands’ status as POWs would result in worse treatment for them and a setback in the government’s attempts to secure the POWs’ release, wives like Phyllis were ordered to keep silent about their husbands and, for awhile, they obeyed. But after several years of inaction by the government, many of the POW and MIA wives grew tired of suffering alone. Fearing their husbands were languishing and deteriorating in prison, the women were also becoming increasingly impatient. Backed financially by Ross Perot, they banded together and decided to raise awareness of their husbands’ plights, overtly defying the military’s directives. It was a bold move and, at the time, their aggressiveness was shocking. But, encouraged by Mr. Perot and their own determination, they walked the halls of Congress and talked to anyone in the White House, the State Department and the media who would lend them an ear. Phyllis became a leader of this forceful group of women.
Addressing a joint session of the Virginia General Assembly, facing down Henry Kissinger, and traveling the world to meet with the North Vietnamese and keep the pressure on the peace negotiations, Phyllis became an outspoken advocate for all the POWs. She was tireless. She never gave up and never lost the faith. More than six years after Paul was shot down and incarcerated at the infamous Hanoi Hilton, he was finally released on February 12, 1973 – 2,432 days after his capture. Four decades later, the wives and their campaign are widely credited with influencing the Paris peace negotiations and securing their husbands’ freedom. That shy, retiring housewife had been replaced with a steely advocate for change. As Kissinger later said to Paul in his thick German accent, “Your vife, she gave me so much trouble.” Paul was so proud.
Statuesque, poised and calm, Phyllis was not easily excitable. She had a softness about her that was disarming. It started with her full head of spun-silver hair, punctuated by a large, sunny grin that filled her fair-skinned face and lit up her blue eyes. She exuded Southern charm, warmth, and class. And she had the patience of an oyster.
Their emotional reunion was captured on the cover of Newsweek magazine and their story had a happy ending: Paul finished out a successful Navy career and is now the Commissioner of the Virginia Department of Veterans Services. They had two sons and three grandchildren. They continued to serve in the community of their adopted home of Richmond, Virginia, through extensive volunteer work – especially at the Virginia War Memorial, which named its new education center after the couple. They were enjoying their golden years. And, then, Phyllis became ill and died very suddenly last week. I’m sure she would say that she had no regrets in her life – except for perhaps more time with Paul and her children and grandchildren.
Einstein was quoted as saying, “In the service of life, sacrifice becomes grace.” Phyllis sacrificed greatly for Paul and her country, but she won her war, and she exited this world quietly and full of grace.
Taylor Baldwin Kiland is the author of two books about Vietnam POWs.
“Where are the carriers?” Regardless of the writing, talking, and pontificating about “Why the carriers?” – when there is a real world crisis – leaders still ask, “Where are the carriers.”
Since we waived the requirement for a floor of 11, we have drifted to the new normal of 10 CVNs – without dedicated additional funding, even 10 isn’t an accurate number. With one undergoing nuclear refueling – you really have 9. Knowing what it takes to deploy, train, maintain and all other preparations – in normal times we require 9 carriers to make three available now – if you are lucky. If you have an emergency that requires multiple carriers on station – you can run out of options very fast, and the calendar gets very short.
Surge? If, as Rear Admiral Thomas Moore said last year, “We’re an 11-carrier Navy in a 15-carrier world.” – what risk are we taking with 9 carriers that can get underway?
Our guest for the full hour to discuss this and more will be Bryan McGrath, CDR, USN (Ret.), Managing Director of The FerryBridge Group. We will use as a basis for our discussion the article he co-authored with the American Enterprise Institute’s Mackenzie Eaglen, America’s Navy needs 12 carriers and 3 hubs.
Join us live at 5pm on the 13th or pick the show up later by clicking here.
If you are feeling daring, you can even join us in the chat room.
For the inaugural edition of Sea Control’s “East Atlantic” series, Alexander Clarke brings on Steve George, former engineer with the F-35 program and Royal Navy veteran to discuss the challenges and misconceptions of the F-35 program. Remember, subscribe on iTunes or Stitcher Stream Radio. Leave a comment and five stars!
Tune in next week for our interview with Erik Prince!
In trying to come to a better understanding of what the CNO’s Rapid Innovation Cell should be, I came across at old (from 1988! ) essay written by Stephen Rosen titled New Ways of War: Understanding Military Innovation (h/t Adam Elkus for the lead on it). Rosen’s essay details the full evolution of innovation, what innovation is as a process, and how ‘disruptive thinking’ is only the first step and is not innovation in and of itself. Innovation doesn’t truly take hold until the intellectual, technical, and political aspects of the new idea has matured. While the tempo of technological change can be breathtaking, institutional changes in the service still have a tempo that iterates at a generational pace. For Rosen, innovation is not complete until an innovation has been fully developed into doctrine and operational paradigm. In other words, only once the disruption from new ways of thinking has dissipated can the innovation process be considered complete.
The organizational struggle that leads to innovation often involves the creation of a new path to senior ranks so that a new officer learning and practicing the new way of war will not be hunted aside into a dead-end speciality that does not qualify him for flag rank.
Rosen frames military innovation in terms of there actually being three struggles: intellectual, political, and technological. He observes this in three case studies. However, in my remarks here, I shall only stick with one of the examples: development of carrier warfare by the USN.
Rosen pays special attention to how Rear Admiral Moffett performed his duties as the first Chief of the Bureau of Aeronautics. Rosen accounts how at first, aviators objected to the notion of a battleship sailor being chosen to lead the newly minted BuAer. However, they would come to find that it was Moffett’s ability to wage the political struggle, and his ability to articulate the role of the carrier in warfare – in a manner that met the evolving nature of the intellectual struggle – that warranted his selection. As Rosen states
The intellectual redefinition of naval warfare from combat among battleships to the development of mobile air bases at sea would have been futile if the political struggle for power within the officer corps in the Navy had not been fought and won by Moffett and his allies.
Technology alone doesn’t cause innovation, nor does it usher in a new way of war, neither does a good idea make it very far if the champion of that idea can’t help foster institutional change. Rosen cites the efforts of Moffet and so many others as having taken 24 years from the general board first considering naval aviation in 1919 to fruition with the publication of PAC-10 in 1943. A truly generational effort, that saw not just the technology of naval aviation develop, but the aviation career field take its initial shape, and the political structure of the officer corps evolve and the wider community adjust accordingly.
Rosen had to chose for his case studies large and significant shifts that do not often occur in militaries. Where the Navy finds itself today doesn’t nearly parallel the example of the development of naval aviation. However, this is not to say that there are no lessons to be gleaned from it, especially in regards to the intellectual and political struggles within the Navy.
People, ideas, hardware… In that order! — Col. John Boyd, USAF (ret)
Boyd was more right than he realized. Not only is that the order of importance for military leaders, it’s also the order what is the hardest to improve, and once improved that is the order which has the greatest impact. As well, it is the evolution of all three aspects that are required for innovation in the military.
Judging from the comments on social media and the notes I have received from active and retired shipmates, the buzz surrounding CDR Guy Snodgrass’ “Keep a Weather Eye on the Horizon” is real and I’m encouraged to see it. It’s no surprise why this paper has become a topic of discussion in wardrooms and ready rooms around the fleet, and passed electronically across warfare communities.
Our Navy has a proud tradition of professional discourse, and this excellent paper lies squarely in that mold. Good arguments are typically dual-edged – one side passion, the other logic. Guy’s passion is evident and it appears many of you share it. More than that, he understands complete loyalty means complete honesty, and I know – personally – that he wrote this paper only to help make our institution better. It already has. Top naval leaders are aware of several of the issues he touches on. Many are being studied, budgeted for, or in the early stages of implementation. Others give us pause.
I share many of the concerns and have similar questions to those detailed in Guy’s paper. A quick example – many of you have heard me on the road talk about how BUPERS (being self-critical) historically “swings behind the pitch”, unable to nimbly react to economic and early stage retention issues. It’s not neglect, good people here trying to do the best they can with limited tools, but the fact is it has cost us in both good people and money. We have to do better, and I must say that this discourse helps.
We’ve all been JO’s and yes we can also fall victim to forgetting what it was like, but this is also the power of discourse. The idea that there is a perception that operational command is not valued and there is an erosion of trust in senior leadership bothers me…I want to hear more, learn more from you.
Fostering an environment where folks feel empowered to share their thoughts on important issues is a core responsibility of leadership. Ideas, good and bad, have no rank. Yet the discourse can’t just stop there. We need thoughtful debate on how to solve problems, not just an articulate accounting of what’s wrong and who’s at fault. We need leaders willing to offer new and innovative solutions to problems that at times appear impossible or hopeless. Those kind of leaders inspire all of us to continue serving men and women in our charge.
Guy has set an example for one way to ensure thoughtful debate has a voice. Please push your ideas forward — write about them, talk about them with your Sailors, up and down the chain of command. This is the only way we will overcome the challenges ahead of us – together.
Please join us at 5pm (Eastern U.S. Daylight Savings time), Sunday March 9, 2014, for Episode 218: Abolishing of the USAF, with Robert M. Farley :
In concept, execution, and ability to effectively provide its part of the national defense infrastructure, has a separate Air Force served this nation well, and does it make sense to keep it a separate service?
Our guest this week makes the case that the experiment in a
separate US Air Force is over, and it has failed. Though we need airpower, we don’t need a separate service to provide it.
With us for the full hour will be Professor Robert M. Farley, PhD, author of the book being released 11 March, Grounded: The Case for Abolishing the United States Air Force.
Rob teaches defense and security courses at the Patterson School of Diplomacy at the University of Kentucky. He blogs at InformationDissemination and LawyersGunsAndMoney.
Join us live or pick the show up for later listening by clicking here.
In a piece in mid-December, the web site NavalDrones detailed the U.S. Navy’s solicitation for an unmmaned aerial vehicle (UAV) that incorporates Magnetic Anomaly Detector (MAD) sensors. As the article notes, this capability is useful for finding submarines as it “detects changes in the earth’s magnetic field caused by a large metal object,” such as yon u-boat. What is perhaps most interesting about the solicitation is that it calls for the UAVs to be expendable and launched from a P-8A Poseidon aircraft.
The concept of aerial motherhips is by no means new – one only need look back to the glory days of zeppelins with biplane detachments, or to the helicarrier in the recent movie The Avengers to get a sense of the breadth of idea. And the solicitation for the Poseidon doesn’t mark the first go at aircraft-launched UAVs:
In 2009, an expendable sonobuoy tube-launched UAV called Coyote was tested out a NOAA’s WP-3D Orion under an Office of Naval Research. A less successful small business grant was awarded to Lite Machines to modify its Voyeur UAV for sonochute launch.
Despite this, more attention is focused on surface and subsurface vessels playing the roles of motherships than aerial drone motherships. DARPA caused a stir earlier in 2013 by announcing the start of a UUV mothership program, named in a not-at-all-sinister fashion “Hydra,” that would be capable of launching embarked UAVs and UUVs, while Coastal Riverine Group-1 received the manned Coastal Command Boat UUV-launching mothership. Elsewhere, debate and intellectual energy is starting to explore the interplay of manned, unmanned, and autonomous aircraft and the tactical possibilities their combinations can provide.
Less attention has been paid to aerial motherships as the constant and exploring the pros and cons of using any of the following as variables:
1. The mission sets of the UAVs and how they would interact with other platforms.
2. Launching non-expendable UAVs.
3. Launching USVs or UUVs.
4. Motherships that are purpose-built (as opposed to ad-hoc such as the Poseidon).
5. Motherships that are themselves unmanned or autonomous.
6. Lighter-than-air (e.g. blimp) craft vs propeller or jet craft.
In many of these combinations the pros will be outweighed by the cons, but it’s possible there are some winning, creative combos worth discovering. An upcoming issue week at CIMSEC will be dedicated to naval drone concepts and tactics. In the latter I hope to explore these variables in more detail. As I’ve likely missed some salient points I look forward to incorporating your feedback.
This article appeared in its original form and was cross-posted by permission from CIMSEC’s NextWar blog.
CDR Salamander joins Matt and Grant for a podcast on writing as a member of the military, anonymity, and some sacred cows military planners hold dear: benefits, high-end systems, equal budgeting, etc… Join us for Episode 8, Sacred Cows and Amphibians (Download).
Articles from Sacred Cows Week:
Quantity over Quality (Michael Madrid)
Holy Bovine, Batman! Sacred Sailors! (Matt McLaughlin)
American Defense Policy: 8 Reality Checks (Martin Skold)
Ain’t Ready for Marines Yet? The Sacred Cow of British Army Organization (Alex Blackford)
SSBN(X): Sacred Cow for a Reason (Grant Greenwell)
Why the United States Should Merge Its Ground Forces (Jeong Lee)
Sacred Cow: Military Pay and Benefits By the Numbers (Richard Mosier)
Sea Control comes out every Monday. Don’t forget to subscribe on Itunes and Xbox Music!