Excel Air Quality Monitoring Dashboard-As of June 30, 2026


Excel Air Quality Monitoring Dashboard-As of June 30, 2026

The monthly Environmental Monitoring Reports may be found on the BPCA Resiliency website. Click HERE to open a new browser window.


To report concerns or ask questions related to the Air Quality Monitoring, click HERE to initiate an email to BPCA.

Gateway Tenant Association

Independent Environmental Monitoring Dashboard

Excel Environmental Resources review of the North/West Battery Park City Resiliency Project

Latest Excel reports reviewed: April through June 2026

BPCA retained Excel Environmental Resources as its independent environmental monitor. Enovate Engineering, the contractor’s monitoring subcontractor, operates the project’s Community Air Monitoring Plan (CAMP) monitoring system. This dashboard translates Excel’s independent findings into plain language and maintains a rolling record as each new monthly report is released.

Latest Month: June 2026 — What Residents Need to Know Now

Watch Total PM events 193 193 short-term particulate events reported by Excel.
Concern Level 2 events 43 27 PM10 + 16 PM2.5 higher-response events requiring stop-work review.
Reassuring 24-hour PM exceedances 0 No 24-hour particulate exceedances were reported by Excel.
Reassuring VOC Action Level events 0 No VOC Action Level events were reported by Excel.
Network size Active monitor IDs at month-end 21 Appendix-based count of stationary monitor IDs active by June 30.
Improving Documented power availability 98.0% 299 documented power-disconnection monitor-hours in June; this does not measure all causes of downtime.
More oversight Excel site visits 2 June 5 & June 26 — more onsite oversight than prior months.
Watch Noise review Pending Independent noise review was still incomplete in June.
Excel again found that required dust-control and stop-work procedures were not consistently followed.

June also marked the first month in which Excel conducted two field inspections. During the June 5 inspection, Excel observed visible dust in Reach 5 and reported that active mitigation was not being used during one stone-handling operation until Excel raised the issue and water spraying began.

Why Level 2 matters: A Level 2 event is the higher CAMP response level. It is important because the project plan requires work to stop, controls to be re-evaluated, and conditions to return below the applicable threshold before work resumes. Definitions & explanations ↓
June's key independent finding: Excel reported repeated occasions when Action Level 1 dust events were not met with adequate mitigation and Action Level 2 events occurred without the required work stoppage and re-evaluation of controls.
Rolling 6-Month SnapshotView detailsHide details

This section will always show the six most recent reporting months using the same resident-facing measures. Excel is BPCA’s independent monitor; Enovate operates the contractor’s CAMP monitoring system. As new Excel reports are released, the cards will update and older months will move to the archive.

Who is who: Excel is BPCA’s independent environmental monitor. Enovate is the contractor’s environmental monitoring subcontractor and operates the project’s CAMP monitoring system.
April 2026
Excel — Independent Monitor
PM events
46
Enovate — Contractor Monitor
PM events
47
24-hour PM exceedances 0Reassuring
VOC Action Level events 0Reassuring
Active monitor IDs 15*Appendix count
Documented power availability 100.0%*Defined active periods
Independent noise reviewNot availableWatch
Public reporting delay151 daysConcern
May 2026
Excel — Independent Monitor
PM events
139
Enovate — Contractor Monitor
PM events
100
24-hour PM exceedances 0Reassuring
VOC Action Level events 0Reassuring
Active monitor IDs 19*Appendix count
Documented power availability 93.9%Concern
Excel site inspections1 (5/15)More oversight
Independent noise reviewNot availableWatch
Public reporting delay121 daysConcern
May report QA note: Excel’s final May report contains internal count and month-label inconsistencies. This dashboard uses the totals stated in Excel’s executive summary.
June 2026
Excel — Independent Monitor
PM events
193
Enovate — Contractor Monitor
PM events
194
24-hour PM exceedances 0Reassuring
VOC Action Level events 0Reassuring
Active monitor IDs 21Network size
Documented power availability 98.0%Improving
Excel site inspections2 (6/5, 6/26)More oversight
Independent noise reviewReview underwayWatch
July 2026
Excel — Independent Monitor
PM events
Awaiting report
Enovate — Contractor Monitor
PM events
—
24-hour PM exceedances —
VOC Action Level events —
Active monitor IDs —
Documented power availability —
Independent noise review—
August 2026
Excel — Independent Monitor
PM events
Awaiting report
Enovate — Contractor Monitor
PM events
—
24-hour PM exceedances —
VOC Action Level events —
Active monitor IDs —
Documented power availability —
Independent noise review—
September 2026
Excel — Independent Monitor
PM events
Awaiting report
Enovate — Contractor Monitor
PM events
—
24-hour PM exceedances —
VOC Action Level events —
Active monitor IDs —
Documented power availability —
Independent noise review—
Noise note: Excel reported that it did not have access to noise-monitoring data in April or May. In June, Excel said it was reviewing Enovate’s noise reports for future incorporation. “Not available” therefore does not mean zero noise alerts.
PM count comparison: Excel and Enovate review the same underlying Aeroqual monitoring network, but their published monthly totals do not always match. April and June differ slightly; May differs materially, with Excel reporting 139 PM events compared with 100 in Enovate’s narrative summary. GTA shows each published total rather than silently reconciling the difference.
Documented power availability: GTA reconstructed expected monitor-hours from the Enovate appendices using the periods in which each monitor group is shown as active, then subtracted intervals Enovate explicitly identified as “disconnected from power.” This metric measures documented power availability only. It does not establish total operational uptime or confirm that a powered monitor was producing valid data, properly calibrated, communicating normally, positioned adequately, or capable of a meaningful upwind/downwind comparison. The April–June reports do not provide a comparable monitor-level ledger for mechanical failure, damage, communications failure, maintenance/calibration, or other non-power downtime. *April: the 100.0% figure applies only to the defined active periods shown in the appendices; Reach 7 monitoring begins April 15 in the appendix record.

*Monitor-count QA note: April and May appendix monitor-ID counts differ from Enovate’s narrative monthly summaries. The dashboard shows the monitor IDs visible in the appendices at month-end: April 15 vs. 14 stated in the summary; May 19 vs. 18 stated in the summary. June is consistent at 21.

Reporting-delay context: The decline from 151 days in April to 121 days in May and 91 days in June largely reflects multiple overdue reports being released in close succession in late September. It should not yet be read as evidence of an established timely monthly reporting cycle.
Independent Field OversightView detailsHide details

April — Remote Review Only

Excel reported that it was not yet fully onboarded, conducted no onsite inspections, and did not yet have access to noise data.

May — First Site Visit

Excel conducted one site visit on May 15. It did not observe visible dust during the visit, although remote monitoring showed PM events in Reach 1 and Reach 5 that day.

June — Two Site Visits

Excel inspected on June 5 and June 26. On June 5, it observed visible dust in Reach 5 and said additional water spraying began after Excel raised the concern.

What “Independent” Means Here

Excel is primarily overseeing Enovate’s contractor-operated network. Excel’s own direct measurements were limited to periodic field inspections rather than a separate 24/7 independent monitoring network. Excel’s scope also indicates that event causes may be relayed as determined by the BPCA project team, so residents should distinguish independent review from fully independent cause attribution.

Monitoring Integrity & CoverageView detailsHide details

Actual Monitor Locations Are Not Always Clear

The reports use a mixture of design and apparent as-built monitoring plans, even though the underlying plans state that monitor locations may be adjusted in the field. A dated, “as-operated” monthly map is not provided.

Reach 5E / Reach 6A North

June acknowledges micropile drilling in Reach 5E, but the inspection narratives do not separately document the Gateway-adjacent work area, reconcile the Reach 5E / Reach 6A North designation, or clearly identify which monitors served that work.

Monitor Outages

Enovate reports multiple monitor power disconnections, but Excel’s reports do not provide a resident-friendly monitor-by-monitor uptime and outage ledger. Future reporting should identify the monitor ID, cause and duration of each outage, whether another monitor provided adequate redundancy, whether the outage affected upwind/downwind site-contribution calculations, and when full monitoring was restored.

Negative Readings

April notes negative rolling-average readings attributed to automatic calibration overcorrection. Excel says they should be treated as zero but does not quantify how often this occurred.

Power Availability Trend

Based on GTA’s reconstruction of Enovate’s appendix data, documented power availability was approximately 93.9% in May and improved to 98.0% in June. April showed no documented April power disconnections during the defined active periods. These percentages measure only periods Enovate explicitly identified as disconnected from power; the reports do not provide an equivalent monitor-level ledger for mechanical, communications, maintenance, calibration, or damage-related downtime.

Low-Wind Conditions Can Limit Site Attribution

Enovate states that when wind speed falls below 1 mph, the downwind monitor is considered undetermined and site contribution cannot be calculated for that interval. GTA’s review of Enovate’s published wind-rose summaries found very low-wind conditions were common. In June, 21 of 34 wind-rose reporting blocks (62%) showed calm and/or sub-2 mph conditions for at least half of the reporting period.

Because Enovate groups winds below 2 mph rather than separately reporting the exact time below 1 mph, the percentage of intervals in which site contribution was unavailable cannot be determined from the published reports.

Important: The 62% figure is a low-wind screening indicator, not a measure of the percentage of time site contribution was unavailable.

Corrective Actions & AccountabilityView detailsHide details
Excel repeatedly identifies issues and recommends corrective action, but the BPCA reports do not provide a clear event-by-event record showing whether each issue was formally corrected, verified by Excel, and closed.

What the Reports Do Provide

Excel identifies events where stronger mitigation, work stoppage, BMP re-evaluation, or other action should have occurred.

What Is Missing

A resident-friendly corrective-action register: date, issue, required response, who was notified, what was done, when Excel verified it, and whether the item is open or closed.

GTA Watch List / Open QuestionsView detailsHide details

1. Document Level 2 Stop-Work Responses

For each Level 2 event, identify whether work stopped as required, what controls were re-evaluated, when conditions returned below the applicable threshold, and when work resumed. This is the most important unresolved compliance/accountability question.

2. Publish As-Operated Monitor Maps & Downtime

Provide a dated monthly map and inventory showing every active air, noise, and vibration monitor; monitor ID; installation, relocation and removal dates; and all periods of unavailable or invalid monitoring. Downtime should be classified by cause, including power loss, equipment failure, communications failure, maintenance/calibration, relocation, physical damage, or another cause, with backup coverage identified.

3. Publish Site-Contribution Availability

Report, by Reach and month, the percentage of valid 15-minute intervals in which wind conditions allowed a meaningful upwind/downwind site-contribution calculation, including the number of intervals excluded because wind speed was below 1 mph.

4. Track Corrective Actions to Closure

Publish an event-by-event corrective-action register showing the date, issue, required response, party notified, action taken, Excel verification date, and whether the issue is open or closed.

5. Complete Independent Noise Oversight

State when Excel received full access to noise-monitoring information, whether earlier months will be reviewed retroactively, and how independent noise findings will be incorporated into future reports.

6. Reconcile Published Counts

Explain material count discrepancies, including Excel vs. Enovate PM-event totals — especially May — and Enovate’s April/May narrative monitor counts versus the monitor IDs shown in the appendices. Future reports should use a dated, as-operated inventory and internally consistent totals.

7. Clarify Reach 5E / Reach 6A North Coverage

Explain which monitors covered the Gateway-adjacent work, when that monitoring began, how Reach 5E and Reach 6A North terminology should be reconciled, and whether the configuration provided meaningful receptor and upwind/downwind coverage.

Definitions & How to Read This DashboardView detailsHide details

This reference section explains the technical shorthand used above. Linked terms throughout the dashboard jump here for readers who want more detail.

Community Air Monitoring Plan (CAMP)

The project's CAMP establishes how construction-related air monitoring is performed and sets short-term response thresholds known as Action Levels. The purpose is to trigger protective action during construction when particulate levels rise.

↑ Back to top

PM / Particulate Matter

PM means particulate matter: tiny airborne solid particles and liquid droplets. The dashboard counts short-term PM Action Level events reported by the project monitors; these are not automatically the same thing as violations of longer-term regulatory air-quality standards.

↑ Back to top

PM10

PM10 refers to inhalable particles with aerodynamic diameters generally 10 micrometers or smaller. Construction dust can contribute to PM10, which is why the CAMP monitors it separately.

↑ Back to top

PM2.5

PM2.5 refers to fine particles with aerodynamic diameters generally 2.5 micrometers or smaller. These particles are smaller than PM10 and are monitored under their own CAMP thresholds.

↑ Back to top

Action Level 1

Level 1 is the lower CAMP response threshold. When construction-related particulate levels reach this level, the plan calls for additional or re-evaluated dust-control measures while work may continue only under the applicable CAMP conditions.

↑ Back to top

Action Level 2

Level 2 is the higher CAMP response threshold. After required suppression efforts, an applicable Level 2 condition requires work to stop, controls to be re-evaluated, and work to resume only after particulate conditions are reduced below the applicable threshold and visible migration is controlled.

Why GTA highlights it: Level 2 events provide an especially important test of whether the project's required protective response was followed.

↑ Back to top

Site Contribution / Upwind & Downwind

The contractor compares upwind and downwind readings to estimate the portion of particulate levels that may be attributable to construction. Wind direction is therefore central to the calculation. When wind is too light to determine a downwind station, the project may be unable to calculate a site-contribution value even though raw monitor readings still exist.

Monitor-siting concern: In several project reaches, only two fixed air monitors appear to be deployed, and in some locations those monitors are oriented generally north–south along the waterfront. When winds move west-to-east across the Hudson River waterfront, a fixed north–south pair may not consistently function as a true upwind/downwind pair and both monitors may be partly crosswind to a construction plume. This does not mean the monitors provide no useful information, but it raises a reasonable question about whether the fixed locations consistently provide the intended upwind/downwind comparison and adequately capture localized emissions near nearby receptors.

GTA has therefore asked BPCA to explain the siting rationale for each reach and to provide dated, as-operated monitor locations together with wind direction, monitor relocations, outages, and any supplemental or mobile monitoring used when fixed locations do not create a meaningful upwind/downwind comparison.

The dashboard does not characterize west-to-east winds as the prevailing condition for all periods unless supported by the project's own meteorological data. The concern applies specifically during periods when wind direction makes a north–south monitor pair crosswind rather than upwind/downwind.

↑ Back to top

Low-wind reporting limitation: Enovate’s wind-rose summaries group conditions into “calm” and “<2 mph” categories, while the CAMP site-contribution cutoff is <1 mph. As a result, the published reports do not provide enough detail to calculate the exact percentage of intervals when site contribution was unavailable because of low wind.

Excel Site Inspection

A site inspection is an onsite visit by Excel, BPCA's independent monitor. Excel also reviews the contractor's monitoring data remotely. A site-inspection count therefore should not be read as the number of days environmental monitoring occurred; the contractor-operated monitors run separately.

↑ Back to top

Noise Alerts / Noise Review

This dashboard reports noise information only when Excel's monthly reports provide enough information to do so. Excel reported that it did not yet have noise-monitoring access in April and May and was reviewing Enovate noise reports in June. “Not available” does not mean zero noise events.

↑ Back to top

Public Reporting Delay

The reporting-delay figure is the number of days from the end of the reporting month to the date shown on Excel's public monthly report. It measures when residents received the report, not whether Excel communicated particular concerns to the project team in real time.

↑ Back to top

Where Is the Work? Understanding the Project Reaches

The project is divided into numbered construction areas called Reaches. The visual below is more intuitive for community use because it shows the full Battery Park City project alignment and all seven reaches.

Overview image showing Reaches 1 through 7 along Battery Park City, including Reach 1 West Street Crossing Tribeca, Reach 2 North Esplanade, Reach 3 Rockefeller Park, Reach 4 Belvedere Plaza, Reach 5 North Cove, Reach 6 South Esplanade, and Reach 7 South Cove.
Community-facing overview of the project reaches. Image is used here as an orientation aid and should not be treated as a precise engineering boundary map.

Why this matters: environmental-monitoring results, monitor locations, outages, work activities and Excel observations are often reported by Reach rather than by familiar building, park or street name.

  • Reach 1 — West Street Crossing / Tribeca
  • Reach 2 — North Esplanade
  • Reach 3 — Rockefeller Park
  • Reach 4 — Belvedere Plaza
  • Reach 5 — North Cove
  • Reach 6 — South Esplanade
  • Reach 7 — South Cove

What the first Excel reports covered: April–June monitoring discussion in Excel’s reports focused mainly on the reaches that were active or producing events during that period, especially Reaches 1, 3, 5, 6 and 7. Even so, this GTA dashboard is intended for the broader Battery Park City community, so it should orient residents to all reaches, including Reach 2 and Reach 4.

Reach 5E / Reach 6A North: the Gateway-adjacent area deserves particular care in interpreting the reports. Excel’s June work summary identifies micropile drilling in Reach 5E, while other project materials and community discussion also refer to the nearby area as Reach 6A North. The dashboard flags this as a monitoring-documentation issue rather than silently treating the names as interchangeable.

Resident-facing recommendation: future independent reports should include a dated “as-operated” map showing the actual location of every active air, noise and vibration monitor, along with installation, relocation, removal and outage dates.

↑ Back to top
Important: CAMP Action Levels are short-term project response thresholds. A reported Action Level event should not automatically be described as a regulatory air-quality violation or as evidence, by itself, of a health impact.

Source: Excel Environmental Resources Independent Environmental Monitoring Monthly Reports Nos. 1–3 for April, May and June 2026, prepared for the Battery Park City Authority's North/West Battery Park City Resiliency Project. Comparison figures also reference the corresponding Enovate Community Air Quality Monitoring reports.

Methodology note: GTA has preserved the event counts reported by each source rather than silently reconciling conflicting totals. Where Excel and Enovate differ, the discrepancy is shown explicitly.

Important note: Short-term Action Level events are project-response thresholds and should not be interpreted as equivalent to sustained 24-hour regulatory exceedances.

Dashboard purpose: GTA summarizes technical monitoring information in plain English for local residents. This dashboard does not replace the underlying Excel or Enovate reports.