<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/" >

<channel>
	<title>Building Department &#8211; Mount Vernon Civic Integrity Project</title>
	<atom:link href="https://mvcip.org/tag/building-department/feed/" rel="self" type="application/rss+xml" />
	<link>https://mvcip.org</link>
	<description>Welcome to the Mount Vernon Civic Integrity Project</description>
	<lastBuildDate>Sun, 15 Mar 2026 20:08:12 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>
	<item>
		<title>Had Trouble With Mount Vernon&#8217;s Building Department?</title>
		<link>https://mvcip.org/blog/had-trouble-with-mount-vernons-building-department/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 14 Mar 2026 20:51:38 +0000</pubDate>
				<category><![CDATA[Building Department]]></category>
		<guid isPermaLink="false">https://mvcip.org/?post_type=blog&#038;p=1172</guid>

					<description><![CDATA[Mount Vernon's Building Department has been plagued by permit backlogs, lost paperwork, and state warnings of a takeover. If you've dealt with it, your experience matters — take the survey.]]></description>
										<content:encoded><![CDATA[<h3>A Record of Dysfunction</h3>
<p>A <a href="https://www.osc.ny.gov/files/local-government/audits/2017-10/lgsa-audit-city-2014-mount-vernon.pdf" target="_blank" rel="noopener">2014 audit by the New York State Office of the State Comptroller</a> found significant deficiencies in how the Mount Vernon Department of Buildings managed fees and fines, including weak oversight of permit collections and a lack of internal controls. The audit found that the department processed roughly 3,150 permits and collected about $881,000 in fees during the audit period, yet lacked the systems to verify that all revenue was properly accounted for.</p>
<p>By 2018, the New York State Senate had taken notice. A <a href="https://www.nysenate.gov/newsroom/press-releases/2019/brian-kavanagh/investigative-report-code-enforcement-new-york-state" target="_blank" rel="noopener">state Senate study that year</a> listed Mount Vernon&#8217;s Building Department as one of the worst in the state, a damning designation that city officials would later have to publicly acknowledge.</p>
<p>The problems that had been quietly documented in government reports were, by the early 2020s, erupting into public view. Residents described a gauntlet of bureaucracy. Homeowners reported waiting six months to two years just to get a permit, and another year or two to close one out. Others described losing paperwork, losing checks and money orders, and being hit with violations for minor or trivial matters. One resident filed a federal complaint alleging that a building department employee asked him to pay fines in cash and that his property was subjected to harassment including up to 30 inspector visits, some on evenings and holidays.</p>
<p><em>&#8220;If you know the right people, your issues are expedited,&#8221; said Matthew Fecteau, an information operations officer in the U.S. Army Reserve, who described the experience as his &#8220;living hell.&#8221; The city has denied his allegations in court.</em></p>
<p>A <a href="https://www.change.org/p/hire-new-mount-vernon-building-department-staff-and-change-their-processes-for-the-better" target="_blank" rel="noopener">Change.org petition</a> calling for new staff captured the frustration of many: &#8220;The home owners, contractors and investors of Mount Vernon are being bullied, mislead, stagnated, losing money and time.&#8221;</p>
<hr style="border: none; border-top: 2px dotted #ccc; width: 65%; margin: 30px auto;" />
<h3>The Mayor Calls In The State</h3>
<p>In <a href="https://dailyvoice.com/new-york/mountvernon/state-to-review-mount-vernon-building-department-ive-had-concerns-mayor-says/" target="_blank" rel="noopener">August 2023, the Patterson-Howard administration formally called in</a> the New York State Department of State&#8217;s Division of Building Standards and Codes to conduct a review of the department&#8217;s internal operations. The mayor acknowledged receiving &#8220;concerns and complaints&#8221; about how the department operates and said that chronic understaffing over the previous decade, outdated codes, and antiquated procedures had produced a backlog of 800 permit applications.</p>
<p>City Communications Director Tim Allen, speaking publicly about the state&#8217;s subsequent intervention in 2024, confirmed what many already suspected: a 2018 New York State Senate study had listed Mount Vernon&#8217;s Building Department as one of the state&#8217;s worst.</p>
<hr style="border: none; border-top: 2px dotted #ccc; width: 65%; margin: 30px auto;" />
<h3>The State Steps In</h3>
<p>The April 2024 report from the state&#8217;s review was blunt. It found backlogged permits, chronic understaffing, outdated city codes, and a failure to conduct timely inspections, including a failure since 2009 to conduct required annual inspections of places of public assembly.</p>
<p>In <a href="https://www.yahoo.com/news/state-threatens-mount-vernon-takeover-070047754.html" target="_blank" rel="noopener">June 2024, the state escalated.</a> A sternly worded letter from John Addario, Director of Building Standards and Codes for the New York State Department of State, warned Mount Vernon that it &#8220;requires that the City give this letter full and immediate attention.&#8221; Failure to show measurable progress by mid-August, the letter warned, could lead the state to take over the department entirely, potentially transferring enforcement authority to Westchester County.</p>
<p>The prospect was not hypothetical. <a href="https://www.yahoo.com/news/rockland-code-enforcement-spring-valley-200024821.html" target="_blank" rel="noopener">In 2021, the state took control of building code enforcement in the village of Spring Valley</a> and handed it to Rockland County, an arrangement that, years later, still shows no end in sight.</p>
<p>Neither outcome materialized in Mount Vernon. The state did not take over, and the city did not demonstrate the kind of compliance the letter demanded. Nearly two years on, residents report that little to nothing has visibly changed. The backlog, the delays, and the dysfunction that prompted the state&#8217;s intervention remain part of daily life for homeowners, contractors, and business owners trying to navigate the department.</p>
<hr style="border: none; border-top: 2px dotted #ccc; width: 65%; margin: 30px auto;" />
<h3>Now It&#8217;s Your Turn</h3>
<p>The state came in, issued its warnings, and left without a takeover. Nearly two years later, the department looks much the same as it did before any of it happened.</p>
<p>If you have dealt with the Mount Vernon Department of Buildings, whether as a homeowner, contractor, tenant, or business owner, this survey is your chance to put it on the record. Official reports and state letters have their place, but resident feedback creates a paper trail that is harder to ignore and harder to spin.</p>
<p>The department has a long way to go. Add your voice.</p>
<p><strong><a href="https://www.recreation.cmvny.com/FormCenter/Building-12/DEPARTMENT-OF-BUILDING-Customer-Satisfac-97" target="_blank" rel="noopener"><u>Take the Department of Buildings Customer Satisfaction Survey here.</u></a></strong></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>What Does Civic Power Look Like?</title>
		<link>https://mvcip.org/blog/what-does-civic-power-look-like-public-pressure-stops-bronxville-field-club-settlement/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 07 Feb 2026 19:19:17 +0000</pubDate>
				<category><![CDATA[Governance]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Building Department]]></category>
		<guid isPermaLink="false">https://mvcip.org/?post_type=blog&#038;p=1122</guid>

					<description><![CDATA[How public pressure and community organizing stopped a backroom settlement, and what this moment reveals about civic power, transparency, and accountability in Mount Vernon.]]></description>
										<content:encoded><![CDATA[<p>For decades, the Bronxville Field Club has occupied a strange and uncomfortable place in Mount Vernon.</p>
<div style="height: 1rem;"></div>
<p>It is an exclusive “recreational and social” club whose name, branding, and mailing address suggest it belongs to toney Bronxville. <strong>For years, and continuing today, the Club has used a Bronxville post office designation, sparing its members the presumably uncomfortable reality that the Bronxville Field Club sits entirely within the City of Mount Vernon.</strong></p>
<p>&nbsp;</p>
<p><img fetchpriority="high" decoding="async" class="alignnone size-full wp-image-1123" src="https://mvcip.org/wp-content/uploads/bronxville-field-club.webp" alt="bronxville-field-club" width="800" height="450" srcset="https://mvcip.org/wp-content/uploads/bronxville-field-club.webp 800w, https://mvcip.org/wp-content/uploads/bronxville-field-club-768x432.webp 768w" sizes="(max-width: 800px) 100vw, 800px" /></p>
<div style="height: 1rem;"></div>
<p>Physically, legally, and environmentally, it is our neighbor. In practice, however, it has rarely acted like one.</p>
<div style="height: 1rem;"></div>
<p>Over the years, the Club has been at the center of repeated controversies: stormwater pushed downhill into Mount Vernon neighborhoods, unpermitted infrastructure, land-use disputes, and litigation triggered whenever regulators or residents pushed back.</p>
<div style="height: 1rem;"></div>
<p>Again and again, the pattern has been the same: expand first, deal with the consequences later.</p>
<div style="height: 1rem;"></div>
<p>So, when residents raised concerns about yet another expansion, and the Planning Board denied the application after reviewing evidence and public testimony, something unusual happened.</p>
<div style="height: 1rem;"></div>
<p>For a brief moment, accountability won.</p>
<div style="height: 1.25rem;"></div>
<div style="height: 1px; border-top: 1px dotted #666; width: 70%; margin: 1.25rem auto;"></div>
<div style="height: 1.25rem;"></div>
<h3>When Pressure Works, and Money Doesn’t</h3>
<div style="height: 1.25rem;"></div>
<p><strong>Rather than accept the decision, the Bronxville Field Club responded the way powerful institutions often do when they encounter resistance: it sued.</strong></p>
<div style="height: 1rem;"></div>
<p>What followed were months of closed-door negotiations between the City and the Club &#8211; negotiations that deliberately excluded the people most affected by the outcome: Mount Vernon residents living adjacent to the Club’s property and downstream from its impacts.</p>
<div style="height: 1rem;"></div>
<p>The proposed solution was a quiet global settlement. Multiple lawsuits would vanish. The Club would receive a fast-tracked path forward. And the City would accept a one-time payment of $450,000 in exchange for ending enforcement and abandoning its litigation posture.</p>
<div style="height: 1rem;"></div>
<p><strong>All of this happened without public notice, without public hearings, and without resident participation.</strong></p>
<div style="height: 1.25rem;"></div>
<div style="height: 1px; border-top: 1px dotted #666; width: 70%; margin: 1.25rem auto;"></div>
<div style="height: 1.25rem;"></div>
<h3>Sunlight Changes the Equation</h3>
<div style="height: 1.25rem;"></div>
<p>Once the settlement terms became public, the response was immediate.</p>
<div style="height: 1rem;"></div>
<p>MVCIP published the agreement in full. Residents mobilized. Emails flooded inboxes. Phones rang. Planning Board members heard directly from the people who live with flooding, runoff, and infrastructure failures &#8211; not from lawyers or lobbyists, but from their neighbors.</p>
<div style="height: 1rem;"></div>
<p><strong>And something rare happened in Mount Vernon government.</strong></p>
<div style="height: 1rem;"></div>
<p><strong>The Planning Board listened. They pulled the item from the agenda, marking in red that it would not be placed on a future agenda.</strong></p>
<div style="height: 1rem;"></div>
<p>This didn’t happen because officials suddenly gained new legal insight. It happened because public pressure made it impossible to pretend this was business as usual.</p>
<div style="height: 1rem;"></div>
<p>Transparency changed the outcome.</p>
<div style="height: 1.25rem;"></div>
<div style="height: 1px; border-top: 1px dotted #666; width: 70%; margin: 1.25rem auto;"></div>
<div style="height: 1.25rem;"></div>
<h3>What This Episode Reveals</h3>
<div style="height: 1.25rem;"></div>
<p>After the Planning Board removed discussion of the settlement from its agenda, the Club sent the following message to its membership.</p>
<p>&nbsp;</p>
<p><img decoding="async" class="alignnone size-full wp-image-1124" src="https://mvcip.org/wp-content/uploads/bronxville-fieldclub-letter.webp" alt="bronxville-fieldclub-letter" width="913" height="752" srcset="https://mvcip.org/wp-content/uploads/bronxville-fieldclub-letter.webp 913w, https://mvcip.org/wp-content/uploads/bronxville-fieldclub-letter-768x633.webp 768w" sizes="(max-width: 913px) 100vw, 913px" /></p>
<div style="height: 1rem;"></div>
<p><strong>It is telling that, while the Bronxville Field Club was reportedly informing its own stakeholders about the settlement, City Hall was working overtime to keep residents in the dark.</strong></p>
<div style="height: 1rem;"></div>
<p>It is also telling that once the deal was exposed to public scrutiny, it could not survive even basic questioning.</p>
<div style="height: 1rem;"></div>
<p>Open Meetings Law exists for a reason. Planning Board statutes exist for a reason. They are meant to ensure that decisions affecting neighborhoods, infrastructure, and public trust are made openly, with public participation, not stitched together privately and presented as a fait accompli.</p>
<div style="height: 1rem;"></div>
<p><strong>This was not a near miss. It was a case study in how governance fails when officials assume no one is watching.</strong></p>
<div style="height: 1.25rem;"></div>
<div style="height: 1px; border-top: 1px dotted #666; width: 70%; margin: 1.25rem auto;"></div>
<div style="height: 1.25rem;"></div>
<h3>What MVCIP Sought to Prevent</h3>
<div style="height: 1.25rem;"></div>
<p><strong>MVCIP agreed to intervene because this settlement was never about protecting Hunt’s Woods.</strong></p>
<div style="height: 1rem;"></div>
<p><strong>It was about shielding City Hall from conflict and shielding the Bronxville Field Club from accountability.</strong></p>
<div style="height: 1rem;"></div>
<p>By insisting on transparency, publishing the agreement in full, and centering the voices of downstream neighbors who were deliberately excluded, MVCIP sought to disrupt a backroom deal that traded away public power, narrowed environmental review, and normalized recurring flooding in exchange for a token payment.</p>
<div style="height: 1rem;"></div>
<p>The goal was not simply to expose what was being negotiated. It was to reclaim a basic principle: land-use decisions must be driven by evidence, equity, and the lived reality of affected residents, not convenience for officials or certainty for a private club.</p>
<div style="height: 1rem;"></div>
<p>Once residents were informed, the response was unified. The deal collapsed under the weight of public scrutiny.</p>
<div style="height: 1.25rem;"></div>
<div style="height: 1px; border-top: 1px dotted #666; width: 70%; margin: 1.25rem auto;"></div>
<div style="height: 1.25rem;"></div>
<h3>The Real Cost of the Deal Wasn’t $450,000</h3>
<div style="height: 1.25rem;"></div>
<p><strong>The true cost of this episode was not the $450,000 payoff. It was the price Mount Vernon paid in squandered resources, lost time, and damaged public trust.</strong> The unanswered questions remain.</p>
<div style="height: 1rem;"></div>
<p>Public money was spent not to fix flooding or protect neighborhoods, but to negotiate a private retreat &#8211; lawyers billing to craft a deal that weakened the City’s own authority. Staff time was diverted from solving real infrastructure problems to managing secrecy, coordinating talking points, and preparing an “executive summary” meant to obscure more than it revealed.</p>
<div style="height: 1rem;"></div>
<p>Most damaging of all was the cost to democratic governance. Residents were excluded from decisions that directly affect their homes, safety, and property values, and only learned what was happening because someone inside the process leaked the agreement. That is not how accountable government is supposed to work.</p>
<div style="height: 1rem;"></div>
<p><strong>When neighbors have to act as watchdogs, whistleblowers, and de facto investigators just to prevent a backroom surrender of public power, something is fundamentally broken. That reality says far more about Mount Vernon’s governance than any dollar figure ever could.</strong></p>
<div style="height: 1.25rem;"></div>
<div style="height: 1px; border-top: 1px dotted #666; width: 70%; margin: 1.25rem auto;"></div>
<div style="height: 1.25rem;"></div>
<h3>This Is What Civic Power Looks Like</h3>
<div style="height: 1.25rem;"></div>
<p>We often end our communications with the phrase: <strong>Power to the People.</strong> This out outcome is what we mean by that, and it deserves to be named plainly.</p>
<div style="height: 1rem;"></div>
<p>A proposed settlement backed by money, lawyers, and institutional inertia did not collapse on its own. You stopped it.</p>
<div style="height: 1rem;"></div>
<p>Residents who paid attention, shared information, asked hard questions, and refused to accept a deal negotiated without them and against their interests. That is what civic power looks like &#8211; practiced in real life, in real time, forcing decisions that affect the public to be justified in public.</p>
<div style="height: 1rem;"></div>
<p><strong>The settlement was pulled because people showed up. That’s worth remembering the next time someone says residents don’t have a voice in Mount Vernon.</strong></p>
<div style="height: 1rem;"></div>
<p><strong>We do, when we use it.</strong></p>
<p>&nbsp;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Planning Didn’t Prevent the 214 Gramatan Project — It Enabled It</title>
		<link>https://mvcip.org/blog/planning-didnt-prevent-the-214-gramatan-project-it-enabled-it/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 11 Jan 2026 20:25:43 +0000</pubDate>
				<category><![CDATA[Planning]]></category>
		<category><![CDATA[Building Department]]></category>
		<category><![CDATA[Comprehensive Plan]]></category>
		<guid isPermaLink="false">https://mvcip.org/?post_type=blog&#038;p=1070</guid>

					<description><![CDATA[The 214 Gramatan project shows how planning failed to stop harm and instead enabled it. A Comprehensive Plan that relies on broken review and record keeping cannot deliver meaningful protection to residents.]]></description>
										<content:encoded><![CDATA[<p>Mount Vernon recently adopted a <a href="https://www.mountvernonny.gov/605/Comprehensive-Plan" target="_blank" rel="noopener">Comprehensive Plan</a> intended to guide growth, density, infrastructure, and neighborhood impacts across the City. That plan necessarily presumes two things: basic competence by the City departments and boards charged with administering land-use laws, and the integrity of the zoning and planning records on which future decisions are supposed to rely.</p>
<p>But what happens when those assumptions fail—when the officials responsible for zoning and planning do not do their jobs, and the “official” records instead appear sloppy, incomplete, or altered after the fact?</p>
<p>214 Gramatan happens.</p>
<p><a href="https://mvcip.org/blog/the-house-next-door" target="_blank" rel="noopener">The 214 Gramatan project is a large apartment building constructed practically on top of the private residence owned by Dina Periello</a>. What was reviewed and approved on paper bears little resemblance to what was ultimately built. And when the project was later scrutinized through FOIL requests, the City’s zoning file revealed discrepancies that raise serious questions about whether the record was retrofitted to justify an unlawful structure rather than to reflect what was actually approved.</p>
<p>When 214 Gramatan happens, the problem is no longer confined to one property or one neighbor. The integrity of not just a single project, but the planning framework the City now claims to follow, is called into question.</p>
<h4>The Records Appear Altered</h4>
<p>Please review the attached documents, particularly the “<a href="http://mvcip.org/downloads/214%20Gramatan%20ZBA%20Application.pdf" target="_blank" rel="noopener">214 Gramatan ZBA Application</a>,” signed by Sal Saleh as owner and Tom Abillama as architect. This document was produced in response to FOIL requests and appears to be the only zoning application on file for this project.</p>
<p>Several key fields in this application show clear signs of alteration. On page 1, the entry for “Existing Site Area,” and on page 4, the entries for “Size of principal building,” “Number of dwelling units on site,” and the number of parking spaces before and after approval are all missing the standard printed line beneath the entry. In each instance, the figures are handwritten in a style that is arguably different from surrounding entries. One parking entry also appears to show that a prior figure was removed and replaced, with remnants of the original number still visible beneath the handwritten “26” and above the printed line. These anomalies do not appear elsewhere in the application.</p>
<p>These are not minor details. Site area, building size, and number of dwelling units are core facts the Zoning Board relies on to evaluate density, scale, and the extent of zoning relief being requested. They are foundational to the Board’s authority and decision-making.</p>
<p>The importance of these altered figures is underscored by the Zoning Board’s September 19, 2017, Findings of Fact. Those Findings repeatedly describe and analyze a project consisting of 36 dwelling units. They do not mention a 53-unit building, nor do they discuss the site-area figures that now appear on the application.</p>
<p>The first time the record reflects consideration of a substantially larger project is in the March 2019 Amended Findings of Fact. Yet the City’s files contain no amended zoning application, no dated revision, and no explanation of when the application data was changed or how those changes were presented to the Board. The file contains only the seemingly altered application, with signatures dated nearly three years earlier.</p>
<p>In other words, the only zoning application currently on file does not correspond to the project the Zoning Board actually reviewed and approved in 2017.</p>
<p>The presence of handwritten changes to the most consequential parts of the application—combined with the absence of any contemporaneous findings addressing those figures—raises serious questions about the integrity of the administrative record. At a minimum, the application and the Board’s findings do not match.</p>
<p>Residents are entitled to know when these changes were made, who made them, and why the official application now reflects numbers that were never the subject of the Board’s original review. Without that information, there is no basis to conclude that the zoning approvals were grounded in a complete, accurate, and transparent record—and no credible basis to offer assurances about the “integrity” of this project.</p>
<h4>The Project Fundamentally Changed &#8211; But the Application and Review Process Did Not</h4>
<p>The contrast between the September 2017 Findings of Fact and the March 2019 Amended Findings exposes a basic contradiction in the City’s own record. The project was treated as if it posed no environmental issues, even as City agencies were raising concerns about traffic, parking, sewer capacity, and shadow impacts—and, in some cases, calling for further investigation. Despite those unresolved issues, the Zoning Board closed out environmental review in 2017 by issuing what’s called a “Negative Declaration,” and never revisited it.</p>
<p>That decision is troubling on its own, but it becomes far more problematic in light of what followed. The Amended Findings were adopted after a substantial change in the project’s scale, intensity, and density. Even assuming—purely for argument’s sake—that the expanded project could be justified on zoning grounds, SEQRA does not permit environmental review to be frozen in time.</p>
<p>A Negative Declaration issued for an earlier version of a project cannot simply be carried forward after a material increase in size and density without revisiting environmental impacts. Yet there is no indication that the ZBA revisited <a href="https://dos.ny.gov/state-environmental-quality-review-act-seqra-basics" target="_blank" rel="noopener">SEQRA</a> at all in connection with the amended approval. There is no supplemental environmental review, no discussion of whether the changes constituted a substantive change under SEQRA regulations, and no explanation for why the earlier Negative Declaration remained valid. The Amended Findings acknowledge a materially different project but are silent as to its environmental consequences.</p>
<p>You don’t need expert reports to see the problem.</p>
<p>The private home next door has been severely impacted—physically, functionally, and in terms of light, air, and livability. That reality makes the conclusion that this project posed “no significant adverse environmental impacts” ring hollow. If a neighboring home can be so profoundly affected, the claim that no deeper review was required was not just wrong—it was reckless.</p>
<p>At best, this reflects a City that failed to take a hard look. At worst, it suggests a willingness to preserve a paper finding long after reality made it indefensible.</p>
<p>Taken together:</p>
<ul>
<li>Altered application entries</li>
<li>Escalating project scope</li>
<li>No amended application matching the final build</li>
<li>No additional substantive review</li>
<li>No change to the SEQRA determination</li>
</ul>
<p>…the question is unavoidable: how far did the City and/or the developers go to paper over zoning and environmental violations after the fact?</p>
<p>District Attorney Cacace should answer that question.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><em>Supporting Documents:</em></p>
<p><em><a href="http://mvcip.org/downloads/214%20Gramatan%20ZBA%20Application.pdf" target="_blank" rel="noopener">214 Gramatan ZBA Application</a></em></p>
<p><em><a href="http://mvcip.org/downloads/Findings%20of%20Fact%20-%20September%2019%2C%202017%201.pdf" target="_blank" rel="noopener">Findings of Fact &#8211; September 19, 2017 1</a></em></p>
<p><em><a href="http://mvcip.org/downloads/Amended%20Finding%20of%20Facts%20-%20March%2028%2C%202019%201.pdf" target="_blank" rel="noopener">Amended Finding of Facts &#8211; March 28, 2019</a></em></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The House Next Door</title>
		<link>https://mvcip.org/blog/the-house-next-door/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Mon, 22 Dec 2025 01:53:10 +0000</pubDate>
				<category><![CDATA[Mount Vernon]]></category>
		<category><![CDATA[Building Department]]></category>
		<category><![CDATA[Planning]]></category>
		<guid isPermaLink="false">https://mvcip.org/?post_type=blog&#038;p=441</guid>

					<description><![CDATA[Mount Vernon loves big speeches about “equity” and “revitalization.” But the paper trail at 214 Gramatan Avenue tells a different story: warnings ignored, approvals allegedly missing, and a city government that said “nothing can be done.”]]></description>
										<content:encoded><![CDATA[<p>Mount Vernon loves big speeches about “equity,” “revitalization,” and “moving the city forward,” especially if those speeches come with a photo op and a gold shovel. But if you want the clearest, most stomach-turning example of what has actually been moving forward in Mount Vernon, look at 214 Gramatan Avenue—and the years-long paper trail of warnings, admissions, shrugs, and bureaucratic duck-and-cover described by homeowner Dina M. Perriello.</p>
<p>Because if what Ms. Perriello lays out is even half true, then this isn’t merely a planning dispute or a neighbor complaint. It’s a case study in what happens when a city government treats residents like obstacles and public service like a branding exercise: gross negligence dressed up as procedure, and incompetence protected by titles.</p>
<div style="height: 1.5rem;"></div>
<h6>“It never should have been approved” — and yet it kept going</h6>
<p>Ms. Perriello’s story is not a single bad day. It’s a five-year slow-motion failure, with repeated claims that officials acknowledged something was wrong—yet the project advanced anyway.</p>
<p>According to her timeline and emails, demolition began in February 2019 with no permit, followed by a building permit in September 2020 for lot 3 only. Soon after, she says she learned the structure next door would have a zero setback and began sending urgent messages to city officials.</p>
<p>She describes being told variations of the same line Mount Vernon residents know too well: “Nothing can be done,” “Not my jurisdiction,” “It’s too late,” and finally, the coup d’grace, “Get a lawyer.”</p>
<p>In Mount Vernon, the highest taxed community in Westchester County, we don’t get governance—we get evasion.</p>
<p>And that’s how Ms. Perriello ends up with a building so close to her house that any old predator could step out of his window right onto her flat roof.</p>
<div style="height: 1.5rem;"></div>
<div>
<figure id="attachment_445" aria-describedby="caption-attachment-445" style="width: 750px" class="wp-caption alignnone"><img decoding="async" class="size-full wp-image-445" src="https://mvcip.org/wp-content/uploads/dina-periello-roof-1.webp" alt="Dina Periello's House - Roof" width="750" height="422" /><figcaption id="caption-attachment-445" class="wp-caption-text">Dina Periello&#8217;s House &#8211; Roof</figcaption></figure>
</div>
<h6>The core allegation: approvals missing for Lots 5 and 6</h6>
<p>Here are the central claims Ms. Perriello repeats—and the ones to which the City has offered no response:</p>
<ul>
<li>The zoning application and approval was issued for Lot 3</li>
<li>The building permit was issued for Lot 3</li>
<li>The development was processed as if it involved multiple lots (Lots 3, 5, and 6)</li>
<li>No further applications or approvals were issued for Lots 5 and 6</li>
<li>After reviewing the property file in City Hall on May 14, 2024, Ms. Perriello discovered there was no zoning application or approval on file for Lots 5 and 6</li>
</ul>
<p>FOIL responses later confirmed the same.</p>
<p>If that’s accurate, this isn’t a “whoops.” If we’re being generous, it’s a systemic breakdown of basic controls—exactly the kind of breakdown that ordinary residents pay for in property damage, legal fees, and sleepless nights while officials keep collecting paychecks.</p>
<p>But if we’re being real—and this is Mount Vernon—it is the clearest, most visible example of public corruption that we’ve seen in a long time.</p>
<div style="height: 1.5rem;"></div>
<h6>The alleged damage: vibration, water, structural harm—and the shrug heard round City Hall</h6>
<p>Ms. Perriello says that during months of excavation—bedrock work that she describes as extreme—she experienced severe vibrations, sought monitoring reports, and received little to nothing back. She claims the consequences now include:</p>
<ul>
<li>Structural concerns (including bedrock shifting into her basement floor)</li>
<li>Asbestosis exposure from frayed insulated pipes</li>
<li>Water drainage problems created by the new adjacent retaining wall</li>
<li>An inability to ever repair a portion of her home where there is a zero setback</li>
<li>Serious safety and quality-of-life impacts (privacy, trespass risk, and more)</li>
</ul>
<p>Equally alarming is her claim that she repeatedly requested records (including vibration monitor reports) and that the response pattern was delay, deflection, and silence.</p>
<p>Mount Vernon residents should ask: If a city can’t produce basic monitoring and compliance records for a project of this scale, what exactly are “inspections” doing besides existing on paper?</p>
<p>Moreover, given the City’s recent crowing over the adoption of a sloppy, thoughtless comprehensive plan without benefit of an environmental review or fiscal study, residents should also ask themselves whether the people responsible for what happened to Ms. Perriello should be entrusted with a plan of that magnitude.</p>
<div style="height: 1.5rem;"></div>
<h6>The cast of “not my job”</h6>
<p>In a July 2025 email exchange, Ms. Perriello directly challenges Comptroller Darren Morton, who responded by emphasizing he was not Commissioner of Buildings and did not have jurisdiction over the Zoning Board.</p>
<p>And this is where Mount Vernon’s culture shows itself in full: the reflex to treat government like a circle of job descriptions instead of a responsibility to protect residents.</p>
<p>Ms. Perriello’s reply cuts to the heart of the problem: she alleges officials acted outside their roles when it suited them, failed to act inside their roles when residents needed them, and now want their titles to operate like immunity shields.</p>
<p>The City will say: that’s not fair. Residents will say: show us the record—and the record speaks for itself.</p>
<p>At the end of the day, two questions rise to the top: (1) if the approvals were proper, where are they? And (2) if they weren’t, who let this proceed—and why?</p>
<p>Because “I wasn’t the right person” isn’t an acceptable answer when a resident is warning you for years, producing documentation, requesting records, and describing harm.</p>
<p>Residents must also ask: who gained from this debacle?</p>
<p>A LoHud article published in August 2025 revealed that the architect behind this project was a longtime tenant of councilperson Caitlin Gleason, who was on the planning board when this was approved—and cast her vote of approval.</p>
<p>This is what public corruption looks like in real life—in real time—in technicolor.</p>
<div style="height: 1.5rem;"></div>
<div>
<figure id="attachment_446" aria-describedby="caption-attachment-446" style="width: 750px" class="wp-caption alignnone"><img loading="lazy" decoding="async" class="size-full wp-image-446" src="https://mvcip.org/wp-content/uploads/dina-house-construction.webp" alt="Dina Periello House Construction Site" width="750" height="363" /><figcaption id="caption-attachment-446" class="wp-caption-text">Dina Periello House Construction Site</figcaption></figure>
</div>
<h6>What corruption actually looks like in Mount Vernon</h6>
<p>People hear “corruption” and imagine a movie: envelopes, back rooms, dramatic arrests. And some of that probably happened here.</p>
<p>But more generally, in Mount Vernon, corruption often looks far more ordinary—and that’s why it survives. It looks like:</p>
<ul>
<li>Records that don’t exist when they should</li>
<li>Enforcement that doesn’t happen when it must</li>
<li>A permanent class of officials who know how to say “not my department” while the public eats the consequences</li>
</ul>
<p>Ms. Perriello’s timeline lays out something far worse than bureaucratic delay. It documents alleged admissions like “it never should have been approved,” followed by years of deliberate inaction.</p>
<p>If those admissions are accurate, this isn’t mere failure. It’s cover-your-own-ass—and residents should be furious.</p>
<p>Senior officials did not fix the problem. They avoided it. They ghosted Ms. Perriello while the damage to her home compounded. That is unacceptable.</p>
<p>A taxpaying resident should not be forced into financial ruin hiring lawyers to correct the City’s own error—whether that error arose from negligence, incompetence, greed, or corruption.</p>
<p>Here, Ms. Perriello was victimized twice: first by Mount Vernon’s outrageous tax burden, and then by the refusal (or inability) of its “leaders” to do their jobs.</p>
<p>City officials must stop hiding behind titles and start taking responsibility. The City caused this harm. The City must make her whole.</p>
<div style="height: 1.5rem;"></div>
<h6>What the City must release—now</h6>
<p>Or, if the City disputes Ms. Perriello’s claims, it should provide the public immediately:</p>
<ol>
<li>The full approval chain, site plan resolutions, and zoning determinations for Lots 3, 5, and 6</li>
<li>Proof of required notices, hearings, and filings (if any)</li>
<li>All inspection history, enforcement actions, and compliance records</li>
<li>Any vibration monitoring reports and related submissions required or received</li>
<li>A clear explanation of how an allegedly unapproved scope could proceed for years without decisive intervention</li>
<li>A pre- and post-survey proving the building is not encroaching</li>
<li>Fire and safety approvals</li>
</ol>
<div style="height: 1rem;"></div>
<p>And to be clear: “we’re looking into it” is not an answer. Not after five years.</p>
<div style="height: 1.5rem;"></div>
<h6>A note to officials tempted to dismiss this as “drama”</h6>
<p>This is not drama. This is what happens when residents discover that the rules only apply to them.</p>
<p>Mount Vernon can keep pretending it’s “revitalizing,” but if residents can’t get straightforward answers about approvals next door to their homes—then what is being revitalized, exactly?</p>
<p>Not trust. Not accountability. Not the rule of law.</p>
<p>Just the same old Mount Vernon machine, grinding forward—until the next resident’s life becomes the next headline, and the next resident’s dream is destroyed.</p>
<p><a href="https://www.dropbox.com/scl/fo/3uav6gcsupn1xpqbgs0gh/AM9Oy7e-v3BfXPopK3rNMMQ?rlkey=8sw9ye5w8ffky6t0q44fds01o&amp;st=5jz8knht&amp;dl=0" target="_blank" rel="noopener"><strong><span style="color: #f89a7c;">Click here for more photos.</span></strong></a></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
