This page shows side‑by‑side drafts generated using the modular reporter prompts.

Source summary: tmp/experiments_runs/reporter-carnage-37d-2559/summary.json

Variant Summary (averages)

VariantAvg Score (1–10)Poignancy PassAvg Cost
default0.00/1 (0%)$0.00
recent_carnage0.00/1 (0%)$0.00

Detailed Runs

GeoVariantTitleWordsQuotesLinksUnmatched DomainsAuto PassPoignancyEditor Score (1–10)Cost
assembly-46defaultOne crash, many streets: the slow surge of danger in Brooklyn’s AD 46814000❌❌0.0$0.00
assembly-46recent_carnageAD 46: A crash on Neptune and Cropsey. A district under pressure.398000❌❌0.0$0.00

default

One crash, many streets: the slow surge of danger in Brooklyn’s AD 46

A single life, many streets

In the early hours, a pedestrian was struck on Neptune Avenue and 24th Avenue in Brooklyn. The crash is recorded in NYC Open Data as CrashID 4788054. The pedestrian was killed. The incident sits in a record that shows one killed in Assembly District 46 since 2022, and it sits among hundreds of injuries logged in the same period.

The data show this district has had at least one fatality in the period, with dozens of injuries and many crashes logged since 2022. See the crash record and the district’s injury panel for the figures.

Crashes dataset

The pattern, not the one moment

The broader record paints a relentless picture. In this period, the city logged 4,155 crashes with 11 deaths and 2,246 injuries overall. The breakdown shows pedestrians, bicyclists, and vehicle occupants alike are harmed in a spectrum of crashes. The local numbers are not isolated. This is part of a citywide trend.

  • Crashes in the dataset window: 4,155
  • Deaths: 11
  • Injuries: 2,246
  • Serious injuries: 16 across all modes

The assembly district in this report is AD 46, which includes neighborhoods such as Bay Ridge, Dyker Heights, and Brighton Beach, among others. The geographic scope includes multiple community boards and NTA areas listed in the context. These neighborhoods sit in the ongoing tally of harms across the city.

Who is being harmed, where it lands

Top locations show repeated trouble at Neptune Avenue and Neptune Park/Ocean Parkway corridors, with intersections like Neptune Ave near Shore Parkway repeatedly appearing in the small-geo analysis for this period. The small-geo analysis highlights pedestrian and bicyclist injuries and notes that vehicles—especially SUVs—contribute to the crash burden in this district.

  • Hot intersections: Neptune Avenue, Shore Parkway, and 82 Street are named in the top intersections cited in the data, illustrating where the risk clusters exist.
  • Vehicle mix: the data show a mix of bicyclists and occupants in crashes; heavy vehicles appear in several incidents, with bikes and SUVs involved in multiple listings.

What must change, on record

The policy thread in the data shows two concrete levers in reach: speed enforcement and speed-limit policy, and a debate over camera-enforced safety in school zones. The state has seen bills and votes around speed safety, including a recent bill (S 8344) and media coverage of politicians’ votes on speed cameras.

  • Speed safety policy: File S 8344 — debates and votes noted in Open States; the record shows a stance in a published vote narrative.
  • Accountability coverage: Streetsblog NYC tracked votes on speed cameras among city and state officials; the reporting notes who opposed and who supported these tools.

Two concrete fixes, grounded in the data

  • Lower the default speed limit citywide and protect school zones with camera enforcement as tools that reduce speeding and injuries.
  • Design safer streets in the AD 46 footprint by emphasizing safer crossings and turn design to reduce conflicts between drivers and vulnerable users.

What comes next

The numbers demand action that matches the record. The path is visible in the data: safer streets, slower speeds, and better design.

  • The data show a pattern that requires city and state action to curb the slow-motion danger. The next step is clear in the policy arena and in the streets themselves.
  • A concrete next step is to pass or advance the Stop Super Speeders Act and related speed-safety measures, paired with local street-design investments in the district.

FAQ: How were these numbers calculated?

  • Dataset: Motor Vehicle Collisions – CrashID dataset (H9G1-NX95). Filters used: date window 2022-01-01 to 2025-09-14; geography covering Brooklyn AD 46 and relevant NTAs/communities; modes include Pedestrian, Bicyclist, and Occupant crashes. Ingested data as of 2025-09-14.

  • Exact filtered query: here.

  • What is CrashCount? CrashCount is a reporting tool that tracks crashes, injuries, and fatalities by neighborhood and district to hold officials accountable for safety gaps. We rely on official datasets and published policy items in the context.

  • How is “killed_total” used here? The context’s injuries panel shows one killed in AD 46 in the period described; this is the one fatality figure used for the district’s mortality tally in the timeline.”

Citations

FAQ

  • Q: What is CrashCount? A: We’re a tool for helping hold local politicians and other actors accountable for their failure to protect you when you’re walking or cycling in NYC. We update our site constantly to provide you with up to date information on what’s happening in your neighborhood.
  • Q: How were these numbers calculated? A: Dataset: Motor Vehicle Collisions – Crashes (NYC Open Data). Fields used: accident date, on_street_name, off_street_name, pedestrian/bicyclist/other pedestrian locations, vehicle modes, injury severity, and person types. Filters: date window 2022-01-01 to 2025-09-14; geography: Assembly District 46 (Neighborhoods BK1001, BK1002, BK1061, BK1091, BK1302, BK1303, BK1391) as provided in context. Ingestion time: 2025-09-12.
  • Q: Where can I read the policy bits mentioned? A: Open States S 8344 and Streetsblog NYC coverage cited in the article.
  • Q: What is CrashCount’s geographic focus here? A: The Brooklyn AD 46 data, including the listed neighborhoods and community boards in the context.

Citations

  • Motor Vehicle Collisions – Crashes - Crashes , NYC Open Data, Accessed 2025-09-14
  • File S 8344 - S8344 , Open States, Published 2025-06-17
  • Ye Shall Know Their Names! Meet the Dirty Dozen City Pols Who Voted Against Speed Camera Program - Streetsblog article , Streetsblog NYC, Published 2025-06-23
  • Motor Vehicle Collisions – Persons - Persons , NYC Open Data, Accessed 2025-09-14

Geo: assembly-46

recent_carnage

AD 46: A crash on Neptune and Cropsey. A district under pressure.

Just after 12:40 PM on Jan 24, 2025, a crash on 24th Ave and Cropsey Ave left a pedestrian dead. The incident is in the dataset for Motor Vehicle Collisions and sits in the Brooklyn Assembly District 46 record. It’s one data point in a long list of harm in this district. Crashes dataset.

They were one of 1 person killed in AD 46 since Jan 1, 2025, and the pattern continues across the district as shown in the period data. The larger tally shows a steady stream of injuries and crashes across the neighborhood blocks in this coverage window. The panel for injuries in AD 46 marks 1 killed, with a spread of injuries across several categories in the time frame.

Where it happens matters. In small-geo analysis, Neptune Ave and Shore Parkway appear as hot intersections in this period, while 82nd St and Neptune Ave show recurring injuries in the data. See the small-geo analysis for the named streets. Small geo analysis.

What the numbers say, plainly: this district bears a steady load of crashes. The rolling data show hundreds of injuries citywide and thousands of crashes in the city, with AD 46 reflecting a share of that burden over 2022–2025. The tally is not a rumor; it’s a record of harm on our streets. The data sources alongside this report provide the exact figures used here. Citations list for data.

What can be done locally? The geography shows two clear cue points from the analysis: (1) hotspots on Neptune Ave and Shore Parkway, (2) intersections where pedestrians and cyclists spill into the streets with high risk. Concrete fixes cited in the context include safer street redesigns, daylighting, and targeted enforcement around high-traffic zones. See the top intersections and contributing factors in the context for reference. Top intersections.

Next step. The Assembly can push for the Stop Super Speeders Act in this session. The data show a pattern of risk concentrated in a small geography; targeting habitual speeders in this district aligns with the policy levers described in the context. S 4045C/A 2299C (Stop Super Speeders Act). A clear, local avenue for change remains.

Action for readers: take action now at /take_action/.

FAQ

  • Q: How were these numbers calculated? A: Dataset: Motor Vehicle Collisions – Crashes (h9gi-nx95). Fields used: crash_date, on_street_name, off_street_name, person_types, injury_severity, borough/assembly district. Filters: 2022-01-01 to 2025-09-14; geography: Assembly District 46 (AD 46) / Brooklyn; modes include pedestrian, bicyclist, vehicle types as shown. Extraction date: 2025-09-12. Filtered query: here.
  • Q: What is CrashCount? A: We’re a tool for helping hold local politicians and other actors accountable for their failure to protect you when you’re walking or cycling in NYC. We update our site constantly to provide you with up to date information on what’s happening in your neighborhood.

Citations

  • Motor Vehicle Collisions – Crashes - Crashes , NYC Open Data, Accessed 2025-09-14
  • Motor Vehicle Collisions – Persons - Persons , NYC Open Data, Accessed 2025-09-14
  • Motor Vehicle Collisions – Vehicles - Vehicles , NYC Open Data, Accessed 2025-09-14
  • File S 8344 - S8344 , Open States, Published 2025-06-17
  • Streetsblog NYC: Dirty Dozen City Pols Who Voted Against Speed Camera Program - article , Streetsblog NYC, Published 2025-06-23
  • Stop Super Speeders Act (S4045C/A2299C) - S4045C , Open States, Accessed 2025-09-14

Geo: assembly-46