Opposition · USPTO

Opposition 91289444

OtherUSPTO

Opposition 91289444 at USPTO between Hexcel Corporation and HexcelPack LLC, over the mark HEXCEL PACK, filed Jan 25, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Jan 25, 2024
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Hexcel Corporation

Company trademarks
Respondent

HexcelPack LLC

Timeline

How the case has moved

Dates from the USPTO record and the HEXCEL PACK filing.

  1. HEXCEL PACK filed

    Application 97820687 filed at the USPTO.
  2. Opposition filed

    Hexcel Corporation started opposition 91289444 at USPTO against HEXCEL PACK.
Marks

Marks involved

5 contested marks, 13 marks the challenger relies on.

MarkRoleApplicationOffice
HEXCEL PACKContested97820687USPTO
HEXCELWRAPContested97820700USPTO
HEXCELSTRETCHContested97820808USPTO
HEXCELSHEETSContested97820818USPTO
HEXCELContested97820858USPTO
HEXCELRelied on73527619USPTO
HEXCELRelied on76321379USPTO
HEXCELRelied on76349442USPTO
HEXCELRelied on78729937USPTO
HEXCEL OFFICIAL DISTRIBUTORRelied on87702877USPTO
HEXCELRelied on97210274USPTO
HEXCELRelied on97212689USPTO

+6 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

GET /v1/proceedings/{id}
ID=prc_a44f2dd0-112b-44d7-bac5-e26d02d4a96e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a44f2dd0-112b-44d7-bac5-e26d02d4a96e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91289444",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-01-25",
  "parties": [
    {
      "name": "Hexcel Corporation",
      "role": "opponent"
    },
    {
      "name": "HexcelPack LLC",
      "role": "respondent"
    }
  ]
}