Town of Amherst — Traffic Safety Board
Amherst's Traffic Safety Board found that a site plan condition from seven years ago — a pedestrian crossing at an apartment complex on North Forest Road — had simply never been carried out. Residents walk across regardless, at a spot one member called “not a safe place to have a crossing.”
The most consequential thing the board discussed on Wednesday was not a request from a resident or a complaint about speeding. It was a discovery about the town's own paperwork.
A site plan approved in 2019 for the Odin apartment development[*] on North Forest Road required a pedestrian crossing. Seven years later, the board established on the record, it does not exist.[1]
What exists instead is a desire path. Residents of the complex cross North Forest Road to reach the other side — without a marked crossing, without a signal, and at a location the board itself regards as poorly chosen. One member put the problem in plain terms: “it's inviting a hazard and it's not a safe place to have a crossing.”[1]
That sentence contains the board's whole dilemma. If the crossing is built where the 2019 plan put it, the town installs a crosswalk at a spot its own traffic people consider unsafe — and a marked crosswalk is an invitation, which is precisely why marking a bad location can be worse than marking nothing. If it is not built, the condition of approval stays unmet and people keep crossing in the same place with no markings at all.
The structural question the discussion raises goes well beyond one apartment complex. A site plan condition is one of the main instruments a town has for extracting public infrastructure from private development: the board approves the project, the developer builds the sidewalk or the crossing or the turn lane. The instrument only works if somebody checks. Here, nobody did — for seven years, until a traffic safety board stumbled onto it while looking at something else.
How many other conditions from how many other site plans are in the same state is not a question this board asked, and not one this record answers. It is the obvious question.
The meeting was chaired by Chairman Eric Fraas[*], with eight members taking part in votes — the board's full seated complement. Staff support came from Christopher P. Schregel[*], the town's Traffic Safety Coordinator, who runs the agenda and supplied the engineering context on most items. He is a non-voting resource person, not a member.
The eight seated members are Chairman Eric Fraas, Vice Chairman Cara Biddlecom, and Nicholas Alterio, Kevin Cantwell, Patricia Dunne, Maxwell Kahn, Joseph Lojacono and Daniel J. Rider, P.E.
Every intelligible vote in the meeting was 8–0. The board did not divide on anything it voted on.
It recommends. In the Town of Amherst the Traffic Safety Board is an advisory body: it reviews requests for stop signs, crosswalks, speed studies and parking restrictions, and forwards recommendations to the Town Board, which decides.
So an 8–0 vote here is not an installation. It is a recommendation that a crossing or a sign should be installed, which then needs the Town Board to act and the highway department to carry out. Nothing in this brief describes anything that has been built.
The second substantial item was a crosswalk request near Casey Middle School[*]. The board recommended it 8–0.[1]
What makes it worth reporting is how the board got there. It recommended the crossing without a warrant analysis — and said so openly. Asked about the threshold, the answer was: “there's just not like a magic pedestrian number.”[1]
In traffic engineering, a warrant is a numerical threshold that justifies installing a control device — so many vehicles per hour, so many pedestrians crossing in a peak period, so many crashes in a given span. Warrants exist to stop devices being installed on the strength of whoever complained loudest, and they are set out in the Manual on Uniform Traffic Control Devices.
Signals and stop signs have well-defined warrants. Marked crosswalks largely do not, and that is deliberate: the engineering literature has found for decades that marking a crosswalk on a multi-lane road without other treatment can make things worse, by giving pedestrians a false sense of protection. So the decision is a judgment about sight lines, speeds, lane count and who is actually walking there — not an arithmetic test.
There is also a circularity problem that the quoted answer is reaching for. Counting pedestrians at a place with no safe crossing measures how many people are willing to risk it, not how many would cross if they could. At a school, where the pedestrians are children, waiting for the count to justify the crossing is a poor bargain. The board's reasoning is sound; the point is simply that the basis was judgment, and readers should know that.
In the course of discussing requests for new stop signs, the board put a number on the record that undercuts a great deal of what residents ask it for. Town-wide stop-sign compliance, a member said, is “less than 20%”.[1]
Taken at face value, that means more than four in five drivers do not come to a full stop at existing signs. It is the single most useful thing in the meeting for a resident to know, because it reframes the most common request a traffic safety board receives. A stop sign is the thing people ask for when they want cars to slow down. If compliance is that low, a new sign largely does not do the job it is being requested to do — and installing one in response to a speeding complaint substitutes a visible gesture for an effective measure.
The figure's provenance was not stated. No study was named, no date given, no methodology described, and whether it reflects a town observation programme, a regional figure or a professional rule of thumb is not in the record. It is reported here as what a board member said, because it plainly informed how the board treated the requests in front of it, and it is flagged as unsourced for the same reason.
The related gap: Amherst has no speed hump policy. The board confirmed there is no adopted framework governing when a speed hump may be requested, where one may be installed, or what criteria apply — so requests for them have no process to run through.[1] For a town whose residents' chief traffic complaint is speed on residential streets, and whose stop signs are obeyed less than a fifth of the time, the absence of a policy on the one device that physically enforces speed is a notable hole.
It also explains something this publication has watched the board do for months. At its October 7 meeting the same board effectively went looking for a volunteer, telling a Lafayette Boulevard neighbourhood it would be “the type of neighbourhood where I think would be a good” candidate for speed humps — a pitch it has made to street after street for years.[6] With no policy, there is no threshold a neighbourhood can meet and no petition it can file. The board can only ask, and a neighbourhood can only say yes or no. That is a canvass, not a process, and it is the predictable consequence of the gap confirmed on Wednesday.
The board established that a pedestrian crossing required by the development's 2019 site plan approval does not exist, and that residents cross North Forest Road there regardless. A member described the specified location as “inviting a hazard” and “not a safe place to have a crossing.”
No recommendation on this item is recorded in this brief. The discussion identified the problem; what the board resolved to do about it, if anything, is not something this record supports stating.
Recommended unanimously with no warrant analysis, on the board's judgment rather than a pedestrian count. See the explainer above on why crosswalks generally have no numerical warrant and why counting pedestrians at an unsafe location measures the wrong thing.
A recommendation goes to the Town Board; it is not an installation.
The board took up item 6 and disposed of it. This brief does not report how the board voted, and gives no tally.
Two things in the recording make a tally unreportable. The vote itself is unintelligible on the audio. And seconds after it, a board member voices opposition to stop signs — which is inconsistent with a clean unanimous result and leaves genuine doubt about what was agreed. Printing “8–0” here, as every other vote in the meeting ran, would be a guess dressed as a fact.
The official minutes are the authority for this item. A reader who needs to know what happened to 4300 Millersport Highway should consult them and should not rely on this brief.
A site plan review for 330 Maple Road was taken off the agenda at the request of the petitioner. No discussion on the merits took place and no vote was held.
No reason for the withdrawal is in the record, and whether the item returns is not stated. 330 Maple Road is a commercial address on Maple Road and is unrelated to Maple Drive in Lancaster; see the Editor's Note.
Running through the board's treatment of resident requests: town-wide stop-sign compliance stated as “less than 20%” (unsourced), and confirmation that the town has no speed hump policy — no criteria, no process, no framework for when one may be installed.
Together these bear on nearly every speeding complaint a resident might bring: the device most often requested is widely ignored, and the device that would physically work has no policy to request it under.
Names, and why no quotation is attributed to one. The board's roster is human-verified in this pipeline against the Traffic-Safety Board's own agenda mastheads of September 2 and June 10, 2026 — the board's publication about itself, which this pipeline treats as governing over the Town website roster after the website's was found to be stale. The transcriber mangles two names that matter here: the chair is rendered “Fras” and “Frahs” and is Eric Fraas; the coordinator is rendered “Chris Regal” and is Christopher P. Schregel. Both are corrected and marked [*].
The member count of eight is what the recording supports and matches the full seated board, but attendance by name was not independently confirmed and no individual member is quoted by name. Quotations are attributed to “a board member” because the recording does not reliably identify which of eight voices is speaking. A verified roster tells us who sits on the board; it does not tell us who said what.
Item 6 is reported without a tally, deliberately. Seven of the meeting's votes were audibly 8–0, which makes it tempting to assume the eighth was too. The audio for item 6 is unintelligible at the vote, and a member objects to stop signs seconds later. This publication does not print a vote it cannot hear, and does not fill a gap with the pattern around it.
Two subjects a reader may be looking for are not here. Coronation Drive and e-bikes were both checked against the transcript and neither appears in it. If either was expected on this agenda, this record does not contain it — which is a statement about the recording, not a statement that the board did not discuss them outside it.
An impossible date appears in the recording. A speaker refers to “comparing the 2027 volumes to the 2026 volumes” — a comparison with a year that has not happened. Most likely a misspeak for 2025, or a transcription error. It is noted rather than silently corrected, because the direction of the comparison matters to whatever it was describing, and we do not know which year was meant.
Street-name validation. “330 Maple Road” was validated against this pipeline's street checks for Amherst. Maple Road is an Amherst thoroughfare and is distinct from Maple Drive in Lancaster; the two are routinely conflated and the pipeline's Amherst corrections file carries a standing note about it. The address here is Maple Road.
No dollar figures were stated for any item in this meeting, and none is reported.
Capture. 76.4 minutes of audio, first speech at 0.1 minutes, 642 segments all distinct with no repeated-segment degeneracy, language confidence p=0.999, effective coverage 93.8% with no single segment spanning dead air. A clean capture; the 6% shortfall is ordinary pauses between speakers, not missing content.
What official minutes would add: attendance by name, the tally on item 6, the disposition of the Odin crossing item, and the provenance of the stop-sign compliance figure.