Air Quality Monitoring Dashboard-As of May 31, 2026
Community Air Quality Monitoring Dashboard
Battery Park City Resiliency Project — Resident-Friendly Monthly Summary
GTA is tracking these reports on behalf of residents because the official air monitoring documents are technical and not easy for most residents to interpret. Our goal is to identify recurring concerns, explain them clearly, and press BPCA and its contractors for reliable monitoring, transparent reporting, and stronger dust prevention before problems affect residents.
First, What Are We Measuring?
The official reports use technical terms like PM10, PM2.5, and VOC. Here is what those mean in plain English.
PM = Particle Pollution
PM stands for particulate matter. In everyday terms, this means tiny particles in the air, including dust, dirt, soot, smoke, or particles created by construction activity.
PM10 = Larger Dust
PM10 refers to larger airborne particles. For residents, this is often the kind of dust most associated with demolition, excavation, soil, debris, and windblown construction material.
PM2.5 = Finer Particles
PM2.5 refers to much smaller particles. These can be more concerning for people with asthma, respiratory conditions, heart or lung conditions, older adults, and young children.
Current At-a-Glance Status
No sustained PM10 or PM2.5 regulatory exceedances reported in the reviewed months.
No vapor or chemical exceedances reported in the reviewed months.
Short-term 15-minute PM events reported in May 2026.
Reach 5 remains the largest hotspot; Reach 7 remained active in May.
Monitoring Coverage Concern
GTA is tracking an unresolved monitoring coverage issue near Gateway. On May 8, BPCA announced that work near Gateway would begin on May 11, including excavation, jackhammering, subsurface investigation, tree work, soil sampling, and salvage activities. GTA asked BPCA to confirm whether noise, air, and vibration monitoring was in place for this work. BPCA responded that monitoring was in place.
GTA later learned that noise and air monitoring equipment for this Gateway-adjacent work area was not installed until June 10. BPCA has not yet provided a written explanation for this discrepancy.
Why this matters: If monitoring was not actually in place when work began, then the reported May exceedance counts may not fully reflect dust, noise, or vibration conditions in the affected Gateway-adjacent area. GTA is asking BPCA to explain when monitoring was installed, what areas were covered, why residents were told monitoring was already in place, and how BPCA will account for any unmonitored work period.
Data Confidence and Transparency Note
GTA summarizes the monthly air monitoring reports for residents in plain English. These dashboard numbers are based on the exceedance entries listed in the official reports; GTA has not independently recalculated every 15-minute reading from the raw monitoring data.
The May report was prepared by Enovate Engineering, identified in the report as a subconsultant to Turner-SPC JV. GTA believes residents would have greater confidence if BPCA provided direct real-time public access to the underlying monitoring data, clearer explanations for exceedance causes, and independent review of monthly results.
GTA is also concerned that the May report was issued nearly a month after the reporting period ended, despite showing the highest number of short-term dust events so far. For months with repeated exceedances, monitor outages, or unusual after-hours readings, residents should not have to wait for the monthly report to learn what happened.
Month-by-Month KPI Summary
| Month | Areas Monitored | 24-Hour PM Exceed-ances | VOC Exceed-ances | PM10 Short-Term Events | PM2.5 Short-Term Events | Total Short-Term PM Events | Main Reported Causes | GTA Watch Item |
|---|---|---|---|---|---|---|---|---|
| Dec. 2025 | Reach 5, Reach 6 | 0 | 0 | 15 | 10 | 25 | Paver demolition, site preparation, test pits, Upper Room demolition | Active demolition dust |
| Jan. 2026 | Reach 1, Reach 5, Reach 6 | 0 | 0 | 5 | 0 | 5 | Wind gusts blowing loose soil during off-hours | After-hours soil stabilization |
| Feb. 2026 | Reach 1, Reach 5, Reach 6 | 0 | 0 | 14 | 5 | 19 | Windblown soil, slab demolition, equipment exhaust, saw-cutting/chopping | Dust control and equipment idling |
| Mar. 2026 | Reach 1, Reach 3, Reach 5, Reach 6 | 0 | 0 | 16 | 11 | 27 | Excavation, hand chopping, tree removal, exposed loose soil, wind events | Reach 5 and off-hours wind events |
| Apr. 2026 | Reach 1, Reach 3, Reach 5, Reach 6, Reach 7 | 0 | 0 | 37 | 10 | 47 | Moving equipment, windblown dust, plywood barriers, waterfront work, Pumphouse Park work, subcontractor vehicles/materials, dewatering tanks, tree trimming, concrete deadman work | Sharp increase in short-term dust events; Reach 5 remained highest, Reach 7 newly active, Reach 6/Gateway dewatering-related events |
| May 2026 | Reach 1, Reach 3, Reach 5, Reach 6 Albany, Reach 6 Rector, Reach 7 | 0 | 0 | 75 | 25 | 100 | Construction activities, subcontractor activities, wind-blown dust, concrete demolition, garden-hose/wetted-soil mitigation, improper generator operation, tree/surface demolition and utility-related work | Highest month so far based on reported exceedance entries; Reach 5 remains dominant hotspot, Reach 7 remains active, and GTA is also tracking a separate Gateway-adjacent monitoring coverage concern for work that reportedly began before noise and air monitoring equipment was installed. |
Monthly Trend: Short-Term Dust Events
These are 15-minute PM10 and PM2.5 exceedance events. They are not the same as sustained 24-hour regulatory exceedances, but they are useful indicators of construction dust-control performance.
PM10 vs. PM2.5 Events
PM10 is larger dust often associated with construction activity. PM2.5 is finer particle pollution and can be more concerning for residents with asthma, respiratory conditions, heart/lung conditions, older adults, and young children.
Where Are the “Reaches”?
The official reports divide the project into construction zones called reaches. Most residents will not know these technical labels, so GTA is translating them into more familiar neighborhood areas.
What Caused the Short-Term Dust Spikes?
| Cause Category | What It Means | Resident Concern |
|---|---|---|
| Construction activities | General active construction work was repeatedly listed as the cause of PM10 and PM2.5 events, especially in Reach 5 and Reach 7. | BPCA should explain what specific activities caused spikes and what controls will be strengthened. |
| Subcontractor activities | Several events were attributed to subcontractor activities, including some late-night or early-morning readings. | All contractors and subcontractors should be held to the same dust-control, notification, and reporting standards. |
| Wind-blown dust | Exposed soil or dust moves during gusts, often after work hours, overnight, or on weekends. | Suggests need for better end-of-day, weekend, and pre-storm stabilization. |
| Concrete demolition | Breaking or removing concrete can generate heavy short-term dust. | Needs wetting, containment, and close monitoring at the source, especially near residences and public walkways. |
| Improper generator operation | The May report states that some Reach 5 readings were tied to wind-blown dust and a generator operating improperly, and that the generator was removed from service. | Equipment checks should be proactive, not only after elevated readings occur. |
| Monitor power outages | Several reaches had monitors disconnected from power during May. | Data gaps reduce public confidence and should be minimized with better power management or backup power. |
| Garden hose / wetted-soil mitigation | The report repeatedly describes wetting areas or using a garden hose after dust events. | Helpful, but GTA should ask whether more robust prevention is needed before spikes occur. |
Resident-Friendly Interpretation
What is reassuring?
- No reported sustained 24-hour PM10 or PM2.5 regulatory exceedances.
- No reported VOC exceedances.
- Most short-term events reportedly returned below action levels by the next monitoring interval.
What remains concerning?
- May had 100 short-term PM events, the highest monthly total so far.
- Reach 5 alone accounted for more than half of May’s reported PM events.
- Reach 7 remained active with concrete demolition and construction-related PM events.
- Several events were attributed to wind-blown dust during overnight, weekend, or off-hour periods.
- Several events were attributed to subcontractor activities, raising questions about subcontractor oversight.
- Many monitor power outages were reported, especially in Reach 7 and Reach 6 Rector Street.
- The report appears to contain at least one wording/threshold inconsistency in the Reach 7 PM2.5 section, which should be corrected or clarified.
GTA Watch List for BPCA / Project Team
| Question / Watch Item | Why It Matters to Residents |
|---|---|
| What explains the May jump to 100 short-term PM events? | May more than doubled April’s reported total. Residents deserve a plain-English explanation of what changed and what will be done differently. |
| What specific corrective actions are being taken in Reach 5? | Reach 5 remains the dominant hotspot, with 45 PM10 events and 8 PM2.5 events in May. |
| Are subcontractors working outside stated construction hours? | The report states standard contractor working hours are 7am–4pm Monday–Friday, but some exceedances attributed to subcontractor activity occurred very early in the morning. BPCA should clarify whether work was authorized, whether attribution is correct, and how after-hours activity is controlled. |
| How is wind-blown dust stabilized overnight, on weekends, and before storms? | Wind-blown dust remains a recurring cause across multiple months and reaches. |
| What stronger controls are being used during concrete demolition? | Concrete demolition was identified as a cause of PM events in Reach 6 Albany and Reach 7. |
| What caused the improperly operating generator in Reach 5? | The report says the generator was removed from service, but residents should know whether equipment inspections are being strengthened. |
| Can monitor power outages be reduced? | May included multiple monitor power disconnections, especially in Reach 7 and Reach 6 Rector Street. Monitoring should be as continuous and reliable as possible. |
| Can report errors or inconsistencies be corrected? | The May report appears to include at least one PM2.5 threshold typo or inconsistency. Accurate, clear reporting is important for public trust. |
| Can BPCA publish a simple monthly public dashboard? | The official reports are technical and difficult for many residents to interpret. A public-facing dashboard would improve transparency. |
| Was Gateway-adjacent work monitored from the first day it began? | BPCA advised GTA that monitoring was in place when work near Gateway was scheduled to begin on May 11. GTA later learned that noise and air monitoring equipment was not installed until June 10. BPCA should explain the discrepancy, identify what monitoring was actually active from May 11 to June 10, and clarify whether the May report undercounts dust conditions in this area. |
How to Read This Dashboard
PM10: Larger dust particles often associated with construction, demolition, soil, and debris.
PM2.5: Finer particles that can be more concerning for people with respiratory or heart conditions.
VOC: Volatile Organic Compounds, generally vapor or chemical-type readings.
15-minute exceedance: A short-term reading above a project action level. It does not necessarily mean the air exceeded a full-day regulatory standard.
24-hour exceedance: A longer-term regulatory exceedance measured over a full day. The reports reviewed did not identify these for PM10 or PM2.5.