My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
COMPLIANCE INFO
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
W
>
WASHINGTON
>
333
>
2900 - Site Mitigation Program
>
PR0545445
>
COMPLIANCE INFO
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/3/2020 4:40:31 PM
Creation date
3/3/2020 4:20:39 PM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2900 - Site Mitigation Program
File Section
COMPLIANCE INFO
RECORD_ID
PR0545445
PE
2961
FACILITY_ID
FA0025798
FACILITY_NAME
CALIFORNIA ARMY NATIONAL GUARD
STREET_NUMBER
333
Direction
N
STREET_NAME
WASHINGTON
STREET_TYPE
ST
City
LODI
Zip
95240
APN
04123045
CURRENT_STATUS
02
SITE_LOCATION
333 N WASHINGTON ST
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.
/
699
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
Diesel Impacted Soil Removal Report May 2010 <br /> California Army National Guard Armory <br /> Lodi, CA <br /> OTIE also evaluated the known depth to first groundwater in the vicinity of the site to determine how <br /> much of a potential threat to ground water the single sample exceedance of the Table A ESL might <br /> represent. Data available through the CVRWQCB's Geotracker database indicated that depth to first <br /> groundwater at two locations within one-half mile of the site in Lodi(40 North Main Street and 221 West <br /> Church Street)ranged from approximately 54 to 67 feet bgs during the November-December 2009 <br /> timeframe.Although depth to groundwater data are not available specifically for this site,the data <br /> available for these two sites appear to accurately reflect the significant depth to first groundwater typical <br /> of the area. In recognition that the ESLs for TPH-D in soil were developed based on leaching potential by <br /> the SFRWQCB,where depth to first groundwater is typically considerably shallower than noted above for <br /> the Central Valley in general, and for the Lodi area specifically, it follows that the ESL for soil in the Bay <br /> Area may be significantly more stringent than is appropriate for soil from a similar depth in this portion of <br /> the Central Valley. <br /> Another consideration is the proximity of the two floor samples (LODI-SO-10 and LODI-SO-11)to each <br /> other(approximately 18 inches). This proximity was,by design, a deliberate spacing to bias confirmation <br /> soil sampling toward the area of the highest pre-characterization sample measurement. Because the two <br /> samples differed significantly(2.2 versus 140 mg/kg,respectively),with the former being generally <br /> consistent with the remainder of the confirmation samples, it can be argued that the 140 mg/kg result is an <br /> outlier and not representative of overall soil conditions following excavation activities. <br /> A final consideration in evaluation of the single elevated floor sample is consideration of the floor sample <br /> with respect to the initial soil conditions found in the pre-characterization soil sampling. The single floor <br /> sample(LODI-SO-11) at 140 mg/kg was collected approximately 30 inches below the initial pre- <br /> characterization sample which had 13,000 mg/kg TPH-D at a depth of approximately 6 inches. Given that <br /> the fuel spill reportedly caused a release of TPH-D at the surface of the soil,these data indicate that there <br /> has been a vertical attenuation of TPH-D by nearly two orders of magnitude across 30 inches of soil. <br /> Roughly speaking, it is reasonable to assume that the continued attenuation of TPH-D will occur such that <br /> the concentration of TPH-D will be reduced to less than 100 mg/kg within the next few inches of soil. <br />
The URL can be used to link to this page
Your browser does not support the video tag.