ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Navajo Code Talkers in World War II

Updated on July 14, 2012

Using Navajo Language to Communicate Securely on the Battlefield

The 2002 movie, Windtalkers, staring Nicholas Cage, is a story about Navajo Indians serving in the Marine Corps in the Pacific theater during World War II.

These members of the Navajo Nation made a unique contribution to the war effort by working in battlefield communications transmitting critical battlefield information to fellow Marines of Navajo descent using a code based upon the Navajo language.

The beauty of this code was that the Navajo language is not only not a written language but it was also unknown to the Japanese which made it impossible for the Japanese to break the code or understand the language it was in.

Hub 21 for 30 Hubs in 30 Days Challenge

My assistant, Chika, and I trying to write and publish 30 Hubs in 30 Days
My assistant, Chika, and I trying to write and publish 30 Hubs in 30 Days | Source

Code Talkers Were Relatively Unknown Until Recently

The movie was a big hit, in part because it dealt with a little known aspect of World War II. In addition to being great entertainment, the movie also helped to raise the nation's consciousness about these men and the contribution that they made.

Despite the critical role that these Navajo Marines played in the war, they were relatively few in number and their service was but one of many critical contributions that led to the Allied Victory in World War II.

This, plus the fact that, like the rest of their comrades in arms, the Navajo men who served as code talkers, looked forward to going home and resuming their lives once the war was over.

Navajo Code Talker Exhibit at Arizona Military Museum

Arizona Military Museum Display of Code Talker in the Field
Arizona Military Museum Display of Code Talker in the Field | Source
National Navajo Code Talkers Commemorative Poster at Arizona Military Museum
National Navajo Code Talkers Commemorative Poster at Arizona Military Museum | Source

They had served their country in her time of need and were happy to have survived the terrible ordeal of war. Like most soldiers at the end of a war they just wanted to forget. Reminiscing about their youthful experience as warriors could wait until they had grandchildren.

Also, to a certain extent, they were sworn to secrecy as the code they used, but not their role in the war using the code, was classified as a military secret.

However, the use of Navajo code talkers in World War II and the role the code talkers played was known after the war and before the declassification of the code in 1968. I remember reading about them in as a young child in a book about American Indians. There was also the 1959 movie. Never So Few, in which Charles Bronson played the role of a Navajo code talker.

The Navajo code talkers didn't just communicate by radio with each other on the battlefield in the Navajo language but, rather spoke in Navajo using a military code and it was the code they used that was classified as a military secret until 1968.

Navajo Code Talkers on Island of Saipan in 1944

Public Domain image courtesy of WikiPedia ( http://en.wikipedia.org/wiki/File:Navajo_Code_Talkers.jpg )
Public Domain image courtesy of WikiPedia ( http://en.wikipedia.org/wiki/File:Navajo_Code_Talkers.jpg )

Message First Translated into Navajo and Then Coded

English, even at the time of World War II, is a very common language and it is either the first or second language of a large portion of the world's population.

Thus, it was fairly easy for members of the Japanese military to decipher American battlefield codes which gave the Japanese an advantage as there were far fewer Americans fluent in Japanese than there were Japanese fluent in English.

It is important to emphasize that the messages that the Navajo code talkers sent and received, were first translated into Navajo and then encrypted before transmitting. Upon receipt the message was decrypted in Navajo and then translated from Navajo to English.

My Wife Bella With Next to Cassing of "Fat Boy" Atom Bomb Similar to One Dropped on Nagasaki

My wife Bella posing next to a model of an Atomic Bomb at the U.S Army White Sands Missile Museum in New Mexico.
My wife Bella posing next to a model of an Atomic Bomb at the U.S Army White Sands Missile Museum in New Mexico. | Source

The Story of Sargent Joe Kieyoomia

Thus, merely knowing the Navajo language, even being fluent in Navajo as ones first language was not sufficient to understand the message.

This fact was proved by the experience of Army Sargent Joe Kieyoomia, a Navajo who had enlisted in the U.S. Army before World War II and was stationed in the Philippines at the time World War II began.

According to his biography in WikiPedia, Sargent Kieyoomia was taken prisoner when Japanese forces invaded the Philippines.

Sargent Kieyoomia was among those who survived the infamous Bataan Death March as well as survived both as a prisoner of war during the entire war and being held in a Japanese prisoner camp in the city of Nagasaki, Japan when the United States dropped an atomic bomb on that city (the first atomic bomb used in war was dropped on Hiroshima on August 6, 1945 and the second on Nagasaki three days later on August 9, 1945).

Atomic Bomb Exploding Over Nagasaki August 9, 1945

Public Domain Image Courtesy of WikiPedia.org ( http://en.wikipedia.org/wiki/File:Nagasakibomb.jpg )
Public Domain Image Courtesy of WikiPedia.org ( http://en.wikipedia.org/wiki/File:Nagasakibomb.jpg )

As if this were not enough, Sargent Kieyoomia was twice tortured extensively during his captivity. When he was first captured, his captors thought he was a Japanese American and tortured him for being a traitor to his race. This ceased once he was able to convince them that he was a Navajo and not Japanese.

As the war progressed and the Japanese learned the U.S. Marines were using Navajos speaking Navajo to send battlefield messages, they tortured Sargent Kieyoomia again in an attempt to get him to break the code for them.

While he could translate Navajo for them, Sargent Kieyoomia was not able to break the code as he was not trained in cryptography. Thus, the code remained secure despite the Japanese having a Navajo prisoner of war.

Sargent Kieyoomia was freed at the end of the war and returned home to the United States where he lived until his death in 1997.

Navajo Not the Only Language Used for Battlefield Communication

While Navajo code talkers appear to have been used only by the U.S. Marine Corps in the Pacific Theater of War during World War II, members of other tribes were used sporadically by the U.S. Army in Europe and the Pacific to send messages in their languages.

The U.S. Army also used Basque speakers (a number of which had migrated from the Basque area of Spain and France to the United States and had retained their native or their parent's native language). Like the Native American languages, Basque is both a somewhat unique language as well as a little known among non-native speakers.

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)