Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
Railware v. Amtrak: Railroad Dispatch & Traffic Control Patent Dispute | PatSnap
Explore in Eureka
Case ID1:22-cv-05013
FiledJun 2022
ClosedJun 2024
Patent Litigation

Railware v. Amtrak: Three Railroad Dispatch Patents, 730 Days, Settled

Railware, Inc. brought a patent infringement action against National Railroad Passenger Corporation (Amtrak) in the Southern District of New York, asserting three patents covering railroad dispatch and centralized traffic control systems — including two reissue patents — against Amtrak’s AMTEC systems and the Rockwell Collins ARINC RailwayNet/AIM platform. The parties reached a settlement in principle exactly two years after filing.

Resolution time
730days
730 days from filing to settlement — a full two-year litigation cycle in S.D.N.Y.
Patents asserted
3
USRE049115E, USRE047835E, and US9517782B2 — railroad dispatch and centralized traffic control systems
Outcome
Dismissed without Prejudice
Conditionally discontinued without prejudice; settlement in principle reported June 14, 2024.
Cost ruling
No Cost Order
Court ordered discontinuance without costs to either party.
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Railware pursues Amtrak over reissue patents in railroad dispatch tech

Railware, Inc. filed suit against the National Railroad Passenger Corporation (Amtrak) on June 15, 2022, in the U.S. District Court for the Southern District of New York. The complaint asserted infringement of three patents — USRE049115E, USRE047835E, and US9517782B2 — directed at railroad dispatch and centralized traffic control systems. The accused products included Amtrak’s proprietary AMTEC dispatch and centralized traffic control systems, as well as the Rockwell Collins ARINC RailwayNet/AIM platform deployed within Amtrak’s operations.

Exactly 730 days after filing, on June 14, 2024, the parties jointly reported to the court that they had reached a settlement in principle. The court conditionally discontinued the action without prejudice and without costs, issuing a 30-day window for the parties to submit a formal Stipulation of Settlement and Dismissal. If no formal stipulation was filed and Railware did not move to restore the action, the order would convert to a final discontinuance with prejudice by operation of its own terms — a structured conditional mechanism common in S.D.N.Y. commercial settlements.

A two-year litigation timeline without a merits ruling suggests the parties likely engaged in substantial discovery and claim-construction proceedings before reaching commercial resolution. The involvement of two reissue patents — which by definition have already passed through USPTO reexamination — may have strengthened Railware’s negotiating position. Financial terms, licensing structure, and any ongoing operational arrangements between the parties remain undisclosed in the public record.

Case at a glance
Case no.1:22-cv-05013
CourtNew York Southern
JudgeN/A
FiledJune 15, 2022
ClosedJune 14, 2024
Duration730 days
OutcomeDismissed without Prejudice
Verdict causeInfringement Action
BasisDismissed without Prejudice
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / New York Southern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Dismissed without Prejudice in 730 days

730 days from filing to settlement — a full two-year litigation cycle in S.D.N.Y.

Case timeline: Complaint filed JUN 15 2022, JUN–JUL — 730 days total Horizontal timeline showing the three key events in Railware, Inc. v National Railroad Passenger Corporation from filing to resolution. Source: PACER, New York Southern District Court. JUN 15 2022 Complaint filed Pre-trial proceedings JUN 14 2024 Dismissed without Prejudice 730 DAYS TOTAL
Dismissal terms

Conditional dismissal without prejudice: what the settlement order means

Legal mechanism

Conditional discontinuance: a structured S.D.N.Y. settlement device

The court’s order conditionally discontinued the action without prejudice, giving the parties 30 days to file a formal Stipulation of Settlement and Dismissal. If no restoration was requested within that window, the order automatically converted to a final discontinuance with prejudice. This two-stage mechanism preserves judicial oversight while allowing parties to finalise commercial terms post-agreement.

Conditional dismissal mechanism
Prejudice status

Without prejudice — but only if Railware acts within 30 days

The initial dismissal was without prejudice, preserving Railware’s right to refile if the settlement collapsed. However, the order contained an automatic conversion clause: failure by Railware to request reinstatement within 30 days would render the dismissal final with prejudice. The public record is silent on whether a formal stipulation was subsequently filed, meaning the precise prejudice status at closure requires verification.

Conditional — auto-converts w/ prejudice
Patent holder outcome

Railware avoids merits ruling — patents remain unchallenged by court

Settlement without a merits adjudication means the validity and scope of USRE049115E, USRE047835E, and US9517782B2 were never judicially tested. For Railware, this preserves the patents’ enforcement value against other potential infringers. The reissue patents in particular retain their strengthened prosecution history, undiluted by an adverse claim construction or invalidity finding.

Patents remain enforceable
Defendant outcome

Amtrak resolves exposure without admitting infringement

Settlement allows Amtrak to resolve uncertainty over its AMTEC and ARINC RailwayNet/AIM platform deployments without a court finding of infringement or damages. Amtrak avoids the operational and reputational risk of a permanent injunction against mission-critical dispatch infrastructure. Whether the settlement included a royalty-bearing license is unknown from the public record, but commercial resolution of this scope typically signals some form of ongoing arrangement.

No infringement finding
Legal analysis based on PACER docket records for case 1:22-cv-05013 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffRailware, Inc.CompanyRailroad dispatch technology licensor — holder of USRE049115E, USRE047835E, and US9517782B2Search in Eureka ↗
DefendantNational Railroad Passenger CorporationCompanyNational Railroad Passenger Corporation (Amtrak) — U.S. passenger rail operator and alleged infringerSearch in Eureka ↗
Plaintiff counselBryan Jason VogelAttorneyCounsel for Railware, Inc.Search in Eureka ↗
Plaintiff counselDerrick CarmanAttorneyCounsel for Railware, Inc.Search in Eureka ↗
Plaintiff counselTravis Keith WallerAttorneyCounsel for Railware, Inc.Search in Eureka ↗
Plaintiff law firmRobins & KaplanLaw FirmRepresenting Railware, Inc.Search in Eureka ↗
Defendant counselAndrew Peter MacArthurAttorneyCounsel for National Railroad Passenger CorporationSearch in Eureka ↗
Defendant counselFrank Michael GasparoAttorneyCounsel for National Railroad Passenger CorporationSearch in Eureka ↗
Defendant counselNicholas D. MarcelloAttorneyCounsel for National Railroad Passenger CorporationSearch in Eureka ↗
Defendant counselRalph A. DenglerAttorneyCounsel for National Railroad Passenger CorporationSearch in Eureka ↗
Defendant counselSean M McCarthyAttorneyCounsel for National Railroad Passenger CorporationSearch in Eureka ↗
Defendant law firmAndrew MacarthurLaw FirmRepresenting National Railroad Passenger CorporationSearch in Eureka ↗
Defendant law firmVenable LLPLaw FirmRepresenting National Railroad Passenger CorporationSearch in Eureka ↗
Presiding judgeJudge N/AJudgeNew York Southern District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“By letter dated June 14, 2024, the parties reported to the Court that they have reached a settlement in principle in this case. Accordingly, it is hereby: ORDERED that this action be conditionally discontinued without prejudice and without costs; provided, however, that within thirty (30) days of the date of this Order, the parties may submit to the Court their own Stipulation of Settlement and Dismissal for the Court to So Order. Otherwise, within such time Plaintiff may apply by letter for restoration of the action to the active calendar of this Court in the event that the settlement is not consummated. Upon such application for reinstatement, the parties shall continue to be subject to the Court’s jurisdiction, the Court shall promptly reinstate the action to its active docket, and the parties shall be directed to appear before the Court, without the necessity of additional process, on a date within ten (10) days of the application, to schedule remaining pretrial proceedings and/or dispositive motions, as appropriate. This Order shall be deemed a final discontinuance of the action with prejudice in the event that Plaintiff has not requested restoration of the case to the active calendar within such 30-day period. The Clerk of Court is directed to terminate all pending motions, adjourn all remaining dates, and close this case.”
Source: PACER Docket, Case 1:22-cv-05013, New York Southern District Court

The court’s conditional discontinuance order reflects a structured S.D.N.Y. settlement mechanism rather than a merits adjudication. The language ‘settled in principle’ indicates the parties had reached commercial agreement but had not yet finalised documentation. Critically, the order built in an automatic conversion from a without-prejudice to a with-prejudice dismissal if Railware did not act within 30 days — placing the burden of preservation squarely on the plaintiff. No findings on infringement, validity, or damages were made.

PACER case 1:22-cv-05013 · Public docket record Explore in Eureka ↗
Patent at issue

USRE049115E, USRE047835E & US9517782B2 — Railroad Dispatch & Traffic Control Systems

Publication No.USRE049115E
Application No.US16/709126
Patent details
ProductReissued railroad dispatch and centralized traffic control systems
Cited in actionJune 15, 2022

Publication No.USRE047835E
Application No.US15/928955
Patent details
ProductReissued railroad dispatch and traffic management methods
Cited in actionJune 15, 2022

Publication No.US9517782B2
Application No.US15/177506
Patent details
ProductRailroad dispatch and centralized traffic control systems and methods
Cited in actionJune 15, 2022

The three asserted patents cover railroad dispatch and centralized traffic control technology — a domain governing how rail networks coordinate train movements, signal states, and operational commands in real time. Two of the patents, USRE049115E and USRE047835E, are reissue patents, meaning the original grants were returned to the USPTO for correction or broadening and survived re-examination. US9517782B2 is a standard utility grant. The application lineage across all three patents spans related application numbers in the US15 and US16 series, suggesting a coordinated family prosecution strategy by Railware.

For the railroad and transit sector, centralized traffic control and dispatch software is mission-critical infrastructure — replacing or augmenting this technology carries substantial switching costs and regulatory complexity. Patents in this space can function as toll gates on the upgrade and modernisation cycle that major operators like Amtrak face. The involvement of the ARINC RailwayNet/AIM platform — a widely deployed rail communications and management product — suggests the claim scope may extend beyond bespoke operator implementations to commercially available platforms, raising the sector-wide risk profile of these patents for integrators and system vendors.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should you run an FTO against USRE049115E, USRE047835E, and US9517782B2?

Any company developing, supplying, or integrating railroad dispatch software, centralized traffic control systems, or rail network management platforms should treat these three patents as priority FTO targets. The fact that both a national rail operator and a third-party platform vendor’s product were named in the same infringement action suggests the claims may read broadly across implementation layers. Rail operators undertaking system modernisation, and platform vendors seeking new contracts in the North American rail market, face the most direct exposure.

PatSnap Eureka’s FTO Search Agent can map the claim scope of USRE049115E, USRE047835E, and US9517782B2 against your specific product architecture — identifying which claims pose genuine risk and which design-arounds are viable. Eureka’s patent family analysis will also surface related applications and continuation risk beyond the three asserted patents, giving your product and legal teams a complete picture before commercial deployment or contract execution.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on USRE049115E to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar railroad dispatch and traffic control patent cases in U.S. district courts

Cases involving railroad dispatch, centralized traffic control, and rail network management patents litigated in U.S. district courts, including the Southern District of New York.

🔍
Access 40+ similar cases in PatSnap Eureka
Railware, Inc. patent enforcement history, New York Southern case history, Railware, Inc.’s full IP portfolio, and comparable case analysis
Rail dispatch patent suitsReissue patent enforcementS.D.N.Y. tech settlementsTraffic control IP disputes
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the railroad technology IP landscape

Three patents, two reissues, and a national rail operator: the Railware-Amtrak settlement has measurable implications for dispatch and traffic control IP strategy.

Reissue patents carry real enforcement leverage in infrastructure disputes

Two of the three patents Railware asserted were reissue patents — meaning they survived additional USPTO scrutiny after original grant. In litigation, reissue patents can signal a more defensible claim scope and typically complicate invalidity arguments for defendants. Infrastructure operators deploying dispatch and traffic control software should audit exposure to reissue patents in their vendor technology stacks.

Platform vendors face triangulated risk when their software is deployed by regulated operators

The ARINC RailwayNet/AIM platform — a Rockwell Collins product deployed within Amtrak’s operations — was named as an accused product despite Rockwell Collins not being a defendant. This suggests the patents may read on platform-level functionality, not just the operator’s integration. Technology vendors supplying dispatch or traffic management software to rail operators should conduct proactive FTO analysis before deployment.

🔒
Full strategic analysis in PatSnap Eureka
Unlock deeper analysis of railroad dispatch IP enforcement strategy and district court settlement dynamics in this case.
30-day reinstatement riskVendor indemnity exposureRailware licensing posture
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Railware v National — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Monitor railroad dispatch IP risk before your next system deployment

With three active reissue and utility patents in the railroad dispatch space, Railware’s portfolio warrants ongoing monitoring. Use PatSnap Eureka to run FTO searches and track new filings across the centralized traffic control and rail network management landscape.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.