BPCA is removing 500 mature trees — about 40% of Battery Park City's waterfront trees for the resilience project — and no design alternative was ever built around saving them. Sign the petition and send an email asking for one.
BPCA is removing 500 mature trees — about 40% of Battery Park City's waterfront trees[14][2] for the resilience project, replacing them with 525 saplings. Cutting has already started — trees in south Battery Park near 3rd Place are already gone.[13]
And it's worse in some areas: on the South Esplanade, about 80% of trees will be cut.[8]
These 40-year-old trees each intercept 1,000+ gallons of stormwater per year and provide cooling, carbon capture, and habitat. The new trees that BPCA says will be planted won't match a 40-year-old canopy on stormwater, shade, or carbon for 20–30 years.See the math →
BPCA didn't take a hard look at saving these trees
The FEIS Alternatives Chapter shows no design alternative was built around tree retention. And in a recent response to community inquiries signed by Michael Ryan, Community Construction Liaison, BPCA stated that USACE guidelines are not directly applicable — making the 500 removals design choices, not federal mandates.
1. No design alternative was built around saving trees.
In none of the alternatives listed in the FEIS Alternatives Chapter is tree retention set as a design objective. That's also reflected in how the chapter handles tree counts: only one of seven reaches has a tree-count comparison across alternatives — Reach 1, comparing 25 trees vs 5 trees. For Reaches 2–7, no equivalent comparison exists.
2. By BPCA's own answer, the removals are design choices — not federal mandates.
BPCA's response states "USACE Guidelines are not directly applicable to NWBPCR because it is not a USACE project." If true, the 15-foot vegetation buffer isn't a federal requirement — it's a BPCA design decision. Every removal becomes a design choice, not an engineering necessity.
The same response continues to reference "the 15-foot USACE 'buffer' zone," and the FEIS Executive Summary (page ES-17) describes the design as one that meets "the objectives of FEMA (and the USACE guidelines)." Until BPCA reconciles those statements, both readings stay open — and that's one of the questions in the email below.
What we're asking BPCA to do
Three steps to confirm tree retention was treated as the design default — before any more trees are cut.
1
Justify each removal, one by one.
For every one of the 500 trees, publish the specific design constraint that made retention impossible. Where that constraint is itself a design choice (alignment, limits of work, foundation type, buffer assumption), publish the alternative considered and the basis for rejecting it.
2
Design alternatives built around saving trees.
For each reach, a design that takes tree retention as the primary objective — with its projected tree count, resilience tradeoffs, and the basis for acceptance or rejection. Not a variation on the current plan.
3
Independent review.
Qualified arborists, flood engineers, and landscape architects with no financial relationship to the design-build contractor — findings published on the public record.
No further removals in any reach until the analyses for that reach have been published and independently reviewed.
Two ways to be counted — do both
BPCA replied. Make the demand on the public record — sign the petition and send the email.
Petition: name + address, ~30 seconds. Email: opens your mail client with the full text — goes to BPCA leadership and 30+ elected officials. Or scroll down to copy & send manually.
Sacramento, 2025 — Army Corps planned to cut 700+ trees for levee work. A federal judge blocked all cutting after the community proved alternatives weren't explored.
San Antonio, 2022 — City planned to remove 105 trees for park renovation. Community pressure cut it to fewer than 50 — more than half saved.
Nationwide, 2014 — The Army Corps had a policy requiring tree removal within 15 feet of levees — the same rule BPCA references. It was reversed after communities and environmental groups pushed back.
Coeur d'Alene, 2012 — Army Corps ordered 1,000+ mature pines removed from a levee. The community fought back, and only dead trees were removed. The rest were saved.
Virginia, 2024 — The National Park Service was already cutting trees when the community caught it and mobilized. All removal was halted. It's not too late.
And under the same FEMA/USACE framework BPCA cites, flood projects have kept their mature trees and stayed accredited. See the precedents →
Talking to a neighbor about this?
See common questions with short, sourced answers — and download a flyer to hand out.
The email
Full email text
Dear BPCA Board and Leadership,
I am a Battery Park City resident writing about the North/West Battery Park City Resiliency Project tree removals.
In a response to community inquiries signed by Michael Ryan, Community Construction Liaison, BPCA confirmed the project will remove 500 mature trees - up from 435 in the Final EIS - with the +65 increase reflected in the December 19, 2025 Technical Memorandum and no Supplemental EIS prepared. The response also stated that USACE Guidelines are "not directly applicable to NWBPCR because it is not a USACE project" while continuing to reference "the 15-foot USACE 'buffer' zone," and that "each tree in the project area was assessed for removal, protection, or transplantation."
The response makes clear that trees are being removed because they fall within "limits of work" or because adjacent root zones would be impacted by construction. But limits of work and foundation geometry are design choices, not external constraints - and no reach in the FEIS was designed with tree conservation as a primary objective. That is the threshold problem, and it is the reason 500 trees, not a substantially smaller number, are being cut.
SEQRA requires that an agency take a "hard look" at significant environmental impacts and at the alternatives that could mitigate them. The three questions below test whether that hard look was actually taken - at the buffer assumption underlying the design, at the post-FEIS changes that grew the count, and at whether the design itself treated tree retention as the default. Pending those answers, we ask that no further removals proceed in any reach until the per-reach analysis has been published and independently reviewed.
1. Is a vegetation-free buffer being applied to NWBPCR, and on what basis?
The response states that "USACE Guidelines are not directly applicable to NWBPCR because it is not a USACE project." That differs from FEIS Executive Summary p. ES-17, which describes the design as one that meets "the objectives of FEMA (and the USACE guidelines)." The response also continues to refer to "the 15-foot USACE 'buffer' zone."
We ask BPCA to confirm on the record:
(a) Is USACE EP 1110-2-18 being applied to NWBPCR - yes or no?
(b) Is BPCA applying any vegetation-free buffer along the flood barrier as a project design standard? If yes, what is the distance, and what is its source: a BPCA-adopted standard, a consultant engineering recommendation, a FEMA requirement, a state regulation, or something else? If no, what clearance criterion, if any, governs which trees fall within the limits of work on vegetation-clearance grounds?
2. December 19, 2025 Technical Memorandum - was a hard look taken at the additional removals?
The Memorandum raised the removal count from 435 to 500 - a 15% increase project-wide, 77% in Reach 1 alone - and concluded that the changes "would not result in any significant adverse impacts not addressed or inadequately addressed in the FEIS." On that basis, no Supplemental EIS was prepared. Section B.2 of the Memo states only that "the design has progressed since the FEIS, the design team has determined that additional trees will need to be removed and replaced," and Section D restates the totals without identifying which design refinements drove the increase or what alternatives were considered.
The "hard look" standard, applied through 6 NYCRR 617.9(a)(7), requires the agency to actually examine significant new information and explain its determination - not to conclude in summary form that no examination is required. We ask BPCA to publish, for each design refinement that produced additional removals: the refinement, its tree-count impact by reach, the alternatives considered with their projected tree counts, and the specific factual and legal basis for the no-Supplemental-EIS conclusion. We further ask that this publication be reviewed by an independent panel of qualified arborists, flood engineers, and landscape architects with no financial relationship to the design-build contractor, and that their findings be published on the record.
3. Per-tree justification, retention-first design alternatives, and independent review.
The response states that each tree was assessed against determinants including foundation type, deployable proximity, wave impact, elevation, species, size, growth habits, and tolerance to flooding, wind, and salt. But across the FEIS Alternatives Chapter (Chapter 5.0), none of the alternatives take tree conservation as a primary design objective. SEQRA's "hard look" standard requires more than a memo certifying the analysis was done - it requires demonstrating that retention was the default, that designs built around retention were genuinely developed, and that an independent review confirmed the analysis was real.
We ask BPCA to:
- Justify each removal individually. Publish, for each of the 500 trees marked for removal, the specific design constraint that made retention impossible - and where that constraint is itself a design choice (alignment, limits of work, foundation type, buffer assumption), the alternative considered to avoid the constraint, its tree-count effect, and the basis for rejecting it. Where this analysis has not been done, the appropriate response is not to certify that it was, but to do it.
- Develop a retention-first design alternative for each reach. Not a variation on the existing design - a design built from the assumption that tree retention is a primary objective, with its projected tree count, resilience tradeoffs, and the basis for acceptance or rejection.
- Submit both analyses for independent review by qualified arborists, flood engineers, and landscape architects with no financial relationship to the design-build contractor - and publish their findings on the public record. The current design-build team has a direct financial interest in the existing design; outside verification is required before residents can be expected to accept that 500 mature trees represent the minimum loss this resilience objective requires.
No further removals in any reach until the analyses for that reach have been published and independently reviewed.
Thank you for your time and engagement. We look forward to your responses on the public record.
Sincerely,
[Your Name]
[Your Address in Battery Park City]
Subject:NWBPCR Tree Removals — Reconciliation Questions on the Public Record
How we got here
The thread on the public record so far.
FEIS — May 2025. 435 mature trees marked for removal, 450 to be planted. BPCA classified the project as "no significant adverse impact."[1]
Technical Memorandum — Dec 19, 2025. Removal count revised from 435 to 500 (+65 — including 50 along the Route 9A median, +15 in Reach 6, +5 in Reach 3, with South Cove falling from 35 to 30). No Supplemental EIS prepared.[15]
BPCA's response to community inquiries — May 2026. Confirmed the 500 figure, stated USACE doesn't directly apply, did not publish the per-tree reasoning. Full text below.[14]
Our first email to BPCA — 3 demands, sent before the December 2025 memo and BPCA's response
Dear BPCA Board and Leadership,
I am a Battery Park City resident. I support the North/West Resilience Project — but I am asking BPCA to pause all tree removal until the following three steps are completed.
The current plan removes 435 mature trees — nearly 40% of every tree in the project area. These are 40-year-old trees that provide shade, absorb stormwater, and define the neighborhood. Of those 435, only 17 are being considered for transplanting — less than 4%. The rest will be cut down. BPCA has never classified which trees are genuinely in the path of the wall and which could be preserved. Without that analysis, there is no basis for concluding that every removal is necessary.
Three steps would establish that basis:
1. File a USACE Vegetation Variance Request. The federal guidelines BPCA cites include a formal process for preserving trees near flood infrastructure. BPCA has never applied — and has never even contacted the USACE New York District about a variance. The Draft EIS committed to exploring the variance process; that commitment was struck from the Final EIS without explanation. Let the Army Corps' own specialists determine which trees can safely remain.
2. Publish a tree-by-tree removal classification. For each of the 435 trees marked for removal, disclose whether it is: (A) in the floodwall footprint, (B) within the 15-foot zone — a variance candidate, (C) in a temporary construction area — a transplant candidate, or (D) being removed for other reasons. Without this breakdown, the public has no way to evaluate which trees could be saved.
3. Submit the classification to independent review. Have the tree-by-tree assessment reviewed by qualified arborists and flood engineers who are not employed by BPCA's design-build contractor — professionals with no financial stake in the current plan. When the Wagner Park community hired the park's original designers, they proved a tree-preserving alternative was feasible. Residents deserve the same transparency here.
The variance process is not theoretical. In Sacramento, the USACE approved a vegetation variance covering 42 miles of levees — one of the first ever granted — allowing trees to remain alongside flood infrastructure. In Idaho, the same 15-foot rule BPCA cites was challenged on a levee lined with mature pines; only dead trees were removed and every healthy tree was preserved. The 15-foot rule itself was reversed nationally in 2014 after Congress found it lacked site-specific engineering justification. BPCA has not even attempted this established pathway.
We are not asking BPCA to stop the resilience project. We are asking BPCA to stop cutting trees until it has proven — tree by tree, with independent verification — that every removal is necessary and every alternative has been exhausted. Floodwall construction can proceed in sections that don't require tree removal while this assessment is completed.
Thank you,
[Your Name]
[Your Address in Battery Park City]
BPCA's response to community inquiries — Michael Ryan, Community Construction Liaison
Good afternoon resident,
Thank you for writing, and for your support of the North/West Battery Park City Resiliency Project (NWBPCR). The vital work now underway will protect our neighborhood against the threat of storm surge and flooding resulting from heavy rains and sea level rise. Nearly 14 years since Superstorm Sandy claimed 44 lives, including one here in Lower Manhattan, and after five years of community input on project design across dozens of public engagement sessions, we’re glad to be delivering a more resilient downtown with our part of New York City’s overall Lower Manhattan Coastal Resiliency Project. As to your specific concerns here, we’re glad to note that NWBPCR will result in a net increase in the number of trees in Battery Park City.
Battery Park City has more than 1,700 total trees across its 92-acre site. As we have articulated over the course of our public engagement, it is, unfortunately, necessary to remove some of these trees to effectuate building of the NWBPCR flood barrier system (FBS). Additionally – and unrelated to the Authority’s resiliency work – a number of trees require removal due to poor health.
The project team has worked diligently to minimize tree removals to the greatest extent possible, and our approach for the planting of new ones will prioritize diversity in species, age, and size to cultivate a more sustainable urban tree canopy.
More detailed information regarding tree removal is reflected in the bullets below. Following that are some more specific answers to your questions.
The NWBPCR Final Environmental Impact Statement (FEIS) contemplated a net increase in the number of trees pre vs. post construction – a total of 435 existing trees to be removed and 450 new trees to be planted – a +15 net increase.
40 of these tree removals are “conditions” removals – meaning trees in poor health that would have required removal even without any resiliency work occurring.
In its post-FEIS Technical Memorandum (December 2025), the Authority noted an increase in the estimated number of trees requiring removal with a corresponding increase in the estimated number of new trees to be planted. The result was a greater net increase in new trees planted – a total of 500 existing trees removed (+65 from FEIS) with 525 new trees planted (+75 from FEIS) – a +25 net increase.
The majority of the increase of removals that were noted in the 12/25 Tech Memo – 50 of 65 trees – are located outside Battery Park City, along the Route 9A median.
The balance, mostly in Reach 6 (South Esplanade), are required to be removed to accommodate a combination of FDNY ambulance access, hydrant removal/installation, utilities conflicts, or grading/draining requirements.
The Tech Memo also noted that in the South Cove area of the project, where construction work recently began, five fewer trees (30) would require removal than the 35 contemplated in the FEIS.
Has each tree been individually assessed? How many of the 435 actually fall within the required clearance zone? Which could remain with modified wall alignments?
Each tree in the project area was assessed for removal, protection, or transplantation.
What design alternatives were evaluated for tree-adjacent sections? The project already uses deployable barriers at multiple locations — were similar approaches considered where they could preserve mature trees?
The alternatives analyzed are set forth in the Alternatives Chapter of the FEIS. NWBPCR has been designed to minimize tree clearing to the extent possible. As a general matter, trees have been designated for removal due to construction either because they are located within the limits of work or because they are sufficiently close to such areas that the root zones of the trees would be impacted. It is instructive to note here that, in comparison to typical wall construction, the flood barrier system (FBS) includes substantial underground elements, including drilled pile foundations and seepage barriers that extend below the surface.
To protect the structural integrity and function of the FBS from detrimental effects of vegetation (for example, root intrusion, falling limbs or trees, or blocking inspection and maintenance access) all trees must be kept at a minimum distance from the system’s wall and gates. This distance is determined through careful analysis of the system’s vulnerability such as the type of foundation used, proximity to operable/deployable elements, exposure to wave impact, and elevation at each site – as well as the species and size of the proposed trees, their growth habits, and their tolerance to flooding, wind, and salt exposure. This analysis will also be part of the overall process for flood protection certification.
Has BPCA explored the USACE Vegetation Variance Request process? Federal guidelines include a formal mechanism for preserving vegetation when site-specific analysis supports it. Has this been pursued? If not, why not?
The US Army Corps of Engineers Guidelines are not directly applicable to NWBPCR because it is not a USACE project, so no variance has been or needs to be sought. As discussed in the FEIS, 60 replacement trees will be planted within the 15-foot USACE “buffer” zone as part of the project.
Has BPCA considered transplanting trees that must be removed during construction and returning them afterward? Other US cities have done this successfully — Phoenix's Central Station redevelopment relocated 20 mature trees during construction, and Stanford's Packard Children's Hospital boxed and stored 12 protected oaks and redwoods for replanting. If transplanting has not been evaluated, why not?
Tree transplantation has been considered, and a total of 7 trees within the project site identified will be transplanted. Considerations that impact tree suitability for transplant include: Species, Size (smaller is better, larger trees are harder and more expensive to transplant and are less likely to survive the process), Overall tree health, Suitable location to be transplanted to.
How does removing 40-year-old canopy — and replacing it with saplings that won’t match its stormwater, cooling, and carbon benefits for decades — serve a project whose purpose is resilience?
NWBPCR will provide for a diversity in tree age at the time of planting. Approximately one-third of the trees proposed to be replanted along the Esplanade and throughout Battery Park City will range from 4- to 8-in trunk caliper, which means that these trees will be several years old at the time of planting (i.e., not young saplings). The balance will be 3-in caliper or are multitrunk species and thus are not measured by trunk diameter, but rather by height, which is anticipated to be 8ft to 14ft at time of planting. Tree purchases will be timed to allow for uninterrupted growth in nurseries before planting occurs.
Thank you again for writing, and for your support of our coastal resiliency work. For regular updates please subscribe to our biweekly construction newsletter, and please send any project-related questions to: nwbpcrinfo@bpca.ny.gov or (917) 436-6739.
Sincerely,
Michael
Michael Ryan
Community Construction Liaison
Also contact these officials
These leaders have direct influence over BPCA or the federal rules it cites — but only accept messages through their websites. Tap a button to open a popup with the ready-to-send message, copy it, then open that office's contact form.
Email your federal reps (Democracy.io) →all three of your federal representatives — House + both Senators — in one form. Rep. Goldman has directed $8.2M to adjacent FiDi-Seaport resilience work
BPCA Final EIS — Response to Comments (May 2025) — Table 10-1: 435 trees removed, 450 planted, per-reach breakdown; ~395 due to construction, ~40 due to health; deployable barrier locations; USACE vegetation policy discussion
BPCA Final EIS — Executive Summary (May 2025) — ES-17/18: tree removal and replacement summary; design "meets the objectives of FEMA (and the USACE guidelines)"; DEIS commitment to explore FEMA variance process struck from Final EIS
@treesbpc on Instagram — community documentation of tree removals already underway in south Battery Park
BPCA response to community inquiries (Michael Ryan, Community Construction Liaison, May 2026) — full text in the "BPCA's response to community inquiries" accordion above
BPCA NWBPCR Technical Memorandum (December 19, 2025) — Sections B.2 and D address the 435 → 500 tree-removal increase and the no-Supplemental-EIS conclusion