Reform Landscape

State legislatures have pursued a range of reforms aimed at curbing revenue-oriented policing, but these efforts reflect two fundamentally different theories of change. The first targets officer behavior directly, seeking to prevent departments from pressuring individual officers to meet numerical enforcement targets. The second targets the fiscal and structural incentives that create that pressure in the first place, by limiting how much revenue local governments can retain from enforcement activity or by triggering oversight when reliance on that revenue becomes excessive. The sections that follow examine both approaches in turn, assessing their design features, legislative histories, and practical impacts.

5.1 Police Quota Bans

Banning police quotas is perhaps the most widespread reform aimed at addressing revenue-oriented policing. As of 2025, at least 25 states have enacted legislation explicitly prohibiting local law enforcement agencies from requiring officers to meet specific numerical targets for arrests, citations, or traffic stops.⁵⁶ These laws reflect a legislative consensus that quotas create perverse incentives that prioritize revenue generation over public safety and undermine the legitimate functions of law enforcement.

Despite this legislative momentum, quotas remain a persistent feature of American policing. A 2017 national survey conducted by the Pew Research Center found that 37% of police officers reported that their department used some sort of arrest or ticket quota, formal or informal.⁵⁷

Recent empirical research examining the effects of quota bans in Illinois, Michigan, Rhode Island, and Tennessee found minimal evidence that state laws banning police quotas reduce citation actions by officers.⁵⁸ In fact, researchers observed a slight increase in the number of traffic citations issued per month and the rate of citations issued per traffic stop after the passage of police ticket quota bans in these states. Similarly, analysis of New York City pedestrian stop data found minimal evidence that the state's expanded quota prohibition contributed to any significant decline in pedestrian stops by the NYPD until public protests and litigation brought greater scrutiny.⁵⁹ The same study found limited evidence that police quota bans may improve the quality of traffic stops, measured as the "hit rate" at which searches of vehicles reveal contraband. However, the magnitude of the effect on vehicle search hit rates was very small. The estimated increase of roughly 0.3 percentage points raises the baseline hit rate from about 0.57 percent—roughly six successful searches per 1,000 stops—to only about nine per 1,000 stops.⁶⁰

State quota ban statutes vary dramatically in how they define quotas, what exceptions they permit, and how violations are identified and addressed. These design variations may help explain why quota bans have proven largely ineffective at reducing revenue-oriented enforcement. When statutes fail to clearly define what constitutes a prohibited quota, include broad exceptions that permit the same behavior under different names, or lack meaningful enforcement mechanisms, police departments can continue using numerical targets while remaining technically compliant with the law.

Quota Ban Landscape

States with local police quota bans

Whether state law prohibits police quotas for local law enforcement agencies.

Has BanScopeFormalityDefinitionEmploymentRemedies

Legend

Yes 25

Partial (state agency only) 1

No 24

Summary

States with local police quota bans

Whether state law prohibits police quotas for local law enforcement agencies.

5.1.1 Defining Quotas

What exactly is a quota? States take vastly different approaches to answering this question, with significant implications for enforcement and comparative analysis. Some states narrowly prohibit only explicit numerical targets for traffic citations, while others cast a wider net to include arrests and investigative stops and even informal pressure to meet numerical goals. These definitional choices determine whether police departments can evade quota bans by shifting to other forms of enforcement or by establishing "performance metrics" that carefully dodge statutory definitions. Three key dimensions shape how states define prohibited quotas: the scope of covered enforcement activities, whether informal pressure is included, and how precisely numerical requirements must be specified.

Scope

All 25 states with quota bans prohibit quotas for traffic citations, but states vary as to whether they prohibit quotas for other enforcement activities. Twelve states (Connecticut, Florida, Illinois, Iowa, Michigan, Minnesota, Missouri, Nebraska, Pennsylvania, South Carolina, Tennessee, and Texas) only explicitly prohibit quotas related to the number of citations issued. Wisconsin's law covers warning notices in addition to citations and complaints.

Twelve states (Arkansas, California, Louisiana, Maryland, Montana, Nevada, New Jersey, New York, Ohio, Rhode Island, Utah, and Virginia) extend their prohibitions to cover both citations and arrests.

The most expansive statutes include preliminary enforcement activities that may precede citations or arrests. Montana prohibits quotas for "investigative stops" as well as arrests and citations. New York's ban includes quotas for "stops of individuals suspected of criminal activity." Rhode Island similarly defines a quota as "any requirement regarding the number of arrests or investigative stops made, or summonses or citations issued."

Formality

States also differ in whether they address only explicit, written quota requirements or also prohibit informal pressure to meet numerical targets.⁶¹ This distinction matters because the 2017 Pew Research Center survey found that among officers reporting quota systems, the overwhelming majority indicated these were informal expectations rather than formalized policies.⁶²

At the narrowest end of the spectrum, Nebraska and Nevada appear to only address formal quotas. Nebraska's statute prohibits agencies from "directly" requiring officers to meet quotas, leaving informal pressure unaddressed. Nevada's statute similarly bars only agency acts that "order, mandate, or require" a quota.⁶³

Other states adopt language designed to capture both formal and informal quota systems. Louisiana's law explicitly covers quotas maintained "formally or informally," and prohibits agencies from even suggesting that officers are "required or expected" to meet numerical targets.⁶⁴ Maryland, Ohio, Rhode Island, Tennessee, Texas, and Virginia's quota prohibitions include similar "formally or informally" language.⁶⁵

Iowa and Pennsylvania prohibit quotas established "directly or indirectly."⁶⁶ New York prohibits agencies from "expressly or impliedly" penalizing or threatening officers based on their failure to meet a quota.⁶⁷ New Jersey prohibits quotas "in writing or otherwise."⁶⁸ Minnesota and Montana specify that agencies cannot "require" or "suggest" quotas.⁶⁹ Missouri prohibits policies "requiring or encouraging" a minimum number of traffic citations.⁷⁰

Nine states (Arkansas, California, Connecticut, Florida, Illinois, Michigan, South Carolina, Utah, and Wisconsin) remain silent on the question of formality, prohibiting "quotas" without explicitly addressing whether informal pressure falls within the statutory definition.

Numerical Specificity

Finally, states differ in how precisely they define what numerical requirements constitute a quota.⁷¹ Some statutes provide generic prohibitions while others specify that quotas must involve predetermined numbers or percentages. Florida's minimal statute simply states that "a traffic enforcement agency may not establish a traffic citation quota" without defining what constitutes a quota.⁷²

Other states adopt more precise definitions. Michigan specifies that officers cannot be required to issue "a certain number of citations."⁷³ Montana defines a quota as "a specific number of arrests, citations, or investigative stops."⁷⁴ New York's statute refers to "a specific number" of tickets, summonses, arrests, or stops "which are required to be made within a specified period of time."⁷⁵ Maryland defines quota as "the mandating of a finite number of arrests made or citations issued that a law enforcement officer must meet in a specified time period."⁷⁶

Several states also address comparative or proportional metrics. Arkansas and California define arrest quota to include not only absolute numbers but also the proportion of arrests made and citations issued by a law enforcement officer relative to the arrests made and citations issued by another officer or group of officers.⁷⁷ New Jersey's definition similarly covers proportional comparisons.⁷⁸ Meanwhile, Maryland explicitly permits agencies to assess the proportion of arrests made and citations issued by an officer or group of officers.⁷⁹

The level of specificity matters because agencies could attempt to evade quota prohibitions by using comparative metrics, averages, or ranges rather than fixed numbers. For instance, rather than requiring officers to write 10 tickets per shift, a department might require officers to maintain citation levels "consistent with department averages" or to fall within certain percentile ranges. Whether such practices violate quota bans may depend on how precisely the statute defines terms and requirements.

5.1.2 Exceptions and Ambiguities

Defining what constitutes a prohibited quota is only half the equation. Equally important is defining what does not constitute a quota. That is, enumerating which uses of enforcement data remain permissible even under quota ban statutes. Many laws that clearly prohibit explicit numerical targets simultaneously carve out exceptions that allow local police agencies to impose analogous pressures on officers. These exceptions and ambiguities can effectively authorize quota-like systems under different auspices.

Employment Actions

Quotas often become visible when they affect officers' careers through evaluations, promotions, or disciplinary actions. Yet many statutes that prohibit explicit quotas simultaneously and affirmatively permit agencies to use enforcement metrics as one input among several in evaluating officers. Because the use of numerical metrics in an evaluation is expressly allowed under these statutes, it may be practically very difficult for an officer to demonstrate evidence of a prohibited quota. An officer who believes they have been penalized in violation of the quota ban must bring a claim challenging the adverse employment action and bears the burden of proving that the agency's use of numerical metrics crossed the precise statutory line.

Eight states (Florida, Iowa, Minnesota, Missouri, Montana, Nebraska, Nevada, and Pennsylvania) are silent on evaluations and employment actions.

Five states explicitly prohibit using quotas to "evaluate, promote, compensate, or discipline" officers. Louisiana employs this language, as do New Jersey, Ohio, and Texas. New York's statute is particularly detailed, prohibiting a range of actions including "a reassignment, a scheduling change, an adverse evaluation, a constructive dismissal, the denial of a promotion, or the denial of overtime" based on failure to meet quotas.⁸⁰

Virginia prohibits the use of quotas for evaluating officer performance, but does not prohibit agencies from "collecting, analyzing, and utilizing information concerning the number of arrests made or summonses issued for any other purpose."⁸¹

At the same time, seven states undermine their quota prohibitions by specifying that agencies can use citation or arrest numbers as long as they are not the "sole criterion" for employment decisions. Arkansas, California, Connecticut, Maryland, Rhode Island, Tennessee, and Virginia all specify that agencies cannot use enforcement numbers as the exclusive basis for promotion, demotion, dismissal, or other personnel actions. These "sole criterion" provisions permit agencies to consider enforcement activity alongside other performance measures, potentially creating room for quota-like pressure that technically complies with statutory language. An officer challenging an adverse employment action in these states must show not merely that numbers appeared in their evaluation, but that numerical metrics functioned as the operative criterion despite the presence of other formal factors. That showing requires evidence of supervisory intent that is rarely documented in writing, particularly because departments in states with quota bans have strong incentives to avoid such documentation.

Michigan's statute allows citation issuance to be part of a performance evaluation system but prohibits giving it greater weight than other factors.⁸² Utah expressly does not prohibit law enforcement agencies from including enforcement activity as "part of an overall determination of a peace officer's performance."⁸³

Wisconsin allows agencies to compare officers' citation numbers to those of other officers with similar duties for performance evaluation purposes, effectively carving out an exception for comparative metrics that many other states explicitly prohibit.⁸⁴

South Carolina and Illinois both carve out exceptions whereby officers can be evaluated based on their volume of "points of contact." ⁸⁵ South Carolina defines points of contact as officers' interactions with citizens and involvement in community-oriented initiatives.⁸⁶ Illinois defines points of contact as "any quantifiable contact made in the furtherance of the police officer's duties, including, but not limited to, the number of traffic stops completed, arrests, written warnings, and crime prevention measures."⁸⁷ Notably, Illinois explicitly excludes the number of citations issued from the definition of points of contact.⁸⁸

Other Exceptions

Several states carve out exceptions allowing law enforcement agencies to continue using quantitative data on citations, arrests, and stops in certain ways. Maryland, New Jersey, and Ohio, for example, allow use of quantitative data to ensure officers meet legal obligations.⁸⁹

Illinois includes language clarifying that its quota prohibition "shall not affect the conditions of any federal or State grants or funds awarded to the municipality and used to fund traffic enforcement programs."⁹⁰ Arkansas provides a similar exception for "requirements under federal law or contracts with federal agencies."⁹¹

Louisiana and Texas specifically do not prohibit municipalities from "obtaining budgetary information from a municipal court or a municipal court of record, including an estimate of the amount of money the court anticipates will be collected in a budget year."⁹² Municipalities may obtain such information but may not use it to evaluate, promote, compensate, or discipline officers and judges. The provisions are nonetheless interesting in that they raise the question of whether entirely ordinary budgeting practices, such as projecting anticipated fine revenue, might themselves create informal pressures that begin to resemble a quota even when no such intent exists. This concern may be most salient in small municipalities where fines and forfeitures are the largest source of revenue and directly fund the police department and municipal court whose activity generates that revenue. In such cases, the fiscal reality—and its associated perverse incentives—may be apparent to individual officers and police chiefs without any explicit pressure from other city officials.

Missouri's statute states that "this section shall not apply to the issuance of warning citations."⁹³ Presumably, this provision is intended to allow police departments to encourage officers to issue warnings rather than tickets.

5.1.3 Enforcement Mechanisms and Remedies

The combination of definitional ambiguity, performance evaluation loopholes, and broad exceptions would be less concerning if quota ban statutes included robust enforcement mechanisms. In practice, however, the most glaring weakness in quota ban laws is the absence of meaningful enforcement.

Reporting Mechanisms and Worker Protections

In 18 states (Arkansas, California, Connecticut, Florida, Illinois, Iowa, Louisiana, Maryland, Minnesota, Missouri, Montana, Nebraska, Nevada, New Jersey, Rhode Island, Utah, Virginia, and Wisconsin), quotas are prohibited, but there are no prescribed consequences for violations and no processes for officers to report or challenge quota policies. Without enforcement mechanisms or penalties, these laws are not likely to provide effective constraints on agency behavior.

A handful of states have adopted more robust enforcement approaches. Most recently, Ohio established a quota ban in 2025 that requires the attorney general to create a reporting form accessible on the internet for officers to report quota violations. Anonymous reports are permitted. Upon receiving a report, the attorney general must investigate within one year and determine whether violations occurred. If an agency is found to be using quotas, the attorney general must order the agency to cease and desist.⁹⁴

New York provides strong worker protections by explicitly prohibiting retaliation against officers who fail to meet quotas and establishing remedies including restoration to previous positions, compensation for lost wages, and restoration of any penalties imposed. Officers can pursue grievances through collective bargaining agreements or civil service procedures.⁹⁵

South Carolina provides whistleblower protections for officers who report quota violations, referencing the state's general whistleblower protection statute.⁹⁶ In practice, general whistleblower statutes have proven difficult to enforce when reporting police quotas.⁹⁷ Officers who speak out about quotas through official channels may find that First Amendment retaliation claims are foreclosed under Garcetti v. Ceballos, 547 U.S. 410 (2006), which held that public employee speech made in the course of official duties is not constitutionally protected.⁹⁸

Penalties and Remedies

Tennessee makes violations a Class B misdemeanor punishable by fine, while Texas allows removal from office for elected officials who violate quota prohibitions and termination for non-elected employees.⁹⁹ Michigan's statute states that any "police officer, judge, district court magistrate, or other person employed by the state or by a local governmental unit" who violates the quota prohibition is "guilty of misconduct in office and subject to removal from office."¹⁰⁰

Pennsylvania takes a unique approach by declaring that "any tickets or citations issued in violation of this act shall be unenforceable, null and void."¹⁰¹

5.2 Addressing Fiscal Incentives Directly

Quota bans address one mechanism through which financial pressures translate into enforcement activity, but they do not eliminate the underlying fiscal incentives. Agencies facing budget pressure may still find ways to increase enforcement even without formal quotas, particularly in jurisdictions that retain substantial citation revenue. A smaller number of states have pursued reforms that target those structures more directly, either by limiting how much fine revenue local governments may retain, by triggering state oversight when reliance on enforcement revenue exceeds specified thresholds, or by requiring public reporting that makes high reliance visible to state authorities. The sections that follow examine each of these approaches in turn.

5.2.1 Fine Caps and Diversion Policies

5.2.1 State Detail

Fine Cap and Diversion States

AL Alabama 10% traffic-fine capMD Maryland 10% speed-camera capMO Missouri 20% municipal-court capUT Utah 25% traffic-fine capTX Texas 30% traffic-fine cap

Current Policy

Alabama

10% traffic-fine cap

Traffic fines and penalties retained by municipalities are capped at 10% of the general operating budget.

View profile

One approach to directly addressing financial incentives would be to restructure how fine revenues flow through government budgets. In states where local governments retain a substantial share of fines and forfeitures, redirecting those revenues to the state, to schools, or to other purposes beyond the control of the collecting government removes the fiscal incentive at its source. As the Urban Institute's analysis of speeding ticket revenue flows demonstrates, the structure of revenue distribution varies considerably across states and shapes the degree to which local governments have an incentive to engage in aggressive enforcement in the first place.¹⁰²

However, comprehensive restructuring of fine revenue flows is complicated, potentially costly, and carries the risk of unintended consequences. Local governments that currently depend on fine revenues to fund legitimate public safety operations would face real fiscal pressure if those revenues were suddenly redirected. Court systems that rely on fee revenues to fund basic operations could face funding shortfalls requiring state assumption of costs. And the political and constitutional barriers to restructuring entrenched revenue streams are substantial in many states. These are not reasons to avoid reform, but they suggest that wholesale restructuring of revenue flows is better understood as a long-term goal than as an immediately actionable policy lever.

A more targeted approach recognizes that the problem is concentrated. As the data in Parts 3 and 4 demonstrate, the vast majority of local governments collect minimal fine revenue relative to their budgets. The fiscal incentive problem is acute in a relatively small number of jurisdictions where fines and forfeitures make up a substantial share of operating revenue. Revenue caps, which prohibit local governments from retaining fine revenues above a specified percentage of their operating budgets and redirect excess amounts to state or county purposes, offer a way to constrain the most problematic cases without requiring a wholesale restructuring of court systems and their funding mechanisms.

Five states (Alabama, Maryland, Missouri, Utah, and Texas) have placed explicit caps on the share of revenues local governments may collect from either speeding tickets or fines and forfeitures more broadly. All or a portion of any revenue in excess of these caps is diverted to purposes beyond the control of the collecting government. Below, the chart highlights and compares important features of each state's policies, after which we explore each state's approach in greater detail.

Alabama

In January 2022, investigative reporting by AL.com exposed how the 1,253-person town of Brookside, Ala., had transformed traffic enforcement into a revenue machine.¹⁰³ Between 2018 and 2020, Brookside's speeding ticket revenues increased by more than 640%, ultimately comprising half the town's $1.2 million budget by 2020. That year, the Brookside Police Department made more misdemeanor arrests than the town had residents.¹⁰⁴

The windfall enabled an aggressive expansion of Brookside's police operations. Town officials used citation revenue to hire additional law enforcement officers and purchase militarized equipment, including a SWAT-style riot control vehicle.¹⁰⁵ The investigation's revelations sparked widespread public outrage. Brookside's police chief resigned under pressure, the U.S. Department of Justice filed a statement of interest supporting a class-action lawsuit against the town, and the AL.com reporting team received a Pulitzer Prize for their work exposing Brookside's exploitative practices.¹⁰⁶

Just over two months after the story broke, in April 2022, Alabama enacted two companion bills addressing municipal taxation by citation. Senate Bill 282 established the 10% cap on fines and penalties from traffic tickets.¹⁰⁷ Senate Bill 203 established the reporting requirements for municipal courts.¹⁰⁸

Alabama's 10% cap on municipal traffic citation revenues is the strictest in the nation, but the state's law still has many limitations. The cap only applies to traffic fines and penalties, not to non-traffic fines and forfeitures. This narrow focus on traffic ticket revenues could allow municipalities to continue generating substantial revenue from non-traffic enforcement activities. The law's limited scope may also contribute to enforcement challenges because it requires municipalities to accurately track and report traffic enforcement revenues separate from other fines and forfeitures.

Reason Foundation contacted the Alabama Department of Finance for information about the implementation of Alabama's fine revenue cap and diversion policy. In response to our inquiry, the Department of Finance stated that, according to the Comptroller, no funds have been remitted under this provision and, as a result, no distributions have occurred.

Maryland

Since Maryland authorized automated speed enforcement in Montgomery County in 2006, the state's speed camera programs have generated substantial revenue while becoming mired in repeated scandals involving inaccurate citations, lack of transparency, and alleged conflicts of interest. In 2009, facing a substantial budget deficit, then-Gov. Martin O'Malley and the General Assembly expanded automated speed camera enforcement authorization to school zones and highway work zones statewide.¹⁰⁹

To address concerns about conflicts of interest between revenue generation and public safety, the 2009 legislation capped revenue from speed cameras at 10% of a local government's total revenues each fiscal year. The law also required that all automated citations be reviewed and validated by sworn law enforcement officers.

An investigative report from the Baltimore Sun found that between 2009 and 2012, automated speed enforcement cameras in and around Baltimore issued more than 2.5 million tickets, generating more than $70 million in revenue.¹¹⁰ In 2012 alone, Baltimore City generated $19.2 million in revenue from 83 speed cameras around the city, $4 million more than the $15 million city officials expected.¹¹¹ At the time, Baltimore Mayor Stephanie Rawlings-Blake rebuffed citizen concerns, saying "we have a spike, but it's an anomaly" and calling the citations "a minor inconvenience for people who routinely break the law."¹¹²

But the Baltimore Sun investigation revealed that many citations were issued in error. In a particularly egregious example, a camera issued an automated speeding citation for going 38 mph in a 25-mph zone to a vehicle that was at a complete stop.¹¹³ A spokesman for the Baltimore Police Department attributed the citation of a motionless vehicle to a "perfect storm of errors."¹¹⁴ Human review of automatic citations is supposed to catch such obvious errors, and the city's spokesman acknowledged that the citation should not have been validated.¹¹⁵

The Baltimore Sun's reporting raised serious questions about the validation process. More than 2,000 citations were purportedly signed by Baltimore City Police Officer James Fowler, who had been killed in a car accident a year prior.¹¹⁶ The posthumous citations were only discovered after a fellow officer was issued an automated red-light citation with Fowler's name on it.¹¹⁷

An internal audit leaked in 2014 to the Baltimore Sun revealed an error rate of 10%, roughly 40 times higher than city officials had publicly claimed.¹¹⁸ Assuming that error rate applied to the 700,000 tickets issued in fiscal year 2012, the audit's findings imply as many as 70,000 citations resulted in $2.8 million in erroneous fines. One camera issued more citations in error than it did correctly.¹¹⁹

Similar concerns emerged in other parts of the state. In Prince George's County, Maryland, a disabled 71-year-old man was allegedly jailed for contempt after attempting to present photographic evidence that a Forest Heights camera was enforcing a 35 mph speed limit in an area where the posted limit was actually 40 mph.¹²⁰ A Riverdale police officer claimed he was suspended in retaliation for saying that his signature was forged on thousands of speed camera citations issued between 2010 and 2012.¹²¹

These controversies ultimately prompted the legislature to adopt Senate Bill 350 in 2014.¹²² The legislation mandated training for program administrators, designated local ombudsmen to investigate complaints, established quarterly calibration requirements, and imposed new restrictions on contracting with private vendors.

Despite various reform efforts, speed camera programs continue to generate substantial revenues in Maryland. In 2017, state and local governments collected a total of $62 million in automated speed enforcement revenue, with 76% coming from Prince George's and Montgomery Counties.¹²³ Recent legislation in 2025 increased penalties through a tiered fine structure ranging from $40 to $425, depending on how far over the speed limit a driver is traveling.¹²⁴ Previously, automated speeding citations were a flat $40 regardless of speed.

Maryland's 10% cap applies only narrowly to automated speed enforcement after subtracting implementation costs, leaving substantial room for revenue generation through other enforcement mechanisms.

Missouri

Missouri's efforts to limit municipal reliance on traffic fine revenue began decades before Ferguson entered into the national spotlight. The state's legislative framework originated with a notorious speed trap in Macks Creek, a town of fewer than 500 residents along U.S. Route 54 near the Lake of the Ozarks. As reported by The Washington Post, the town issued approximately 2,900 tickets per year to make up nearly 75% of its revenue in the 1990s.¹²⁵ Then-state Rep. Delbert Scott authored the "Macks Creek Law" in 1995 after personally falling victim to the town's revenue-oriented policing tactics.¹²⁶ The law established a 45% cap on the percentage of municipal revenue that could come from speeding tickets, with excess amounts remitted to the Missouri Department of Revenue and distributed to county school districts.

Macks Creek initially attempted to circumvent the law by issuing parking citations instead of speeding tickets, according to a 1996 state audit.¹²⁷ After the audit, the town's mayor resigned and its police officers were laid off.¹²⁸ Macks Creek declared bankruptcy in 1998 before eventually being disincorporated in 2012. Yet the Macks Creek Law itself proved difficult to enforce. A 2009 investigation by the St. Louis Post-Dispatch found the law "riddled with loopholes," with unclear definitions and no tracking mechanisms to distinguish traffic fines from other court revenues.¹²⁹

Recognizing these weaknesses, the General Assembly gradually strengthened the statute over the next two decades. In 2009, the cap was lowered to 35% and then to 30% in 2013. The 2013 amendments also added a requirement that municipalities include an accounting of traffic fine revenue percentages in their annual financial reports and created a penalty of losing municipal court authority for non-compliance.

The DOJ investigation of Ferguson in 2014, discussed in Part 2, brought renewed national scrutiny to revenue-oriented policing in Missouri and exposed the apparent failures of the Macks Creek Law. That a city operating under the law's provisions could nonetheless develop the patterns of enforcement documented by the DOJ suggested that the statute's definitions, thresholds, and enforcement mechanisms were insufficient to address the problem it was designed to solve. In a report of the investigation's findings, the DOJ offered a scathing review of the Ferguson Police Department, citing widespread racial bias and discrimination. In particular, the DOJ investigation found that City officials routinely pressured the police department to increase citation revenue, concluding:

This emphasis on revenue has compromised the institutional character of Ferguson's police department, contributing to a pattern of unconstitutional policing, and has also shaped its municipal court, leading to procedures that raise due process concerns and inflict unnecessary harm on members of the Ferguson community.¹³⁰

A 2014 report from Better Together, a local research organization in the St. Louis region, found that 20 municipalities in St. Louis County collected more than 20% of their revenue from fines and fees, and eight collected more than the 30% cap imposed by state law at the time.¹³¹

In response, the Missouri General Assembly once again made amendments to the Macks Creek Law through the passage of Senate Bill 5, which was signed into law by then-Gov. Jay Nixon in July 2015.¹³² The 2015 reforms capped fines, bond forfeitures, and court costs arising from municipal ordinance violations and minor traffic violations to 12.5% of general operating revenue for municipalities in St. Louis County (counties with a charter form of government and more than 950,000 inhabitants) and 20% for municipalities in the rest of the state, effective Jan. 1, 2016.

Senate Bill 5 also included provisions addressing the systemic issues identified in Ferguson. The law required police departments in St. Louis County to adopt specific written policies for pursuits and the use of force, and prohibited municipalities from imposing minimum fine requirements on municipal judges or dictating fine amounts.

The tiered structure targeting St. Louis County, however, sparked immediate legal challenges. In 2017, the Missouri Supreme Court struck down the St. Louis County–specific provisions in City of Normandy v. Greitens, ruling that the classification constituted an unconstitutional "special law" because the state failed to demonstrate substantial justification for treating St. Louis County differently.¹³³ The court severed the St. Louis County classification from the remainder of the statute, leaving a uniform 20% cap statewide.

Missouri's law is one of the most aggressive state-level approaches to curbing revenue-driven enforcement. The 20% statewide threshold is more restrictive than Arkansas's 30% cap or Georgia's 35% limit for speed detection device revenue. Moreover, the redistribution mechanism, which channels excess revenue to education, creates a clear financial disincentive for municipalities to engage in predatory practices. However, Missouri's repeatedly botched attempts at reform suggest that enforcement is likely to remain a challenge despite improvements to statutory definitions and increased reporting requirements.

Utah

Mantua, a town of fewer than 1,300 residents in northern Utah, has maintained a notorious reputation as a speed trap spanning decades. Located on U.S. Highway 89-91 in Sardine Canyon, the town's aggressive traffic enforcement has been the subject of media reports and legislative scrutiny since at least the late 1990s. In 1997, Mantua police issued 1,338 traffic tickets, generating $60,000 in revenue that accounted for about one-third of the town's budget.¹³⁴ In 2014, Mantua police issued 2,185 traffic tickets, generating approximately $220,000 in fines and comprising more than one-third of the town's $649,000 in total revenue.¹³⁵

The first serious legislative attempt to curb Mantua's speed trapping came in 2016. Then-state Sen. Lyle Hillyard, a Republican from nearby Logan, introduced Senate Bill 100, which would have limited traffic fine revenue to 25% of any municipality's general fund budget.¹³⁶ Hillyard explained that he had received complaints from people statewide about being unreasonably ticketed in Mantua, and noted he had "never had a complaint" about Utah Highway Patrol or police in neighboring communities enforcing traffic laws on the same stretch of highway.¹³⁷

Mantua officials fought back aggressively. Then-Mayor Mike Johnson, who simultaneously served as the town's police chief, accused Hillyard of crafting "ill-conceived and shortsighted" legislation that was "truly unbecoming of a senior senator" and suggested Hillyard should instead focus on "term-limit legislation."¹³⁸ Hillyard's legislation passed the Utah state Senate with broad support, but ultimately failed in the state House.¹³⁹

In early 2021, Mantua's traffic enforcement became subject to renewed scrutiny when Police Chief Michael Castro claimed he was terminated by Johnson because he "did not go along with making [his] officers have a quota for citations." Castro, who had been hired in July 2020, alleged that Johnson and at least one town council member repeatedly pressured him to increase traffic citations.¹⁴⁰ Castro stated he was given unwritten quotas requiring officers to write between three and five citations per day, with his sergeant told to issue six per shift. According to Castro, town officials informed him that approximately $110,000 of the police department's $195,000 budget was expected to come from citation revenue, meaning he and his officers were responsible for funding nearly three-fifths of their own department's budget.¹⁴¹ Notably, Utah adopted a ban on formal police quotas in 2018.

Within days of Castro's firing, Mantua Police Cpl. Bret Bergstrom submitted his resignation, writing that he had been repeatedly asked to patrol the highway and write citations and that he had begun to feel like "part of a revenue stream and not law enforcement."¹⁴² Four other officers resigned within two weeks, ultimately prompting Johnson's resignation on April 26, 2021.¹⁴³ Just days before resigning, Johnson told residents at an April town council meeting that increased traffic enforcement could be one solution to the town's budget shortfall, with raising taxes being another option.¹⁴⁴

The Utah Legislature enacted Senate Bill 75 in 2022, establishing the state's 25% cap on revenue from traffic fines.¹⁴⁵ The bill's sponsor, state Sen. Lincoln Fillmore, stated the bill was intended to ensure that "police officers don't turn into revenue agents."¹⁴⁶

For both fiscal years 2023 and 2024, the State Auditor's Office found that all Utah municipalities were in compliance with the 25% cap.¹⁴⁷ In 2024, Sunset, a city of about 5,000 people in Davis County, generated the highest percentage of general fund revenue from traffic fines at approximately 15%, well below the cap. Mantua itself generated 13% of its general fund revenue from traffic fines in 2024, earning approximately $206,800 from such fines.¹⁴⁸ While the 25% cap is a meaningful reform, it applies only to traffic fine revenue, not to other types of fines and forfeitures that municipalities collect.

Texas

In Texas, legislative efforts to limit local government reliance on traffic fine revenue trace back to the early 1970s in response to examples of revenue-driven enforcement in small jurisdictions along interstate highways. The most notorious case was Selma, a town of approximately 207 residents at the time, located along Interstate 35 between Austin and San Antonio. In a 1974 expose, Texas Monthly described Selma as "the perfect speed trap."¹⁴⁹ The article claimed that Selma concealed the full extent of its activities by violating several Texas statutes and withholding access to public records but estimated that the town generated $168,000 from fines annually.¹⁵⁰ That translates to roughly $812 in court revenue per resident (roughly $5,000 in 2025 dollars adjusting for inflation). The magazine further claimed that Selma's city limits were deliberately drawn as a narrow corridor along I-35, beginning at the crest of a hill where radar was strategically positioned under a bridge to catch motorists whose speed naturally increased while descending.¹⁵¹ Selma's notoriety persisted into the 1980s, memorialized in Steve Earle's 1986 song "Guitar Town," which warns travelers "there's a speed trap up ahead in Selma Town."

The first legislative attempt to address such practices came in 1973 when Representative Bennie Bock of New Braunfels introduced House Bill 550 during the 63rd Legislature.¹⁵² The bill sought to prohibit towns with populations under 5,000 from using radar on interstate highways, instead reserving interstate speed enforcement in those areas to the state Department of Public Safety. Despite passing both chambers, then-Gov. Dolph Briscoe vetoed the legislation. The Texas Monthly article noted that "thanks to Briscoe, Selma's operation continues to thrive," along with similar practices in nearby Georgetown and Live Oak.¹⁵³

A second legislative attempt, House Bill 405, succeeded in 1975 and amended Article 6701d of Vernon's Texas Civil Statutes (the Uniform Act Regulating Traffic on Highways) to establish a fine-sharing formula for speeding violations on Interstate highways detected by speed-measuring devices in municipalities.¹⁵⁴ Under this original framework, municipal courts were required to remit to the state treasurer any portion of speeding fines exceeding $2 multiplied by the number of miles per hour over the posted speed limit.

In 1981, House Bill 1162 exempted municipalities with more than 5,000 residents from having to share fine revenue from speeding violations on interstate highways.¹⁵⁵ A legislative bill analysis of HB 1162 noted that the law's purpose was "to discourage the use of radar as a local revenue device by certain small cities in which most of the interstate travel is not local traffic" and explained that in larger cities "the interstate freeway system plays an important part of the city's internal transportation system, and much of it is local traffic."¹⁵⁶

The most significant expansion came in 1989 with House Bill 243.¹⁵⁷ Rather than focusing solely on interstate speeding violations, the new law broadened the restriction to encompass all highway law enforcement and introduced a revenue cap mechanism at 30% of total revenue.

A 1990 Texas attorney general opinion addressing the implementation of HB 243 concluded that the population-based classification was constitutional, finding "a reasonable basis for the classification made by section 144" and that the legislature may have "concluded that the chance for abuse in charging traffic violations on interstate highways was greater in small municipalities that utilize the money generated from traffic fines from nonresidents as a substantial portion of their revenue."¹⁵⁸

However, the 1989 reforms were partially undermined during the 1995 recodification of Texas transportation laws. According to a 1999 bill analysis for House Bill 352, the 74th Legislature "sought to prevent cities from circumventing the intent of the law by correcting technical deficiencies in 1995, but the corrections were not carried into the Transportation Code by the recodification of the law that same year."¹⁵⁹ This created a loophole where the 30% threshold applied only to violations of highway laws in a subtitle of Title 7 rather than the entire title. The legislature corrected this error in 1999 via HB 352.¹⁶⁰

In 2011, the Texas Legislature enacted House Bill 1517, which extended the law to apply to counties with fewer than 5,000 residents and added reporting requirements for jurisdictions collecting at least 20% of revenue from traffic fines.¹⁶¹

Enforcement of these provisions has been limited. According to a 2022 Houston Chronicle investigation, comptroller records showed that over a five-year period, only four municipalities were forced to return excess revenue collected from traffic fines.¹⁶² Pat Monks, founder and past president of Traffic Lawyers of Texas, told the Chronicle that the law is rarely invoked because "relying on municipalities to self-report gives them the opportunity to skirt the requirement."¹⁶³ The statute also allows municipalities to count self-sustaining enterprise funds such as water and sewer in their total revenue calculations, which can keep the fine revenue percentage just below the 30% threshold.¹⁶⁴

5.2.2 Threshold-Based Investigations

5.2.2 State Detail

Threshold-Based Investigation States

GA Georgia 35% speed-detection triggerAR Arkansas 30% traffic-revenue triggerOK Oklahoma 50% ticket-revenue trigger

Current Policy

Georgia

35% speed-detection trigger

Speed-detection revenue at or above 35% of a police agency budget can trigger state oversight.

View profile

Arkansas, Georgia, and Oklahoma have adopted laws that trigger state investigations of local governments when law enforcement revenues exceed specified thresholds.

Georgia

Georgia's reform efforts trace to one of the most notorious speed traps in American history: the Long County town of Ludowici, located at the junction of U.S. Routes 25, 82, and 301 along what was, before the construction of Interstate 95, the primary north-south corridor for motorists traveling between the Northeast and Florida.¹⁶⁵ By the 1950s, an estimated one million motorists passed through Ludowici each year, and the town had developed an array of schemes to extract revenue from them.¹⁶⁶ The most infamous involved a downtown traffic signal rigged to switch from green to red without a yellow interval, controlled by a remote switch reportedly operated from a local barber shop, with a Ludowici police officer stationed at the intersection to ticket drivers who "ran" the light.¹⁶⁷ The intersection was on a stretch of road that local residents bypassed via a shortcut, ensuring that nearly all citations went to out-of-town motorists.¹⁶⁸ By 1959, Time magazine had already labeled Ludowici a "jerkwater traffic trap," and AAA formally designated the town a speed trap.¹⁶⁹

Ludowici's enforcement practices proved remarkably resistant to state intervention. In 1963, then-Gov. Carl Sanders temporarily suspended police arrest powers in Long County in response to widespread corruption.¹⁷⁰ The most theatrical intervention came in April 1970 when then-Gov. Lester Maddox ordered state workers to erect large billboards just inside the county lines north and south of town. The signs read: "BEWARE! YOU ARE IN LONG COUNTY AND APPROACHING LUDOWICI, GEORGIA. DON'T GET FLEECED IN A CLIP JOINT. DON'T GET CAUGHT IN A SPEED TRAP."¹⁷¹ After locals tore one of the signs down, Maddox posted Georgia state troopers on twenty-four-hour shifts to guard them.¹⁷² Maddox, who described Ludowici as "lousy, rotten, corrupt, nasty and no good," reportedly threatened to declare martial law and at one point hinted that the Department of Transportation might find that a bridge into town needed to be closed for repairs lasting eighteen months.¹⁷³

The Georgia General Assembly's first major legislative response predated Maddox's billboard campaign. Between 1962 and 1968, the state prohibited local law enforcement agencies from using speed detection devices altogether.¹⁷⁴ In 1968, the General Assembly enacted what became the foundation of Georgia's modern oversight framework, authorizing the Department of Public Safety to issue permits to county and city law enforcement agencies for the use of speed detection devices on specific roadways.¹⁷⁵ The 1968 law required that permit applications name each street or road on which a device would be used, gave DPS authority to deny or revoke permits, and prohibited the use of speed detection devices in any jurisdiction where arresting officers or court officials were paid on a fee system. Preventing local governments from "employing the use of speed detection devices primarily for the collection of revenue rather than for purposes of public safety" was among the stated purposes of the framework.

Despite the new permitting regime, Ludowici continued to operate aggressively for another decade and a half. In 1983, the Georgia State Patrol stripped the Ludowici Police Department of its license to use radar guns following a state investigation, and the state invalidated all 1,553 traffic citations the city had issued between January 1982 and October 1983 due to errors and procedural violations uncovered in the investigation.¹⁷⁶ By that point, however, the completion of Interstate 95 had already begun to divert traffic away from U.S. 301, depriving Ludowici of the through-traffic on which its enforcement economy depended. As one account later put it, Ludowici was brought down "not by Maddox, but by Interstate 95."¹⁷⁷

Ludowici's decline did not end revenue-oriented enforcement in Georgia, and the General Assembly returned to the issue in 1999.¹⁷⁸ New provisions adopted that year created a rebuttable presumption in DPS investigations that a law enforcement agency was using speed detection devices for "purposes other than the promotion of public health, welfare, and safety" if revenue from speeding fines equaled or exceeded 40% of the municipal law enforcement agency's budget. Fines for speeding more than 17 mph over the posted limit were excluded from the calculation.

In October 2014, the Atlanta Journal-Constitution published an investigation identifying a number of small Georgia towns where traffic ticket revenue had become a dominant source of municipal funding.¹⁷⁹ Among the towns highlighted was Warwick, a community of approximately 500 residents in Worth County situated along Georgia State Route 300. Warwick had collected nearly $1.5 million in fines and forfeitures in fiscal year 2013. A Warwick city councilman told the Journal-Constitution: "We had the opportunity to generate revenue on Highway 300 … And that's what we did."¹⁸⁰ The 2014 reporting also drew attention to Poulan, profiled earlier in Part 4 of this report, and to several other small jurisdictions along U.S. 82 and Interstate 75.

In 2015, the General Assembly responded with Senate Bill 134, lowering the rebuttable-presumption threshold from 40% to 35% of a municipal police agency's budget and adjusting the exclusion to cover only fines for speeding more than 20 mph (rather than 17 mph) over the posted limit.¹⁸¹

Despite these reforms, enforcement actions have been intermittent and the law's narrow scope has limited its effectiveness. Warwick itself remained a heavy collector of enforcement revenue well after the 2015 reform. A 2019 DPS investigation concluded that Warwick Police Department violated O.C.G.A. 40-14-11(d), but no penalties were imposed.¹⁸² The city's fines and forfeitures revenue still amounted to roughly 65% of its budget in 2022,¹⁸³ with Warwick remaining technically compliant with the 35% speeding-citation threshold because much of its revenue came from non-speeding offenses or from speeding citations excluded from the calculation.

A more recent investigation by DPS found that the city of Lenox "consistently altered" the dispensations of speeding violations below 20 mph so that the final dispensations were for non-speeding violations.¹⁸⁴ This had the effect of excluding the fine revenue associated with those citations from the 35% threshold. The city collected $1.3 million in fines and forfeitures revenue in 2022, which accounted for 73% of the city's budget that year. That's nearly $1,800 for every man, woman, and child in a city of less than 800 residents.

Georgia's framework, even after the 2015 reforms, applies only to revenue from speed detection devices. It places no limit on revenue from non-speeding fines, court fees, civil penalties, or other monetary charges. As the Lenox investigation suggests, this narrow focus invites the same kind of reclassification and accounting maneuvers that have undermined narrow caps in other states.

Arkansas

Arkansas' "Speed Trap Law" was first adopted in 1995 as Act 855.¹⁸⁵ The legislation came in response to egregious examples of revenue-driven enforcement in small towns along the state's highways, particularly the city of Gilmore along U.S. 63 in northeast Arkansas.¹⁸⁶ In the early 1990s, the Gilmore Police Department issued up to 450 speeding tickets per month in a town of just 331 residents, generating more than half of the city's budget. Then-state Sen. Jerry Bookout of Jonesboro introduced the Arkansas Speed Trap Law to curb such practices, which he described as legalized "bushwhacking."¹⁸⁷ The law notably defined "abusing police power" as "the exercise of police power to enforce criminal and traffic laws for the principal purpose of raising revenue for the municipality, and not for the purpose of public safety and welfare."

The original 1995 law created a rebuttable presumption that a municipality was "abusing police power" if traffic fine revenue exceeded 30% of the municipality's total expenditures (excluding capital expenditures and debt service) or if more than 50% of speeding citations were written for violations of 10 mph or less over the posted limit. Upon a finding of abuse, the Director of Arkansas State Police had authority to order municipalities to cease highway patrols and divert future fines to county general funds.

Just two years later, in 1997, Act 842 altered the enforcement mechanism by shifting decision-making authority from the state police director to local prosecuting attorneys.¹⁸⁸ The law now required the director to conduct investigations and forward findings to the prosecuting attorney, who would determine whether abuse occurred and impose appropriate sanctions.

The most comprehensive reform came in 2019 with Act 364, sponsored by then-state Rep. Michelle Gray and then-state Sen. Jason Rapert.¹⁸⁹ Rapert explained at the time that "in the past few years we have had some places where we've had some issues from what is called a 'speed trap'" and that the bill would "clarify what classes of city it expands to, which means we can take a look at more cities in the state who might fall into a speed trap situation."¹⁹⁰ The 2019 reforms expanded coverage to first-class cities and all state highways (not just multi-lane divided highways), refined the definition of revenue to exclude certain municipal functions like water and sewer departments, and required that municipal audits automatically include inquiries into potential speed trap violations.

The 2019 reforms came after years of high-profile enforcement actions. Damascus, a town of 385 residents situated on U.S. 65, reportedly operated a speed trap for more than half a century on the heavily traveled highway.¹⁹¹ In 2014 alone, the town's four-person police force wrote 2,032 speeding tickets and generated nearly $400,000 in fines and court costs.¹⁹² In May 2017, then-Prosecuting Attorney Cody Hiland ordered the Damascus Police Department to cease patrolling U.S. 65 and a state highway running through the town, effective until the end of 2018.¹⁹³

More recently, Menifee, a town with a population of less than 300, was caught breaking Arkansas' speed trap law after collecting about $120,000 in 2020, nearly half of the city's revenue that year.¹⁹⁴ City officials claimed that about $46,000 came from unpaid fines and fees from 2013 to 2019 that were collected in 2020, which pushed the city over the 30% threshold.¹⁹⁵ Complaints from Menifee and Damascus led to the most recent reform in 2023. Act 520 amended the definition of "revenue" to exclude ancillary enforcement revenues such as failure to appear and failure to pay citations, as well as late fees assessed on traffic citations.¹⁹⁶ This change narrowed what counts as revenue under the speed trap calculation, making it somewhat easier for municipalities to come in under the 30% threshold.

Arkansas' anti-speed-trap law, like Georgia's, has significant limitations. The statute applies only to traffic offenses that are misdemeanors or violations of state law or local ordinances and excludes certain types of municipal expenditures from the calculation. The narrow 30% threshold, while stricter than Georgia's 35% limit for speed detection devices, still allows municipalities to derive substantial portions of their budgets from traffic enforcement. Unlike Georgia's focus specifically on speed detection devices, Arkansas' law covers all traffic offense citations, providing somewhat broader protection for motorists but still leaving room for municipalities to fund operations through non-traffic enforcement.

Separately, Arkansas recently enacted a structural reform in 2025 that addresses fiscal incentives from a different angle. Act 371 eliminated the obligation of cities and counties to contribute to the salaries of state district court judges and capped at 50% the share of district court filing fees and uniform court costs that local governments may retain, with the remainder remitted to the State Administration of Justice Fund.¹⁹⁷ Act 371 did not alter the Speed Trap Law's 30% threshold as the operative ceiling on overall fines reliance, but by severing the direct link between local government payrolls and district court judges it weakens one of the institutional predictors of fines and forfeitures reliance identified in Part 2.

Oklahoma

Legislative efforts to address revenue-driven enforcement in Oklahoma trace at least as far back as 1999, when SB 234, passed both chambers before dying at session's end after the House adjourned without acting on the conference committee report.¹⁹⁸ The bill appears to have been modeled on Arkansas's "Speed Trap Law," enacted four years earlier in 1995, defining "abusing police power" in nearly identical terms, setting the same 30% expenditure threshold, including the same alternative trigger based on the proportion of citations written for minor speed violations, and prescribing the same sanctions of ceasing highway patrols and diverting fine revenue to county general funds.

Prior to SB 234, the city of Stringtown (profiled in Part 4), perhaps Oklahoma's most notorious speed trap, had been subject to investigation by the state Transportation Department as far back as the 1980s.¹⁹⁹ In the early 1990s, the speed limit on U.S. 69 through Stringtown was raised to 55 mph following a Transportation Department investigation.²⁰⁰

Oklahoma's current framework, including the 50% revenue threshold and the formal complaint and investigation process, was established in 2003 through HB 1456.²⁰¹ Subsequent legislation, HB 2265, in 2004 simplified the complaint trigger by removing the requirement that the preponderance of citations be for violations of 10 mph or less over the posted speed limit.²⁰² The law's first high-profile enforcement action came in July 2005, when the Department of Public Safety suspended Big Cabin's ticket-writing authority on U.S. Highway 69.²⁰³ An investigation found that nearly three-quarters of the town's revenue ($492,826 of its $681,028 budget) came from traffic citations in the prior fiscal year.²⁰⁴ That investigation was triggered by a local truck stop owner who, frustrated that aggressive enforcement was deterring customers, erected a "speed trap ahead" sign before filing a formal written complaint with the DPS.²⁰⁵

A 2006 report from Tulsa World found that among 73 eastern and southeastern Oklahoma towns, 15 relied upon traffic citations as their primary source of revenue.²⁰⁶ By the time the Tulsa World report was published, the state had already taken formal enforcement action against several of the towns it identified. In addition to Big Cabin, both Shamrock and Moffett had been stripped of their authority to issue citations on state highways, and Shamrock's police department was subsequently shut down entirely after investigators found that its officers lacked valid law enforcement certification.²⁰⁷

In April 2007, then-state Rep. Paul D. Roan attached a provision to HB 1616, a technical corrections bill governing the state police, that severely weakened Oklahoma's law.²⁰⁸ HB 1616 deleted state highways from the statutory definition of a speed trap and converted speed trap investigations from a mandatory to a discretionary matter. Only one legislator opposed the bill before then-Gov. Brad Henry signed it into law on April 30, 2007.²⁰⁹ Legislators who had not closely read the bill were furious upon learning of the change. Then-state Rep. Glen "Bud" Smithson told the Sequoyah County Times: "When I found out about it, I was sick. I still am. Most definitely we're going to bring it back next session. … Public safety should not be a revenue raiser."²¹⁰

Within weeks, the state Senate voted 43-3 to pass SB 748, with the House approving the measure the following day.²¹¹ The bill restored the commissioner's authority to designate portions of state highways for special traffic enforcement and reinstated the structured investigation process, taking effect Nov. 1, 2007. However, the restored law made investigations optional rather than requiring the commissioner to act upon a confirmed finding.

Despite attempts at reform, speed trap practices have persisted across Oklahoma. In 2012, the state auditor found that Bernice, a town of 500 residents on Highway 85A, collected $300,253 in traffic citations between 2006 and 2011, including $106,308 in excess of the $50 maximum permitted by state law for ordinance violations.²¹² The town's trustees voted not to refund the illegally collected fines.²¹³ In 2014, the owner of a Meeker pawn shop filed a federal lawsuit against the city after a reserve police officer set up a speed trap blocking his business's driveway in apparent retaliation for a sign he had posted warning drivers of the speed trap ahead.²¹⁴

Oklahoma's threshold-based investigation framework has several notable limitations. The 50% threshold is the most permissive among states with threshold-based oversight, permitting municipalities to derive nearly half of all operating revenue from traffic enforcement before triggering any state scrutiny. The law applies only to enforcement on state and federal highways and only to traffic-related citations, leaving non-traffic enforcement and enforcement on local roads entirely unregulated. The complaint-driven process places the burden on citizens or public officials who may face political or economic disincentives to file formal complaints, and the discretionary nature investigations since 2007 means that even valid complaints may be neglected.

As the case of Stringtown, profiled in Part 4, illustrates, towns that have been stripped of citation authority on multiple separate occasions have repeatedly reconstituted their police departments and resumed enforcement once legal restrictions lapsed or were lifted.

5.2.3 Threshold-Based Reporting Requirements

5.2.3 State Detail

Threshold-Based Reporting State

FL Florida 33% reporting trigger

Current Policy

Florida

33% reporting trigger

Traffic citation revenue above 33% of law-enforcement funding triggers reporting to the Legislative Auditing Committee.

View profile

One state, Florida, has adopted a law that imposes reporting requirements if traffic citation revenues exceed a specified threshold. However, Florida's law does not explicitly provide for any investigation or remedy beyond delineating these reporting requirements.

Florida

Florida's legislative efforts to prevent taxation by citation originated in 1992, when the Legislature passed House Bill 223 to prohibit state agencies from "establishing a traffic citation quota."²¹⁵ However, this quota ban did not explicitly apply to county sheriffs' offices or municipal police departments. This omission became apparent following a scandal in Waldo, a town of approximately 1,000 residents located in north-central Florida along U.S. Highway 301.

By the early 2010s, Waldo had become nationally known as one of the country's most aggressive speed traps. In 2013, the town generated approximately $464,400 in "police revenue," accounting for roughly half of its $1 million in general revenue.²¹⁶ Waldo's seven police officers issued more than 11,000 traffic citations that year—roughly 11 citations per resident, leading AAA to designate Waldo as a "traffic trap" and erect a billboard warning oncoming drivers at the edge of town.²¹⁷

On Sept. 5, 2014, Waldo police chief Mike Szabo resigned after being placed on administrative leave amid a Florida Department of Law Enforcement investigation into allegations he had secretly recorded a conversation with another officer.²¹⁸ The scandal deepened when five Waldo police officers came forward at an August City Council meeting alleging that Szabo and City Manager Kim Worley had implemented a quota requiring officers to write one ticket per hour during their 12-hour shifts.²¹⁹ The officers also claimed they had reported these concerns to Worley as early as 2010 but were ignored. Following the revelations, Szabo's interim replacement was also suspended, and the city brought in outside leadership from the Alachua County Sheriff's Office to temporarily run the department. The Waldo Police Department was ultimately disbanded on October 2, 2014, less than a month after Szabo's resignation.²²⁰

In response to the Waldo scandal, the Legislature passed Senate Bill 264 in 2015, commonly referred to as the "Waldo Bill."²²¹ The legislation clarified that the quota prohibition applied to all traffic enforcement agencies, including county sheriff's offices and municipal police departments. The Waldo Bill also established the financial reporting mechanism for jurisdictions whose traffic fine revenue exceeds 33% of law enforcement funding.

Florida's Legislative Auditing Committee does not appear to publish public summaries showing which jurisdictions exceed the 33% threshold or how many reports are submitted annually. The statute does not mandate public disclosure or specify enforcement mechanisms for non-compliance. This lack of transparency makes it difficult to assess whether the reporting requirement is functioning as intended. The law relies on municipalities to self-report when they exceed the threshold, but without independent verification or consequences for failing to report, compliance may be limited.