My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
COMPLIANCE INFO
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
C
>
CORRAL HOLLOW
>
15999
>
2200 - Hazardous Waste Program
>
PR0514115
>
COMPLIANCE INFO
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/6/2019 3:47:36 PM
Creation date
6/6/2019 3:39:32 PM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2200 - Hazardous Waste Program
File Section
COMPLIANCE INFO
RECORD_ID
PR0514115
PE
2249
FACILITY_ID
FA0003934
FACILITY_NAME
Lawrence Livermore National Lab - Site 300
STREET_NUMBER
15999
Direction
W
STREET_NAME
CORRAL HOLLOW
STREET_TYPE
RD
City
TRACY
Zip
95376
CURRENT_STATUS
01
SITE_LOCATION
15999 W CORRAL HOLLOW RD
P_LOCATION
99
P_DISTRICT
005
QC Status
Approved
Scanner
FRuiz
Tags
EHD - Public
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
112
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
I-4.2.3 Description of the Waste Left in Place <br /> The wastes treated at the former B-829 Facility were hazardous primarily because of their <br /> reactivity. The four principal explosives compounds that were treated at the B-829 Facility were <br /> HMX(cyclotetramethylene tetranitramine), RDX(cyclotrimethylene trinitramine),TATB <br /> (triamino-trinitrobenzene)and TNT(2,4,6-trinitrotoluene). Explosives and explosives- <br /> contaminated wastes were generated from explosives formulation,the manufacturing process, <br /> and detonation testing on the firing tables. The wastes included pieces of undetonated <br /> explosives, miscellaneous burnable materials that are judged to be contaminated with explosives, <br /> and fines collected in clarifiers from explosives materials machining. <br /> After burning,the waste residue consisted of non-reactive ash and potentially unreacted <br /> explosive hazardous waste. Small amounts of solvent,plastic and metal may also remain in the <br /> pits. <br /> I4.3 RESPONSIBILITIES <br /> This Contingency Plan utilizes the Incident Command System to coordinate activities of <br /> personnel during an emergency at Site 300. Section 4 of this Plan describes the individual <br /> responsibilities during an emergency at Site 300. This Section presents the responsibilities of B- <br /> 829 support personnel during an emergency. <br /> For incidental releases and minor, first-aid injuries at the B-829,the B-829 Facility Manager or <br /> designated alternate, manages the incident.These individuals and their phone numbers are listed <br /> in Table I-4-3. If additional support is needed during a minor incident,the Facility <br /> Representative will contact the Environment, Safety, and Health(ES&H) Support Team <br /> members, if necessary. <br /> For most other non-security emergencies, the first or senior Fire Department Officer dispatched <br /> to,or present at the scene becomes the IC until relieved by a Chief Officer. <br /> Table I4-3 List of B-829 Emergency Contacts <br /> Primary <br /> Contact Alternate <br /> Name Valerie Dibley,Facility Manager Jim Woollett,Environmental <br /> Oversight and Special Projects <br /> Manager <br /> Office (925)422-9777 (925)424-3203 <br /> Pager# On site: 37777,60288 On site: 37777, 50480 <br /> Off site:423-7705, 60288 Off site: 423-7705,50480 <br /> I-4.4 EMERGENCY CONTROL PROCEDURES <br /> Response to an emergency at a Site 300 Facility is designed to be appropriate to the incident. <br /> The transition from one level of emergency to another must be automatic and keyed to well- <br /> defined criteria. The Fire Department emergency action levels are defined according to the event <br /> and the potential hazard to onsite personnel and offsite persons. <br /> LLNL Site 300 Contingency Plan I-4-5 January 2019 <br /> Appendix I-4,Building 829 <br />
The URL can be used to link to this page
Your browser does not support the video tag.