13.08.2013 Views

History and genealogy of Peter Montague, of Nansemond and ...

History and genealogy of Peter Montague, of Nansemond and ...

History and genealogy of Peter Montague, of Nansemond and ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

»i* • '»*'».<br />

1 INTRODUCTION.<br />

Isl<strong>and</strong> <strong>and</strong> enjoyed it in her right many years. (Camden says it was<br />

Simon's son William who recovered the Isl<strong>and</strong>.)<br />

He had been summoned to parliament from the 28th <strong>of</strong> Edward I.<br />

to the 8th <strong>of</strong> Edwd II. (13 15), soon after which he died. Their<br />

issue was William <strong>and</strong> Simon de Montacute, the former succeeded<br />

his father <strong>and</strong> continued the line, the latter was married to Hawise,<br />

daughter <strong>of</strong> Almeric lord St. Am<strong>and</strong>.<br />

Almeric de St. Am<strong>and</strong> was a great baron <strong>of</strong> that age whose chief<br />

seat was at Grendon Underwood, a parish in the hundred <strong>of</strong> Ashendon<br />

in Buckinghamshire ten miles west N. W. from Aylesbury. The male<br />

line became extinct <strong>and</strong> the property passed (through daughters) to<br />

other families. It would seem that Simon Montacute <strong>and</strong> Hawise de<br />

St. Am<strong>and</strong>, his wife, probably had a son whose name was William<br />

Montacute from the following passage taken from a very rare <strong>and</strong><br />

ancient work.^ " From thence he (the King) passeth on to the<br />

Castle <strong>of</strong> Salisbury which Castle belonged to William Montacute<br />

Earl <strong>of</strong> Salisbury in right <strong>of</strong> his wife but himself being then prisoner<br />

in France, onely his Countesse, <strong>and</strong> one William Montacute, a cousi?i<br />

<strong>of</strong> his was in the Castle." This William Montacute, who is called a<br />

cousin <strong>of</strong> the first Earl <strong>of</strong> Salisbury, was therefore a son <strong>of</strong> Simon<br />

<strong>and</strong> Hawise (Am<strong>and</strong>) Montacute, as it is recorded that the Earl's<br />

father had only two sons. As this Simon Montacute was the<br />

younger son, his subsequent history (<strong>and</strong> that <strong>of</strong> his son William)<br />

is unrecorded.<br />

IX. William, lord <strong>of</strong> Montacute, eldest son <strong>of</strong> Sir Simon de<br />

Montacute (No. VIII.), served in several expeditions into Scotl<strong>and</strong>,<br />

both before <strong>and</strong> after his father's death, in the reigns <strong>of</strong> Edward I.<br />

<strong>and</strong> II. In the former he also received the honor <strong>of</strong> Knighthood,<br />

along with Edward prince <strong>of</strong> WT<br />

ales ; <strong>and</strong><br />

in the second year <strong>of</strong> the<br />

latter, he obtained the royal charter for free warren at his manor <strong>of</strong><br />

Aston Clinton in Buckinghamshire, as he did afterward for those <strong>of</strong><br />

Saxlingham, in the County <strong>of</strong> Norfolk, Knolle in the County <strong>of</strong> Som-<br />

erset, <strong>and</strong> Woneford in the County <strong>of</strong> Devon. In the same reign he<br />

was governor <strong>of</strong> Berhamstead Castle <strong>and</strong> steward <strong>of</strong> the King's<br />

household ;<br />

<strong>and</strong><br />

had a grant <strong>of</strong> the bodies <strong>and</strong> ransoms <strong>of</strong> Rene ap<br />

Grenon, Madock ap Vaughan <strong>and</strong> Audoen ap Madock, Welsh barons<br />

who had rebelled <strong>and</strong> been taken prisoners.<br />

* The work referred to is, "A Chronicle <strong>of</strong> the Kings <strong>of</strong> Engl<strong>and</strong> by Sir Rich d Baker,<br />

Knight." London, 1660.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!