Wildfire smoke Officially verified
Daily PM2.5 peaked at 28 µg/m³ near Palm Bay across 1 covered metro home to 658,447 people. 1 metro placed a top-ten day in their record.
Why we think this happened
An exact-date NWS discussion directly attributes Melbourne-area haze and reduced visibility to smoke from smoldering brush fires. Nearby surface observations independently show haze and reduced visibility. The broad wildfire-smoke cause is official; the responsible individual fire remains unresolved because contemporaneous reports conflict about the onset of a later large Brevard fire.
Officially verified A directly applicable government determination or qualified scientific attribution product identifies this cause.
National Weather Service Melbourne via Iowa Environmental Mesonet · May 26, 2006 official
NWS Melbourne reported areas of reduced flight conditions near Melbourne caused by haze and smoke from smoldering brush fires on the catalog date.
Local 6 News via Firehouse · May 29, 2006 hypothesis
Contemporaneous local reporting said lightning on Friday, May 26 sparked a Brevard-Orange brush fire that grew to about 1,000 acres and later closed roads in Melbourne and the surrounding corridor because of fire and smoke.
NOAA/NWS surface observations via Iowa Environmental Mesonet · May 26, 2006 hypothesis
Melbourne Regional Airport, 5.7 kilometers from the target PM2.5 monitor, reported haze twice and mist five times; visibility fell to two miles while median wind was four knots.
Evidence path
A cause is more convincing when the record connects three things: something happened, the air mass moved toward the region, and local instruments responded. Here is how much of that chain is documented for this event.
Source or mechanism
NWS Melbourne reported areas of reduced flight conditions near Melbourne caused by haze and smoke from smoldering brush fires on the catalog date.
View supporting source ↗Air-mass movement
The retained record does not yet show how air traveled from the proposed source to these metros. A trajectory replay or dated plume analysis belongs here.
Local response
EPA monitors recorded the event across 1 metro. The peak daily concentration is roughly 1.3 cigarette-equivalents at the outdoor daily rate.
Inspect the pollutant and weather signals ↓Event autopsy
Before, during, and after the episode: nearby pollutant monitors and surface-weather stations show what changed. This context tests the “Wildfire smoke” explanation; it does not assign the cause by itself.
Palm Bay-Melbourne-Titusville, FL
Monitor comparison window 2006-05-23 to 2006-05-29 · PM2.5 target: Melbourne
0% above nearby days
4 calm hours observed
Haze reported during 2 hours
About the same as surrounding days
21% lower than surrounding days
14 kt maximum · 4 of 23 observed hours calm
4 observed hours at or below 3 miles
67°F to 86°F
97% maximum
Source: U.S. EPA AirData daily observations and, where available, nearby ASOS/AWOS surface observations. Values are descriptive medians over the retained monitor set; missing measurements remain missing. Transport and source evidence remain separate layers because this instrument pattern does not assign a cause by itself.
Episode peak
-- cigarettes
The smoke map's scale, replayed over this event: the surface interpolates between covered metros' daily records, framed to the affected region. Hover for a reading, click a metro to pin it to the card. Days a monitor did not report draw nothing.
Views from the selected metro
Select a metro on the map to see nearby cameras. Where an operator archive reaches the event, drag the divider to compare two moments, adjust either date and time, or play the available event-day frames. Camera imagery is visual context, not an air-quality measurement or proof of smoke.
No useful public camera views are currently available within 80 km of this metro.
| Metro | Peak PM2.5 | Cigarettes, whole event | Peak day | All-time standing |
|---|---|---|---|---|
| Palm Bay-Melbourne-Titusville, FL | 28 µg/m³ | 1.3 | May 26, 2006 | #6 of its top days |
"Cigarettes, whole event" totals a metro's ranked event days at 22 µg/m³ per cigarette: what a person outdoors there breathed across the event, as the illustration. "All-time standing" is where this episode's days sit in each metro's ranked record (worst-area measure, since 1999). Full local context is on each metro's Air Records page.
Public evidence library
Each card states what a source supports—and what it does not. Official records, research, reporting, community observations, and transparent inferences remain visibly different kinds of evidence.
NOAA/NWS surface observations via Iowa Environmental Mesonet
Melbourne Regional Airport, 5.7 kilometers from the target PM2.5 monitor, reported haze twice and mist five times; visibility fell to two miles while median wind was four knots.
This source supports a possible mechanism or occurrence; it does not establish the cause by itself.
The airport and regulatory PM2.5 monitor are nearby but not co-located.
National Weather Service Melbourne via Iowa Environmental Mesonet
NWS Melbourne reported areas of reduced flight conditions near Melbourne caused by haze and smoke from smoldering brush fires on the catalog date.
An official source supports the attributed cause for the stated place and dates.
The discussion establishes the broad wildfire-smoke cause near Melbourne but does not name an individual fire or apportion the daily PM2.5 mass.
Associated Press via the Houston Chronicle
The Associated Press documented the same broad Brevard smoke problem but reported that the roughly 1,000-acre fire began Sunday, conflicting with the Friday-start account.
Context for the event; this item does not establish the attributed cause by itself.
This conflict concerns the identity and onset of the later named-size incident, not the NWS statement that smoke from smoldering brush fires affected Melbourne on May 26.
Local 6 News via Firehouse
Contemporaneous local reporting said lightning on Friday, May 26 sparked a Brevard-Orange brush fire that grew to about 1,000 acres and later closed roads in Melbourne and the surrounding corridor because of fire and smoke.
This source supports a possible mechanism or occurrence; it does not establish the cause by itself.
A contemporaneous Associated Press account instead says the large fire began Sunday, so this report cannot establish that the later 1,000-acre incident was the specific source of Friday's PM2.5 event.
Officially verified A directly applicable government determination or qualified scientific attribution product identifies this cause.
This episode was grouped from the monitor record by the catalog pipeline and given its cause from the evidence listed above. It has not been individually reviewed and signed off, so its boundaries, cause, and name may change as evidence accumulates. Grouping policy common_sense_root_cause_grouping.v2. The cause label reflects the assembled evidence above, not an IAQng detection formula. If it is wrong, tell us.