French ship Mont-Blanc (1791)

Mont-Blanc was a Téméraire class 74-gun third-rate ship of the line of the French Navy. In the course of her career, she was renamed no less than four times, reflecting the tides of politics with the French Revolution.

The Mont-Blanc off Marseille (detail of this image), by Antoine Roux.
History
France
Name: Pyrrhus[1]
Namesake:
Builder: Rochefort[1]
Laid down: 1791[1]
Renamed:
  • Mont-Blanc on 7 January 1793
  • Trente-et-un Mai on 7 April 1794
  • Républicain on 18 April 1795
  • Mont-Blanc on 4 January 1796
Captured: 4 November 1805[1]
United Kingdom
Name: Mont-Blanc
Acquired: by capture, 4 November 1805[1]
Fate:
General characteristics [2]
Class and type: Téméraire-class ship of the line
Displacement:
Length: 55.87 metres (183.3 ft) (172 pied)[1]
Beam: 14.90 metres (48 ft 11 in)[1]
Draught: 7.26 metres (23.8 ft) (22 pied)[1]
Propulsion: Up to 2,485 m2 (26,750 sq ft) of sails[1]
Armament:
Armour: Timber

During the Wars of the First and Second Coalitions, Mont-Blanc took part in the last actions of the Glorious First of June, in the Croisière du Grand Hiver, in the Battle of Hyères Islands and in Bruix' expedition of 1799; after peace was restored in the Treaty of Lunéville, she served during the Saint-Domingue expedition.

Mont-Blanc took part of the vanguard of the French fleet the Battle of Trafalgar on 21 October 1805, and consequently saw little action as this division was cut off from the battle. The squadron was destroyed during the Battle of Cape Ortegal on 4 November 1805, where Mont-Blanc was captured. She was recommissioned in the Royal Navy but never saw action again.

Career

She was built at Rochefort as Pyrrhus in 1791.[1] She was renamed Mont-Blanc in 1793 before being renamed Trente-et-un Mai in 1794. Under that name she fought at the Glorious First of June in 1794 under Captain Ganteaume.[1] She took part in the Croisière du Grand Hiver, where she rescued the crew of the sinking Scipion.[1][3]

In 1795 she was renamed Républicain, taking part in the Battle of Hyères Islands,[3] and Ganteaume's expedition of 1795, and then became Mont-Blanc again in 1796. She took part in Bruix' expedition of 1799 under Captain Maistral.[1]

In 1802 she took part in the Saint-Domingue expedition under Magon.[1]

She was one of the ships of Rear-Admiral Lepelley at the Battle of Trafalgar on 21 October 1805. Dumanoir commanded the six ship vanguard of the French fleet, with Formidable, Scipion, Duguay-Trouin, Mont-Blanc, Intrépide and Neptune. Nelson's attacks left these ships downwind of the main confrontation and Dumanoir did not immediately obey Villeneuve's orders to return to the battle. When the ships did turn back, most of them only exchanged a few shots before retiring.[1]

On 4 November 1805, Admiral Sir Richard Strachan, with HMS Caesar, Hero, Courageux, Namur and four frigates, defeated and captured what remained of the squadron at the Battle of Cape Ortegal.[1]

Mont-Blanc was taken and commissioned in the Royal Navy as HMS Mont Blanc. She was used as a gunpowder hulk from 1811, and was sold in 1819.[1]

Notes and references

Notes

    References

    1. Roche, p.313-314
    2. Clouet, Alain (2007). "La marine de Napoléon III : classe Téméraire - caractéristiques". dossiersmarine.free.fr (in French). Archived from the original on 23 March 2013. Retrieved 4 April 2013.
    3. Levot, p.207

    Bibliography

    gollark: This person apparently reverse-engineered it statically, not at runtime, but it *can* probably detect if you're trying to reverse-engineer it a bit while running.
    gollark: > > App behavior changes slightly if they know you're trying to figure out what they're doing> this sentence makes no sense to me, "if they know"? he's dissecting the code as per his own statement, thus looking at rows of text in various format. the app isn't running - so how can it change? does the app have self-awareness? this sounds like something out of a bad sci-fi movie from the 90's.It's totally possible for applications to detect and resist being debugged a bit.
    gollark: > this is standard programming dogma, detailed logging takes a lot of space and typically you enable logging on the fly on clients to catch errors. this is literally cookie cutter "how to build apps 101", and not scary. or, phrased differently, is it scary if all of that logging was always on? obviously not as it's agreed upon and detailed in TikTok's privacy policy (really), so why is it scary that there's an on and off switch?This is them saying that remotely configurable logging is fine and normal; I don't think them being able to arbitrarily gather more data is good.
    gollark: > on the topic of setting up a proxy server - it's a very standard practice to transcode and buffer media via a server, they have simply reversed the roles here by having server and client on the client, which makes sense as transcoding is very intensive CPU-wise, which means they have distributed that power requirement to the end user's devices instead of having to have servers capable of transcoding millions of videos.Transcoding media locally is not the same as having some sort of locally running *server* to do it.
    gollark: That doesn't mean it's actually always what happens.
    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.