FANDOM


Michel de Grammont
Michel de Grammont
Historical Figure
Nationality: France
Date of Birth: c. 1645
Date of Death: 1686
Cause of Death: Lost at sea, presumed drowned
Occupation: Pirate
Turtledove Appearances:
Atlantis
POD: c 85,000,000 BCE;
Relevant POD: 1452
Appearance(s): "Avalon"
Type of Appearance: Direct
Nationality: French resident of Atlantis
Date of Death: 1666
Cause of Death: Battle of the Hesperian Gulf
Michel de Grammont (born c. 1645-1686) was a French pirate. His career spanned from c.1670-1686. He and his ship were lost at sea in 1686, and he was presumed drowned.

Michel de Grammont in AtlantisEdit

Michel de Grammont (1645-1666) was a pirate captain based in Avalon. When Red Rodney Radcliffe learned that William Radcliff intended to attack the Avalon pirates, Grammont became the high captain of the fleet, mainly because he was the least disliked among his colleagues.[1]

However, Grammont was also inconsequential. He was a figurehead at best, which suited Red Rodney Radcliffe's plans.[2] During the Battle of the Hesperian Gulf, Grammont was careful not to engage his ship, the Aigle d'Argent, directly in battle.[3]

After the first day of battle, the pirate captains met aboard the Aigle d'Argent to discuss their next course of action. Most assumed that Radcliff's Armada had turned and run. The next morning proved them wrong, and the pirates fled.[4]

Avalon fell in short order to Radcliff's Armada, and Grammont was killed along with the rest of the pirates.[5]

Literary commentEdit

Given the obvious anachronisms of Goldbeard Walter Kennedy, Stede Bonnet, etc., it's possible that this Michel de Grammont is not the historical figure.

ReferencesEdit

  1. Opening Atlantis, pg. 187.
  2. Ibid., pg. 197.
  3. Ibid., pg. 227.
  4. Ibid. pgs. 231-234.
  5. This is never specifically stated, but the stakes were clear throughout.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.