June 7, 2017 Technical Track Work Group Meeting

The next meeting of the SRRTTF Task Force and Technical Track Work group is:

Date: Wednesday June 7, 2017
Time: 10:00 a.m. to 12:00 p.m.

Location: Washington Department of Ecology
N. 4601 Monroe St.
Spokane, WA 99205
Click here for a map.

Audio Call In Number: 509-335-2277
Conference ID: 2740350

Meeting Materials:
 TTWG agn 06-07-17
–  TCP process flowchart
 SRRTTF PCB Database Tsk1&2 TechMemo DRAFT

Compiled TCP Information

On August 3, 2016, the Technical Track Work group discussed data from the background wells on the Kaiser site. LimnoTech has determined that there may be evidence from a comparison of background well data and that from Kaiser site, along with synoptic river data, of an unknown groundwater source up-gradient of this site, but there is more information needed. Coordinating with the Toxics Cleanup Program in the future may help in the task. However, given the legal restrictions that MTCA/TCP has to work within (for existing and closed cleanup sites, and identification of new sites) this may be a difficult task.

For now, we have compiled list of documents provided to the Task Force regarding Toxics Cleanup Program (TCP) that may be of use in charting a path forward to identify this groundwater source, and how TCP can help to complement this work. If you have additional information that would be useful, please send them to Kara Whitman (kmwhitman@wsu.edu) for posting on this page. Note: these are also posted on the Department of Ecology Publications Page.


– Approach for TCP sites – (From Adriane Borgias (Feb 2016)
– PCB TCP Sites 4-17-15 (TCP site presentation April 2015)
– Appendix A-TCP Sites (June 2015)
– Appendix B-Spokane Wells (June 2015)
– Standard Operating Procedure for Purging and Sampling Monitoring Wells plus Guidance on Collecting Samples for Volatiles and other Organic Compounds 
– Tech Memo – PCBs in Spokane Valley GW – Marti – 9-16-15 FINAL  (September 2015)

Ecology Resources: Searchable map database of TCP Sites

TCP memos regarding analytical data: Information regarding policy decision by TCP to use 1668