Jump to ContentJump to Main Navigation
Sparta's Second Attic WarThe Grand Strategy of Classical Sparta, 446-418 B.C.$
Users without a subscription are not able to see the full content.

Paul A. Rahe

Print publication date: 2020

Print ISBN-13: 9780300242621

Published to Yale Scholarship Online: January 2021

DOI: 10.12987/yale/9780300242621.001.0001

Show Summary Details
Page of

PRINTED FROM YALE SCHOLARSHIP ONLINE (www.yale.universitypressscholarship.com). (c) Copyright Yale University Press, 2021. All Rights Reserved. An individual user may print out a PDF of a single chapter of a monograph in YSO for personal use.date: 17 September 2021

Lacedaemon at Bay

Lacedaemon at Bay

(p.163) Chapter 5 Lacedaemon at Bay
Sparta's Second Attic War

Paul A. Rahe

Yale University Press

This chapter talks about the Lacedaemonian and allied Peloponnesian's defeat in Navarino Bay. It investigates the Spartans' local truce with the Athenian generals and negotiations for a peace agreement in order to recover their infantry men and safeguard the men trapped on Sphacteria. The chapter also mentions how Spartans suffered additional and catastrophic losses at the time of the plague. It points out how the Spartans negotiated a peace agreement with Argos in 420 that included an unprecedented clause contemplating the possibility that one or the other community might succumb to an epidemic. It also highlights the Peloponnesians' repeated attempts to assert their preeminence at sea in the Corinthian Gulf, the Ionian Sea, and the Adriatic, which had failed ignominiously.

Keywords:   Lacedaemonian, Peloponnesian, Navarino Bay, Spartans, Athenian, Sphacteria, peace agreement, Argos

Yale Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs , and if you can't find the answer there, please contact us.