Legal Opinion

Clevite Corporation v. The United States

United States Court of Claims

Decided November 9, 1967No. 70-64PublishedCited by 11 opinions

1Opinion of the Court

OPINION

2Per curiam

This case was referred to Chief Trial Commissioner Marion T. Bennett, with directions to make findings of fact and recommendation for conclusions of law. The commissioner has done so in an opinion and report filed on December 20, 1966. Exceptions were filed by plaintiff and the case was submitted to the court on the briefs of the parties and oral argu- xnent of counsel. Since the court is in agreement with the opinion, findings, and recommended conclusion of law of the commissioner, as hereinafter set forth, it hereby adopts the same as the basis for its judgment in this case.…

3Cases cited9 opinions

  1. United States v. AndersonSupreme Court of the United States · 1926
  2. United States v. Consolidated Edison Co. of NYSupreme Court of the United States · 1961
  3. Champion Spark Plug Co. v. CommissionerUnited States Tax Court · 1958
  4. Commissioner of Internal Revenue v. Champion Spark Plug CompanyCourt of Appeals for the Sixth Circuit · 1959
  5. John Wanamaker Philadelphia, Inc. v. The United States. John Wanamaker Philadelphia, Inc. (Successor by Merger to John Wanamaker New York, Inc.) v. The United StatesUnited States Court of Claims · 1966

4 more not listed; retrieve them via the Exa API.

4Cited by11 opinions

  1. Putoma Corp., Successor by Merger of Pro-Mac Company, Petitioners- Cross-Appellants v. Commissioner of Internal Revenue, Cross-AppelleeCourt of Appeals for the Fifth Circuit · 1979
  2. The Washington Post Company v. The United StatesUnited States Court of Claims · 1969
  3. Union Pacific Railroad v. United StatesUnited States Court of Claims · 1975
  4. Baker v. United StatesUnited States Court of Claims · 1980
  5. Bennett Paper Corp. & Subsidiaries v. CommissionerUnited States Tax Court · 1982

6 more not listed; retrieve them via the Exa API.

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

Powered by the Exa API