My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SITE INFORMATION AND CORRESPONDENCE
Environmental Health - Public
>
EHD Program Facility Records by Street Name
>
C
>
CHRISMAN
>
25700
>
2900 - Site Mitigation Program
>
PR0508450
>
SITE INFORMATION AND CORRESPONDENCE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/29/2019 11:58:23 AM
Creation date
5/29/2019 11:10:41 AM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2900 - Site Mitigation Program
File Section
SITE INFORMATION AND CORRESPONDENCE
RECORD_ID
PR0508450
PE
2960
FACILITY_ID
FA0008087
FACILITY_NAME
DDJC-TRACY
STREET_NUMBER
25700
STREET_NAME
CHRISMAN
STREET_TYPE
RD
City
TRACY
Zip
95376
APN
25207002
CURRENT_STATUS
01
SITE_LOCATION
25700 CHRISMAN RD
P_LOCATION
99
P_DISTRICT
005
QC Status
Approved
Scanner
SJGOV\wng
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.
/
2212
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
SPECIFIC COMMENTS <br /> 1. Section 1.3.3.4, Baseline Ecological Risk Assessment, Page 1-4: The summary <br /> indicates that the post-excavation soil samples collected from SWMUs 2 and 3 had DDX <br /> concentrations greater than the cleanup level established by the ROD. It is further <br /> indicated that the exposure and toxicity assumptions used to derive the ROD clean up <br /> levels were re-evaluated in the ESD. The text does not clearly indicate the reasons that <br /> the original clean up level was unable to be achieved during by the remedial action <br /> performed at the site. It has not been clearly justified as to why the original exposure and <br /> toxicity assumptions were considered appropriate at the time of the ROD, however, are <br /> now considered overly protective. Revise the report to clarify why the clean up levels <br /> could not be met. <br /> 2. Section 1.3.3.5, Baseline Ecological Risk Assessment, Page 1-4: It is indicated that the <br /> ROD assumed that the diet of the killdeer consisted of 100% earthworms, while <br /> conversely the ESD assumed 75% flying invertebrates for the re-evaluation. The rationale <br /> provided indicates that it is probably overly conservative to assume that the killdeer <br /> would consume only earthworms, since the bioaccumulation factor(BAF) associated with <br /> earthworms would be much greater than assumptions for other invertebrates. It is not <br /> evident that the specific assumptions for the killdeer are representative for other birds <br /> within this functional feeding group, that were intended to be represented by the killdeer. <br /> It is also not clear whether the killdeer was intended to represent other vermivore species <br /> (e.g., songbirds) which would be expected to consume a higher percentage of <br /> earthworms. Revise the document to clarify how the assumption is protective of all <br /> species within the functional feeding guild represented by the killdeer, and that other <br /> vermivore species are not expected to use the site. <br /> 3. Section 1.3.3.6, Baseline Ecological Risk Assessment, Page 1-4: It is stated, "the <br /> cleanup standard for DDX has been deleted from the remedy as documented in the ESD." <br /> It is further indicated that the re-calculated hazard quotients "are interpreted not to present <br /> a biologically significant risk." It is not clear whether the ESD is final and has been <br /> approved by regulatory agencies or whether the interpretation of risk was agreed by all <br /> risk managers at the site. Revise the document to provide the full citation for the ESD, <br /> and indicate whether the ESD has been finalized and approved, and clarify that biological <br /> significance was determined by consensus by all risk managers. <br /> 2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.