Flight tracking platform FlightAware sues Kalshi in New York, alleging Kalshi is using its data without permission to let users bet on flight cancellations
Context & Ripple Effects
FlightAware’s complaint adds a data-rights dispute to Kalshi’s wider legal exposure. New York had already challenged Kalshi’s compliance with state gambling law, while the CFTC sought to block that enforcement in the New York regulatory clash.
The episode resolved quickly: FlightAware later withdrew the suit after Kalshi stopped identifying it as a source. That makes provenance, rather than the underlying flight-cancellation contracts alone, the immediate point of pressure.
First-order effects
- Kalshi loses FlightAware’s named-source association for flight-cancellation markets, while FlightAware establishes that use of its data requires permission under its complaint.
- The withdrawal ends this particular litigation without a disclosed ruling, but Kalshi’s source disclosures have already changed.
Second-order effects
- Other data providers whose information supports Kalshi contracts gain a concrete incentive to scrutinize attribution and licensing terms before their data is presented as an input to tradable markets.
- Kalshi must manage data-access and provenance questions alongside the state-level challenges it is already contesting in New York and Nevada.
Third-order effects
- If proprietary-data owners increasingly police use in event contracts, prediction-market platforms may need more formal data-licensing and source-governance practices as part of market design.
- The dispute points to prediction markets becoming platforms accountable not only for contract legality, but also for the permission chain behind the information used to frame those contracts.
The trend: Prediction-market platformization is bringing data provenance and supplier permission into the same compliance perimeter as gambling-law disputes.