Archive for the 'Marine Corps' Category
Congressman J. Randy Forbes (R-VA) addresses the attendees of Defense Forum Washington.
After nearly three decades of peace the U.S. Navy went to war again, this time with Mexico. This conflict was fought both on the Pacific coast and in the Gulf of Mexico, and marked the Navy’s first large-scale amphibious operations.
By Mark Tempest
When one hangs up the uniform after decades of service, but still wants to contribute to their nations national security needs, what paths can that take? How does one find a path forward, and what are the keys to success?
In a budgetary challenge not seen by the US military in two decades, what are the important “must haves” that need to be kept at full strength, and what “nice to haves” may have to be put in to the side?
What are the legacy ideas, concepts, and capabilities that the Navy and Marine Corps need to make sure they maintain mastery of, and what new things are either here or are soon on the way that we need to set conditions for success now?
Our guest for the full hour to discuss this and more will be Robert O. Work, Col. USMC (Ret), presently CEO of the Center for a New American Security (CNAS), and former Undersecretary of the Navy from 2009-2013.
After 27-years of active duty service in the Marine Corps, Work joined the Center for Strategic and Budgetary Assessments (CSBA), where he focused on defense strategy and programs, revolutions in war, Department of Defense transformation, and maritime affairs. He also contributed to Department of Defense studies on global basing and emerging military missions; and provided support for the 2006 Quadrennial Defense Review.
During this time, Work was also an adjunct professor at George Washington University, where he taught defense analysis and roles and missions of the armed forces.
In late 2008, Work served on President Barack Obama’s Department of Defense Transition Team.
He earned his Bachelor of Science degree from the University of Illinois; and has Masters Degrees from the University of Southern California, the Naval Postgraduate School; and Johns Hopkins School of Advanced International Studies.
Join us live (5pm EST) or pick the show up later by clicking here.
The inevitable fiscal crunch that is starting our Military down has the Pharisees of the defense industry, think tanks, and senior military leaders all rabble-rabbling about the need for change. Some of that change is strategic- Asia Pacific pivot anyone? Other bits of it reside in the acquisitions department, as we see with the pros and cons of developing “revolutionary” weapons systems to confront “new” threats. The most harrowing changes for military leaders are the all too well known cuts to manpower that will come in some fashion, no matter the logic, or lack thereof, which delineates how those cuts will happen. There is more change in the air than cordite after an end of fiscal year shooting range, but it is important to reflect on some history in order to avoid stepping on the same proverbial rakes that have smacked our national security establishment in the face during previous drawdowns.
Ideas like this one are an especially pervasive form of bad, and seem unable to die even when history proves them inadvisable. We saw the call for unification in President Eisenhower’s attempts to reevaluate our national security establishment in light of the massive technological, strategic, and social changes that occurred after World War Two. It was vital to acknowledge the necessity of change in that period, because much like Eisenhower’s dictum on planning, self-examination is vital even if most of the individual recommendations may turn out to be worthless. Reconsidering defense in light of nuclear weapons, ICBMS, and the bi-polar nature of security dilemmas when facing the Soviet Union was important. Trusting academic tea-leaf readers in their assessments and then proclaiming there would “never be another amphibious landing”, that ground forces would not be used in limited wars, and that tactical airpower was only needed to defend or shoot down strategic airpower looks downright foolhardy when viewed as historical record. What saved us from the march to a monolithic Star Fleet force that all wore the small uniforms and all died like red shirts landing on Klingon? The pluralistic competition of our service structure, which was inefficient and far from perfect, but possessed a flexibility that made it anti-fragile.
Separate services, even separate services that possess redundant capabilities, are a vital part of American national defense. The Army needs the Marine Corps to soak up public attention as a motivation for better performance as badly as the Marine Corps need the Army to keep its constant self worry about irrelevance and drive its performance. Those intangible reasons can be criticized as they are not measurable, but of direct consequence are the different service outlooks which spurn actual innovation.
The Marine Corps decided it would gladly incorporate vulnerable and unwieldy rotary aircraft that Army and Air Force leaders largely ignored during Korea, and in doing so enabled the much better resourced Army to perfect the techniques of vertical envelopment to a higher degree than it ever could in Vietnam. The Navy had to have an Air Force that threatened its budget in order to develop SSBNs, and not pursue the much less effective option of carrier borne strategic bombers. Our most recent wars have shown the truth that a market place of defense ideas is better than a command economy for strategy. While the Marine Corps stubbornly resisted SOCOM membership, the other services gladly perfected the techniques needed to combat global terrorism in the learning laboratories of Somalia, Bosnia, Afghanistan, and Iraq. Those were bloody lessons, but proved that some enemies cannot be defeated by large MEUs waiting off shores, although the synergy created between such a force and SOCOM has proven to be vital, and continues to pay national security dividends. Service diversity even ensures we do not forget lessons learned in blood that may seem inefficient during peacetime arguments on Capitol Hill. Even the best planners can shortchange things that are easily forgotten as peace breaks out. Something as boring as oil platform protection is a skill the world’s preeminent Navy forgot, and had to relearn from the worlds 12th largest navy (the U.S. Coast Guard). There is known historical value and definite future value in keeping a diverse and flexible force, but to do so one must resist the urge to unify in the name of declining dollars. Cost savings are easy to evaluate in peacetime dollars, but take on a morbid tone when seen in defeat and death at the opening stages of a conflict.
Cleary such an arrangement has inefficiencies, and wasting taxpayer dollars in the worst economy in years should be viewed as criminal no matter if the DOD is committing the waste or not. Grenada, Desert One, and Vietnam all demonstrated the tragic human cost of pursuing service parochialism over higher interests. Such costs have been mitigated in part by the Goldwater-Nichols act of 1986. Goldwater-Nichols is far from perfect and could use an upgrade to incorporate recent lessons from the Long War. Jointness in our operations, communications, and interoperability is a good thing. Understanding perspective, knowing how the whole of the military functions instead of just one’s own slice, and talk the language of service peers are also good things. Making claims that bureaucratic restructuring to “align” and “combine” are fools errands, they repeat the mistakes that we almost made in trying to tear down an organic system. Our current force has grown through invaluable combat experience, to replace it with a theoretical framework that has never worked is a bad idea of immense magnitude.
There have been examples of “unified” militaries, look at Saddam’s Republican Guard, it clearly combined the best equipment, personnel, and training available to fulfill “civilian” leadership’s strategic wishes. Such a system is horribly fragile, and succumbs to the groupthink that all bureaucracies do. In this age of belt tightening, we should correctly become more efficient, but there are better ways than throwing out everything and starting from scratch. Reexamining our bloated personnel policies, taking a hard look at our compensation and retirement systems that resemble ticking fiscal bombs, and revamping our professional military education are all better places to start than tired and historically bankrupt calls for the “merger of …[U.S.]…ground forces”. The diversity of thought which comes from each service is one of the strongest weapons our joint force possesses, it would wise to avoid dulling such fine tool so we can save dollars only to spend lives unnecessarily in a future conflict.
It is relatively well-known that students at the Naval Academy are called midshipmen. But what is less-known is where that term comes from. How were officers prepared and trained prior to the founding of the Naval Academy and other, later commissioning programs like ROTC? For the month of May, we are looking at the midshipman training process at the Naval Academy, and we begin with a discussion of the origin of the term midshipman using today’s object, a dirk owned by Stephen Decatur.
It was four years ago today that the Coast Guard and the Marine Corps lost some of their Shipmates during a midair collision of Coast Guard Rescue 1705 and a Marine Corps helicopter off the coast of California.
On the night of 29 October 2009 I was standing watch within the LANT Area Command Center as the SAR Controller; I took the Critical Incident Communications (CIC) call as it came in from the West Coast via HQ. I can easily recall the near three hour long conference call and listening to the voice fluctuations of the Search and Rescue Controllers as they were getting the direct communications from those on scene.
The most vivid moment that’s still ground into my skull was hearing- through a radio over the phone- that those on scene had found a “huge tire” with a marking of “Sacto” on it… my heart sank; my stomach hurt. As I rushed to find out who was on that flight I remember going into a cold sweat; the Coast Guard isn’t that large of a service. The aviation community within is even smaller. I was, as many know, a prior Navigator aboard our C-130′s. While most of my time was spent in Kodiak, AK I have a deep appreciation of those who fly in the more traffic-heavy areas of the nation- it’s hard work.
In the end little to nothing was found from the downed aircraft, less immediate debris, nor any bodies recovered. Please take a moment today to remember those who were lost four years ago today;
- Lt. Cmdr. Che J. Barnes was the commander of CG-1705, an HC-130 long-range surveillance aircraft based at Coast Guard Air Station Sacramento, Calif. A 1996 graduate of the Coast Guard Academy, Barnes was awarded the 2009 Cmdr. Elmer F. Stone Aviation Crew Rescue Award. During his 17-year Coast Guard career, Barnes also received the Coast Guard Commendation Medal, three Coast Guard Achievement Medals and two Coast Guard Letter of Commendation
A native of Capay, Calif., Barnes is survived by his father, Martin K. Barnes; twin brother, Noah L. Barnes, brothers; Thaddeus F.M. Barsotti, and Freeman O. Barsotti; and girlfriend, Carrie Reynolds. He is preceded in death by his mother, Kathleen F. Barsotti.
- Lt. Adam W. Bryant was the co-pilot of CG-1705. Bryant was a 2003 graduate of the Coast Guard Academy and was a recipient of the Coast Guard Commandant’s Letter of Commendation ribbon.
A native of Crewe, Va., Bryant is survived by his mother, Nina Bryant; father, Jerry Bryant; and brother, Benjamin Bryant.
- Chief Petty Officer John F. Seidman was the flight engineer of CG-1705, an HC-130 long-range surveillance aircraft based at Coast Guard Air Station Sacramento, Calif. In his 23 years of service, Seidman was awarded the Coast Guard Commendation Medal, Coast Guard Achievement Medal, Coast Guard Commandant’s Letter of Commendation Ribbon, and
seven Coast Guard Good Conduct Medals.
A native of Stockton, Calif., Seidman is survived by his wife, Jennifer Seidman; parents, William (Bill) and Connie Seidman; and brother, Jeffery Seidman.
- Petty Officer 2nd Class Carl P. Grigonis was the navigator of CG-1705. In his nine years of service, Grigonis was awarded the Coast Guard Achievement Medal, Coast Guard Commandant’s Letter of Commendation Ribbon, and three Coast Guard Good Conduct Medals.
A native of Mayfield Heights, Ohio, Grigonis is survived by his wife, Kristen Grigonis; his son, Hayden; the upcoming arrival of their daughter, Kalina; his mother, Janina Grigonis; and brother, George Grigonis.
- Petty Officer 2nd Class Monica L. Beacham was the radio operator of CG-1705. In her nine years of service, Beacham was awarded two Coast Guard good conduct medals.
A native of Decaturville, Tenn., Beacham is survived by her husband, Seaman Travis Beacham; her daughter, Hailey; her mother, Shirl Jean Merrell; brother, Michael Gipson; and sister, Kelly Johnson.
- Petty Officer 2nd Class Jason S. Moletzsky was air crew for CG-1705. In his seven years of service, Moletzky was awarded the Coast Guard Achievement Medal, two Coast Guard Commandant’s Letter of Commendation Ribbons, and two Coast Guard Good Conduct Medals.
A native of Norristown, Pa., Moletzky is survived by his fiancé, Christiana Biscardi; parents, John and Lisa Moletzsky; and sisters, Amanda and Rebecca Moletzsky.
- Petty Officer 3rd Class Danny R. Kreder II was drop master for CG-1705. In his four years of service, Kreder was awarded the Coast Guard Commandant’s Letter of Commendation Ribbon, and the Coast Guard Good Conduct Medal.
A native of Elm Mott, Texas, Kreder is survived by his wife, Victoria (Sovey) Kreder; parents, Jeff and Jodi Woodruff; brothers, Brandon and Cory Kreder; grandmother, Pamela Sue Lyle; grandparents, Wayne and Shirley Sovey; and in-laws, Sam and Tracy Sovey.
Never forget, always remember.
(Cross post from ryanerickson.com)
Over the Columbus Day weekend I had the great opportunity to participate in the first national Defense Entrepreneur’s Forum conference. The event was hosted at The Booth School of Business at the University of Chicago and a number of other organizations, like USNI, sponsored events from breakfasts to happy hours. At its heart, however, the conference was independently organized by a group of mid-grade and junior officers to explore the nexus of innovation and entrepreneurship with military affairs and defense industry.
Off the top, the very existence of the event was something to behold. Over a hundred men and women from the junior ranks of the military, civilians from the defense world both inside and outside government, and innovation/silicon valley folks, got together for three days to talk about how to make the military better in the 21st century. They paid their own way. The government is shutdown. Even if it wasn’t, sequestration meant there was no travel money. They filled out a leave chit and pulled out their personal credit cards. These individuals have such a belief in the idea that the military needs new ways of looking at things and doing things, and such an overwhelming desire to be part of that, that they all dropped hundreds of dollars and their long weekend to go to Chicago to meet with one another.
I do have a personal note about attendance that I think should be made: while many junior personnel had the guts to vote with their wallets and their time, only one General officer showed up, and a couple of Colonels. I’m not sure what any of that means, but it is worth noting because ALL ranks, rates, and grades were invited. In fact, there was some pretty significant outreach to the Flag and General Officer community by the organizers.
So, the Defense Entrepreneur’s Forum 2013 set out in part to inspire, in part to educate, and in part to execute. The events were livecast with the support of Google, and there is a DEF Youtube Channel. The Tweetwall went up and participants were encouraged to tweet as the event went on to highlight ideas and lessons. You can read back through the tweets from the weekend at #DEF2013 if you are interested.
Over the next week or two I’m hoping that there will be a number of blog posts across the web about what we all experienced at DEF. LT Hipple has already reported back at USNI Blog and there are a few others (here, here, here) to get us started.
I just wanted to share one observation that I took away from the weekend. On Sunday, Sean Maday, a former USAF Captain who now works at Google pointed out in his Keynote that a few short years ago, when he was wearing baby blue with railroad tracks on his collar, a three or four-star wouldn’t even acknowledge his existence, never mind listen to his ideas. Today, just because he put on a pair of jeans and a t-shirt instead of a uniform, they travel to Palo Alto to meet him, desperate to know what he thinks. This illustrates one of the great truths that was only hinted at in the excitement of DEF: Innovative junior officers don’t have the power to execute their ideas.
One of the mantras of the weekend was that we must have results. Ben Kohlmann quoted fellow board member Micha Murphy that “execution is the new innovation.” This is a valid observation, but only after the innovator is given the nod, a green deck if you will. Someone in a position of power and influence has to buy into the idea that a) there is a problem and b) this is a good solution. In the world of Silicon Valley they don’t have Flag and General Officers who are part of a massive, centuries old bureaucracy. However, they do have the venture capitalists and money men, and if you can’t get a money man to buy into your grand IT innovation or start-up it’s going to be pretty tough to get anywhere.
It may be that the best way to look at this is to think about military strategy, maybe think a little bit about Sun Tzu and stir in some Liddell Hart with a touch of John Boyd, and look for an indirect approach. In the closing hours of the conference Colonel Michael-Bob Starr (USAF, one of the few senior officers at DEF) tweeted:
Implementation is not the goal. Goal is to INFLUENCE the implementers. #DEF2013
— Michael Bob Starr (@mbobstarr) October 14, 2013
So how do you influence the decision makers? While it was not formally talked about, it did come up again and again with comments about communicating your idea. As Howard Lieberman said on Sunday in a breakout: “Publish your idea and get credit for it.”
So, here’s my lesson observed from DEF 2013: It isn’t good enough to have a great idea or to figure out how you would implement it. Neither of those things matter unless you figure out how to influence the influencer, how to get your idea in front of someone who can make a decision and get the green-light. We heard repeatedly this weekend that one of the best ways to get your idea in front of someone is to publish it. The hyperlink, the pdf, or the hard copy of the magazine are a lot more likely to find their way in front of the person with that power than you are just wandering aimlessly around your base with a great innovation in your head.
I think we’ve heard this before: Dare to read, think, write…publish.
The incredible power of innovation and entrepreneurship often produces an unfortunate exhaust of innovocabulations. Ideate is one of those words, and made quite a show of force at DEF 2013, hosted graciously at the Chicago Booth School of Business. However, as irritating as a not-words may be, ideate serves DEF2013 core spirit as a fitting metaphor. Ideate is merely the word “idea” verbed. Rather than concentrating as many do on creativity and the idea-creation process, DEF2013’s central thrust was the array of actions necessary to turn ideas into realities.
To foster that concentration on acting on ideas, the conference content was split between presentations and break-out problem-solving sessions.
Pleasant Surprise- Presentation Twitter-Wall:
Although the break-out sessions would be the conventional show-case of attendee collaboration, the integration of the twitter-wall to the presentations was a great way to get the audience engaged. While following the flow of “#DEF2013″ commentary on the boards, members of DEF could note particular phrases or points of the speaker, argue amongst themselves, or perhaps just be snarky cough #hipstermahan /cough.
The twitter conversation during presentations was also great track-two way of “meeting” forum attendees as you retweeted poignant observations on presentations, debated points of contention, or collaborated in solutions to problems brought up by speakers and form members alike. In the break sessions, I “met” forum members, though often much of the ice was already broken by conversations we’d already had I’ve long incredibly skeptical of twitter, but I found its use in this context a rather redeeming and collaborative experience!
Oh… and it was nice to get a tweet from Harris Teeter about the Oxford Comma too. As you can tell, some of us may have gotten off topic occasionally. But hey, why buy pizza not worth defending? #pizzafort
Presentations- A Mile Wide and a Mile Deep:
Part of me will never graduate college and will always enjoy a rich lecture. While the twitter was fun, it’s foundation was the excellent presentations being given by our guest speakers. You can find those on YouTube if you missed the live feed. Some of the video is uncut and you have to jump around to find the speeches, but many are well worth it.
Rather than turn this into a book report, I’ll delve into a by-no-means-comprehensive collection of points I thought were worth taking away.
You Don’t Have To Be The Innovator/Doing Your Homework: BJ Armstrong’s The “Gun Doctor” presentation is an instant classic, and has appeared in various forms at several venues. It only gets better with time. That said, a key piece of information from that presentation is that ADM Sims started with an innovation from someone else that he considered worth his effort and attention. The conference closed with a presentation by Phil Nevil of Power2Switch taking a similar angle, how his own ideas failed but he succeeded when he championed the cause of another. In both cases, an important part of championing an idea was doing the research: becoming familiar with both your market and your product. If ADM Sims hadn’t done his research and tests on Percy Scott’s continuous-aim firing, no one would have taken him seriously. Likewise, if people in private industry just “ideate” without doing tests, research, prototyping, and probing their market, they’re not “innovating”, you’re just talking.
Fighting a Loyal Insurgency Inside the System: Stealth, focus, and aggression are not always necessary when innovating, but can be good tools when combatting entrenched interests. Peter Munson’s speech was about how leaf-eaters learn to defend the system for at the detriment of adaption and effectiveness and meat-eaters charge forward at opportunity. In an organization like the DoD, there is a reality to the necessity and purpose for the system and its leaf-eater accolytes. Innovators must carefully pick and choose their battles. This idea was summed up by the delightful peregrine falcon, Dora. Play in the system (like dora moves stealthily through the clouds) and aggressively attack when opportunity arises (poor, stupid duck). If Dora flew around squawking all day and making a mess without that focused action, too many leaf-eaters would be alerted and defend their steaming piles of process.
Building an Army: Human capital is a critical part of innovation, if not the tipping-factor in-and-of itself. Howard R. Lieberman’s presentation hit the hammer hard on the point of building a body of stakeholders and champions to help push your ideas. Don’t start with the question of what the value of your product is, but rather push what value it brings to people. Finding the meaning of your idea for other people is what builds stakeholders, who may be champions for your ideas or loyal foot-soldiers doing the testing and development who will sacrifice their time and resources to see your idea through to the end. Some of those stakeholders may provide top-cover. Many of his stories involved his company president giving him cover for his “special projects” that the board didn’t always agree with. The ground-forces are great for “taking the hill” of an idea, but close-air-support flying high in the chain of command can really change the equation. No man is an island, and no innovation is a one-man mission.
Execution, Execution, Execution: Every presentation was about how action, not creativity, is the germ of real innovation. That said, the second day of private-sector entrepreneur presentations was a wall-to-wall show of how the ability to find market-demand while developing the necessary supply is the center of the innovation universe. The difference between a real-life innovator and the chatting classes is action.
My one real criticism of the conference does lie in this category. I felt like the innovations we discussed were mostly historical or from private industry. We didn’t have a body of speakers who, as members of the military, wrestled with and executed significant innovations. That may be an indictment of our system and whether those people have been able to be truly successful or just that it is easier to success in the business world. Whatever the case may be, there will be plenty of years of DEF to find more live-streaming innovation successes within the life-lines. And yes, before you say it, I know DEF itself is a successful inside-the-lifelines success… but you know what I mean!
Don’t Get Killed in a Good Battle: Dan Moore’s presentation on breakthrough leadership through the lense of Boyd was particularly great because I found myself in a room full of Boydians debating the legacy of Boyd, army tactics, thrust lines, decision-analysis, etc… but while all of this was fascinating, the newest detail to a complete Boyd amateur like me was the disaster of his personal life. “To be or to do,” shouldn’t happen to the detriment of “being” things like a good father, husband, or just healthy individual. If you’re a hard charger and an innovator, the military needs you healthy, not burnt out fighting every battle to the hilt. You’re needed in far more than the one fight you might be in now. Dan Moore’s final point, and one to always keep close is, “don’t get killed in a good battle.”
USNI Is Awesome: Sam LaGrone’s presentation was about some self-evident truths.
There is far more material, and none of the descriptions are by any means comprehensive. While these are good takeaways, the speeches are definitely worth watching on the YouTube channel.
Breakout Groups- Thoughtifying:
What would an Entrepreneurs conference be without some actual innovating? It certainly wouldn’t be as fun. The afternoons at DEF were dedicated to breakout sessions intended to building actionable solutions to real-world problems.
I found my time in the PME “ideation” group to be an education in many already-existing processes of other branches that I wished the navy had, from selection-means-attendance to the USCG’s libertine “selection-ignores-rank”. I hadn’t realized how different the different services PME systems were, and I found it a bit depressing how some may put PME in the side-car when others described the rigor and seriousness of their selection processes.
Nathan Finney led our group, and the vast array of “free the beast” ideas to put education in the driving seat were, very pragmatically, whittled down to a single free and actionable item: use of twitter for class comprehension analysis by teachers. A great example of how the system would work was Michael-Bob Starr’s discovery that the reason he had an odd feeling he’d lost his audience for about 5 seconds was that I had tweeted “never trust a man with two first names,” during his speech. Of course, in the PME version, it wouldn’t be on all the screens and would be more a way for teachers to get input on comprehension, class observations, and the like.
Other great innovations were produced, from the Emotional Vitality Assitant (EVA) to create a hand-held link directly to mental health professionals to the DEF X-prize, rewarding military members for great ideas or great execution of ideas (we hadn’t decided yet). The dream of pushing half the acquisition system into the sea and replacing it with a 100 page paper was quite the utopian ideal, but no knives yet exist that are long enough to penetrate to the heart of the procurement beast.
The People are the Product
The lectures and break-out sessions were great, but the real reward of DEF2013 was meeting the people I’d only known through writing and reputation (or the ones I didn’t know, for that matter). In his closing words for the conference, a closing speaker said it best, “people don’t buy what you do, but why you do it.” No one came to DEF2013 to see a particular innovation or idea, but to spend a weekend chatting about their passions with people of the same level of intensity. Every branch was represented with civilians and veterans alike, but we were all there for the same “why.” They came because they believed in that process of critical thinking and seeking the greater good. We didn’t seek innovation for innovation sake, but we sought mission victories, safety and effectiveness for our fellow warfighters, good stewardship of the resources in which we were entrusted, and the importance of good ideas having their day in the arena. DEF2013 didn’t create an innovation, it bolstered the community that is going to build them together.
The U.S. Naval Institute’s 2013 annual history conference, “Past, Present, and Future of Human Space Flight” at Alumni Hall on the grounds of the U.S. Naval Academy opened with the morning keynote presented by astronaut and retired Lt. Gen. Thomas P. Stafford.
Stafford, a veteran of the Gemini and Apollo programs and the Apollo-Soyuz Test Project, opened his remarks by expressing his pleasure at returning to his alma mater. “I’ll be talking fast today because there’s a lot of history to cover,” he said. Stafford explained that the launch of Sputnik 1 in October 1957 had a galvanizing political effect in the United States that led to a push across the country to boost science, technical, and math (STEM) education, and inspired Senator Lyndon Johnson to push for a manned space program. Stafford summarized the subsequent creation of the Mercury program, explaining that the Mercury spacecraft suffered from limitations largely imposed by the limited size of the available launch vehicles. For example, while astronauts were able to change the Mercury spacecraft’s attitude, they were not able to affect its vector — a factor that would play a significant role in the design of the subsequent two-person Gemini spacecraft.
When Yuri Gagarin made mankind’s first manned space flight on April 12, 1961, it spurred the United States to respond by launching Alan Shepard on a suborbital flight President Kennedy to make his famous speech before Congress a month later in which he called for a man to be landed on the moon and safely returned to Earth. “I’m glad he used the words, ‘safely returned,’” Stafford quipped. A little-known fact about the speech was that Kennedy had already informed, and secured the support of, key Congressional leaders prior to the speech. “So while the speech came as a surprise to many of those in Congress, to the power brokers, the deal was already done,” said Stafford. “This is a lesson in political history.”