D.C. Race Cash Split—Wait Till You See Which

race track curve at sunset with motion blur
Photo: jamesteohart / Shutterstock

When people argue about whether a big sports event is “taxpayer funded,” they’re usually talking about two different ledgers: the private production budget and the public-safety and city-operations tab. The Washington, D.C., IndyCar street race made that split plain.

At a Glance

  • The core race production was financed privately, led by Penske/IndyCar; public money covered police, fire, and security typical of large-scale events.
  • Critics who called the event a “waste of taxpayer money” conflated security spending with the race’s production costs; supporters who said “no taxpayer funds” focused on the production ledger, not the security tab.
  • D.C. drew from a congressionally appropriated emergency planning and security fund used for major events, rather than paying from its general budget.
  • Economic research finds public subsidies for sports and mega-events rarely deliver fiscal gains large enough to justify their costs, even when the outlays are limited to security and operations.

What was paid for privately, and what wasn’t

The clearest through-line in the public record is the division of costs. Penske and IndyCar shouldered the race’s production—course build-out, operations, and the event footprint—reported at more than $35 million, with free general-admission tickets to maximize attendance and visibility. Organizers stressed that the race itself did not draw on taxpayer funds. That claim holds when you confine “the race” to its production budget: private capital and sponsorships covered it, and principals said they took no federal money to produce the event.

But a city cannot host a 100,000-plus-person street race without police, fire and EMS staging, traffic management, and protective services. Those public-safety and operations costs were covered through a federal emergency planning and security fund for major events in the District—exactly the pot Congress sets aside for occasions with outsized security requirements. In short: private money ran the race; public money safeguarded the city around it.

Why the messaging sounded contradictory—yet both sides cite real facts

The rhetoric diverged because the term “taxpayer-funded” was used imprecisely. Critics keyed on the presence of public dollars anywhere in the enterprise and labeled the whole thing a taxpayer burden. Supporters narrowed the definition to the race’s production ledger and declared it privately financed. Both statements ride a kernel of truth and a gloss: yes, taxpayers underwrote security; no, taxpayers didn’t bankroll the racing product. Local reporting captured the nuance finely: the “vast majority” of event costs came from Penske, with security supported by the federal fund Congress provides for big events in D.C..

This public-private blend is normal for marquee events. Political conventions, major marches, New Year’s on the Mall, and championship parades all rely on public-safety funding even when their production is privately organized. The D.C. IndyCar race followed that template; it was unusual in location and scale for motorsport, not in its reliance on public-safety appropriations.

The economics question that actually matters

Strip away the social-media crossfire and a more durable question remains: is the public piece—policing, fire, EMS, traffic control—worth it? On that, decades of independent research are stark. Economists repeatedly find that subsidies tied to sports facilities and mega-events, including limited outlays for event-related public services, rarely yield measurable economic gains that offset costs. Peer-reviewed surveys and policy reviews converge on the same conclusion: the promised boosts to jobs, income, and tax revenue are typically overstated, while the fiscal returns to residents are smaller than the public expenditures required to stage and secure the events.

Why the mismatch? Event spending often substitutes for other local consumption rather than adding to it; visitors crowd out routine activity; overtime and operational strain on public agencies are real costs; and much of the private event revenue accrues to promoters, rights-holders, and suppliers whose tax footprints may be modest locally. Even when civic pride and amenity value are meaningful, the spreadsheets—where police overtime and barricades actually sit—rarely balance on fiscal returns alone.

Security funding in D.C. is structurally different from most cities

There is, however, a governance wrinkle particular to the nation’s capital. Because D.C. hosts federal institutions and national-scale events as a matter of course, Congress provides a dedicated emergency planning and security fund that helps the city manage episodic, high-intensity demands. Tapping that fund for a multi-day, high-profile street race that pulls large crowds and dignitaries aligns with its purpose; it is not a budgetary expedient unique to this event, but part of how the capital’s security apparatus is financed during major gatherings.

That matters for judging “who paid.” In a typical city, such costs might hit the municipal general fund, forcing trade-offs visible to local taxpayers. In D.C., the marginal burden is partially socialized nationally via congressional appropriation. Residents may still experience congestion or service strain; the fiscal incidence, however, is not identical to a standard city subsidy to a franchise or stadium operator.

How to read the next “taxpayer-funded sports” fight

First, separate the ledgers. Ask what the private organizers paid to stage the event and, separately, what public agencies spent on security, traffic, sanitation, and temporary infrastructure. Second, identify the funding source of the public piece: a city’s general fund, a state grant, or a dedicated federal program. Third, ignore headline economic-impact numbers unless they specify net new spending and provide a transparent methodology; independent literature finds such figures routinely exaggerate gains relative to public costs.

Finally, decide what value you care about. If your yardstick is narrow fiscal return, the consensus says these events rarely pencil out for taxpayers. If your yardstick includes civic celebration, national branding, or cultural capital, then the calculus changes—but those benefits are qualitative and should be named as such. The D.C. IndyCar race is a case study in that clarity: a privately financed spectacle wrapped in a standard, publicly funded security envelope. Call it waste or wise investment—but call the two ledgers what they are.

Sources:

redstate.com, youtube.com, politico.com, x.com, thecentersquare.com, nytimes.com