Fire Emissions Tracking System Development & Implementation

1. Fire Emissions Tracking System Development & Implementation Workshop on Regional Emissions & Air Quality Modeling Studies Biogenics, Ammonia, Dust, and Fire Emissions Section 1p MDT July 29, 2008 Denver, Colorado

2. For the next 20 minutes or so… • Description of FETS current functions. • Introduction of future ideas for the FETS and fire emissions data. www.wrapfets.org

3. FETS Intro The FETS is Intended for regional coordination of fire activity and storage/retrieval of fire activity and emissions data. A “commodity based” system requiring only access to the Internet to upload, view, and report data. Housed at the Cooperative Institute for Research in the Atmosphere (CIRA) and is managed by the WRAP. 1/7/2020 3

4. FETS Intro The FETS can accept data pertaining to any fire type in any geographic area. Fire activity and emissions are always associated with a specific fire type. Performs other “WRAP-specific” functions Emissions averted with use of Emission Reduction Techniques Tracking of Annual Emission Goals “New user” development tasks are limited to Establishing the handshake to submit data, Training on the use of the FETS, Customizing data fields, queries, and reporting to meet user-specific needs. 1/7/2020 4

5. SQL Server FETS Users SMOKE files FETS Design Batch Files Raw Data EI Reports Manual Entry Annual Emission Goals Internet Tools FETS Website WIMS/ RAWS NIFC ICS-209 TSS FTP Site Data Entry Screens View/ Edit Screens Map Tool Reporting Services Data QC Data QC FETS Technical Node Emissions Calculation GIS Services

6. Current Functions of the FETS • Fire Activity data acquisition and status of data reported. • Instant emissions (PM2.5) estimate. • Display of current wildland fire, planned burns, and recent MODIS fire detects on Regional Coordination Map. • Behind-the-scenes fire science.

7. Current Functions of the FETS • Basic fire activity and emissions reporting functions. • Updated Smoke Management Program contacts list. • Documentation of methods implemented in the FETS. VERY BRIEF ON-LINE TOUR OF FETS

8. CriticalFunctionsof the FETS • Storage Device for Fire Activity Data • Real-time Information Tool for SMPs • Cost Effective Data Retrieval Tool • Integrates Fire Data into Regional Haze SIPs COLLECT AND STORE Output Results Planned emissions/regional coordination: very frequent use Level 0 CURRENT QC’d data and periodic reporting Level 1 Improve quality of emissions estimates Refined emissions for input to modeling Levels 2 & 3 FUTURE

9. FETS Data Level Definitions (Draft)

10. FETS Development • Future • Implement Level 2 • Draft methods for and implement Level 3 • Continued coordination with other fire-related systems. • Provide data for modeling analyses. • Done • Reported data acquisition & QC (low hanging fruit) • Regional Coordination functions • Level 1 emissions inventory data • Rudimentary EI queries and reporting • Going-on • User training (webinars) • Data acquisition • Info gathering on satellite detect • Coordinate with other fire-tracking and emissions systems • Drafting methods for Level 2 refinements • Integrate FETS data with TSS

11. Discussion/Questions

12. Level 1 Data (Current) • Emission Factors • Look-up table (AP-42/WRAP Ph. II) in SQL database. • Fuels Information (one loading per event-day) • User-provided • FCCS fuel category • GIS FCCS tool • Uniform emission calculations • Fire Activity Data (accomplished acres/day per event) • From SMP • Accomplishment Reports • From Federal ICS209 • Day[N] – Day[N-1] • Assume 100% of reported acres burned.

13. Level 1 Data • A large number of small wildland fires go unreported. • Reporting is highly variable across states and Tribes with SMPs • Spatial Coverage • Federal Lands for WF and WFU • >100 acres timber • >300 acres grass/brush • Active Smoke Management Programs • Prescribed (Rx) • Agricultural Burning (Ag) • Non-Federal Rangeland (NFR)

14. Level 1 Data • Chemical Speciation • Standard suite of pollutants from Phase II Fire Emissions Inventory • Readily available in the literature • Simple mathematical relationships • To date, PM2.5 is the pollutant most frequently used for Level 1.

15. Level 2 Data (future) • Primary Goals for Level 2 data: • Fill “gaps” in the Level 1 fire data for western North America (SW Canada, N Mexico, US W of 100th meridian of longitude) • Spatial • Temporal • Fire types • Publish level 2 data 6-8 weeks after the end of quarter.

16. Level 2 Data • Fire Activity Data • Fill in spatially and temporally for all fire types. • Use detects from one or more satellite products. • Use land use and land cover data to classify unreported fire detects. • QA and improve daily spatial location of each Level 1 event. • Adopt method to refine estimate of daily acres burned. • Improve completeness of the number of daily fire events across the region.

17. Level 2 Data • Emission Factors & Emissions • Continue to apply AP-42/Phase II emission factors. • Maintain consistency with historical and Level 1 data • Emissions based on CONSUME currently available in FETS

18. Level 2 Data • Fuels Information – reported events • User-provided • FCCS fuel category • GIS FCCS tool • CONSIDER: • Weighted fuel loading for event-day. • Using unique fuel loading for each fire detect. • Fuels Information – “unknown events” • Develop methods for a “first principals” estimate of fuel loading, emissions, and fire type assignment.

19. Level 2 Data • Spatial Coverage • Capture SW Canada and N Mexico. • Capture small wildland fires on Federal Lands. • Capture and categorize planned fires to lessen the effect of variations in SMPs. • Chemical Speciation • Same as Level 1 Document changes in fire emissions by county and 36km grid cell

20. Level 3 Data (future) • Primary Goals for Level 3 data: • Free-standing replacement for SMOKE emissions modeling for fire: • 3-dimensional hourly emissions • Enhanced chemical speciation • Gridded emission inventory • Create calendar-year product annually by March 31st of the next year.

21. Level 3 Data • Fire Activity, Fuels Information, Spatial Coverage • Consider effort needed vs. data quality improvement for any approach to improve Level 2 data. • Likely maintain Level 2 activity data quality and completeness. • Emission Factors and Emissions • FETS would report QA and analysis steps to prepare and report Level 3 data. • FETS would disclose method for estimating speciated fire emissions. • Peer-reviewed publication required.

22. Level 3 Data • Chemical Composition of Fire Emissions • Develop chemical speciation specific to fuel loading and fuel characteristics for each fire event.

23. Data Acquisition • Wildfire • FTP-get ICS-209 data set from federal site. Pulls previous day’s burns. • All other fire types • FTP-get from Agency sites (OR, WA, NM) • FTP-put to FETS site from Smoke Management Programs (AZ) • Automated direct acquisition from SMP databases (MT,ID, Nez Perce) • Manual data entry at FETS Automated Data Acquisition 0200 & 0700 MDT 0700 – 1900 MDT 0200 MDT

24. Recent Data Acquisition Developments Data stream active Data stream pending Data stream known, not initiated

25. FUEL AND EMISSIONS Fuel Consumption User Provided GIS overlay with FCCS 1.1 (lower 48) or CFFDRS (Alaska) CFFDRS FCCS 1.1 Emission Estimates User Provided WRAP Phase II (simple) [always used for Regional Coordination] CONSUME 3.0 [includes GIS lookup of daily fuel moisture and precipitation] 1k-hr Fuel Moisture Interpolated surface Integration of WRAP Fire Policy Elements Natural/Anthropogenic Emission Reduction Techniques