FlightAware, a widely used flight-tracking and aviation data company, filed a lawsuit against Kalshi and then withdrew it within a single day, Unchained reported. The rapid reversal has drawn attention because it happened before any substantive court proceedings could unfold.
Kalshi is a federally regulated prediction market platform that lists event contracts on a range of outcomes, including some tied to real-world scheduling and performance data. Companies like FlightAware supply the kind of granular tracking information that such contracts can depend on for settlement and pricing.
Neither company has publicly detailed the specific claims raised in the now-withdrawn filing. Unchained’s reporting establishes only that a suit was filed and then pulled, without clarifying what prompted either action.
Lawsuits filed and withdrawn within a day are unusual in commercial litigation. Such quick reversals can reflect a procedural filing error, an emerging settlement discussion, or a strategic decision to pause before amending a complaint. Without further disclosure, the exact motivation behind FlightAware’s move remains unclear.
The episode nonetheless points to a broader issue facing prediction markets. Platforms like Kalshi increasingly rely on third-party data providers to define, verify, and settle contracts tied to specific real-world events. When that underlying data comes from a commercial source, questions about licensing terms, usage rights, and attribution can surface quickly.
Kalshi has expanded its contract offerings substantially in recent periods, drawing regulatory and industry attention as it tests the boundaries of event-based trading under existing commodities law. Disputes over data inputs, even when resolved quickly or quietly, can signal friction points as the sector grows.
For now, the core question raised by FlightAware’s original filing, namely how Kalshi sources or licenses aviation-related data for any relevant contracts, has not been publicly answered. The withdrawal closes the immediate legal action but does not settle that underlying issue.
Market participants and industry observers will likely watch for whether FlightAware refiles its claims, issues a public statement, or reaches a private arrangement with Kalshi. Any of those outcomes would help clarify what triggered the brief legal confrontation in the first place.
Sources disagree on this story
This article was published before the reports below were compared. The reporting above stands; what follows is where the published accounts do not agree.
Unchained and Cryptopolitan give conflicting details about whether the AeroAPI account Kalshi used was free or paid.
What all sources agree on
- FlightAware filed a notice of voluntary dismissal in the U.S. District Court for the Southern District of New York, ending the case it had brought against Kalshi the previous day.
- The filing dismisses the action against all four defendants, Kalshi Inc., KalshiEX LLC, Kalshi Klear Inc. and Kalshi Klear LLC, and it is without prejudice under Rule 41(a)(1)(A)(i).
- FlightAware had sought a temporary restraining order and preliminary and permanent injunctions.
- Kalshi has revised website language, replacing references to FlightAware with 'Primary Source Agency' language.
- Corporate lawyer Ariel Givner suggested the quick dismissal likely indicates a private settlement.
Where the reports disagree
1Whether the Kalshi AeroAPI account was free or paid
Kalshi settled contracts using data pulled through a free Personal AeroAPI account opened on July 14, 2022, under terms barring use in furtherance of any business.
A Kalshi employee signed up for a paid AeroAPI subscription in 2022, and FlightAware said the terms prohibited commercial use.
What would settle it: FlightAware's original complaint or the AeroAPI account records referenced in it.
What to make of it
Treat the dismissal, its timing, and Kalshi's website changes as established; the specific detail of whether the underlying AeroAPI account was free or paid is unresolved between these reports.
Market Impact
The withdrawal itself is unlikely to move markets directly, since no specific financial claims or contract suspensions were confirmed as part of the filing. However, it highlights a structural risk for prediction market operators that depend on external data providers to define and settle contracts.
If similar disputes recur or escalate, platforms like Kalshi could face pressure to formalize data licensing arrangements more transparently, which may affect how quickly new contract types can launch. Data providers, meanwhile, may become more assertive about protecting how their information is used in derivative or event-contract products.
The quick withdrawal ends the immediate legal action but leaves unanswered how Kalshi handles the flight data at the center of the dispute, a question that may resurface as prediction markets continue to expand their reliance on third-party information.
Frequently Asked Questions
What happened between FlightAware and Kalshi?
FlightAware filed a lawsuit against Kalshi and then withdrew it one day later, according to Unchained, without a public explanation for either action.
What was the lawsuit reportedly about?
The specific claims have not been publicly detailed, but the dispute is understood to relate to data used in connection with Kalshi's event contracts.
Does the withdrawal mean the issue is resolved?
Not necessarily. Withdrawing a lawsuit ends that specific legal filing but does not confirm that the underlying data question has been settled between the two companies.
Why does this matter for prediction markets generally?
Prediction market platforms often rely on outside data providers to define and settle contracts, so disputes over data licensing can raise broader questions about how these products source their underlying information.