Menu
Norwich CT Fire.com — helmet and flames
Decorative AI-assisted adaptation of Norwich harbor, Bobphoenix (November 8, 2018). Adaptation shared under CC BY-SA 4.0. Not a documentary image.

THE STORY / UPDATED OCTOBER 3, 2026

Why I challenge the City’s case.

I believe the drive for control shaped the case made against Norwich’s volunteers. The test is whether the cited problems justify the particular actions the City took.

A sourced starting point, with the limits of each record kept visible.

AUTHOR’S ACCOUNT

I started with a question.

I knew very little about Norwich’s fire service when the news of Yantic’s closure led me to start asking questions. I spoke with volunteers and City officials, requested records, visited firehouses and worked through the reports. The question I kept coming back to was simple: is this true?

Why I started looking — the personal account

WHAT THE RECORD ESTABLISHES

Follow the dates, the claimed authority and the particular actions. The documents establish what was proposed, said or ordered; that is separate from whether an action was justified or legally valid.

JUNE 9, 2021

The policy debate predates 2026.

Public Safety Committee minutes record discussion of a citywide administrative fire-service director. They also record opposition and concerns from volunteer leaders. That is evidence of an earlier policy debate; it does not, by itself, settle the merits of a later proposal.

Primary source: committee minutes, pp. 4–8

DECEMBER 5, 2022 / FEBRUARY 1, 2023

Read adoption beside repeal.

Ordinance 1832 established an automatic-aid framework and assigned policy responsibilities. Norwich's published Code history identifies its adoption on December 5, 2022 and repeal following the February 1, 2023 special election.

The original ordinance remains important historical evidence. Its text should not be presented as an unchanged statement of current law.

Primary source: Ordinance 1832Code record: adoption and repeal
Decorative AI-assisted adaptation of Marc N. Belanger’s City Hall photograph (2009), original released into the public domain. Not a documentary night photograph.

FEBRUARY 24, 2026 / REVIEWED OCTOBER 2

Written assessments do exist.

The reviewed FOIA production contains four February written fire assessments and a February 24 email transmitting them from Chief Wilson to City Manager Salomone under “Thoughts moving forward.” The email describes a starting point for work with the public-relations company.

A MATERIAL CORRECTION

A blanket claim that no written fire analysis existed is too broad. The remaining question is whether these assessments are the particular six-month system analysis described publicly, and how their findings support each proposed action. That connection has not been established by this review.

Source reference: FOIA Part 5, 000009093-c837cb59e4f1578b.pdf, pp. 1–2, and four attached assessments. A verified selected transcription of the transmittal appears below; contact details are omitted.

SELECTED SOURCE TRANSCRIPTION / FEBRUARY 24, 2026

“Thoughts moving forward”

Samuel Wilson, Norwich Fire Chief, to John Salomone, Norwich City Manager. These names and public roles identify the correspondents; the original header displays email addresses, omitted here.

Displayed date: Tuesday, February 24, 2026 at 3:57 PM (UTC+00:00).

EXACT WORDING / PAGE 1

“Ive create these as a start to working with the PR company. They have a proposal in your email.”

Original wording preserved; line wrapping normalized.

FOUR ASSESSMENT ATTACHMENTS / PAGE 2

  • Public Safety Review - Public.docx
  • Public safety Review - Legal Consideration.docx
  • Public Safety Review - Media Plain Language Fact Sheet.docx
  • Norwich_Fire_EMS_Fact_Sheet.docx

The source lists five attachments. The fifth is image001.png, separate from the four assessment documents.

Source: produced PDF 000009093-c837cb59e4f1578b.pdf, pages 1–2, FOIA Part 5. Both pages visually checked for this transcription.

Selection note: email addresses, phone numbers, the signature block, postal address and unrelated details are omitted. This is a selected transcription, not the full record.

This rendered email establishes its visible wording and attachment list. By itself, it does not establish the attachments' contents, final approval, publication, native-message authenticity or improper intent.

FEBRUARY 25, 2026

The communications work is documented.

An Intersect Public Solutions engagement letter describes public-affairs support for the City's Unified Command effort at $4,500 per month. It establishes a proposed scope and monthly rate; it is not proof of every payment or activity performed.

Communications planning belongs in the story. The existence of that work alone does not establish fabricated incident findings or an improper motive.

Primary source: IPS engagement letter, one page

THE INCIDENT REVIEW / SCOPE MATTERS

Read the reports in context.

The reviewed packet contains 18 report files covering 17 incident identities. Two files concern incident 25-0004323 and contain different versions. The October 2 focused review read all narratives across 141 pages; it did not independently reconstruct each incident or verify every tabular field. Additional production remains outside this bounded review.

The narratives include operational criticism and examples of volunteer contribution. Timing inconsistencies in a summary table also require careful separation from the actual arrival clocks. A calculation mismatch does not establish the true response time or intentional manipulation.

KEEP CONTRARY EVIDENCE IN VIEW

Four written assessments were located. Most criticisms in the reviewed incident narratives concern specific operations. Other passages credit volunteer work or identify problems involving paid crews and city alerting. A fair account must carry those facts alongside the concerns.

Open the existing evidence inventory

Archive note: the linked evidence inventory is an earlier publication, with material dated through September 29, 2026. Read its incident-count shorthand alongside the October 2 source notes below. Historical litigation coverage dated August 12 is not a statement of current case status.

SELECTED INCIDENT SOURCE NOTES / OCTOBER 2, 2026

Citations below give the individual PDF page, then the page in “18 Incident Reports order provided.pdf” (141 pages). These are selected excerpts and paraphrases from the completed narrative review, not the full records or an independent reconstruction.

What the wording supports.

1391.pdf, p. 4 / combined p. 40: Andrew Thomasson's April 4, 2025 update states, “Yantic crew unable to do anything due to members who arrived first.” The surrounding account identifies a driver and probationary member, then describes reassignment to T1. The broad wording is worth examining; it remains incident-specific and does not establish that volunteers generally lacked qualifications.

1469.pdf, p. 17 / combined p. 59: Stephen Fricke's account criticizes size-up and accountability, including accountability of paid crews, and records a city-alerting problem. That context must accompany a summary of its criticism.

1638.pdf, p. 7 / combined p. 69: Marc Landry's narrative records, “Yantic personnel entered and monitored the fire room while NFD crews rehabbed.” Useful volunteer work is part of this record too.

Two versions, one incident.

4323.pdf, pp. 1–11 / combined pp. 95–105, and 4323-2.pdf, pp. 1–7 / combined pp. 106–112, concern the same incident. The longer file includes an additional unit, an aiding-company section and expanded incident and origin-and-cause references. They are different versions, not identical duplicate reports. The reviewed differences do not establish why revisions occurred; no timing-change claim is made.

Scope: all 18 report narratives were read; significant passages and version differences were visually checked. Not every tabular field was independently verified. Repeated narrative text is not independent corroboration. These sources do not by themselves connect the 17 incident identities to the February assessments or establish a public-relations motive for report wording.

MY PERSPECTIVE / INTERPRETATION

Test the justification against the action.

I believe the City’s case against the volunteers has been overstated, and that the push for one chief needs to be examined alongside the actions taken against companies that resisted.

There are legitimate improvements to make. I support improvements that preserve volunteer service and a trustworthy process. Safety concerns and orders existed before the closure; this view does not depend on claiming every criticism was manufactured afterward.

QUESTIONS THE RECORD STILL NEEDS TO ANSWER

Connect each claim to a decision.

Which records support each stated systemwide deficiency? Which written assessment or dataset was relied on for each restriction or structural change? What contrary evidence was considered? Which authority permits the action, and what would it cost?

The chronology supports scrutiny of continuity in policy goals. It does not establish that every later concern was manufactured. The test is the documented connection between the problem, the evidence and the chosen response.

CHOOSE THE NEXT QUESTION

Keep the source within reach.

Who has authority to change the system?What do the volunteer companies provide?What could this mean for my tax bill?Read the corrections and right-of-reply standards