History revisited

A hundred years ago, Indian soldiers in a WWI siege chose death over horsemeat

The British Indian Army suffered many miseries in Kut in Iraq. Starvation was one.

Kut Al-Amara was an unremarkable town nestled in a bend in the Tigris river, in what is today Iraq. Its history was thin, virtually non-existent, until it became the place of a great military defeat.

On April 29, 1916, approximately 13,000 starving Indians and Britons trapped inside the town gave themselves up to the Ottoman army. They had been under siege for nearly five months, during which they had braved enemy fire, loss of comrades and gnawing hunger. For their ambitious commander, Major General Charles Townshend, it was a career-ending humiliation, but for many of the ordinary Indian soldiers the surrender meant much worse: they would never see their homes again.

The path to Kut

The first Indian soldiers landed in Mesopotamia to take part in World War I in November 1914, a day after Britain declared war on the Ottoman Empire. By the next year, the Indian Army’s 6th Division headed by Charles Townshend was fighting its way up the Tigris River towards Baghdad, notching a string of easy victories.

In late November, the 6th Division reached Ctesiphon, where the Ottomans had anchored their formidable defences around the ancient ruins of an arched gateway. Three days of savage fighting followed but Townshend’s outnumbered army failed to evict the Ottomans.

With the Ottomans in pursuit, the 6th Division conducted a fighting retreat, reaching Kut on December 3. It was here that Townshend fatefully decided to make a stand with his 15,000 soldiers and civilian staff.

Major General Charles Townshend. Credit: Wikimedia Commons
Major General Charles Townshend. Credit: Wikimedia Commons

Kut was, in the words of one historian, “an unbeguiling place to be stuck in”. A warren of mud houses and narrow streets, it had just 6,000 inhabitants. The Tigris enveloped the town on three sides like a moat, so the men of the 6th Division quickly began digging trenches on the exposed northern end.

The Ottomans surrounded Kut on December 7 and launched a series of attacks, all of which the 6th Division beat off, leaving the ground outside the town littered with Turkish dead and wounded.

The Ottomans then changed tactics. Instead of trying to storm Kut, they would strangle it.

The looping Tigris turned into Kut’s noose as Ottoman soldiers moved downriver and fought off repeated attempts by the British forces to relieve the town. In the meantime, they continued to shell Kut and sweep it with machine gun fire, later graduating to air bombardment.

Sisir Sarbadhikari, a civilian with the Bengal Ambulance Corps, described the horrors in his extraordinary memoir, excerpts from which have been translated by the author Amitav Ghosh:

“One shell, instead of bursting above, hit a sepoy who was lying in bed, in one of the tents; it took off half his face before burying itself. The man rose to his feet as he was dying and then fell to the ground.”

Starvation deaths

Enemy fire was not the only killer. Food supplies were running out and, with no relief force in sight, Townshend cut rations by half in late January 1916. Their food would last three months, but only if his men took to eating the horses and mules that served as the 6th Division’s pack animals.

The first ration of horsemeat was issued on January 28, but the Indian soldiers refused to touch it. They were given an extra ration of atta in its stead, but this was meagre allowance, “just enough to keep the garrison alive,” as one British officer put it.

Townshend tried to allay what he presumed were his sepoys’ religious scruples by obtaining approval for eating horsemeat from the Imam of Delhi’s Jama Masjid and a “leading Pandit”.

It was not religious dogma, however, that had united Hindu, Muslim and Sikh soldiers against horseflesh – it was fear of social ostracism. As a lieutenant with the 66th Punjabis observed, the men “declared that every village pundit would be against them on their return to India and that… no one would give them their daughters to marry”.

Malnutrition began to reduce soldiers to sickly skeletal figures. Beds at Kut’s makeshift hospital began to fill up with sepoys afflicted by scurvy, jaundice and pneumonia.

The Siege of Kut Al Amara. Credit: Wikimedia Commons
The Siege of Kut Al Amara. Credit: Wikimedia Commons

“There were instances of Indians returning from trench duty in the evening seemingly with nothing the matter who lay down and were found dead in the morning,” a British medical officer recalled.

Some soldiers sought to escape their misery by attempting suicide. One Briton saw “a young sepoy who had put the muzzle of his loaded rifle against his stomach and discharged it with his toe”. Another saw Indian soldiers who would “walk to the river bank, stand with folded arms, and wait for an enemy sniper to shoot them”.

As desperation mounted, Townshend finally acted. On April 12, he gave his Indian officers and non-commissioned officers an ultimatum: eat horsemeat or be replaced by someone who would.

Faced with the threat of losing their hard won ranks, the Indian officers and non-commissioned officers took horsemeat, setting an example for their men, who lost their fear of becoming social outcasts. Within the next two days, most sepoys were consuming what little horsemeat was left.

Rescue attempts

While Kut starved, its would-be rescuers bled. British forces had been fighting the Ottomans continuously since the beginning of 1916. By the end of March they had suffered 23,000 wounded and killed but had still failed to relieve Kut.

In early April, a British intelligence officer, Captain TE Lawrence (who would go on to be immortalised as Lawrence of Arabia) tried to encourage a rebellion among the Arabs of the Euphrates that might divert Ottoman troops away from Kut. He failed.

TE Lawrence. Credit: Wikimedia Commons
TE Lawrence. Credit: Wikimedia Commons

The British then carried out what was likely the first air supply operation in history, using planes to drop sacks of provisions for the 6th Division. However, many sacks fell into Ottoman lines or splashed into the Tigris. In any case, they were too meagre to matter.

On April 24, the steamer Julnar, loaded with supplies, sailed towards Kut, running the gauntlet of enemy fire until it was stopped by a cable the Ottomans had laid across the river. By now Kut was out of options and food. Townshend began negotiations with the Ottomans. The surrender came on the morning of April 29.

By midday, Ottoman troops began streaming into the town. British and Indian officers were loaded onto steamers to Baghdad from where they were transported into the Turkish heartland for the rest of the war.

Ordinary sepoys were not so lucky. Though starving and weak, they would be marched across the desert where any unfortunate stragglers would be pounced upon by the Bedouin. Most were taken to Ras al-Ayn in modern Syria, where they were put to work on a railroad. Few survived.

Sarbadhikari found himself a prisoner of war in Turkey, where he would get into conversations with locals who wondered why they were fighting each other. “You live in Hindustan, we live in Turkey, neither of us have ever met, we have no quarrel with each other, but at the behest of a couple of men we’ve become enemies overnight.” He wondered: “Is this what’s in the heart of every soldier, in every country, at all times?”

Charles Townshend with Khalil Pasha after the fall of Kut. Credit: Wikimedia Commons
Charles Townshend with Khalil Pasha after the fall of Kut. Credit: Wikimedia Commons
We welcome your comments at letters@scroll.in.
Sponsored Content BY 

The ordeal of choosing the right data pack for your connectivity needs

"Your data has been activated." <10 seconds later> "You have crossed your data limit."

The internet is an amazing space where you can watch a donkey playing football while simultaneously looking up whether the mole on your elbow is a symptom of a terminal diseases. It’s as busy as it’s big with at least 2.96 billion pages in the indexed web and over 40,000 Google search queries processed every second. If you have access to this vast expanse of information through your mobile, then you’re probably on something known as a data plan.

However, data plans or data packs are a lot like prescription pills. You need to go through a barrage of perplexing words to understand what they really do. Not to mention the call from the telecom company rattling on at 400 words per minute about a life-changing data pack which is as undecipherable as reading a doctor’s handwriting on the prescription. On top of it all, most data packs expect you to solve complex algorithms on permutations to figure out which one is the right one.

Source: giphy.com
Source: giphy.com

Even the most sophisticated and evolved beings of the digital era would agree that choosing a data pack is a lot like getting stuck on a seesaw, struggling to find the right balance between getting the most out of your data and not paying for more than you need. Running out of data is frustrating, but losing the data that you paid for but couldn’t use during a busy month is outright infuriating. Shouldn’t your unused data be rolled over to the next month?

You peruse the advice available online on how to go about choosing the right data pack, most of which talks about understanding your own data usage. Armed with wisdom, you escape to your mind palace, Sherlock style, and review your access to Wifi zones, the size of the websites you regularly visit, the number of emails you send and receive, even the number of cat videos you watch. You somehow manage to figure out your daily usage which you multiply by 30 and there it is. All you need to do now is find the appropriate data pack.

Promptly ignoring the above calculations, you fall for unlimited data plans with an “all you can eat” buffet style data offering. You immediately text a code to the telecom company to activate this portal to unlimited video calls, selfies, instastories, snapchats – sky is the limit. You tell all your friends and colleagues about the genius new plan you have and how you’ve been watching funny sloth videos on YouTube all day, well, because you CAN!

Source: giphy.com
Source: giphy.com

Alas, after a day of reign, you realise that your phone has run out of data. Anyone who has suffered the terms and conditions of unlimited data packs knows the importance of reading the fine print before committing yourself to one. Some plans place limits on video quality to 480p on mobile phones, some limit the speed after reaching a mark mentioned in the fine print. Is it too much to ask for a plan that lets us binge on our favourite shows on Amazon Prime, unconditionally?

You find yourself stuck in an endless loop of estimating your data usage, figuring out how you crossed your data limit and arguing with customer care about your sky-high phone bill. Exasperated, you somehow muster up the strength to do it all over again and decide to browse for more data packs. Regrettably, the website wont load on your mobile because of expired data.

Source: giphy.com
Source: giphy.com

Getting the right data plan shouldn’t be this complicated a decision. Instead of getting confused by the numerous offers, focus on your usage and guide yourself out of the maze by having a clear idea of what you want. And if all you want is to enjoy unlimited calls with friends and uninterrupted Snapchat, then you know exactly what to look for in a plan.

Source: giphy.com
Source: giphy.com

The Airtel Postpaid at Rs. 499 comes closest to a plan that is up front with its offerings, making it easy to choose exactly what you need. One of the best-selling Airtel Postpaid plans, the Rs. 499 pack offers 40 GB 3G/4G data that you can carry forward to the next bill cycle if unused. The pack also offers a one year subscription to Amazon Prime on the Airtel TV app.

So, next time, don’t let your frustration get the better of you. Click here to find a plan that’s right for you.

Source: giphy.com
Source: giphy.com

This article was produced by the Scroll marketing team on behalf of Airtel and not by the Scroll editorial team.