My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WORK PLANS_FILE 2
Environmental Health - Public
>
EHD Program Facility Records by Street Name
>
N
>
NEWTON
>
3931
>
2900 - Site Mitigation Program
>
PR0540573
>
WORK PLANS_FILE 2
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/8/2020 4:18:20 PM
Creation date
4/8/2020 4:05:44 PM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2900 - Site Mitigation Program
File Section
WORK PLANS
FileName_PostFix
FILE 2
RECORD_ID
PR0540573
PE
2960
FACILITY_ID
FA0023207
FACILITY_NAME
GILLIES TRUCKING INC
STREET_NUMBER
3931
STREET_NAME
NEWTON
STREET_TYPE
RD
City
STOCKTON
Zip
95205
APN
13207017
CURRENT_STATUS
01
SITE_LOCATION
3931 NEWTON RD
P_LOCATION
01
QC Status
Approved
Scanner
SJGOV\sballwahn
Tags
EHD - Public
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
38
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
WORKPLAN FOR DELINEATION D <br /> OF GROUNDWATER CONTAMINATION <br /> IN THE RIVERBANK AQUIFER <br /> Gillies Trucking Co. <br /> 3931 Newton Road <br /> Stockton, California <br /> 1.0 INTRODUCTION <br /> In a letter dated June 17, 2004, San Joaquin County Environmental Health Department <br /> (EHD)requested a work plan to complete the vertical and lateral delineation of <br /> groundwater contamination at 3931 Newton Road in Stockton, California. This request. <br /> derived from Staff review of the Fourth Quarter 2004 Report, which was prepared by <br /> Upgradient Environmental and submitted in December 2003. EHD concurred that the <br /> geologic model for the Modesto Formation and upper two sand bodies of the Riverbank <br /> Formation is consistent with the site-generated data, but correctly pointed out that there is <br /> insufficient data to fully evaluate the third Riverbank sand. Only two borings have been <br /> drilled deep enough to penetrate this unit, so neither its geometry nor its groundwater <br /> chemistry is known. EHD further observed that questions remain regarding the full extent <br /> of groundwater contamination within both the first and second Riverbank sand bodies, <br /> and that due to poor hydrogeologic communication between these units, the . <br /> potentiometric maps that have been generated in the past from water-depth measurements <br /> are not definitive. The purpose of this work plan is to remedy these shortcomings in the <br /> database by drilling additional wells in areas where data are currently lacking. <br /> 2.0 THIRD RIVERBANK AQUIFER <br /> As noted above, three hydrologically separate sand bodies have been identified by past <br /> drilling below the Modesto Formation at the site, and the deepest of these is the least <br /> well-known. It was penetrated in boring GT-11'in 1999,and in boring CPT-1 in 2003, at <br /> a depth of approximately 110 feet. This sand body did not appear to be contaminated by <br /> diesel fuel in GT-11, but diesel-range hydrocarbons were detected in a groundwater <br /> sample from this sand body in CPT-1, implying that there has been some degree of . <br /> impact to this aquifer. It appears to be less than 10 feet thick in CPT-1, but it is.clearly <br /> more than10 feet thick nearby in GT-11; although its base was not reached. In other <br /> borings,than, <br /> sand bodies 1 and 2 range from less than 5 to more than 20 feet thick, <br /> so it is reasonable to assume that the thickness of sand body 3 also exceeds 20 feet, at <br /> least locally. Inasmuch as groundwater flow and contaminant migration rates often tend <br /> to be greatest along the thickness axis of fluvial sand bodies, additional drill holes <br /> through the 3rd Riverbank sand body are needed to identify and map the axis and <br /> determine the lateral extent of diesel contamination. <br />
The URL can be used to link to this page
Your browser does not support the video tag.