Kalshi Kills Flight Cancellation Contracts After Backlash and FlightAware Data Refusal

Kalshi has scrapped its planned flight cancellation contracts, pulling the product a day after a regulatory filing had set a Wednesday, July 16, 2026 launch. A Kalshi spokesperson told Fortune on Thursday, July 17, that the company would not move forward with the contracts “for now” — a deliberately non-final phrasing that leaves the door open but signals a clear retreat driven by two forces: a social media backlash over moral-hazard fears and a hard operational blocker when FlightAware refused to supply settlement data.

How the contracts worked

The contracts were structured around airport-wide cancellations, not individual flights. A wager would pay out based on whether a defined cancellation threshold was met across an entire airport — not whether a specific traveler’s plane took off. Because Kalshi operates in a CFTC-regulated environment, any new contract type requires a regulatory filing before listing, and that filing had already been submitted before the reversal. The proposed rules also explicitly prohibited insiders — TSA agents, airport officials, union officials — from placing wagers, an attempt to wall off the most obvious conflict-of-interest scenarios before they could materialize.

The FlightAware problem

Rules on paper only go so far when you cannot settle the bet. FlightAware, the popular airline-tracking service that Kalshi had apparently lined up as its data source, told the company it could not use its data to resolve the contracts. Without a reliable, independent feed to determine whether a cancellation threshold had been crossed, the contracts had no settlement mechanism. That is not a reputational problem a press strategy can fix. It is a structural defect. The FlightAware refusal, as reported by Fortune and surfaced widely via Reddit’s r/CryptoCurrency community, effectively made the product unlistable regardless of how the public debate unfolded.

The social media backlash

The public debate was ugly anyway. Social media users raised the specter of bad actors — airport workers, outside parties, anyone with the means to trigger a disruption — colluding to force cancellations and collect a payout. Critics warned specifically that someone could call in fake bomb or security threats to shut down air travel and profit from the resulting cancellation spike. The scenario spread virally. The optics were grim: a prediction market that, at first glance, appeared to incentivize the deliberate sabotage of American airports.

How justified was the fear?

The insider prohibition was already written into the rules, and stiff criminal penalties already exist for threats or hoaxes directed at the airport industry — penalties that make a profit-driven bomb-threat scheme a remarkably high-risk way to earn a wager payout. The gap between the legal reality and the public perception, though, was wide enough to matter. Kalshi did not need the concern to be well-founded to feel the reputational pressure; it needed only enough people to believe the concern was plausible. They did, and the backlash compounded.

Broader context: prediction markets under pressure

The episode mirrors the regulatory and public-relations friction now hitting prediction markets across the board. Polymarket, Kalshi’s most prominent rival, recently faced a France-ordered geoblock that cut off French users — an escalation in the ongoing push by national regulators to constrain platforms that let users bet on real-world outcomes. Kalshi’s CFTC-regulated status gives it a structural advantage over unregulated offshore competitors, but that same status means every novel contract invites scrutiny, and every public misstep becomes a data point for skeptics who argue the entire category invites moral hazard. The flight contracts were, in effect, a stress test of how far the product envelope can stretch before public tolerance snaps. It snapped.

What comes next

Kalshi’s “for now” language is the detail that matters most for what comes next. The company has not permanently abandoned the product. The FlightAware data issue may be solvable with an alternative provider — another aviation data service, a government feed, a composite source — and the CFTC filing already on record means the regulatory groundwork would not have to start from zero. If Kalshi can source settlement data elsewhere and weather the reputational storm, a relisted version of the contracts is not off the table. What to watch: whether Kalshi names a replacement data partner, whether the CFTC weighs in on the contract type, and whether rival prediction platforms read the retreat as cautionary or as an invitation to try the same product themselves.