ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The First Tanks in the Middle East 1917

Updated on February 2, 2010

 By mid-1917, the British situation in the Middle East was critical. Costly failures at Gallipoli in 1915 and Kut, Mesopotamia, in 1916 had stymied early British victory. Turkish forces with German commanders were proving a successful combination. Preparations for a massive assault toward Jerusalem via Gaza and Beersheba, with the aim of driving the Turks back northward, out of Palestine and Syria altogether. Gaza's history, the defeat of the Philistines by the Chaldean Babylonians in 604 BC; Crusader victories and setbacks between 1099 and 1270; the campaigns of Napoleon Bonaparte in 1799, seem to be premonition of what was to come. The first Battle of Gaza had already proven true and ended in a British fiasco and missed opportunity of momumental kind.

Two thousand gas shells and 6-8 Mk I tanks were available. While the tanks were the first in the Middle East, they were not the newest as requested, the Mark IV. Instead, the British sent the first version of the tank and were already obsolete in many ways since they debuted in 1916. Mechanically, they were even more unreliable now.

It was estimated that the Turkish forces occupying the Gaza-Beersheba defenses numbered between 20,000 and 25,000. In reality, it was almost 50,000, 86 MG, 68 guns, 18000 rifles. The defenses had been strengthened significantly since the first battle with the help of German leadership. The west flank of the line was defended by the fortress of Gaza. To the east the line was held by a series of redoubts located on ridges, with each redoubt providing support for its neighbors.

The British leaders were not impressed with the projected plan, all knew it would be a slugfest head on and bloody. The tanks, it was hoped, would cause the Turks to panic resulting in holes in the defenses to which British troops would advance. The tank detachment arrived with 22 officers and 226 men. Originally, 12 Mk I tanks were to have been sent, only eight arrived. The tanks were assigned piecemeal, that is, the 52nd Division had four, the 53rd and 54th, two each. To insure success, the British had a dazzling amount of artillery brought up some 27 artillery batteries and naval ships would also bombard. Air support would be provided by the 14th RAF (17 BE 2). In reserve, yet another division, the 74th, sat. Ironically, it was never used until the 3rd Gaza battle!

The Turks were greatly helped by the Germans in building incredible defensive systems and by the FA300 squadron with 16 Halberstadt fighters. Quickly, the RAF was shot to pieces. The Turkish 3rd Division with three regiments had 12 battalions, not the usual nine. This defended the Gaza town and surrounding area. This was further reinforced by the 163 Reg\53xx at Muntar. The ridge called Tank Redoubt, was defended by the 165 Reg\53xx and the 14th Artillery Regiment. The remaining parts of the 53rd were spread out as reserves. Their 16th division and 3rd Cav, Division were along the 14 mile frontage opposite the British Imperial and ANZAC units.

The first phase began April 17, a day when the British were allowed to advance closer to the Turks. Once complete, the British paused and resumed in earnest at 0530 on April 19. That is when all hell broke loose and despite the gas, artillery and tanks, the Brits were simply battering their head against the wall.  None of the objectives were achieved and the tanks found tough going attracting the wrath of artillery guns whose barrels were lowered and fired direct as an antitank weapon. Even without any AP shells, any hit on the tank would disable it. The Turks, in most case, did not throw down the weapons and run. When it did happen, Turk artillery honed in on the tanks. British success could only be measured in yards and by 1500, artillery fire was limited due to lack of shells. By 1830, the folly was over and over 6000 British bodies showed for it. Turkish losses came to 2300.


    0 of 8192 characters used
    Post Comment

    No comments yet.


    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)
    ClickscoThis is a data management platform studying reader behavior (Privacy Policy)