Legal Opinion

Otis v. United States

United States Court of Claims

Decided May 11, 1885No. 14245PublishedCited by 4 opinions

The Reporters’ statement of the case: • The following are the facts as found by the court: I. The defendants advertised for carrying the mails in New York City as follows : - ' “ Mail-station service, New Yorlc City.

Read the full summary

The Reporters’ statement of the case: • The following are the facts as found by the court: I. The defendants advertised for carrying the mails in New York City as follows : - ' “ Mail-station service, New Yorlc City. “ Post-Ofeice Department, “ Washington, March 1,1877. “ Proposals will be received at the contract office of this department until 3 p. m. of April 7, 1877 (to be decided on or before the 10th of April following), for carrying the mails of the United States from July 1, 1877, to June 30,1881, in the city of New York, as herein specified.” (Route No. 6636, R., p. 12.) Which, after…

1Opinion of the CourtDavis, J.

In the spring of 1877 the claimant contracted to transport the mails between the United States post-office in New York City and various railroad stations and steamboat landings, and also to transfer certain through mails from one railroad station to another. The route covered by this agreement was known as No. 6635. The contract ran for four years from July 1, 1877, and the service was designated “ mail-messenger service in the city of New York.” Among other things the claimant agreed in this contract to carry the mails from the city post-office “ to the Pennsylvania Railroad depot (foot of…

2Cases cited1 opinion

  1. Gibbons v. United StatesUnited States Court of Claims · 1879

3Cited by4 opinions

  1. Sheridan-Kirk Contract Co. v. United StatesUnited States Court of Claims · 1917
  2. Halstead v. United StatesUnited States Court of Claims · 1920
  3. Slavens v. United StatesUnited States Court of Claims · 1903
  4. Woolverton v. United StatesUnited States Court of Claims · 1892

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

Powered by the Exa API