ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Chaco War in South America 1933

Updated on January 17, 2011

Nawana: Verdun in the Chaco War was a three day battle between Bolivia and Paraguay during the long Chaco War. The Chaco War remains the only declared war that occurred in South America in the 20th Century. In brief, Bolivia wanted access to the Atlantic. The discovery of minerals and oil by Shell and Standard Oil prompted both countries to pursue these objectives in the Chaco desert area.

For Bolivia, access to the Atlantic would allow projected oil pipelines to the Paraguay River to be built and allow for commerce. Total war actually began in 1932 and ended in late 1934 with both countries nearly broke. The Bolivians were defeated in all major battles and by the end of 1934, they had been driven back 482 kilometers from their original positions deep to the foothills of the Andes. Serious strategic errors, poor intelligence, and logistical problems in reaching the distant battle lines contributed to the losses. In addition, the morale of the Bolivian troops was low.

Bolivia lost the Chaco but retained the petroleum fields, which Paraguay had failed to reach. Both countries suffered heavy losses, Bolivia alone, an estimated 65,000 people were killed and 35,000 wounded.

Nawana (a small town) was a turning point battle. It was here, a Bolivian Army led by German General Kundt, armed with new weapons (six tanks, flamethrowers, fighter-bombers) assaulted the Paraguayan defenses. Kundt had been led to believe the defenses were weak, that the tanks would break through and that once Nanawa fell, the road would be open to Paraguay’s capital. This was in fact true, however, that was the only thing which was true. The Paraguayan forces had been issued special antitank ammo and built well defended trenches with mines. Their lines were not weak and numerically almost as strong as the Bolivian! The three day battle ended with the Bolivians surrounding but failing to seize Nanawa in face of growing Paraguayan forces (the Bolivians had no reserves), eventually returned to their start positions. 

The six tanks, made in England, were in fact, light tanks, all armed with machine guns not cannons. Their armor was thin and when they moved bravely across the lines they met with antitank shells and AP rifle fire. Some tanks broke down, some destroyed but none caused much of a panic. The battle was akin to WW1 style warfare.


    0 of 8192 characters used
    Post Comment
    • perrya profile imageAUTHOR


      7 years ago

      Mucho gracias, Rodrigo. Subtle data differences, though.

    • profile image


      7 years ago

      the note has some unaccurate data:

      "Total war actually began in 1932 and ended in late 1934 with both countries nearly broke"

      The war ended in July 1935, with the pease protocol signed in 1938. The peace was reached after the intervention of Argentina, when Bolivia raised a third army and Paraguayan logistic lines were too long to help them resist a new offensive.

      "The six tanks, made in England, were in fact, light tanks, all armed with machine guns not cannons."

      In fact Bolivia has 5 armored vehicles, 3 Vickers 6-ton tanks (2 armed with cannon and machine gun, 1 armed with a couple of machine guns) and 2 carden-loyd tankettes armed with a machine gun

      "The three day battle ended with the Bolivians surrounding but failing to seize Nanawa in face of growing Paraguayan forces "

      Bolivia never surrounded completely Nanawa, the lines formed a semi circle from northwest to south. Paraguayan army had around 7000 troops in the fort, while Bolivia employed about 5000 in the attack. The obvious inferiority of the attackers affected the outcome of the battle

    • perrya profile imageAUTHOR


      8 years ago

      Another interesting later battle was at Campo Via, where the Bolivian army under Gen. Kundt, was nearly surrounded.

    • mquee profile image


      8 years ago from Columbia, SC

      This is an interesting bit of history of which I had never heard. Very good! Thank you for informing and sharing.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, 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:

    Show Details
    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 or domains, for performance and efficiency reasons. (Privacy Policy)
    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)
    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.
    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)