A complex, high-stakes 41-lot subdivision with unresolved stormwater, road safety, aquifer protection, and rural character conflicts produced direct board-applicant friction, strong public opposition that went entirely unaddressed, off-agenda legal and traffic issues of significant magnitude, and frank board admissions about the limits of local authority to protect community interests.
Date Wednesday, August 20, 2025Duration 2.2hSpeakers 11Public comments 3Decisions 4Heated
Why this is flagged: A complex, high-stakes 41-lot subdivision with unresolved stormwater, road safety, aquifer protection, and rural character conflicts produced direct board-applicant friction, strong public opposition that went entirely unaddressed, off-agenda legal and traffic issues of significant magnitude, and frank board admissions about the limits of local authority to protect community interests.
Public impact
Issues from this meeting with documented community impact.
01
41-Lot Residential Subdivision on County Road
41-lot subdivision (characterized by board as effectively 55 units) generating an estimated 619 additional vehicle trips per day, impacting the town's last remaining aquifer, altering rural road infrastructure, and permanently transforming a large undeveloped tract Affected: Residents of County Road, Thornton Ferry Road, and the surrounding rural area of Amherst; the broader town given aquifer and rural character implications
zoning change
02
County Road Infrastructure Improvements Required for Development
Nine culvert installations/replacements, drainage improvements, fire cistern, and 50-foot right-of-way dedication required; road deemed currently inadequate for development, with risk of years of unpaved widened road if phasing is not properly conditioned Affected: Current County Road residents and future subdivision residents who will depend on road safety and adequacy during a potentially multi-year phased construction period
other high impact
Decisions logged
Every recorded vote, with timestamps and dissents.
Motion to continue application until September 17th at 7:00 PM
Continuance granted to allow applicant to address board concerns including road phasing, technical requirements, and rural character preservation measures
Continuation of public hearing for proposed 41-lot subdivision on County Road. Applicant presented revised proposal dropping some previous requests while maintaining key asks regarding stormwater plan timing and bonding alternatives.
Debate over timing of stormwater plan submissions, with applicant requesting deferral until building permit stage. Board members expressed concerns about missing stormwater details including erosion controls, detention facilities, and outfall locations. Later discussion questioned how detention basins and water management systems can be properly sized without knowing details about individual lot development plans.
Discussion of proposed County Road improvements including 9 cross culverts (4 replacements, 5 new), drainage improvements, fire cistern installation, and dedication of 50-foot right of way. Road currently deemed inadequate for development without improvements.
Applicant proposed 50-foot woodland buffer along County Road frontage to preserve rural character, with restrictions on tree removal except for driveways and diseased trees. Board raised concerns about clearing limits on remainder of lots and later discussed revised buffer language and concerns about property owners' rights within the buffer area.
Discussion of 35.5 acres proposed for conservation (14.5 acres buildable upland) and 10-foot pedestrian trail easement. Board member suggested increasing trail easement to 20-25 feet for construction purposes.
Speakers: Unidentified speaker
▶ 1:03:48
Road Construction Phasing and Paving Requirements
Extended debate about whether houses can be occupied before road is fully paved, with concerns about maintaining a widened dirt road for years versus requiring base pavement before occupancy.
Debate over whether individual lot stormwater plans should be reviewed by the Planning Board or delegated to staff and third-party engineers as conditions precedent.
Speakers: Unidentified speaker
▶ 1:16:05
Bonding Requirements for Individual Lots
Discussion of bonding requirements for individual lot stormwater management, with applicant preferring to use certificate of occupancy withholding instead of surety bonds.
Public comment highlighting that 619 additional cars per day from the development would severely impact Thornton Ferry Road, which currently handles 570 cars per week.
Speakers: Unidentified speaker
▶ 1:23:43
Rural Character Preservation and Development Scale
Public comments criticizing the project's impact on rural character, noting the developer has built a 6-bedroom house despite promises of 3-4 bedroom homes.
Speakers: Unidentified speaker
▶ 1:32:54
Technical Requirements and Information Gaps
Board discussion of numerous technical items still needed before approval, including stormwater calculations, septic plans, and stone wall preservation details. Later discussion covered various missing details including stump disposal methods and debate over whether extensive upfront information should be required for this large project.
Board member requested more detailed information about how stone walls on the development site will be addressed, expressing dissatisfaction with vague commitments to 'do our best.'
Correction made to minutes regarding Supreme Court remand language, clarifying that the court required reconsideration under certain guidelines, not approval of 39 units.
Speakers: Unidentified speaker
Controversy & dissent
Where the board, the community, or the agenda diverged.
•
Board unity: Board members were broadly aligned in skepticism of the applicant's requests for deference on stormwater and road paving, but differences in emphasis — particularly a speaker's harder line on road capacity and a speaker's stronger environmental stance — revealed gradations of concern rather than sharp internal division.
Potentially controversial issues
01
Stormwater Management Timing and Environmental Review
The applicant wants to defer stormwater plan submissions until the building permit stage, but board members — particularly a speaker — argue this is irresponsible given the site sits on the town's last remaining aquifer. The technical feasibility of sizing detention basins without lot-level data is also disputed, creating a fundamental standoff between developer convenience and environmental protection.
Board position: Board signaled strong reluctance to defer stormwater review, with a speaker and a speaker pushing for comprehensive upfront information; no final resolution reached, continued to September 17th.
Internal dissent
a speaker was the most vocal opponent of deferral, calling it 'irresponsible' given aquifer sensitivity. a speaker and a speaker aligned with requiring more upfront detail. The applicant's preferred approach of delegating review to staff/third-party engineers was resisted by multiple board members.
high concern
02
Road Construction Phasing and Occupancy Before Paving
The question of whether houses can be occupied before County Road is fully paved could leave residents on a widened dirt road for potentially eight years during phased development. a speaker called this 'stupid,' a speaker consistently argued the road cannot sustain the development at all, and the board has not resolved the phasing requirements.
Board position: Board directed applicant to meet with DPW Director to develop a road construction schedule requiring paved access before occupancy, but no binding decision was made.
Internal dissent
a speaker maintained consistent opposition, stating the road 'will not sustain this development.' a speaker strongly opposed leaving the road unpaved during construction. The board was unified in concern but divided on exactly what standard to impose, with resolution deferred.
high concern
03
Scale and Rural Character Impact of 41-Lot (Effectively 55-Unit) Subdivision
a speaker characterized this as 'essentially a 55-unit subdivision' representing a 'very significant change to a large tract of land.' Public commenters criticized the developer's track record and broken promises about home sizes. The board acknowledged limited legal authority to reject development outright due to state-level override of local control.
Board position: Board expressed deep concern about rural character but acknowledged via a speaker that state law constrains their ability to block development; the only alternative is municipal land purchase.
high concern
04
Traffic Impact on Thornton Ferry Road — Off-Agenda, Unaddressed
A resident presented data showing 619 additional cars per day from the development would impact a road that currently handles only 570 cars per week — an approximately 6x traffic increase with obvious pedestrian and cyclist safety implications. This was not on the agenda and the board offered no response, denying residents an opportunity to prepare or engage meaningfully.
Board position: The board did not respond to or address this concern during the meeting.
high concern
05
Developer Credibility and Past Compliance
Public commenter Sullivan alleged the developer built a 6-bedroom house despite promises of 3-4 bedroom homes, raised concerns about unpermitted tree removal, construction in wetland areas, and absence of septic plans. These credibility concerns are directly relevant to whether the board can trust the developer's current commitments on rural character, clearing limits, and stone wall preservation.
Board position: The board did not directly respond to these allegations during the meeting.
Nancy Williams raised a specific legal question about whether RSA 231:157-158 scenic road regulations apply to the developer's planned road improvements, which would trigger public hearings and planning board consent requirements for tree removal and stone wall destruction. The board did not respond, leaving a potentially significant legal protection unexamined.
Board position: The board did not address this legal question.
medium concern
07
Board vs. Staff Authority in Decision-Making
a speaker twice explicitly corrected the record to clarify that staff opinions are not binding on the board, suggesting the applicant had been leveraging staff views to soften board requirements. This raises a transparency concern about whether staff recommendations have been improperly substituting for board decisions in prior interactions.
Board position: a speaker firmly asserted board primacy over staff, stating staff opinions are 'not going to be dispositive.'
medium concern
08
Supreme Court Remand Language in Minutes
The August 6th minutes incorrectly implied the Supreme Court required approval of 39 units, when in fact it required reconsideration under specific guidelines. This distinction matters enormously — a correction was required to prevent the mischaracterization from becoming part of the official record and potentially being cited to limit the board's discretion.
Board position: Board corrected the minutes to accurately reflect the court's directive as reconsideration, not mandated approval.
medium concern
Community vs. board tension
⚖
Traffic Safety on Thornton Ferry Road Community wants: A resident presented alarming traffic data showing a potential 6x increase in daily traffic on a road currently handling 570 cars per week, raising safety concerns for pedestrians, children, and cyclists. Board response: The board offered no response whatsoever to this concern, neither acknowledging the data nor explaining how or whether traffic impacts would be evaluated before approval.
⚖
Developer's Track Record and Environmental Compliance Community wants: Resident Sullivan raised specific allegations of broken promises on home size, unpermitted tree removal, construction in wetlands, and missing septic plans — directly undermining trust in the developer's current commitments. Board response: The board did not respond to or engage with these allegations, leaving community members without any assurance that past non-compliance would be factored into the approval process.
⚖
Scenic Road Legal Protections Community wants: Nancy Williams asked whether RSA 231:157-158 scenic road regulations would require a public hearing before trees and stone walls are removed during road improvements, suggesting residents may have statutory rights to participate that have not been acknowledged. Board response: The board did not address this question at all, leaving a potential legal protection unexplored.
⚖
Rural Character and Development Scale Community wants: Residents want preservation of rural character and are skeptical of the developer's commitments given past behavior. Board response: The board shares these concerns but a speaker candidly acknowledged that state law limits local ability to block development, and the only real alternative is municipal land purchase — a frank admission that may frustrate community members expecting stronger protection.
Ready to share? AI-written accountability posts about this meeting's controversies.
Discuss road construction phasing and timing with Department of Public Works Director
Assigned: Applicant · Due: Before next meeting
Consider increasing trail easement width to 20-25 feet with construction easement
Assigned: Applicant · Due: For board consideration
Address outstanding technical items in Steve Keech's review letter
Assigned: Applicant · Due: Before approval
Meet with DPW to develop road construction schedule ensuring paved access before house occupancy
Assigned: Applicant · Due: September 17th meeting
Consult with Steve Keech on outstanding technical requirements and provide his recommendations to the board
Assigned: Applicant · Due: September 17th meeting
Develop enhanced rural character preservation plan addressing clearing limits and expanded buffer zones
Assigned: Applicant · Due: September 17th meeting
Provide detailed stone wall preservation plan beyond 'we'll do our best' commitment
Assigned: Applicant · Due: September 17th meeting
Review missing application items and determine what additional information can be provided, consulting with staff member Steve
Assigned: Applicant · Due: September 17th meeting
Have Steve attend next meeting to provide direct technical input on application questions
Assigned: Board/Staff · Due: September 17th meeting
Notable statements
This development cannot go forward by everybody's admission, including the applicants, unless the road gets changed
— Unidentified speaker · Challenging applicant's claim that development could proceed on existing road ▶ 34:37
This is the lone remaining aquifer in town, and to glance over it and just hand it off to office staff, to me, is just irresponsible
— Unidentified speaker · Expressing concerns about deferring stormwater plan review given environmental sensitivity ▶ 32:38
I continue to say that I would like to see at least some indication of the limits of clearing to ensure that... the 25 foot undisturbed wetland buffer is observed by everyone
— Unidentified speaker · Advocating for clearing restrictions beyond the proposed 50-foot road buffer ▶ 49:43
There are a number of comments from the staff that do not represent the views of this board. The staff are employees of the town. It's the board that's making decisions, not the staff
— Unidentified speaker · Clarifying decision-making authority when applicant referenced staff opinions on tree clearing ▶ 53:53
This is essentially a 55 unit subdivision...it's obviously a very significant change to a large tract of land to an area of town
— Unidentified speaker · Emphasizing the scale and impact of the development when discussing flexibility on preservation measures ▶ 1:11:14
You can't just leave it widened in dirt and expect Mr. Slosik to maintain it for a period of eight years potentially...It's just stupid and it's not the way it's done
— Unidentified speaker · Strong opposition to leaving County Road partially constructed during phased development ▶ 1:37:14
This development will not be sustained by this road or this road won't sustain this development
— Unidentified speaker · Maintaining consistent opposition to the project based on road capacity concerns ▶ 1:33:01
There is not local control over development. There is statewide imposition insisting on more development...the only way to stop this kind of more intense development is for the town to buy land
— Unidentified speaker · Explaining legal and political constraints on the board's ability to reject development ▶ 1:46:57
I think a pretty good argument to be made that if it's a really large project that actually militates in favor of getting the information because the potential impact is so great.
— Unidentified speaker · Justifying need for comprehensive upfront information on large development projects ▶ 2:06:06
It's ultimately our decision to make policy decisions... Steve's word is not going to be dispositive. It's the board that's going to make decisions.
— Unidentified speaker · Clarifying board authority vs. staff recommendations in decision-making process ▶ 2:05:25
I do not understand how you can size detention basins, level spreaders and everything else where all of these lot flows are going to go to without knowing anything about the lots.
— Unidentified speaker · Questioning technical feasibility of stormwater planning without individual lot details ▶ 2:07:37
A resident from Thornton Ferry Road 1 raised concerns about traffic impacts from the proposed 41-lot development. They cited a traffic study showing potential for 619 cars per day, while a recent town study showed 570 cars per week on their road, expressing safety concerns for pedestrians, children, and cyclists.
Key concern
Traffic safety and increased vehicle volume on Thornton Ferry Road 1 from the development
The board did not respond to or address the traffic concerns raised by this speaker
Sullivan from Thornton Ferry criticized the developer's track record, citing examples of houses not fitting rural character and questioning permits for tree removal. They expressed concerns about building in wetland areas, potential mosquito spraying affecting bees, and lack of septic plans for a six-bedroom house already under construction.
Key concern
Developer's poor track record, environmental impacts, and lack of proper permitting compliance
The board did not respond to these specific concerns about the developer's past actions or environmental impacts
Nancy Williams from County Road questioned whether scenic road regulations (RSA 231:157-158) would apply to the developer's road work, which requires public hearings and planning board consent for tree removal over 15 inches in circumference or stone wall destruction.
Key concern
Whether scenic road regulations apply to developer-funded road improvements
The board did not address this specific legal question about scenic road regulations
Accountability flags
Documented procedural gaps. Each item links to its source.
Topics discussed — not on agenda
⚠
Traffic Impact Analysis on Thornton Ferry Roadhigh — Public comment highlighted that 619 additional cars per day from the development would severely impact Thornton Ferry Road, which currently handles only 570 cars per week - a significant traffic concern not mentioned in the agenda
⚠
Developer's Previous Construction Practicesmedium — Public comments criticized the project noting the developer has built a 6-bedroom house despite promises of 3-4 bedroom homes, raising credibility concerns about project commitments
⚠
August 6th Meeting Minutes Correctionmedium — Correction made to minutes regarding Supreme Court remand language, clarifying that the court required reconsideration under certain guidelines, not approval of 39 units
●
Minutes comparison will appear here once the official minutes are published.
Support coverage
Creating this report cost real money.
MeetingWatch attended, transcribed, and analyzed this meeting on its own dime. If this work is valuable to you, chip in to keep covering Amherst.
Follow Amherst
One email when a new report is published from the Planning Board — or one weekly digest.
Report composed by claude-sonnet-4-20250514, claude-opus-4-6 · analyzed 2026-06-01.
Show me what's happening near me.
MeetingWatch covers communities across the country. Tell us where you are and we'll surface the meetings, votes, and decisions in your town.
Request coverage
We'll let you know when MeetingWatch starts covering your area.
Please add your name and a valid email.
Check your inbox — click the link in our email to finish your request.
Or browse covered communities:
Send feedback
Spotted an error, or have a tip? Let us know — we read every note.
Know where the video for this meeting lives? Paste the link below and we'll add it.
We'll email you a link to confirm — this keeps out spam. We won't share your address.
Please add a valid email and a message.
Check your inbox — click the link in our email to confirm your feedback.
Search MeetingWatch
MeetingWatchStay informed — without the slant.
Hours of public meetings. Zero time to watch them.
MeetingWatch uses AI to attend every public meeting in covered communities —
transcribing debates, logging votes, and surfacing what actually mattered.
No slant. No bias. Just what was said on the record, so you can stay
informed about your town without burning your evenings.
46
Communities covered
1252
Meetings analyzed
3903
Voices logged
Get started in three steps
1
Tell us where you live.
We'll surface the meetings, votes, and decisions in your town first.
One weekly email. Decisions, dissents, and the off-agenda items from every covered community. Unsubscribe in one click.
✓ Subscribed — check your inbox to confirm
3
Support the work.
MeetingWatch is a civic accountability project. Reader contributions cover transcription, hosting, and the cost of attending every meeting — and help grow coverage to more towns.