My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WORK PLANS_CASE 1
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
W
>
WELTY
>
35275
>
2900 - Site Mitigation Program
>
PR0508042
>
WORK PLANS_CASE 1
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/19/2021 4:33:02 PM
Creation date
5/19/2021 4:04:23 PM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2900 - Site Mitigation Program
File Section
WORK PLANS
FileName_PostFix
CASE 1
RECORD_ID
PR0508042
PE
2960
FACILITY_ID
FA0005316
FACILITY_NAME
U S CAN COMPANY
STREET_NUMBER
35275
Direction
S
STREET_NAME
WELTY
STREET_TYPE
RD
City
VERNALIS
Zip
95385
APN
25518009
CURRENT_STATUS
01
SITE_LOCATION
35275 S WELTY RD
P_LOCATION
99
P_DISTRICT
005
QC Status
Approved
Scanner
SJGOV\dsedra
Tags
EHD - Public
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
103
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
Scott Mansholt - 2 - 4 December 2003 <br /> ChevronTexaco <br /> US Can/Welty Road <br /> Additionally, volatile organic compounds (VOCs), including among others, trichloroethylene (TCE) were <br /> detected in soil near a former drainpipe at the northeastern side of an existing site building. According to <br /> the reports, the presence of VOCs in soil and groundwater are likely due to a former can manufacturer at <br /> the site. <br /> Similarly, concentrations of benzene (1.5 pg/L) and total petroleum hydrocarbons as gasoline (TPH-g, <br /> 110 µg/L) reported in groundwater from an off-site boring(GMX-6), north of the site, may be <br /> attributable to a former retail gasoline station located at the northeast intersection of State Highway 33 <br /> and Welty Road. <br /> We have the following comments: <br /> 1) The analytical results indicate that the area of petroleum hydrocarbons in soils on-site is generally <br /> limited in extent and has been delineated, occurring within two areas along the northeastern <br /> property boundary. <br /> 2) Based on the reports' findings, it appears that the vertical extent of petroleum-impacted soil on-site <br /> has been delineated, defined by boring GMX-8, where TPH as crude oil (TPH-c) was detected at 55 <br /> feet but not at 89 feet. <br /> 3) Impacted soil has not been delineated off-site, (northeast), where petroleum-impacted soil was <br /> observed from 45-50 feet in boring GMX-10. Additional borings are needed off-site to obtain soil <br /> samples for analysis to evaluate the lateral extent of TPH-impacted soil. <br /> 4) The lateral extent of affected groundwater on-site has generally been delineated, but has not been <br /> defined downgradient. Additional downgradient borings are needed to define the lateral extent of <br /> TPH in groundwater. <br /> Regional Board staff agrees with your consultants observations that the vertical extent of TPH-d <br /> concentrations in groundwater exceeding the Water Quality Objective (>100pg/L) generally corresponds <br /> to the vertical extent of petroleum-impacted soil. However, additional soil and groundwater sampling <br /> and analysis are needed, and additional monitoring wells need to be installed to delineate the extent of <br /> groundwater impact. Once TPH-impacted groundwater is defined and additional monitoring wells are <br /> installed, a sampling and monitoring plan needs to be implemented. <br /> Borings completed during the additional investigation should incorporate areas that require further <br /> delineation. In conjunction, a site evaluation needs to include soil sampling that is consistent with the <br /> depths and analytical levels required for a human health risk assessment. Additionally, Regional Board <br /> staff concurs that a well survey needs to be conducted to identify possible receptors in the area. <br />
The URL can be used to link to this page
Your browser does not support the video tag.