My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SITE INFORMATION AND CORRESPONDENCE
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
N
>
NAVY
>
0
>
2900 - Site Mitigation Program
>
PR0009171
>
SITE INFORMATION AND CORRESPONDENCE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/30/2020 11:50:21 AM
Creation date
3/30/2020 11:19:42 AM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2900 - Site Mitigation Program
File Section
SITE INFORMATION AND CORRESPONDENCE
RECORD_ID
PR0009171
PE
2960
FACILITY_ID
FA0004011
FACILITY_NAME
PORT OF STOCKTON-FUEL TERMINAL
STREET_NUMBER
0
STREET_NAME
NAVY
STREET_TYPE
DR
City
STOCKTON
Zip
95203
CURRENT_STATUS
01
SITE_LOCATION
NAVY DR
P_LOCATION
01
P_DISTRICT
001
QC Status
Approved
Scanner
SJGOV\sballwahn
Tags
EHD - Public
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
577
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Stantec Co ting Corporation vd�— ID <br /> 3017 Kilgore Road Suite 100 <br /> Rancho Cordova CA 95670 <br /> Tel:(916)861-0400 SEP u u 2008 <br /> Fax:(916)861-0430 <br /> Stantec PERPAIT%SERV10ES <br /> September 19, 2008 <br /> Mr. Brian Taylor <br /> California Regional Water Quality Control Board — Central Valley Region <br /> 11020 Sun Center Drive, #200 <br /> Rancho Cordova, California 95670 <br /> RE: Response to RWQCB July 30, 2008 Letter <br /> Stockton Terminals Technical Committee Facilities <br /> Port of Stockton <br /> Stockton, California <br /> Stantec Project No. 77OT.43673.014.0002 <br /> Dear Mr. Taylor: <br /> On behalf of the Stockton Terminals Technical Committee (STTC), Stantec Consulting Corporation <br /> (Stantec, formerly SECOR) submits this response to the July 30, 2008 Regional Water Quality <br /> Control Board (RWQCB) letter, related comments in the May 30, 2008 RWQCB letter, and an email <br /> from the RWQCB caseworker on September 10, 2008. In general the comments relate to formally <br /> establishing a list analytes for the evaluation monitoring program (EMP) and a recommendation to <br /> include tertiary butyl alcohol (TBA) in that list. This issue was also discussed during the June 5, <br /> 2008 meeting at the RWQCB attended by representatives of STTC and Stantec. The May 30, 2008 <br /> RWQCB letter had not been received by Stantec or STTC prior to the June 5, 2008 meeting. <br /> Specifically, the issue was first raised by the RWQCB in Comment Number 2 of the May 30, 2008 <br /> letter. <br /> • "The data trends show that TBA sustained concentration increases over three consecutive <br /> quarters, in excess of the only existing historical data point of <5.0 ug/L, from May 2006 to <br /> November 2006, and from August 2007 to February 2008. The February 2008 detection of <br /> 9.4 ug/L is the highest TBA concentration ever observed in AR/MW-18B. However, TBA is <br /> not among the list of trigger hydrocarbons in the ozone injection monitoring program. The <br /> recent detections of TBA in remedial observation well AR/MW-18B shows that the STTC <br /> needs to calculate an historical average for this constituent, establish a list of "trigger" <br /> hydrocarbons including the historical average for TBA, and monitor this constituent to <br /> ensure that off-site migration is not occurring." <br /> In the July 30, 2008 letter, Page 2 Paragraph 2, the RWQCB stated in part regarding discussions <br /> held in the June 5th, meeting: <br /> • ...However, the document does not list the specific hydrocarbons that trigger application <br /> of the contingency plan. On behalf of ARCO, Mr. Haeck, said that he would be in touch <br /> I:\STTC-Stockton\Reports\Resp to RWQCB July 30,2008\Response to RWQCB July 30,2008 Letter final.doc <br />
The URL can be used to link to this page
Your browser does not support the video tag.