Opposition · USPTO

Opposition 91220017

OtherUSPTO

Opposition 91220017 at USPTO between JetBlue Airways Corporation and JetBlack Aviation, Inc., over the mark JETBLACK LISTED. SOLD., filed Jan 5, 2015. Status in the office record: other.

View JETBLACK LISTED. SOLD.Get this data via the API
Status
Other
Result
Other
Filed
Jan 5, 2015
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

JetBlue Airways Corporation

Company trademarks
Respondent

JetBlack Aviation, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the JETBLACK LISTED. SOLD. filing.

  1. JETBLACK LISTED. SOLD. filed

    Application 85665063 filed at the USPTO.

  2. Opposition filed

    JetBlue Airways Corporation started opposition 91220017 at USPTO against JETBLACK LISTED. SOLD..
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
JETBLACK LISTED. SOLD.Contested85665063USPTO
JETBLUE AIRWAYSRelied on75746534USPTO
JETBLUERelied on75746535USPTO
JETBLUERelied on76593680USPTO
JETBLUERelied on76593681USPTO
JETBLUERelied on85680540USPTO
JETBLUE MINTRelied on86054364USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_520190b7-b7ea-4a6b-8a6e-f5b88b6e21de
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_520190b7-b7ea-4a6b-8a6e-f5b88b6e21de",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91220017",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-01-05",
  "parties": [
    {
      "name": "JetBlue Airways Corporation",
      "role": "opponent"
    },
    {
      "name": "JetBlack Aviation, Inc.",
      "role": "respondent"
    }
  ]
}