Legal Opinion

In Re FMC Corp. Patent Litigation

United States Judicial Panel on Multidistrict Litigation

Decided November 22, 1976No. 255PublishedCited by 36 opinions

1Opinion of the Court

OPINION AND ORDER

2Per curiam

This litigation consists of five actions pending in three different federal districts — two each in the District of Kansas and the Eastern District of Wisconsin, and one in the Northern District of Ohio. All the actions involve the validity and alleged infringement of a single patent, No. 3,875,-607, the rights to which are held by FMC Corporation. The patent relates to the construction of a gutter brush used in street sweeping machines, and to wear-replacement parts for this brush. FMC, through its Industrial Brush Division, manufactures street sweepers, and brushes and…

3Cases cited6 opinions

  1. In Re Smith Patent LitigationUnited States Judicial Panel on Multidistrict Litigation · 1976
  2. In Re Griseofulvin Antitrust LitigationUnited States Judicial Panel on Multidistrict Litigation · 1975
  3. In Re Sugar Industry Antitrust LitigationUnited States Judicial Panel on Multidistrict Litigation · 1975
  4. In re Revenue Properties Co.United States Judicial Panel on Multidistrict Litigation · 1970
  5. In re Plumbing Fixture CasesUnited States Judicial Panel on Multidistrict Litigation · 1968

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

4Cited by36 opinions

  1. In Re "Agent Orange" Product Liability Litigation Mdl No. 381Court of Appeals for the Second Circuit · 1987
  2. In Re KOREAN AIR LINES DISASTER OF SEPTEMBER 1, 1983. Appeal of Plaintiffs Steering CommitteeCourt of Appeals for the D.C. Circuit · 1987
  3. Laura Canaday v. The Anthem Companies, Inc.Court of Appeals for the Sixth Circuit · 2021
  4. In re Upjohn Co. Antibiotic Cleocin Products Liability LitigationDistrict Court, E.D. Michigan · 1979
  5. In Re Telectronics Pacing Systems, Inc.District Court, S.D. Ohio · 1997

31 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