My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SITE INFORMATION AND CORRESPONDENCE
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
H
>
HARDING
>
45
>
3500 - Local Oversight Program
>
PR0545259
>
SITE INFORMATION AND CORRESPONDENCE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/31/2020 6:04:48 PM
Creation date
1/31/2020 2:30:07 PM
Metadata
Fields
Template:
EHD - Public
ProgramCode
3500 - Local Oversight Program
File Section
SITE INFORMATION AND CORRESPONDENCE
RECORD_ID
PR0545259
PE
3528
FACILITY_ID
FA0004966
FACILITY_NAME
CHEVRON USA (INACT)
STREET_NUMBER
45
Direction
E
STREET_NAME
HARDING
STREET_TYPE
WAY
City
STOCKTON
Zip
95204
APN
12707037
CURRENT_STATUS
02
SITE_LOCATION
45 E HARDING WAY
P_LOCATION
01
P_DISTRICT
002
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.
/
485
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
I aaoro ca[ 6370 CHEVRON U.S.A. <br /> 2002/006 <br /> 1 <br /> Chevron <br /> Chevron Products Company <br /> April 9, 1997 6001 Bollinger Canyon Road <br /> Building l <br /> San Ramon,CA 94583 <br /> P.O.Box 6004 j <br /> Ms.Mary Ways San Ramon.CA 94583.0904 <br /> San Joaquin County Environmental Health <br /> P.O.Boa 388 Markning—Sales Wast <br /> Stockton,CA 95201-0388 Phone 510 842-950C <br /> I <br /> Re: Former Chevron Station#9-1918.45 East Harding Way,Stockton CA <br /> Attached uniform hazardous waste manifests(Nos.87415042,92652999) <br /> Attached informational letter(Oil Equipment Service.7/3/95) <br /> Dcar Ms,Meays: <br /> Per your request and to complete file records for case closure,Chevron offers the following information <br /> regarding the disposition of underground storage tanks(UST's),groundwater monitoring purgewater,and <br /> soil stockpiles generated during excavation activities at the subject site. <br /> UST's <br /> According to all known information,there were ten UST's discovered and removed from the subject site. <br /> the following list describes each UST.the date of discovery,and/or the date of removal: <br /> i <br /> UST/contents Discovered Removed <br /> 3- 10,000 gal, (gasoline) 2/7/88 2/7/88 <br /> 1- 1,000 gal. (used oil) 217/88 2/7/88 <br /> 1-550 gal. (used oil?) 11/7.11/88 12/7/88 <br /> 1 -3,000 gal. (gasoline?) 11/15/88 12/?/88 <br /> 1 -4,000 gat.(gasolitte?) 11/15/88 12/7/88 <br /> t -1,000 gal. (gasoline?) 12/13-15/93 3/18/94 <br /> 2-70-80 gal. (hydr. oil) 3/7/97 3/10/97 <br /> The attached uniform hazardous waste manifests provide documentation for the handling and destination <br /> of four of the ten UST's described above:They are the 3 -10,000 gallon UST's removed on 2/7188 and the <br /> 1 - 1,000 gallon UST removed on 3/18/94.No other documentation was found to describe the <br /> handling/destination of the remaining UST's discovered onsite. <br /> Pumewater <br /> There was no formal documentation found relating to the handling or destination of purgewater generated <br /> at the subject site since 11/88. The earliest and most relevant documentation on file are the monitoring <br /> consultants statements on their reports that the purgewater was transported to Chevron's refinery in <br /> Richmond. California.The earliest documentation of such is a report dated December 21, 1992 by <br /> Chevron's consultant Groundwater Technology,Iuc.All subsequent monitoring reports contained similar <br /> statements.To my knowledge,Chevron has always handled its purgewater as non-hazardotts. As such I <br /> would guess that in the absence of such documentation,purgewater generated at the subject site prior to <br /> October, 1992 was handled the same way and was transported to the Richmond refinery. <br />
The URL can be used to link to this page
Your browser does not support the video tag.