HMS Somerset (1731)

HMS Somerset was an 80-gun third rate ship of the line of the Royal Navy, built to the 1719 Establishment at Woolwich and launched on 21 October 1731.[1] She was the second ship to bear the name.

History
Great Britain
Name: HMS Somerset
Ordered: 23 December 1725
Builder: Woolwich Dockyard
Launched: 21 October 1731
Honours and
awards:
Fate: Broken up, 1746
General characteristics [1]
Class and type: 1719 Establishment 80-gun third rate ship of the line
Tons burthen: 1,354 long tons (1,375.7 t)
Length: 158 ft (48 m) (gundeck)
Beam: 44 ft 6 in (13.56 m)
Depth of hold: 18 ft 2 in (5.54 m)
Propulsion: Sails
Sail plan: Full rigged ship
Armament:
  • 80 guns:
  • Gundeck: 26 × 32 pdrs
  • Middle gundeck: 26 × 12 pdrs
  • Upper gundeck: 24 × 6 pdrs
  • Quarterdeck: 4 × 6 pdrs

Lord George Rodney, later to triumph at the Battle of the Saintes in 1782, served on HMS Somerset in 1739 while preparing for his Lieutenant’s exams. The ship saw action at the Battle of Toulon in 1744. Toulon was an infamous engagement and consequently no battle honour was awarded. A combined Franco-Spanish fleet that had been blockaded in Toulon for two years finally put to sea, led by Admiral de Court de La Bruyère. The blockading British fleet under Admiral Thomas Mathews was roughly the same size as the Franco-Spanish fleet but fearing that the enemy fleet movement was designed to force him out of position and allow a troop convoy to reach Italy, Mathews ordered his fleet to attack before forming up into line. Admiral Richard Lestock, Mathew’s second in command, appears to have deliberately misunderstood his orders, and the resulting battle was indecisive, with the British taking more damage than they inflicted. Mathews was dismissed from the Navy for failing to obey permanent fighting instructions for battle.

Somerset was broken up in 1746.[1]

Notes

  1. Lavery, Ships of the Line vol.1, p169.
gollark: Row ID? I forget.
gollark: The number the uninstaller prints?
gollark: The incident report system does actually work, by the way. All incidents are logged in SPUDNET. The only ones I know of are the test ones I triggered to test the system and various incident triggers. Incidents are reported when:- one known sandbox escape is detected- banned programs (Webicity) are executed- potatOS is uninstalled- invalid disk signing key
gollark: You can't make a program to fully autonomously uninstall potatOS from within it - ignoring sandbox escapes - because while sandboxed processes can use queueEvent to fake keypresses they cannot read the output of the uninstaller. The best they can do is, I don't know, guess what the random seed was when it was generating two primes, figure out what the primes were, and queue the key/char events accordingly.
gollark: <@184468521042968577> `is_valid_lua` isn't deliberately bad, but it's also IIRC not actually used anywhere.Also, that person was bundling potatOS with some other project but wanted people to be able to remove it even more easily if they don't like it. This feature does actually work but must be enabled before installation. Weirdly enough factorizing small semiprimes is beyond many users.

References

  • Lavery, Brian (2003) The Ship of the Line - Volume 1: The development of the battlefleet 1650-1850. Conway Maritime Press. ISBN 0-85177-252-8.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.