ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

World One War: Seizing Turkey's Dreadnoughts

Updated on May 3, 2011
Photograph of British battleship HMS Erin (formerly the Reshadieh), photographed circa. 1912-1922
Photograph of British battleship HMS Erin (formerly the Reshadieh), photographed circa. 1912-1922
Drawing showing the transformation from the Ottoman 'Reshadieh' to HMS Erin
Drawing showing the transformation from the Ottoman 'Reshadieh' to HMS Erin
HMS Agincourt, photograph showing the design of the ship which was to be delivered to the Ottoman Empire
HMS Agincourt, photograph showing the design of the ship which was to be delivered to the Ottoman Empire
HMS Agincourt, formerly the 'Sultan Osman I'
HMS Agincourt, formerly the 'Sultan Osman I'

At the outbreak of war in 1914, Ottoman Turkey received a vital blow when two Dreadnoughts destined for Turkey, were seized by the Royal Navy.

The first ship, ‘Rio de Janeiro’, as HMS Agincourt was first known, was laid down on the 14th of September 1911 by Armstrong’s in Newcastle-upon-Tyne and launched in 1913.  The ship was ordered due to an arms race in South America between Brazil, Argentina and Chile.  Brazil wished to purchase a capital ship which would outclass any vessel which either Chile or Argentina could build or purchase.

Despite this, the rubber trade in Brazil, on which Brazil was reliant, collapsed.  Thus the vessel was placed on the market on October 1913.  The Ottoman Navy bought the vessel for £2,750,000 on the 28th December 1913.  Subsequently re-named the Sultan Osman I, the vessel underwent sea trials and was completed upon the outbreak of war in August 1914.

In regard to the second Dreadnought, HMS Erin was ordered by the Ottoman Navy under the name Reshhad, but was renamed Reshadieh during its completion.  Originally laid down by the Vickers Company in 1911, the Reshadieh was launched on the 3rd of September 1913 and completed, like the Agincourt, at the outbreak of war in August 1914.  The Ottoman Navy’s intention was to acquire a surface ship which was equal to any Western Navy ship afloat at that time.  The initial design was based on the King George V, but featured aspects of HMS Iron Duke.

When war broke out in August 1914, although the Ottoman crew had arrived to collect the ‘Sultan Osman I’, the British Government seized the vessel.  During the same period the ‘Reshadieh’ was seized and renamed Erin.

The British Governments actions were stipulated within the signed contracts as the then First Lord of the Admiralty, Winston Churchill, did not want the ships to be used against Great Britain.  Despite Churchill’s intentions, there were severe consequences.

Since the armistice of 1918, it has been argued that the seizing of the ‘Erin’ and ‘Agincourt’ were pivotal in bringing the Ottoman Empire into war on the side of Germany and Austro-Hungary.  The take-over itself caused considerable ill-feeling within the Ottoman Empire where public donations partially funded the ships.  When the Ottoman government had been financially unable to fund the ships, the people’s donations were taken.  In order to encourage the donation campaign, a medal was presented to high donations tilted “The Navy Donation Medal”.  The fundraising and subsequent loss of both ships proved to0 be a crucial factor in turning Turkey against the allies.

In terms of Royal Naval Service and modifications made, the ‘Agincourt’ was a bit of a problem for the Royal Navy.  The Admiralty was unprepared to man a ship of Agincourt’s size on such short notice, thus the crew came from the highest and lowest ‘ranks’ of the admiralty.

‘Agincourt’ was formally accepted into the Royal Navy on the 7th of September 1914 and saw very little action throughout the war.  Despite this, ‘Agincourt’ was present at the surrender of the German High Seas Fleet on the 21st of November 1918.

In looking at the ‘Erin’, she joined the Fleet on September 5th 1914 and was stationed at Scapa Flow.  The ship was present at the Battle of Jutland and remained with the Fleet for the remainder of the war.  Following the armistice, in October 1919 she was placed in reserve at the Nore, and from December of that year served as a turret drill ship at Chatham Dockyard.

For complete, detailed and factual ship lists of the Navies of the First World War, check out DUGOUT WW1 and sign up to get your FREE EDITION BELOW

http://www.worldonewar.com

http://www.worldonewar.com/world-one-war-blog

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)