My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SITE INFORMATION AND CORRESPONDENCE
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
W
>
WEBER
>
2025
>
2900 - Site Mitigation Program
>
PR0506438
>
SITE INFORMATION AND CORRESPONDENCE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/31/2019 11:02:14 AM
Creation date
10/31/2019 10:42:40 AM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2900 - Site Mitigation Program
File Section
SITE INFORMATION AND CORRESPONDENCE
RECORD_ID
PR0506438
PE
2960
FACILITY_ID
FA0007424
FACILITY_NAME
TEICHERT INDUSTRIAL LAND
STREET_NUMBER
2025
Direction
E
STREET_NAME
WEBER
STREET_TYPE
AVE
City
STOCKTON
Zip
95202
CURRENT_STATUS
01
SITE_LOCATION
2025 E WEBER AVE
P_LOCATION
01
P_DISTRICT
001
QC Status
Approved
Scanner
SJGOV\wng
Tags
EHD - Public
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
170
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
y <br /> *AW <br /> STATE OF CALIFORNIA GEORGE DEUKMEJIAN,Governor <br /> CALIFORNIA REGIONAL WATER QUALITY CONTROL BOARD— <br /> CENTRAL VALLEY REGION ..�; <br /> 3443 ROUTIER ROAD <br /> SACRAMENTO,CA 95827-3098 <br /> 12 July 1989 <br /> Ms. Virginia Cahill V t <br /> McDonough, Holland, and Allen <br /> 555 Capitol Mall , Suite 950 <br /> Sacramento, CA 95814 <br /> Proposed Monitoring Wells, Teichert Land Company, Stockton, San Joaquin County <br /> We have reviewed your 21 June 1989 letter regarding the above subject. We <br /> appreciate Teichert's initiative to investigate possible pollution at London <br /> Produce and we agree that monitoring wells are appropriate. However, we have <br /> a number of questions and/or comments regarding the proposed work plan <br /> submitted by LBME Corporation, dated 17 August 1988, and enclosed with your <br /> 21 June letter. Our comments are as follows: <br /> 1. Dual completion monitoring wells are proposed; the two screened intervals <br /> being separated by five feet. It is unclear why dual completion wells are <br /> proposed. Besides being difficult to construct and effectively sample, <br /> the proposed minimal separation of the screened intervals without regard <br /> to lithology will probably not result in monitoring of separate, discreet <br /> zones. Monitoring of the deeper portions of the aquifer should be <br /> accomplished with separate monitoring wells screened across the <br /> appropriate permeable zones. <br /> 2. The work plan proposes to use sampling data from existing monitoring wells <br /> 4 and 5 as "reference" (background) values. Have water level data been <br /> collected which establish that these wells are upgradient (or sufficiently <br /> cross-gradient) to be used as background indicators? For that matter, is <br /> the placement of proposed monitoring wells 7 and 8 based on water level <br /> data to ensure they will be downgradient of the London Produce facility? <br /> In Practice, water laurels from all monitoring wellc should be collected <br /> during each sampling event and at regular time intervals, then <br /> individually plotted on contour maps. The work plan should include this <br /> work. <br /> 3. The work plan states that monitoring well development and purge water will <br /> be discharged to the storm sewer "unless there is some indication of the <br /> presence of hydrocarbons or other hazardous material". It is not clear, <br /> how, such a determination will be made without sampling. Additionally, if <br /> London Produce has polluted the groundwater, this water may not be <br /> appropriate for discharge to the storm sewer even though it is not <br /> "hazardous" . It would probably be best to contain all waters until <br /> properly tested, then dispose of them accordingly. <br />
The URL can be used to link to this page
Your browser does not support the video tag.