Individual Page


Family
Marriage: Children:
  1. Nicholas De Moels: Birth: 10 Aug 1289. Death: Bef 29 Jan 1315-1306

  2. Roger Moels, Lord Moels: Birth: Abt 11 Jun 1295. Death: Bef 13 Jul 1316

  3. John De Moels, Lord Moels: Birth: Bef 17 Sep 1304 in Marnhull, Dorsetshire, England. Death: Bef 21 Aug 1337 in Maperton & Cadbury, Somerset, England


Notes
a. Note:   Note: Following copied from "Some Corrections and Additions toComplete Peerage" website: MOELS or MOELES Volume 9, page 6: He [John de Moels (d. 1310)] m., in or before 1302, Maud.(b) Note b: Cal. Patent Rolls, 1301-7, p. 53. Her parentage has notbeen ascertained. John P. Ravilious, in January 2002, pointed out that in 1311John, Lord Grey of Wilton, (d. 1323) settled by fines lands onhis younger son Roger, with successive remainders to Roger, sonof John de Moels and John and Ralph, sons of Ralph Basset ofDrayton [Complete Peerage, vol. 6, p. 153, note a]. RalphBasset of Drayton had married a daughter of John, Lord Grey, sothis evidence supports the statement of Dugdale [Baronage, p.620] that John de Moels married a daughter of Lord Grey ofRuthin (which was held, with Wilton, by John de Grey). The Roger de Moels mentioned in the fines was born "about 11June 1295" [p. 6]. Note that neither his elder brother Nicholas(b. 1289), nor his younger brother John (presumably born in1304, as he proved his age in 1325) are mentioned, which mayimply that they were children of different marriages. [This problem was also discussed by Douglas Richardson.]
b. Note:   BI147602
Note:   Sources for this Information: parents: [Ref: John Ravilious SGM 1/15/2002-022301], father: [Ref: John Ravilious SGM 12/18/2005-192820]
c. Note:   NF58391
Note:   Sources for this Information: date: before 1295 [Ref: John Ravilious SGM 12/18/2005-192820], child: [Ref: CP IX p6, CP IX p7, John Ravilious SGM 12/18/2005-151423, John Ravilious SGM 12/18/2005-192820]


RootsWeb.com is NOT responsible for the content of the GEDCOMs uploaded through the WorldConnect Program. The creator of each GEDCOM is solely responsible for its content.