Raleigh Council Reviews 11 p.m. to 5 a.m. Youth Curfew Proposal, With a Vote Set for Sept. 15

An 11 P.M. Deadline for Raleigh Teenagers

Nine people were shot in Raleigh over a few hours on the night of July 4 and into the early morning of July 5. Four of them were teenagers^[3][14]. The shootings happened in a string of separate incidents, not one event, spread across a nightlife district where police say more than 5,000 young people had gathered^[3][6]. Officers made 29 arrests that night and recovered 11 guns^[3].

Now Raleigh's city council is deciding what to do about it. On Aug. 18, the council reviewed a draft ordinance that would bar anyone under 18 from public spaces between 11 p.m. and 5 a.m., with exceptions for work, school events, religious activities, emergencies, and travel with a parent^[1][2][6]. A teen caught out would be sent to juvenile court. A parent could face a fine or a misdemeanor charge^[1]. A vote is tentatively set for Sept. 15, after more public comment^[6][17].

The two sides agree on almost everything that happened that night. They do not agree on what a curfew would actually do about it.

The Fact Both Sides Use Differently

Here is the timing problem nobody disputes: the shootings that night happened at Brier Creek around 10:30 p.m., and then in a string of incidents in Glenwood South between roughly 1:30 and 3:30 a.m.^[3]. An 11 p.m. curfew would have missed the first fight entirely. It would have covered the four Glenwood South shootings that came later.

That split matters because it shows what a curfew can and can't do. It doesn't erase the fact that guns were on the street that night. Police recovered 11 firearms from the incidents, which the department reads as evidence that the danger was real and immediate^[3]. But it also means the ordinance is a narrower fix than "stop this from happening again" — it changes who's allowed outside during only part of the window when trouble occurred.

Both camps also agree the gatherings were organized fast, on social media, which is part of why police were caught off guard. Officers had advance word about one planned gathering at Moore Square and dispersed about 75 people there. They were then surprised by crowds roughly 40 times larger elsewhere^[3][15]. That gap between what police can plan for and what actually shows up is at the center of the police department's argument for a new tool.

Why Police Want a Law That Kicks In Before Anything Happens

Raleigh police currently have no legal basis to move a group of teenagers out of a public area just because they're there. Officers can only act once a crime happens — a fight starts, a gun goes off. By the time that happens with a crowd of thousands, the department is already behind.

A curfew changes that. It makes presence itself, past a certain hour, the violation. That's the mechanism at the center of this fight: it lets police intervene before trouble starts, instead of only after^[3][9]. Police Chief Rico Boyce points to department data showing crimes involving juvenile suspects or victims are up 9% over the same point last year, and calls it part of a "trend of violence" the department needs new tools to address^[13].

Supporters also point to Winston-Salem, where a similar ordinance took effect June 22^[10]. That city's police chief said youth encounters — counting both offenders and victims — fell 26% in the ordinance's first 42 days, with no further viral gatherings^[10]. It's the single most-cited piece of evidence for the pro-curfew side statewide right now.

The Number Curfew Supporters Don't Mention

There's a catch with the Winston-Salem number, and with the research on curfews generally. Winston-Salem's citywide crime was already down about 13% before the curfew even started, for reasons unrelated to the ordinance^[6][10]. Teen gatherings also tend to ebb over the course of a summer regardless of what a city does. Neither fact proves the curfew did nothing — but it means the 26% figure can't be cleanly credited to the ordinance alone.

The stronger evidence against curfews is older and broader. A 2016 review by researchers Wilson, Gill, Olaghere and McClure, published by the Campbell Collaboration, looked at 12 separate studies of youth curfews around the country. It found that, on average, curfews didn't reduce youth crime or victimization. During curfew hours specifically, the measured effect was slightly positive — meaning crime went up slightly, not down^[8]. Across all hours, the effect was close to zero.

The review's own authors noted a limit worth keeping in mind: none of the 12 studies were randomized experiments, so the finding is not proof a curfew can't ever work, just evidence that none of the ones studied did^[8]. Opponents on Raleigh's council, along with the ACLU of North Carolina, cite this research as the reason to expect the ordinance won't reduce the violence it's meant to stop^[8][9].

Who Actually Gets Stopped

The research argument is only half of what opponents are making. The other half is about what happens once police have the authority to stop any teenager outdoors at night. The ACLU of North Carolina has previously warned Raleigh that broad curfews raise concerns about equal protection and due process, and can lead to arbitrary enforcement^[9].

Council Member Stormie Forte raised the concern directly at the Aug. 18 meeting: kids in certain neighborhoods, she said, could be stopped for normal teenage activity that wouldn't draw police attention somewhere else^[1]. It's not a claim that the ordinance is written to target anyone. It's a concern about how enforcement plays out once the law exists — an argument about discretion, not intent.

There's a related, quieter argument in local reporting: Raleigh has closed off a lot of the indoor places teenagers used to gather at night — malls, arcades, and similar public spaces^[19]. A curfew removes an option without adding anywhere new for teens to go. That's a structural fact about the city that the ordinance itself doesn't change.

What the Council Actually Has to Weigh by Sept. 15

Set aside the research question for a moment, because there's a separate pressure driving this vote regardless of what the studies say. Winston-Salem already has a curfew. Charlotte is considering one that would start even earlier, at 9 p.m.^[7][12]. If Raleigh is the one city in the region without one and another large gathering happens, city officials expect to be asked why.

That pressure explains why the mayor and council majority are moving toward a vote rather than waiting for more data. A city government that appears to do nothing after nine people are shot risks losing credibility to ask anything of parents going forward — a real institutional stake, separate from whether the policy will work^[5][6].

The people caught in between are residents, business owners, and families. Glenwood South merchants watched their district empty out during the disturbances and want something that restores predictability. Many parents of Black and Latino teenagers support tougher action on gun violence while also opposing a law that makes their own kids more likely to be stopped — positions that aren't in conflict, even though the debate often treats them as if they are^[10][19]. Under the draft ordinance, a parent working a night shift could also be the one fined if their teenager is out past 11 p.m^[1].

Coverage of the debate splits along familiar lines: outlets on the right, like Fox News and Carolina Journal, lead with the shootings and the police data, often without mentioning the Campbell Collaboration findings at all^[5][6]. Outlets on the left, including NC Newsline and The Marshall Project, foreground the research and the discretion concerns, giving less space to the shooting victims themselves^[7][18]. WUNC and WRAL land closer to the middle, laying out both the council's skepticism and the police department's numbers side by side^[1][3]. The council votes on Sept. 15. Whichever way it goes, both the shooting and the research showing curfews don't reliably prevent the next one will still be true.