Norwich CT Fire.com — helmet and flames
Menu

MY PERSPECTIVE / FOLLOWING THE RECORD

I started with a question: why?

Volunteer service matters to this city. A decision that changes its future should come with an explanation people can follow.

Back to the homepage

How I got involved

I’ve lived in Norwich for 20 years. When I heard in February 2026 that Yantic had been closed, I knew very little about how our fire service worked. I wanted to understand what had happened.

That Saturday, I went to Yantic and spent about two hours with the chief and deputy chief. They described the Town Street incident, the discipline dispute that followed, and their concerns about the City’s demands. That was their account. I wanted to see the records behind it. I requested the video and related documents.

I also heard the City’s explanation that the Chief had spent six months attending roughly 100 incidents to understand the system. What had he observed? What problems had he identified? How did those findings lead to removing a volunteer company from service?

Personal recollection and the public account

The visit, conversations and length of residency are my account, not independently verified findings. The public six-month / more-than-100 account is a caption-derived paraphrase, not an audio-verified quotation.

Read the review question and source limits

Listening, reading and checking

I visited all the stations and met members. I attended City Council and Public Safety meetings. I spent several hours with Chief Wilson listening to the City’s side. I watched video, read incident reports and correspondence, and worked through fire-service policies, the Charter, and material on EMS, NFPA and OSHA standards.

As new information came in, I followed leads and compared statements with the records. The question was straightforward: is this true, and what supports it?

I support the volunteers. I also recognize that Norwich’s fire service needs updates. Consistent command, training, reliable staffing and accountability are legitimate concerns. Hearing those concerns made it important to understand the specific deficiencies and whether the response was proportionate.

The work continues. I haven’t finished every question or reviewed every possible record. What I have examined has left me with serious concerns about the justification for the City’s actions.

What the incident review covers

The October 2 review read 18 report files representing 17 incident identities across 141 pages. It did not independently reconstruct each incident or verify every table field. Two files are versions of the same incident; repeated wording is not independent corroboration. Useful volunteer work and criticism of paid crews and city alerting belong beside criticism of volunteer operations.

Selected incident passages — individual and combined page referencesVolunteer calls, training and joint work — City minutes

I explained what would answer the questions

The requests were specific. On February 25, I asked for incident numbers, dates, locations, incident types, responding units, personnel totals and whether volunteer companies attended. I offered to clarify the relevant timeframe.

When the Chief supplied reporting-system records, he explained that they recorded incidents where he took official action and did not capture every event he attended. I took that distinction seriously.

On March 10, I asked for any list or dataset identifying the roughly 100 incidents, dispatch records or the equivalent system then in use, incident summaries, contemporaneous notes, analyses and briefing materials. If the number did not come from a documented compilation, I asked for confirmation.

After the Chief said he had provided all records kept by the Fire Department, I initially acknowledged the request as complete. Later that day, examining the reports raised a separate problem: some units appeared to have identical dispatch and arrival times even though the narratives described sequential arrivals. I asked how the timestamps were generated and requested the underlying unit-level times.

Then, at the April 7 budget hearing, the City Manager referred to receiving a report back. I renewed the request for the report, drafts and transmittal emails. I also asked him to identify a different document or record set if that was what he meant. The Chief’s April 8 answer was limited to documentation in his possession. I clarified that my request was not limited to his office.

Four written assessments were sent to the manager on February 24. They contain substantive criticism and must be considered. In later correspondence, the manager said he had verbal reports rather than written reports. The relationship between those replies, the four assessments and the specific six-month review remains unclear.

I still cannot reconstruct that complete review from the materials examined: which incidents formed the sample, what was recorded, how the conclusions were reached and how they justified company removal.

What happened to the 100-call review?

We asked for the records behind the “100 incidents” account: incident identifiers, staffing, dispatch records, contemporaneous notes, analyses and briefings. When the supplied reports raised timing questions, we requested unit-level timestamps. We later asked for report drafts and transmittal emails, or identification of another record set.

The unresolved link: Four February written assessments exist. How do those assessments, the incident records and verbal reports document the specific review and support the conclusions drawn?

Read the dated requests

What we asked for, and what came back

February 25, 2026 · Incident details

The request specified incident numbers, dates and times, locations, incident types, dispatched and on-scene units, personnel totals and volunteer participation. The requester offered to clarify the time frame. The Clerk acknowledged forwarding it that day.

The Chief supplied reporting-system records on March 10, explaining that recorded official actions do not capture every incident he attended.

Source: 16-page chain, pp. 13-16; redacted packet pp. 14-17.

Read these pages in the redacted packet
March 10–11 · The compilation behind the account

The follow-up sought a list, dataset or compilation; dispatch/CAD or the currently used equivalent; incident and command summaries; contemporaneous notes; internal analyses and briefings; and confirmation if no documented compilation existed.

On March 11 the Chief said he had supplied all records kept by the Fire Department, again distinguishing recorded actions from attendance. At 9:47 AM the requester initially acknowledged completion. Later questions followed examination of the records.

Source: 16-page chain, pp. 7-13; redacted packet pp. 8-14.

Read these pages in the redacted packet
March 11, 1:21 PM · Unit-level timestamps

After examining the reports, the requester questioned identical dispatch/arrival times despite narratives describing sequential arrivals. He asked how the timestamps were generated and sought underlying unit-level dispatch and arrival timestamps if the displayed times were summaries.

No resolving reply appears in this 16-page chain. That does not prove no reply or records exist elsewhere, or establish the actual incident durations.

Source: 16-page chain, pp. 5-8; redacted packet pp. 6-9.

Read these pages in the redacted packet
April 7–8 · Identify the report or another record set

The renewed request sought drafts, a final report, written analysis and transmittal emails. If the budget-meeting statement referred to a different document or record set, the requester asked for it to be identified specifically.

On April 8 the Chief limited his assurance to requested documents in his possession. The requester clarified that the request also included the City Manager’s records, not just the Chief’s office.

Source: 16-page chain, pp. 1-5; redacted packet pp. 2-6. The final request is dated April 13, 2026, 6:36:58 PM (chain p. 1 / packet p. 2).

Read these pages in the redacted packet

These are paraphrased selections from a 16-page correspondence chain. The screened 19-page review packet contains that chain, a reading guide and two separate February 24 context pages. Only the requester’s name and email are redacted; officials’ business details, signatures, dates and contrary context remain. The private original is not published.

The four written assessments and their February 24 transmittal were located elsewhere. The Manager’s April 14 “verbal reports” reply is in a separate verified request-and-reply exhibit. Read its request and possession context alongside those assessments; neither chain proves that no review or safety concerns existed.

February 24 attachment-title context — packet pp. 18–19Four assessments and February 24 transmittal · existing source notesSeparate April 14 replies · screened public transcription

The public six-month / more-than-100 account is a caption-derived paraphrase, not an audio-verified quotation. The remaining question is the connection between the review, the evidence, each action and the alternatives considered.

Download the redacted request trail (PDF)

Why the gaps matter

The consequences were substantial. The City’s own September court brief defends removing Yantic and Taftville from fire-service operations. Paid coverage continued, but the companies’ ability to serve changed fundamentally. Individual volunteers being offered a role does not by itself restore their companies.

I remain unconvinced that the evidence adequately explains why company removal was necessary. Residents deserve to see the connection between identified problems, the remedy chosen and the alternatives considered.

The decision and the City’s rationale

The City’s September 10, 2026 brief, page 2, defends the removal. Its rationale must be considered alongside the criticism and safety concerns in the four written assessments. This is a party’s position in litigation, rather than a court ruling on the merits of every action.

City brief — September 10, 2026 — p. 2Four February assessments — source notes

The June 3 order concerns station vacation and six apparatus, a distinct consequence.

June 3 order — pp. 1–2

What I want Norwich to do

The City’s 2021 McGrath study supported continuing career and volunteer providers while calling for substantial improvements in coordination, training and oversight. It identified genuine problems and proposed reform with volunteers still serving. That is a direction worth pursuing.

I want qualified volunteers restored under clear, lawful operating terms, with measurable standards and a workable path to meeting them. I want reliable performance information, understandable costs and specific explanations of why less disruptive alternatives would not work.

The Charter dispute remains contested. I’m not presenting a settled court ruling. I’m asking Norwich to make full use of people willing to give their time and skills to this community, and to support consequential decisions with evidence residents can examine.

Reform and the unresolved authority questionMcGrath study — February 2021 — pp. 15–17

The study is a historical recommendation, not certification of today’s readiness or proof of consensus on the present dispute.

The contested Charter authority questionCorrections and right of reply