A flight tracking service is suing Kalshi for using its data without authorization

FlightAware’s lawsuit centers on two technical violations: unauthorized data scraping and trademark use. Kalshi’s flight cancellation markets relied on FlightAware’s real-time feed, which the tracking service explicitly prohibits for gambling purposes. The trademark claim adds a secondary layer, arguing that Kalshi’s public association with FlightAware harms its reputation. For engineers, this underscores the need to audit data sources for permitted use cases before integrating them into commercial products. Even if the data is publicly accessible, terms of service may restrict its application in ways that aren’t immediately obvious.

The cost of compliance here is twofold. First, Kalshi would need to negotiate a licensing agreement with FlightAware, likely at a premium given the controversial nature of the markets. Second, the platform must implement additional safeguards to prevent misuse, such as insider trading rules or employer verification. These measures add operational overhead and may deter users. The lawsuit also reveals a gap in Kalshi’s due diligence: FlightAware claims it only discovered the data use after media inquiries, suggesting Kalshi didn’t proactively disclose its plans. This reactive approach to data sourcing is a common pitfall for startups scaling quickly.

The dispute exposes a fundamental tension between data providers and prediction markets. FlightAware’s terms of service prohibit using its data for gambling, but Kalshi’s business model depends on it. This mismatch isn’t unique to aviation, similar conflicts could arise in logistics, weather, or supply chain data. The lawsuit also highlights industry pushback: airlines argue that flight disruption markets incentivize bad actors to manipulate cancellations for profit. For engineers, this means even technically feasible products may face legal or reputational barriers if they conflict with the interests of data providers or their partners.

Regulatory uncertainty compounds the problem. While the Commodity Futures Trading Commission has defended Kalshi’s right to operate, New York’s lawsuit could set a precedent for treating prediction markets as illegal gambling. This creates a fragmented legal landscape where the same product might be permissible in one jurisdiction but banned in another. For engineers, this means designing systems that can adapt to varying compliance requirements, such as geofencing or user verification. The case also raises questions about data provenance: if FlightAware’s injunction succeeds, Kalshi may need to find alternative data sources, which could introduce latency or accuracy trade-offs.