Legal Opinion

Gilmanton v. Sanbornton

Supreme Court of New Hampshire

Decided March 20, 1876PublishedCited by 2 opinions

From Belkkai? Circuit Court. Assumpsít. The case was referred to a referee, who reported that the action was brought to recover of Sanbornton for aid rendered by Gilmanton to one Ebenezer Chase for the support of John Chase, between December 10, 1874, and June 14, 1875, the expenditures amounting to $47. Notice of the expenditure was duly given to Sanbornton.

Read the full summary

From Belkkai? Circuit Court. Assumpsít. The case was referred to a referee, who reported that the action was brought to recover of Sanbornton for aid rendered by Gilmanton to one Ebenezer Chase for the support of John Chase, between December 10, 1874, and June 14, 1875, the expenditures amounting to $47. Notice of the expenditure was duly given to Sanbornton. Ebenezer Chase, the father of John Chase, now 78 years of age, resided in Sanbornton prior to 1840, and from that time to December, 1868, when he removed to Gilmanton. John Chase, the son, for whose support the action is brought, is now…

1Opinion of the Court

FROM BELKNAP CIRCUIT COURT. It appears, from the statement of facts in this case that Ebenezer Chase, between the years 1840 and 1846, resided in Sanbornton, and during that time was the owner of sufficient property, and paid taxes thereon, to gain a settlement. The case does not show that Ebenezer Chase had gained a settlement in Sanbornton prior to 1840, so that, under the present law, settlements might be derived from his settlement.

John Chase, for whose support this action was brought, would, therefore, by derivation, have the settlement of his father, Ebenezer Chase, in Sanbornton,…

2Cases cited1 opinion

  1. Town of Croydon v. County of SullivanSupreme Court of New Hampshire · 1866

3Cited by2 opinions

  1. Langevin v. Hillsborough CountySupreme Court of New Hampshire · 1974
  2. Belknap County v. Carroll CountySupreme Court of New Hampshire · 1940

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API