USER'S GUIDE TO FEDERAL AGCIDENTAL RELEASE
DATABASES
-------
-------
ACKNOWLEDGEMENTS
The U.S. Environmental Protection Agency (EPA) developed this User's Guide with the assistance
of the other fifteen member agencies of the National Response Team (NRT). For their contribution of
resources and wise counsel, we wish to acknowledge and thank the members of the NRT, the members of
the Presidential Review Ad Hoc Committee, and especially the members of the NRT Presidential Review
Accident Data Workgroup who provided insights and valuable suggestions. We also wish to. thank various
individuals who contributed to the research and review of this guide. ,
National Response Team Representatives
Jim Makris, Environmental Protection Agency, Chairman
Capt. Michael Donohoe, U.S. Coast Guard, Vice Chairman .
Charles Adkins, Occupational Safety and Health Administration, Department of Labor
Steven Baer, Department of Justice - -
Bob Blumberg, Department of State
Ken Brockman, Nuclear Regulatory Commission
Ed Clawspn, Department of Treasury
Dr. Georgi Jones, Agency for Toxic Substances Disease Registry, Department of Health and Human
Services . .. " : """.
D. Anne Martin, Federal Emergency Management Agency
Vince McClelland, Department of Energy
Capt. Raymond McCofd, Department of Defense ...
Bill Opfer, Department of Agriculture
Alan I. Roberts, Department of Transportation
Dr. Jean Snider, National Oceanic and Atmospheric Administration, Department of Commerce
Gordon Tassi, General Services Administration
Dr. Willie Taylor, Department of the Interior
-------
National Response Team Presidential Review Ad Hoc Committee
David Speights, Environmental Protection Agency, Chairman
Alan Carpien, Environmental Protection Agency
Maria Eisemann, Environmental Protection Agency
James Fairobent, Department of Energy
Lt. Cdr. Paul Gugg, U.S. Coast Guard
Paul Hankins, Department of Defense
Judy Hecht, Environmental Protection Agency
John Hess, Department of Transportation
Henry Hudson, Environmental Protection Agency
Ken Hunt, Occupational Safety and Health Administration, Department of Labor
Art Johnson, Environmental Protection Agency
David Knorowski, Department of Health and Human Services
Bobbie Lively-Diebold, Environmental Protection Agency
Frank McAlister, Environmental Protection Agency
Andy O'Palko, Environmental Protection Agency
James O'Steen, Department of Transportation
Bill Opfer, Department of Agriculture
Nancy Pate, Environmental Protection Agency
Chris Prins, Environmental Protection Agency
Lisa Ratcliff, Environmental Protection Agency
Fred Talcott, Environmental Protection Agency
Gordon Tassi, General Services Administration
James Thomas, Federal Emergency Management Agency
Jan Thorman, Department of Interior
Paul Tobin, Environmental Protection Agency
National Response Team-Presidential Review Accident Data Workgroup
David Speights, Environmental Protection Agency, Workgroup Chair
Cdr. Ed Blackadar, U.S. Coast Guard
David Chung, Environmental Protection Agency
Kevin Coburn, Department of Transportation
Joe DuBois, Occupational Safety and Health Administration
Schatzi Fitz-James, Environmental Protection Agency
Ken Hunt, Occupational Safety and Health Administration
Tyrone Pettiford, U.S. Coast Guard
Dana Stalcup, Environmental Protection Agency
George Sundstrom, Department of Agriculture
Fred Talcott, Environmentai:Protection Agency
11
-------
Research Contributors
Judy Chapman, Marasco Newton Group Ltd.
Richard Douglas, ICF Incorporated
Ron Duych, Marasco Newton Group Ltd.
Milton Freifeld, Environmental Protection Agency
Cdr. Rich Gaudiosi, U.S. Coast Guard
Lt. Cdr. Rhae Giacoma, U.S. Coast Guard
David Goldbloom-Helzner, ICF Incorporated
Irene Hall, Agency for Toxic Substances Disease Registry
Mary Hillstrom, Marasco Newton Group Ltd.
Steve Kerr, Marasco Newton Group Ltd.
Roger Little, Department of Transportation
George Montserrat, U.S. Coast Guard '.
Matthew Naud, ICF Incorporated
Monica Spaim, ICF Incorporated
Marie Xeras, ICF Incorporated
m
-------
-------
TABLE OF CONTENTS
./ Page
Acronyms ' _ . ;
I. Introduction ..;..: .:..'. .\ .............. 1
Background . . . . . 1
The Database Compatibility Problem 1
A Helpful Step: Today's User's Guide .............. ... ...,.' ; 2
II. Databases Featured and Search Strategies . ..'. 3
Databases Featured ....... ......; ................. 3
Search Strategies .......:......,.......... .5
III. Database Profiles . . . .................................. 11
Incident, Reporting Information System , . . / '.--. . . 13
Emergency Response Notification System f . .;. ..... . . . . . 17
Accidental Release Information Program . . . ...;.... 21
Hazardous Materials Incident Reporting System . : 25
Hazardous Liquid Pipeline Accident Database 29
Integrated Management Information System . 33
Hazardous Substances Emergency Events Surveillance . . .' . . . 35
Short Descriptions of Additional Federal Release Databases. ........................ .37
IV. Quick Cross Reference to Databases,. 41
Quick Reference on Scope of Databases '..'.'. '. ~. . 42
Comparison of Data Elements in Databases . . . ..,..:..... . . 44
Database Information Contained in Each Data Element .:....,... 47
Top Five Chemicals or Substances (non-petroleum) in Databases . . 55
V. Looking to the Future - Linking Databases .'..... ... . 57
Value of Linking Database .'....-....:' . . .-. . 57
Linking Databases . ; . . 58
Basis of Linkage - Common Data Elements ..' 59
Efforts to Support Database Linkage 60
Appendix A - Examples of Completed Accident Report Forms for Federal Databases
Appendix B - Datafield Dictionaries .
-------
-------
ACRONYMS
ARIP
ATSDR
CAA
CDC
CERCLA
CFR
CWA
DOD
DOS
DOT
EHS
EPA'
EPCRA
ERNS
FEMA
FHMTL ,.
FNM ' '
FOIA
FWPCA
HLPAD
HMIRS*
HMIS "
HPSA
HSEES'
IMIS
IRIS
ISR
NRC
NRT
NTIS
OPS "
osc
OSHA
RCRA
RQ
RSPA ,
SARA
SAS
SNM
TELERNS
TSA
TSCA
USCG
Accidental Release Information Program
Agency for Toxic Substances and Disease Registry -
Clean Air Act
Center for Disease Control and Prevention
Comprehensive Environmental Response, Compensation and Liability Act of 1980
Code of Federal Regulations
Clean Water Act -.'.''.
. Department of Defense .
Disk Operating System
Department of Transportation
Extremely Hazardous Substance '
Environmental Protection Agency
Emergency Planning and Community Right-to-Know Act of 1986 -' ' .
Emergency Response Notification System
Federal Emergency Management Agency "
Federal Hazardous Materials Transportation Law .
Federal Notification Modules
Freedom of Information Act >
Federal Water Pollution Control Act ',
Hazardous Liquid Pipeline Accident Database
Hazardous Materials Incident Reporting System
Hazardous Materials Information System -.'.-'.
Hazardous Pipeline Safety Act
Hazardous Substances Emergency Events Surveillance
Integrated Management Information System . .
Incident Reporting Information System
Incident Summary Report ,
National Response Center
National Response Team ,
, National Technical Information Service
Office of Pipeline Safety . . ,
,On-Scene Coordinators
Occupational Safety and Health Administration
Resource Conservation and Recovery Act
Reportable Quantity
Research and Special -Programs Administration
Superfund Amendments and Reauthorization Act of 1986
Statistical Analysis System ,
State Notification Modules
DOT Telephonic/EPA National ERNS Database ", '
Transportation Safety Act , :'."...
Toxic Substances Control Act ' .
United States Coast Guard
* HMIRS is part of the HMIS (as is HLPAD) and in all cases in this document HMIRS is the correct
reference. '
-------
-------
I. INTRODUCTION
Background
'Although progress continues to be made in preventing accidental releases of hazardous chemicals,
these releases remain a recurring problem. A broad range of groups, from industry and trade associations
to federal, state, and local government agencies, environmental groups, and other concerned citizens, have
a stake in learning more about these accidental releases - where, when, and how they have occurred ~ in
order to determine why such releases occur and, consequently, how to prevent them in the future.
To meet this large demand for information about chemical releases, data have been collected by a
number, of different sources (both public and private) and on multiple levels (facility, parent company,
association, local, state, regional, and national). In some cases, this collection of chemical release data has
been voluntary; in many cases, however, federal laws (e.g., the Clean Air Act, the Comprehensive
Environmental Response, Compensation, and Liability Act (CERCLA), etc.) require that chemical release
information be reported to certain governmental authorities. For example, the federal, government
currently collects accidental release information based on certain criteria, including characterization of the
release (e.g., its size and source), type of chemical released, industry category (e.g., chemical or petroleum
manufacturers), and impact of the release (death, injury, and/or evacuation).
In response to laws and federal agency mandates for this type of information, numerous databases
that contain accidental release information have appeared over the years. For example, EPA developed
the Accidental Release Information Program (ARIP) database to collect information on the ways in which.
facilities have tried .to prevent recurring releases. Another EPA database, known as the Emergency
Release Notification System (ERNS) database, was created to help federal on-scene coordinators
determine the appropriate federal emergency response to an individual release. None of the federal
accidental release databases contain information on long-term economic or environmental impacts.
The Database Compatibility Problem
The existence of many-different (and often incompatible) federal databases makes it difficult to
develop a national picture of the problem of accidental releases. This conclusion was confirmed by a
Report to Congress entitled, A Review of Federal Authorities For Hazardous Materials Accident Safety
(EPA 550-R-93-002, December 1993). The report, referred, to as the Presidential Review, was prepared by
EPA in coordination with the,National Response Team (NRT), It catalogues certain deficiencies in data
quality, accessibility, and the compatibility of federal accidental release databases.
Some of the report's findings were based on an evaluation of accidental release databases
maintained by several federal agencies including Department of Transportation (DOT), Occupational
Safety and Health Administration (OSHA), Environmental Protection Agency (EPA), and the U.S. Coast
Guard (USCG). Each regulatory agency charged with controlling hazardous materials has developed at
least one accident reporting system or database to accommodate its specific accidental release notification
requirements and data needs. Consequently, the databases reflect different statutory definitions and terms
(e.g., spill, release, accident, incident), different chemical lists, and different impact concerns (e.g., death).
This complicates accidental release reporting. Also, the absence of comparable data sets and lack of
database coordination among agencies has inhibited data interpretation, comparative analysis, and cross
agency use of accident data. Although this situation has presented a confusing array of databases to
industry, environmental groups, and the public, full merger of existing databases has been ruled out as
being not realistic, feasible, or preferable. However, the NRT is considering a,pilot project for linking the
databases; this project is outlined in Chapter V. -
.'"..- ' ' - ' -.1- .".:'
-------
A Helpful Step: Today's User's Guide
In follow-up efforts to the Presidential Review, an accident workgroup, composed of members of
the NRT, decided that developing a user's guide to federal accidental release databases might make these
databases more usable, available, and comparable. Potential users for this guide include staff from federal
government (both for agencies that maintain the data and for other agencies), state and local governments,
industry and business, environmental groups, and the public. Users may come to this guide with different
questions or hypotheses regarding accidental releases. By consulting this guide, users should be able to
obtain a range of information, from data about specific releases to data about national release trends. As
always, the information varies in quality, and is only useful if the user understands the limitations of the
data and interprets the data appropriately. The guide is organized with these assumptions in mind.
Chapter II of the guide provides a list of the databases featured in this document, and outlines
some general search strategies to assist the user in formulating a search and choosing the appropriate
databases. Chapter III includes brief,, descriptive profiles of seven federal accidental release databases
maintained by the National Response Center (NRC), EPA, DOT, OSHA, and the Agency for Toxic
Substances and Disease Registry (ATSDR). Each profile is two to four pages in length and briefly
describes the database for those unfamiliar with the specific characteristics of the database. Additional
databases not featured in these profiles are described at the end of Chapter III. Chapter IV provides a
quick cross reference to the databases and to information of interest (e.g., chemicals covered, number of
records). By reviewing Chapter IVs comparison of different databases, users of this guidance document
may be better equipped to choose the database that best meets their information needs. Chapter V
discusses the value of and possible pilot project for linking the databases to enable comparative analysis.
This guide is designed to be both accessible to the lay person and sufficiently detailed to assist the
policy analyst or computer-oriented person. For instance, users who are'unfamiliar with database search
strategies and the specific databases described in this document should read Chapter II carefully and
consult the cross reference exhibits in Chapter IV. Other users who are already somewhat familiar with
these federal accidental release databases and who want more detailed information about a specific
database should read Chapter III. Each agency has reviewed relevant sections of this guide for content and
accuracy. As changes in regulations or agency needs occur, some information in this user's guide may
become outdated.
-2-
-------
II. DATABASES FEATURED AND SEARCH STRATEGIES
Databases Featured ,
Because of the large and potentially confusing number of accidental release databases in existence,
the focus of this user's guide was limited to seven, federally maintained databases. The seven databases
were selected because they: (1) contain information on accidental releases of hazardous chemicals; (2) are
important data sources that, support federal agency goals; and (3) are on-going collection efforts. 'The
following table lists the selected databases profiled.in this user's guide.
Acronym
IRIS
; / .BENS ':
ARIP
HMIRS
HLPAD
IMIS
HSEES
; Database
Incident Reporting Information System
Emergency Response Notification System
Accidental Release Information Program ,
Hazardous Materials Incident Reporting System
Hazardous Liquid Pipeline Accident Database
Integrated Management Information System
Hazardous Substances Emergency Events Surveillance
Lead Agency
NRC
EPA
EPA
DOT
DOT
OSHA
ATSDR
-
Most of these featured federal accidental release databases are currently not directly accessible to
the public. Although this lack of accessibility is changing, the user generally will need to contact the
federal agency directly to obtain desired information. Generally, different federal agencies have different '
procedures for requesting information. Under the Freedom of Information Act (FOIA), the user can ~
request information by following the agency procedures in the Code of Federal Regulations (CFRV
National Response Center/United States Coast Guard, 33 CFR 1; Environmental Protection Agency 40
CFR 1; Department of Transportation, 49 CFR 7; Occupational Safety and Health Administration, 29 :'. '
CFR 1912; and Agency for Toxic Substances and Disease Registry, 48 CFR 324. However, the user should
first consult mdrvidual database profiles in Chapter III to learn more detailed information about the
featured databases and to identify alternative ways to access them.
Many of these databases are related to' one another in that they are built on the same basic
information. The "parent" database is the National Response Center's IRIS database, which is the
depository of almost all release notifications reported to the federal government. NRC's IRIS database
supports many federal government agencies that have responsibilities for emergency response, emergency
planning and release prevention. These agencies include the U.S. Coast Guard, Environmental Protection
Agency (EPA), Department of Transportation (DOT), Federal Emergency Management Agency
Department of Energy, and the Department of Defense. '.'
- ' ... - \
^Exhibit 1 presents the general relationship among the seven federal accidental release databases
featured m this user's guide. NRC's IRIS forms the core for a family of other federal databases that
collect more detailed or follow-up information to support release prevention, enforcement, and policy
dedsions^Other databases combine IRIS information with other release notification information For
example, EPAs ERNS database combines release notifications contained in IRIS with the notifications
-3-
-------
Exhibit 1
General Relationship Among Accidental Release/Notification Databases
01
o
5
u
ft
w
ฃ
Abandoned Sites (A) Fixed Facility (B) Marine Transport (C) Pipeline (D)
Land/Air Iran sport (E)
Worker Injury Worker Death
EPA
Regional Offices
State Governments
Telephone Notification
Survey
Survey
Telephone
Notification
Survey
Survey
Survey
-------
reported to the EPA regions. In turn, a subset of the ERNS database is used to form EPA's ARIP
database, which focuses on collecting specific follow-up information about the prevention of more severe
releases.
Two databases featured in this guide are not outgrowths of NRC's IRIS database, but may contain
information about similar releases (Exhibit 1). Inclusion of information in OSHA's IMIS database is
triggered ,by a fatality or at least three worker injuries, and may not necessarily involve the release of a
hazardous substance, Similarly, the source for release arid consequence information for ATStJR's HSEES
database is not the IRIS database, but data collected primarily from state health departments.
The user should also recognize that the number of release records in the seven featured databases
varies greatly (Exhibit 2). IRIS, ERNS, and HMIRS contain the largest volume of release notification
records. These three databases may provide information about a larger number of releases, but they may
not be the most accurate or complete. In addition, the types of releases covered in the seven featured
databases also vary greatly (Exhibit 3). The different types of releases include releases from fixed facilities,
from transport sources (e.g., ship, truck, rail, pipelines, aircraft), and from abandoned dumps or waste
sites. .. " '.''- ,
Search Strategies
To help guide the user in conducting a database search, this section provides users with some
general database search strategies and suggestions for analyses. Using this guidance, users can formulate a
search, and then select the most appropriate database or databases with which to work. Examples are
included that demonstrate how the databases can be examined. An applied approach is provided to
address some of the same issues of database compatibility and. utility mentioned in the Presidential
Review. Chapter V of this document advances this discussion of search strategies by describing the value
and possibility of using information from several different databases to get more complete information
about releases.
STEP 1 - Formulate objectives and scope
An important and critical step in obtaining the desired information is to first define the objective
or goal of a search. One objective could be to test a hypothesis, such as: releases of toxic gases have
greater consequences for the public than liquid spills even though gas releases are significantly smaller
than liquid spills. Another objective could be to obtain background information (e.g., number of spills .per
year) or to supplement existing information about a specific incident. Formulating the objective helps to
determine the scope of the analysis. Even a comprehensive analysis should be sufficiently detailed so that
the scope of the data search is narrow enough to make the data meaningful. The search can be
appropriately narrowed by focusing on releases of certain chemicals, releases in certain geographic areas, "
releases of certain sizes, and releases in certain years. For example, a sufficiently defined search might
examine the number of chlorine releases at water treatment facilities. In addition, a narrow scope can
reveal findings that might otherwise be diluted in searches of larger data sets and/or large databases like
IMIS, ERNS, and HMIRS.
STEP 2 - Determine the types of information needed
After a goal or objective has been defined, the user should identify all of the types of information
or data elements that might be applicable to his or her objective, such as quantity released, chemical
released, and injuries. The data element or kind of information contained in a database should match the
user's desired information before choosing an appropriate database. For example, for a data element on
injuries, the user should ask what level of detail about the injury is needed (i.e., is it'sufficient for a
-5-
-------
Number of Incidents/Notifications
01
o
o. ง
o
o
o
o
01
o
o
o
O
O
O
o
o
01
o
o
o
o
10
o
o
o
o
o
N>
01
o
o
o
o
CO
o
o
o
o
o
1
o _
o -.
ง1.
ง
CQ
>
O
o
E
(D
I
o
o
a
3
-------
Exhibits
Types of Releases Covered
C57021-4
-------
yes/no response that the injury occurred, or is it necessary to have the number of injuries or, even further,
is it necessary to have information about who was injured (e.g., facility employee, public, contractor,
responder?)). Also, if regulatory issues are being explored, it is important to outline the regulatory
definitions needed in the data elements. For example, a database search on releases of interest to the
Coast Guard should focus on a data element that covers releases to navigable waterways rather than just
releases to water. ,
STEP 3 - Examine level of accuracy required for analysis
To consider this issue, the user may need to ask if the results have to reflect national trends. Is it
more important to have verified information in a relatively small data set (e.g., ARIP) or to have a larger
database of initial release notification information (e.g., ERNS)? More records do not necessarily increase
the accuracy of the data findings, especially if the information is unverified or particularly subject to
uncertainty. For example, an analysis of release quantity in ERNS is probably subject to significant error
because the information is reported soon after or during a release when the release quantity may not be
known accurately. ARIP can provide better release quantity information because the information is
provided several months after the release. However, the ARIP database focuses on only the more serious
releases and therefore, the quantity information cannot be extrapolated to national trends.
STEP 4 - Know your desired output
Is a printout of a single release record desired? For comprehensive aggregate analyses, are simple
frequency distributions required or are more sophisticated correlations or statistical analysis required? By
asking these questions in advance to define the search, the user will allow" the agency contact to better
respond to the user's database needs. Of course, the user can work along with the database contacts to
prepare the information request further.
STEP 5 - Use Steps 1-4 as the basis to select the most appropriate database
The most common database searches involve identifying a single release, requesting information
on all releases from a specific company or facility, or performing an aggregate analysis. If the user is
unsure which database will meet his or her needs, the user should first consult the Chapter, IV exhibits,
keeping in mind the kind of search that is desired. Cross-comparison of databases presented in these
exhibits can help determine which databases can meet the objectives of the search. Then, the user should
review the more detailed database profiles in Chapter III to confirm his or her choice and to learn how to
request the search or to gain access to the data.
If the search focuses on a single release, the user may have to determine if this kind of release
(e.g., transportation) is likely to be reported in a given database, considering the characteristics and scope
of the database. Exhibit 4 in Chapter IV provides information about the chemicals and industries covered
and the criteria for including the release in the database. The user may also ask what critical information
(e.g., release date, company name, and chemical released) he or she must have for identifying the release.
If the search asks for all releases or notifications related to a specific company for a particular material,
the user should also include in the search a listing of the company name, including subsidiaries and
common misspellings. In both kinds of searches, the user should request the kind of information about
the release that is important to him or her (e.g., damage, cause) and that is collected in the database.
Sometimes, federal agencies provide a standard set of information about the release. Exhibit 5 in Chapter
IV will assist the user in identifying the data elements needed. Exhibit*6 can provide specific details on
whether a specialized piece of information, such as Dunn and Bradstreet number, can be used to further
identify the release or facility.
-8-
-------
For aggregate searches, the user should carefully choose the database that provides the
information to satisfy the objective of the analysis. The user should use the database profiles in Chapter
III and the exhibits in Chapter IV to become familiar with the precise definition of the data elements in
order to prevent misinterpretation of the data. For example, an analysis of deaths that involve releases of
hazardous substances may be misleading if OSHA's IMIS database is selected. The death information in
IMIS does not differentiate between a death due to release exposure or to mechanical exposure (e.g.,
crushed by ah overturned forklift that happened to spill a pallet of hydrochloric acid). Along with an
understanding of the definition of the data elements, ,the user must determine if the types of information
needed are found in the database. For example, the number of chlorine releases at pulp/paper mills can
be effectively searched in ARIP, because ARIP contains information on the chemical or CAS number and
on the SJC code, which can identify pulp/paper mills. For overall trend analysis (e.g., frequency
distributions on the number of releases or chemicals released), the larger national databases such as
ERNS, HMIRS, and IRIS are most useful.
Some users have conducted risk analyses with the release data. For overall risk analyses on
transportation releases, the user could use HMIRS to determine the number of transportation releases and
use another information source to determine the number of chemical shipments. The larger databases are
also valuable if the user wants to identify the number of releases/notifications and associated release
information related to a company for a particular material over a certain period of time. Databases that
have detailed, verified information such as ARIP, HMIRS, and HSEES are suited to the testing of specific
hypotheses (e.g., chlorine releases disproportionately cause consequences) and to analyses on different
subsets of data (e.g., data on releases during operations versus releases during maintenance activities). The
user should be cautioned about comparing the results of an analysis conducted on one database with the
results from another database. Broad statistical analysis is not comparable across database due to differing
scopes of the databases (e.g., criteria, for reporting, industries covered).
As noted above, Chapter V of this document takes this discussion of search strategies a step
further, by describing possible ways to use-information from linked databases to get more complete
information about releases.
-9-
-------
-------
in. DATABASE PROFILES
In this chapter, a profile format is used to describe each of the seven federal accidental release
databases. Using the information provided in each profile, the user can request or access desired data and
can analyze the data appropriately. The profile outlines a general description of the database including its
history, purpose of collection, typical users, database size, and a list of potentialcontacts. Along with
general information, the user is provided with information on the characteristics of the data that include
data sources, data scope (e.g., types of chemical reported, industries reported, criteria for reporting), and
data limitations and quality (e.g., missing data, data accuracy, data verification). In addition, the user is
supplied with a listing of key data elements" contained in the database. Another section of the profile
covers ways and costs to access the data and a final section provides helpful hints in searching for data,
given the idiosyncracies of each database. The user can also refer to two appendices: one that presents
examples of completed accident report forms for the databases (Appendix A) and another that includes
datafield dictionaries listing the computer format and data elements in each database (Appendix B).
The database profiles are valuable for users who:
* Want to introduce and familiarize themselves with details of several federal accident release
databases;
-'. > Have heard of a federal database and are not sure if it is the right one for their needs;
* Are interested in linking or using several databases to perform an analysis;
* Know which database has the desired information, but do not know how to access it; or
+ Have used one of the databases before, but may seek ways to make their information search more
efficient or effective.
Following the profile section, short descriptions of several other federal release or reporting databases are
provided.
-11-
-------
-------
Acronym:
Database Name:
Agency Office:
Primary Contact:
Contact Address:
Contact Phone:
Profile
IRIS
Incident Reporting Information System
U.S. Coast Guard, National Response Center
Logistics Support Officer, National Response Center
Chief, NRC
U.S: Coast Guard, National Response Center
Room 2611, G-TGC-2
2100 2nd Street, SW
Washington, DC 20593
(202) 267-2185 " /
GENERAL DESCRIPTION
The Incident Reporting Information System (IRIS) is a relational database operated by the
National Response Center (NRC) at the U.S. Coast Guard Headquarters. This database system
should not be confused with another EPA system with the same acronym Integrated Risk
Information System (also known as IRIS). IRIS contains data on oil, chemical, biological, and
etiological discharges into the environment anywhere in the U.S. or its territories. There are many
federal statutes that require reporting of such releases:
Oil spills are reported under Section 311 (b) of the Federal Water Pollution Control Act
(FWPCA)-of 1973, Section 306(a) of the Outef-Shelf Lands Act Amendments of 1978, %
and Section 18(b) of the Deepwater Ports Act of 1974.
. Chemical spills are reported under Section 302 of the Comprehensive Environmental
Response, Compensation, and Liability Act (CERCLA) of 1980, Section 304 of the
Emergency Planning and Community Right-to-Know Act (EPCRA) of 1986, and Federal
Hazardous Materials Transportation Laws.
Pipeline spills are reported under the Hazardous Liquid Pipeline Safety Act. ,
Air releases are reported under the Clean Air Act (CAA), the Toxic Substances Control
Act (TSCA), Federal Hazardous Materials Transportation Laws, and the Resource
Conservation and Recovery Act (RCRA). <
IRIS supports the informational needs of various organizations within the National Response
Team (NRT), though it is used primarily for emergency response notification. Staffed by the U.S.
Coast Guard,.the NRC collects information nationally on reports of hazardous material releases as
well as releases of hazardous substances and oil from fixed facility and transportation incidents.
These reports are transmitted daily to Volpe National Transportation'Systems Center in
Cambridge, MA, and compiled in a separate database. This database is reviewed to eliminate
duplicates and merged with DOT-EPA's jointly-managed TELERNS database. The NRC's
primary role is to relay incident information immediately to ,the Federal On-Scene Coordinator
(Coast Guard or Environmental Protection Agency official) who coordinates any potential federal
response to the incident. --
-13-
-------
IRIS (continued) |
Data from IRIS reports are also disseminated to other response agencies, including USCG, EPA,
Department of Transportation, Federal Emergency Management Agency, and the Department of
Defense. Data are also passed to several states via a system called STATE*FAX. The NRC is
encouraging more states to link up with the NRC notification process and incident database. IRIS
* data can be provided to other agencies for guidance and regulatory development, compliance and
enforcement support, statistical and trend analysis, academic research, or property transfer/site
audits. The NRC handles approximately 300,000 telephone calls per year, and most are recorded.
Not all of the telephone calls relate to unique incidents. For example, of the 300,000 calls
received in 1990, only 25,200 unique incident reports were recorded. The NRC estimates the
annual growth rate of incident reports to be approximately ten percent. As of September 30,1994
there were 247,276 incidents in the IRIS database. This represents all notifications made to the
NRC since 1982. For CY 1994, NRC expects over 33,000 incidents to be reported. Notification
reports received by the NRC from 1974 to 1982 are archived. The relational database maintained
by the U.S. Coast Guard was initiated in 1982 and reorganized in 1988 to become, the IRIS system
that is in existence today. The data collected have remained unaltered; specific packaging
"features" have been recently added. In cases where new information on previous notifications
becomes available, the new data are entered as a new record while the old information remains
unchanged. Periodic data reviews occur to ensure that data in the IRIS database are accurate
(e.g., spelling and geographical location).
CHARACTERISTICS OF DATA
Source IRIS data are entered directly into a database when a release is reported to the NRC.
Such information is usually provided by telephone reports from persons associated with
the facility or transportation vehicle that had the release, or from government officials or
private citizens who observed the release.
Scope IRIS contains three categories of release reports: hazardous substances as designated by
CERCLA; oil and petroleum products defined by the Clean Water Act; and materials that
are not CERCLA- or CWA-defined substances.
The number and types of chemical releases that are reported to IRIS have changed over
the years because of regulatory changes, changes in the chemical industry (packaging and
increased productivity), changes to lists of chemicals in the regulations, and surges in
reporting from a specific industry. Information about specific changes in the IRIS
database over time can be obtained from the NRC's Logistics Support Officer at (202)
267-2185. ,
IRIS contains data on reported releases from fixed facilities, marine/offshore facilities,
pipelines, and transportatiqn vehicles. Both actual and potential releases may be reported
to IRIS. Practice drills for emergency releases are also captured in the database. IRIS
notification reports are comprised of primarily short answer questions.
Data Because IRIS is a database of initial notifications made during or immediately after a
Limitations release occurs, exact details of the release are often unknown. Consequently, the
information provided to the NRC may be incomplete, preliminary, or inaccurate. For
example, release quantity information is often not reported accurately at the time of NRC
notification. If the notifying party is representing the responsible party, the information in
the database is usually more complete than if reported by a citizen or observer.
Duplicate reports may appear when a caller makes a second report to update original
data, or a release is observed and reported by more than one person. Less than 20
14-
-------
IBIS (continued)
percent of IRIS records are estimated to be duplicates. Notifications are never removed
from the database. Updates are occasionally provided by the responsible party or the
OSC. Reports are taken over the telephone; for this reason, errors in transcription (e.g.,
misspellings) may limit the quality of some data. A Duty Officer reviews each report in
an effort to eliminate these errors.
IRIS is not an incident-specific database because it contains notification information on
both actual, misreported, and potential releases. Therefore, conclusions about release
distributions or correlations based on IRIS information may be deceptive because the data
analysis may include information on potential or misreported releases. Methods or
resources to help overcome or adapt to these data limitations are described, in the helpful
hints section.
IRIS does not distinguish whether deaths and/or injuries resulted from the release of the
chemical or from the incident that caused the chemical release.
DATA ELEMENTS
There are approximately 140 datafields in IRIS. The following key categories are included in
IRIS:
date/time of incident
incident location
medium affected
response actions
quantity spilled
evaluation of response
material released
cause
source
reporting source/person
responsible company/discharger
persons/agencies notified
damage (deaths, property)
personnel/agencies to be notified
Refer to the Datafield Dictionary (Appendix B), for a complete list of IRIS data elements. -
ACCESS
Availability FOIA Requests: Currently, for personnel from state and local government, industry, and
the general public, a written FOIA request to the FOIA Officer is the preferred manner
to request specific data or obtain more information about IRIS. Federal government
personnel do not need to make a data request under FOIA, however, written data queries
should still be directed to the FOIA Officer. All requests should be addressed to: FOIA
Officer, Commandant USCG, Room 2611, 2100 2nd Street SW, Washington D.C., 20593.
The Logistics Support section of the National Response Center oversees the database.
The Logistics Support section may be contacted at (202) 267-2185 to assist in focusing
requests, and answering questions about performing searches in IRIS. Requests for IRIS
. information are also available through e-mail using the Internet at foia.insg/g-
tl7@cgsmtp.comdtuscg.Mili The cost for an IRIS search depends on the data medium
requested (e.g., hard copy, floppy disk) and the time and effort expended to fill the
request. Costs are usually minimal and are based on the fee schedule for Freedom of
Information Act (FOIA) requests outlined in 40 CFR 2.120. There is no fee for data
query requests made by the federal government.
Subscription for Information Government agencies can set up a query account to receive
notification of major, potential major, and medium-size incidents within a specific region
or type. This information is released weekly, sometimes daily, depending oil the number
of reports. These reports are called Incident Summary Reports (ISRs). To receive'a
subscription to these data, a written request is required, as is a commitment not to release
-15-
-------
IRIS (continued)
Conditions
of Use
Data Outputs,
Hardware, and
Software
Requirements
Training/
Support
certain information contained in the reports. If the agency is responsible or obligated to
publish all of the information, including information protected by the Privacy Act, the
NRC can provide abbreviated reports excluding the sensitive information. Currently, over
250 individuals from various federal agencies subscribe to the ISRs.
Another service recently offered through the IRIS system is the Federal and State
Notification Modules referred to as FNM and SNM. These modules immediately notify
certain persons or groups in federal and state agencies of releases if the person has
expressed interest in being notified in a timely manner. The program was initiated to
notify governors of releases within their state. There- are currently over a dozen different
federal offices and 27 states enrolled in this new program. The agencies, such as the Fish
& Wildlife Service, and states may use FNM and SNM information to notify sensitive
populations of releases (e.g., zoos, and water treatment plants). These parties have an
interest in responding quickly to releases to reduce the impact. To receive a subscription
to these data, a written request is required, as is a commitment not to release certain
information contained in the reports. If the federal or state agency receiving the
notification is responsible or obligated to publish all of the information, including
information protected by the Privacy Act, the NRC can provide abbreviated reports
excluding- the sensitive information.
IRIS data have various conditions that limit the use or disbursement of these data. For
example, proprietary or trade secret information may not be released. "Sensitive" reports
are available to tailor the formatted information to best meet the user's needs. Call the
NRC for specific requests.
The Logistics Support section performs queries for information and manages the IRIS
database. IRIS data and analyses can be presented in various formats and are available in
hard copy or on floppy diskettes.
IRIS can provide information in DOS or UNIX, DYNIX-PTX compatible files.
The Logistics Support section provides support for IRIS-related requests and questions.
The support group is available to assist in interpreting data and focusing FOIA requests.
HELPFUL HINTS
Keep in mind that most IRIS data are based on initial notification, and may not have
been verified. Therefore, historical IRIS data on a specific incident may be inconsistent
with data from other sources.
There is a flag in the database that identifies duplicates or updates reported to the NRC.
Release information on specific chemicals can be searched by chemical name or CAS
number.
Users undertaking statistical analysis should avoid small data sets because of the
inaccuracy and incompleteness of the notification records.
Users undertaking statistical analysis should be careful to consider and address multiple
notifications for a single release.
Any analysis should be sufficiently broad to minimize the influence of data spikes and
regulatory changes.
Consult with the Logistics Support section to help focus the analysis.
-16-
-------
Acronym:
Database Name:
Agency Office:
Primary Contact:
Contact Address:
Contact Phone:
Profile
ERNS
Emergency Response Notification System
U.S. EPA Office of Emergency and Remedial
Response
ERNS Information Line
ERNS Manager
U.S. Environmental Protection Agency
Mail Code 5202G
401 M Street, SW
Washington, DC 20460
(202) 260-2342 or (703) 603-8960
GENERAL DESCRIPTION
The Emergency Response Notification System (ERNS) is an EPA database that contains data on
release notifications of oil and hazardous substances reported to the National Response Center or
the ten EPA regional offices. There are four primary federal statutes that require release
reporting: -
Section 103 of the Comprehensive Environmental Response, Compensation, and Liability
Act (CERCLA) of 1980;
Section 304 of the Emergency Planning and Community Right-to-Know Act (EPCRA) of
.- . ' ' 1986; . ;""..,,.
.Section 1808(b) of the Hazardous Materials Transportation Act (HMTA) Of 1974; and
, Section 311 of the Clean Water Act (CWA).
Part or all of the information included in reports to the NRC may be collected in ERNS. ERNS
notifications are used by On-Scene Coordinators (OSCs) to determine an appropriate federal
response action. Data in ERNS reports may also be given to other response agencies including
the state emergency response commission, local emergency planning committee, U.S. Coast Guard
(USGC), Department of Transportation (DOE), Federal Emergency Management Agency-Office
of Hazardous Materials (FEMA-OHM), and the Department of Defense (DOD). Other data
applications include guidance and regulatory development, compliance and enforcement support,
statistical and trend analysis, academic research, and property transfer/site audits. ERNS has
received approximately 300,000 release notifications since its inception in 1986. All notifications
reported to the NRC and EPA regional offices become part of the national ERNS database
managed jointly by EPA and DOT as the TELERNS database. In cases where new information
on previous notifications becomes available, EPA regional offices can provide periodic updates to
the ERNS database at EPA Headquarters. Each EPA region also maintains its own region-
specific database, which is a subset of the national database. New notifications are input daily:
-17-
-------
ERNS
(continued)!
CHARACTERISTICS OF DATA
Source ERNS data are captured electronically when a release is reported to the NRC or EPA
regional offices. Such information is usually provided by a person associated with the -
facility or transportation vehicle that had the release, though other observers of the
release may also report it. .
Scope ERNS contains three categories of release reports: hazardous substances as designated by
CERCLA; oil and petroleum products defined by the Clean Water Act; and materials that
are not CERCLA- or CWA-defined substances. CERCLA substances account for, on
average, 19 percent of all notifications in ERNS. Oil notifications (as required by the
CWA) account for 57 percent, and notifications of other chemicals comprise 24 percent.
CERCLA releases that meet or exceed the reportable quantity (RQ) set forth in 40 CFR
302.4 must be reported. Oil releases that violate applicable water quality standards, cause
a film, or cause a sludge/emulsion beneath the surface of water must be reported. Some
of the release notifications of other chemicals (non-CERCLA and non oil chemicals) are
generated by criteria established for reporting of transportation releases under HMTA or
pipeline safety regulations.
The number and types of chemical releases that are reported to ERNS have changed over
the years because of regulatory changes, listing/delisting chemicals in the regulations, and
surges in reporting from a specific industry. Information about specific changes in the
ERNS database o'ver time can be obtained from the ERNS Information Line.
ERNS contains data on reported releases from fixed facilities, marine/offshore facilities,
pipelines, and transportation vehicles. Both actual and potential releases may be reported
to ERNS. ERNS notification reports are comprised of both short answers and long
comments.
Data Because ERNS is a database of initial notifications made during or immediately after a
Limitations release occurs, exact details of the release are often unknown. Consequently, the
information provided to the NRC or EPA may be incomplete, preliminary, or inaccurate.
Only about a third of the 193 information datafields are completed for most of the release
notifications.
The majority of ERNS information is not verified or validated. The data are usually not
updated with more current information unless an EPA region is involved in the response
action. Data quality varies from one region to another.
Approximately five percent of ERNS records are estimated to be duplicates. Duplicate
reports may appear when a caller makes a second report to update original data or a
release is observed and reported by more than one person. Reports are taken over the
telephone, therefore, errors in transcription (e.g., misspellings) may limit the quality of
some data. '
-18-
-------
ERNS (continued)
DATA ELEMENTS
The following key categories are included in ERNS:
date/time of incident
incident location
medium affected
response actions
* region information
evaluation of response
material released
cause
persons/agencies notified
follow-up actions
responsible company/discharger
source
damage (deaths, property)
Refer to the Datafield Dictionary (Appendix B), for a complete list of ERNS data elements.
ACCESS
Availability
ERNS Information Line Currently, for industry, regulatory and enforcement support, and
general public requests, the ERNS Information Line is the preferred way to request
specific data or obtain more information about ERNS. Operated by EPA Headquarters,
the ERNS Information Line at (202) 260-2342 can be used to address questions about'"
ERNS arid to perform reasonable data searches. The line accepts recorded messages from
callers, and requests will be followed-up by a telephone call or letter from EPA or an
EPA contractor, as appropriate. Requests for ERNS information may be made through e--
mail using the Internet at erns.info@epamail.epa.gov. The cost for an ERNS search
depends on the data medium requested (e.g., hard, copy,"floppy disk) and the time and
effort expended to fill the request. Costs are based on the fee schedule for Freedom of
Information Act (FOIA) requests outlined in 40 CFR 2.120. pata can be delivered via
First Class Mail.
Bulletin Board In FY 1995, a bulletin board is expected to enable downloading of ERNS
information. The bulletin board will have several advantages over the ERNS Information
Line including more quick and easy access and no cost for the data.
Channels for EPA Personnel EPA Headquarters and regional personnel may access ERNS
through the EPA local area network or by contacting the ERNS Manager at (703) 603-
8735 or a regional ERNS Coordinator. Also, EPA and other government groups can set
up a query account system with the Emergency Response Division to maintain easy access
to the ERNS information.
FOIA Requests Both EPA Headquarters and regional offices can address ERNS
information requests through Freedom of Information Act (FOIA) requests. A listing of
regional FOIA offices is listed in the fact sheets on ERNS (see below). The fee schedule
for FOIA requests is outlined in 40 CFR 2.120.
Published Information General ERNS information and data analysis is available in. the
following fact sheets from the ERNS Information Line at (202) 260-2342:
An Overview of ERNS, March 1995, Publication 9360.0-29FSA
ERNS and Site Searches, March 1995, Publication 9360.0-36FS ,
ERNS Statistics, March 1995, Publication 9360.0-37FS
ERNS and CERCLA, May 1994, Publication 9360.0-22FSA
ERNS and Oil, May 1994, Publication 9360.0-23FSA
-19-
-------
ERNS (continued)!
Conditions
of Use
AT/5 Magnetic data tapes containing ERNS data are currently available through National
Technical Information Service in Springfield, VA at (703) 487-4650. The order numbers
for magnetic data tapes for 1987-1994 are as follows: 1987- PB94-504180; 1988- PB94-
504198; 1989- PB94-504206; 1990- PB94-504131; 1991- PB94-504149; 1992---PB94-
504156; 1993- PB94-504164; and 1994- PB94-593350. A single update costs $240 (see
section on data outputs, hardware, and software requirements for further information on
magnetic tapes).
Generally, ERNS data are available without conditions or usage limitations. Reporting
party (caller) data is typically not released.
Data Outputs,
Hardware, and
Software
Requirements
Training/
Support
From the ERNS Information Line, ERNS data and analyses can be presented as summary
release information or as standard ERNS reports.. Both are available in hard copy or
electronically on floppy disks. Summary release information reports are organized in table
form to provide a broad overview of data. These reports are useful for analyzing trends in
chemical and oil releases, or for comparing groups (e.g., total release reports involving
crude oil by year).
Standard ERNS reports are either dBASEฎ files or one-page reports in various
wordprocessing formats containing information about specific release notifications. This
one-page report is best suited to presenting small subsets of data, such as notifications
from a particular geographical region, on a specific chemical, or about an individual site.
Magnetic data tapes are also available through NTIS for requestors who have extensive
needs for ERNS data and who have the hardware necessary to read 9 mm 6250 or 1600
bip ASCII magnetic tapes or 3480 cartridges. Included with each tape is a data dictionary
that describes the fields in ERNS and a tapeout log that shows the number and lengths of
records and blocks. . .
The ERNS Information Line provides support for ERNS-related requests and questions.
HELPFUL HINTS
Keep in mind that most ERNS data are based on initial notification, and may not have
been verified. Therefore, historical.ERNS data on a specific incident may be inconsistent
with data from other sources. .
Release information on specific'chemicals can be searched by chemical name or CAS
number. .
Because names and addresses may include misspellings or alternative spellings (e.g.,
avenue or ave.), a site-specific search should encompass a larger area of investigation (e.g.,
county) to assure that all site information will be captured regardless of any data
inconsistencies in the site-specific name or address.
Users undertaking statistical analysis should avoid small data sets because of the
inaccuracy and incompleteness of the notification records.
Users undertaking statistical analysis should be careful to consider and address multiple
notification for a single release. ERNS maintains flags to minimize this problem.
Any analysis should be sufficiently broad to minimize influence of data spikes and
regulatory changes. -
Consult with the ERNS Information Line to help focus the analysis.
-20-
-------
Acronym:
Database Name:
Agency Office:
.Primary Contact:
Contact Address:
Contact Phone:
Profile
ARIP
Accidental Release Information Program
U.S. EPA's Chemical Emergency Preparedness and
Prevention Office
ARIP Manager
U.S. Environmental Protection Agency
Mall Code 5101
401 M Street, SW
Washington, DC 20460
(202) 260-8942 or (202) 260-1448
GENERAL DESCRIPTION
The Accidental Release Information Program (ARIP) database was developed by EPA to
determine the causes of accidental chemical releases, to identify the steps that could be taken by
industrial facilities to prevent releases, and to outline industry prevention practices. The database
is assembled from information provided by facilities that have had significant releases of hazardous
substances in response to a specially designed questionnaire. The questionnaire consists of 23
questions about the facility, the circumstances and causes of the incident, the accidental release
prevention practices and technologies in place prior to -the event, and any additions or changes
made to these technologies and practices as a result of the event. The questionnaire focuses on
several areas of accident prevention including hazard assessments, training, emergency response,
public notification procedures, mitigation techniques, and prevention equipment and controls.
EPA is authorized to collect information on accidental releases under:
Section 3007(a) of the Resource Conservation and Recovery Act (RCRA);
Section 104(b)(l) and (e) of the Comprehensive'Environmental Response Compensation .
and Liability Act (CERCLA); ~
Section 308(a) of the Clean Water Act (CWA); arid
Section 114 of the amended Clean Air Act (CAA).
EPA Headquarters maintains the national ARIP database, although the EPA regions may have
hard copy printouts or electronic records of the ARIP questionnaires in some cases. The ARIP
database has collected over 4,800 release records since its inception in-1986. It is updated once a
year. ' ' .<_-". ,
CHARACTERISTICS OF DATA
Source ARIP data are provided by facilities that have had significant releases of hazardous
substances. " ' . ,
-21-
-------
ARIP (continue
Scope
Data
Limitations
Collection of ARIP data is triggered initially by incidents reported to the ERNS system.
U.S. facilities are required by law to report releases of certain substances when those
releases exceed a certain chemical-specific quantity or reportable quantity (RQ). EPA
periodically screens the ERNS database to find fixed facility release events that meet one
or more of the following triggers:
The release resulted in a death or injury;
The release involved 1,000 pounds or more of a hazardous substance with an RQ
of 1, 10, or 100 pounds, or the release involved 10,000 pounds jar more of a
hazardous substance with an RQ of 1,000 or 5,000 pounds;
The release was the fourth through tenth release in a 12-month period (repeat
'release); or
c The release involved an extremely hazardous substance from section 302 of
EPCRA.
EPA sends a detailed questionnaire to any facility with a reported release that meets one
or more of these criteria. When the questionnaire is returned, the data are recorded into
the ARIP database. ARIP does not capture events associated with flammable or
petroleum products.
In September 1993, the criteria for ARIP releases changed to target those accidental
releases at fixed facilities that resulted in casualties with off-site consequences or
environmental damage. Off-site consequences include any casualty, evacuation, shelter-in-
place, of other necessary precaution taken by individuals off-site as a result of the release.
Environmental damage includes wildlife kills, significant vegetation damage, soil
contamination, and ground and surface water contamination. Most records in ARIP
consist of incidents that took place prior to September 1993 when the less restrictive
criteria was used for inclusion in the database.
For several years, the ARIP questionnaire was revised so that some information was added
and other information was deleted. Thus, analysis on some datafields cannot be
performed on the entire database. Also, the short description of the accident is not
contained in the database and must be analyzed in the hard copy of the questionnaire.
Because ARIP is designed to capture the most serious or potentially serious releases, it is
not statistically representative of all industry releases. The collection of ARIP data was
dependent on the sometimes uneven collection efforts of the EPA Regions; therefore, the
data does not truly represent the geographic distribution of releases nor reflect release
trends over time. However, the information is considered accurate because the data are
provided directly by facilities several months after the release when most information
should be known. The database is also periodically reviewed for data assurance/quality
control to identify data entry errors, inconsistent information, or questionable data.
DATA ELEMENTS
The following key categories are included in ARIP:
date/time of incident
quantity released
medium affected
costs to facility and public
number of deaths/injuries to
workers, contractors,
duration of release
whether and type of hazard evaluation conducted
cause
release prevention practices prior to release
relea'se prevention practices installed after release
environmental damage
-22-
-------
ARIP (continued) |
responders, and public
number evacuated or sheltered
persons/agencies notified
changes to training
end effect of release (e.g., explosion, spill)
location of release (e.g., vessel, pipe)
how public notified
immediate repairs.
Refer to the Datafield Dictionary (Appendix B), for a complete list of ARIP data elements.
ACCESS , , , ' ' .
Availability
Conditions
of Use
Bulletin Board In fiscal year 1995, a bulletin board is expected to enable downloading of
ARIP information. The bulletin board will have several advantages over contacting the
EPA ARIP manager, including quicker and easier access, more frequent updates, and no
cost for the data:
^Channels for EPA Personnel EPA Headquarters and regional personnel may access ARIP
- by contacting the ARIP Manager or an EPA regional ARIP Coordinator.
FOIA Requests Both EPA Headquarters and regions can address ARIP information
requests through Freedom of Information Act (FOIA) requests. A listing of Regional
FOIA offices is referenced through the ERNS database profile. The fee schedule for
FOIA requests is outlined in 40 CFR 2.120.
Published Information General ARIP information'and data analysis are available in the
following fact sheets and publications from the EPCRA hotline at 1-(800) 535-0202:
Accidental Release information Program Fact Sheet, September 1991 and
November 1993.
Chemical Accident-Prevention Bulletin - Why Accidents Occur: Insights From the
Accidental Release Information Program, June 1989.
Accidental Release Information"Program Implementation Guide, October 1991.
Generally, ARIP data are available without conditions or usage limitations.
Data Outputs, Custom hard copy reports are available from the EPA ARIP manager. A dBase version
Hardware, and of the database or analysis may also be available.
Software
Requirements - " /
Training/
Support
The EPA ARIP manager provides support for ARIP-related requests and questions.
HELPFUL HINTS
ป , Because the ARIP questionnaire has changed several times, certain data may not be
available for all records (e.g., cost damage data are only available starting with log number
2991, hazard evaluation data are only available starting from log number 355). Contact '
the EPA ARIP manager for further detailed information on cautions in using data.
ป Release information on specific chemicals can be searched by chemical name or CAS
number.
-23-
-------
-------
Acronym:
Database Name:
Agency Office:
Primary Contact:
Contact Address:
Contact Phone:
Profile
HMIRS
Hazardous Materials Incident Reporting System
U.S. DOT's Research and Special Programs
Administration, Information Systems
Information Systems Manager
U.S. Department of Transportation, RSPA
Information Systems ,
Mail Code DHM-63
400 7th Street, SW
Washington, DC 20590
(202) 366-4555
GENERAL DESCRIPTION
The Hazardous Materials Incident Reporting System (HMIRS), a part of the DOT's HMIS, is a
computer database that contains data on the unintentional release of hazardous materials during
the course of transportation. The information is compiled in accordance with the requirements of
the Federal Hazardous Materials Transportation Law (49 U.S.C. 5101). ^DOT regulations
stemming from FHMTL require carriers to notify the NRC immediately via telephone of releases
of hazardous materials occurring during the course of transportation that result in human injury
or death; estimated carrier or property damage exceeds $50,000; an evacuation of the general
public occurs; one or more major transportation arteries or facpities are closed or shut down; the
operational flight pattern or routine of an aircraft is altered; fire, breakage, spillage, or suspected
radioactive,contamination occurs involving shipment of radioactive material; fire, breakage,
spillage or suspected contamination occurs involving shipment of etiologic agents; or a release of a
marine pollutant in a quantity exceeding 450 L for liquids or 400 kg for solids. These telephonic
notifications are received by the NRC and transmitted to the DOT-EPA's jointly managed
TELERNS database. These regulations also require interstate carriers, and certain intrastate
carriers, to submit written reports on all unintentional releases of hazardous materials occurring
during the course of transportation. These written reports are entered into the HMIRS database.
The database contains approximately 220,000 records (as of 9/94) of written reports on
unintentional hazardous material releases since 1971. RSPA, the office that manages HMIRS,
estimates that over 15,000 reports are received annually.
The HMIRS system is used to highlight problem areas, to pinpoint needs for corrective action,
and to provide a statistical compilation of transportation incidents involving hazardous materials.
Written reports to HMIRS are updated monthly; telephonic reports are entered daily.
CHARACTERISTICS OF DATA
Source Carriers of hazardous materials are required to report certain unintentional releases that
occur during transportation, The reporting process includes: (1) immediate telephone
notification to NRC, and (2) a written incident report on DOT Form F5800.1, to be
submitted within 30 days of the incident by a representative of the releasing carrier.
-25-
-------
iiffmued)
HMIRS data are captured electronically when a written report is received by DOT. A
subsystem of HMIRS contains telephonic reports received by the NRC since 1982.
Scope HMIRS contains unintentional release reports of DOT regulated materials, CERCLA
chemicals, petroleum, explosives, pesticides, and other chemicals. HMIRS also contains
information on any unintentional release of hazardous materials during the course of
transportation. RSPA has indicated that the number of the releases has been steadily
increasing as more carriers are aware of the reporting requirements, but the number of
serious incidents has remained relatively constant. Information about specific changes in
the HMIRS database over time can be pbtained from the Information Systems Manager at
DOT/RSPA Information Systems.
HMIRS incident reports are comprised of text information boxes, check box responses,
and a descriptive comment section. See Appendix A for a copy of a sample report and
Appendix B for a datafields dictionary for HMIRS. ' . -
Because the HMIRS database is based on written reports submitted by the carrier, details
of each release are usually accurate. The majority of HMIRS information is validated, as
fatality and injury information is verified through follow-up reports, increasing the
accuracy of the HMIRS data. RSPA estimates that virtually all of the approximately 175
datafields are completed for most of the incidents because written reports are filed within
30 days of the release. The HMIRS database is believed to be a highly accurate record of
incidental releases of hazardous material during transportation. To attest to the
completeness of the data, RSPA estimates that less than 0.1 % of the records contain
duplicates. Though duplicates are possible, the data are periodically reviewed and
reconciled to avoid them. -
The Incident Report Form (DOT F5800.1) was revised and expanded in 1990 to capture
additional location and packaging information.
Data Quality/ HMIRS captures only the injuries or deaths that were a direct result of the material's
Limitations release, not from the event which caused the release. For instance, if a barrel is dropped,
two types of injuries could result: (1) a chemical burn from the exposed chemical and (2)
an injury from the physical impact of the barrel. Only the first is recorded.
HMIRS materials are listed by their proper shipping name, which is sometimes a category
(e.g., pesticides or flammables) rather than a specific chemical. Materials can not be
searched by CAS Number because no CAS Number is entered into HMIRS.
HMIRS contains information reported by carriers by rail car, aircraft and vessel; interstate
and foreign carriers by motor vehicle; and intrastate carriers by motor vehicle for
hazardous waste, hazardous substances, flammable cryogenic liquids in portable tanks and
cargo tanks, and marine pollutants. Other releases occurring during intra-state
transportation by an intra-state carrier are not included.
DATA ELEMENTS
The following key categories are included in HMIRS:
date/time of incident shipper name
incident location ' carrier name
-26-
-------
mode of transport
commodity involved
release cause (e.g., vehicular accident)
package failure information
monetary damage estimates
consequences: deaths, injuries, evacuations
>. quantity released
number of containers shipped
Refer to the Datafield Dictionary (Appendix B), for a complete list of HMIRS data elements.
ACCESS
Availability
Conditions
of Use
RSPA Information Systems Manager Currently, for industry, regulatory and enforcement
support, and general public requests,1 the DOT, RSPA Information Systems Manager is
the preferred contact to request specific data or obtain jnore information about HMIRS.
The RSPA Information Systems. Manager can be used to address questions about HMIRS
and to perform reasonable data searches! The cost of these searches varies, dependent on
the length and detail of the report and media requested for information. The minimum
cost for a request is $35. HMIRS information is available, to federal agencies at no cpst.
For more information contact DOT, RSPA at (202) 366-4555.
Channels for. EPA Personnel EPA Headquarters and regional personnel should contact the
Information Systems Manager at (202) 366-4555 to obtain written or electronic reports, or
alternatively to receive assistance interpreting the data.
FOIA Requests FQIA requests should be addressed to the FOIA Officer of the U.S.
DOT, Mail Code OCR 1, 400 7th Street, SW, Washington, DC 20590.
Published Information Compiled HMIRS statistics are published biennially in the
DOT/RSPA "Biennial Report On Hazardous Materials Transportation."
Generally, HMIRS data is available without conditions or usage limitations.
Data Outputs, HMIRS data and analyses can be presented as summary release information or standard
Hardware, and HMIRS reports. Both are available in hard copy or electronically on floppy disks,
Software 9-track tapes, or VAX tape cartridges.
Requirements , .
Standard HMIRS reports are either ASCII, EBCDIC, or xbase (DBF) files.
Training/
Support
The RSPA HMIRS Information Systems Manager provides support for all HMIRS-related
requests and questions. , .
HELPFUL HINTS
analysis should be sufficiently broad to minimize influence of data spikes.
Consult with the RSPA HMIRS Information Systems Manager to help focus the analysis.
The telephonic notification data is contained in the TELERNS database. This database is
jointly managed by the DOT and EPA.
-27 -
-------
-------
Acronym:
Database Name:
Agency Office:
Primary Contact:
Contact Address:
Contact Phone:
Profile
HLPAD
Hazardous Liquid Pipeline Accident Database
U.S. Department of Transportation
Office of Pipeline Safety ;
Research and Special Programs Administration
HLPAD Manager .
U.S. DOT Office of Pipeline Safety, RSPA
400 7th Street S.W.
Washington, D.C. 20590
(202) 366-4569
GENERAL DESCRIPTION
The Hazardous Liquid Pipeline Accident Database (HLPAD) is a DOT Office of Pipeline Safety
database that contains information on the accidental release of liquids. The database is a result of
the Hazardous Liquid Pipeline Safety Act of 1979. The Act requires that liquid pipeline operators
immediately notify the NRC via telephone of accidental releases. These telephone notifications
' are forwarded from the NRC to the DOT-EPA's jointly managed TELERNS database to DOT.
Pipeline operators must also submit written reports on all releases. These reports are entered into
HLPAD. The database's primary use is to fulfill the mandate of the Act, and to gather statistics
for regulatory activity and inspection priorities. Data, included in the database include background
on the carrier, background on the release, cause of the accident, and consequences. HLPAD
contains nearly 2,000 records. The database has been in existence since 1985 and is updated every
two to four weeks. .
/- -. ' . - , - '
CHARACTERISTICS OF DATA
Source Accident information from pipeline releases is submitted by the pipeline operators on
accident report forms and filed at the Office of Pipeline Safety. (See Appendix A for a
copy of the report form). The information from the accident report form is verified later
with the pipeline operator by an Office of Pipeline Safety contractor.
Scope The database contains information on any failure in a pipeline system where there is a
release of a transported commodity resulting in any of the following consequences:
explosion or fire not intentionally set by the carrier; loss of 50 or more barrels of liquid;
escape to the atmosphere of more than five barrels a day of liquified petroleum gas or
other liquified gas; death of any person; or property damage of at least $50,000. The
death of any person is verified by contacting the operator official that completed the
accident report form.
The following is a list of the types of chemicals that are reported in the database:- ,
alkylate
carbon dioxide
crude oil
butane
condensate
diesel fuel
anhydrous ammonia
fuel oil
fertilizer, ammonium nitrate
-29-
-------
HLPAD (continued)!
gasoline
kerosene
toluene
xylene
LPG
ethane
transmix
propane
jet fuel'
oil and gasoline
turbine fuel -
Data Reports are only submitted for accidents that meet the previously mentioned criteria and
Limitations are under Office of Pipeline Safety (OPS) jurisdiction; therefore, not all accidents are
included in the database. The information that is submitted by the operator may not be
altered until it is verified by the Office of Pipeline Safety and a supplemental report is
received from the operator.
DATA ELEMENTS
The following key categories are included in HLPAD:
time and location of accident
origin of release of liquid or vapor
cause of accident
commodity spilled
amount spilled
result of release (i.e., explosion, fire)
pipeline data
corrosion information
information on natural and human causes
death or injury (employees, non-employees)
total property damage
Refer to the Datafield Dictionary (Appendix B), for a complete list of data elements.
ACCESS
Availability FOIA Requests Requestors can solicit information from the HLPAD through Freedom of
Information Act (FOIA) requests. The information can be provided in either ASCII
format or hard copy. The hourly cost for the FOIA request is about $35. Contact the
FOIA Office for the Department of Transportation at (202)366-9639 for assistance with
completing FOIA requests.
Federal Government Requests Personnel from federal agencies should contact the Chief
Information Officer at (202)366-4569.
Published Information The Office of Pipeline Safety Annual Report contains specific
release information on pipelines. To request-a copy of the report, call the Transportation
Safety Institute at (405)954-4643.
Conditions Certain information within the database is considered confidential (e.g., names, addresses,
of Use phone numbers) and is therefore unavailable.
Data Outputs, The Hazardous Liquid Pipeline Accident Database is available electronically on floppy
Hardware, and disk in ASCII form or on hard copy.
Software
Requirements
-30-
-------
HLPAD (continued)
HELPFUL HINTS
When contacting the OPS, the user should specify if he or she is requesting information
on .hazardous liquid spills, so that natural gas release information is not included in the
report. , .
Pipeline accident information on fire or explosion can be accessed by searching the fire
and explosion fields. , ,
A data schema is sent to each requestor that has the database's information provided in
ASCII fixed-field form. The schema explains the coding system for fields within the
database.
-31 -
-------
-------
Acronym:
Database Name:
Agency Office:
Primary Contact:
Contact Address:
Contact Phone:
Profile
IMIS
Integrated Management Information System
Occupational Safety and Health Administration
IMIS Manager
Director, Office of Management Data Systems
Occupational Safety arid Health Administration
Room N-J661
200 Constitution Avenue N.W.
Washington, D.C, 20210
(202) 219-7008
GENERAL DESCRIPTION
The Integrated Management Information System (IMIS) is an Occupational Safety and Health
Administration (OSHA) database that contains records of workplace inspections conducted by
OSHA. Included in these inspections are investigations of workplace incidents where there is one
fatality or five or more worker hospitalizations (changedln 1993 to three worker hospitalizations).
The database is a result of inspection and information gathering, covered by Section 8 of the
Occupational Safety and Health Act of 1970, 29 USC 657.
The database is used primarily as a management information system to track OSHA's activities. It
maintains a record of OSHA's activities at each workplace that has been inspected. Data include
name and address of the worksite, employment level, results of the inspection including all
standards violated, abatement dates, any penalties accessed, and air sampling results. Data are
collected by state offices that operate their own OSHA programs and by federal offices that have
to implement the program in states that decline the program responsibility. The federal data have
been incorporated into a database since 1972, and the state data between 1982 and 1990 were
incorporated into, the database.
IMIS adds more than 120,000 inspection records a year, of which 4,000-5,000 are related to
accidents. For accident inspections, a short description of the incident is included and information
is collected relative to each worker that is injured. This information includes the extent of the
injury, coded data on the nature of the injury, and any hazardous substance that may be involved,
though the vast majority of incidents do not involve the release of a hazardous substance. After
an incident has been reported, it takes about a month for the data to be entered into the database.
Data are entered from the area offices of OSHA and downloaded daily to the national database
maintained at the OSHA Headquarters.
CHARACTERISTICS OF DATA
Source
Information from all OSHA accident inspections is gathered by the OSHA compliance
officer conducting the inspection. The data are inputted into the database at the area
offices. -.--.. ' - '.
-33-
-------
IMIS (continued) |
Scope The reporting requirement for IMIS has changed, from five to three hospiializations in the
last year. It is estimated that there are 100 incidents reported each year involving
hazardous substances. Information about specific changes in the IMIS database over time
can be obtained from the IMIS contact person.
Data Before 1990, IMIS did not contain data from some states' accident inspection reporting.
Limitations Most of the accidents that are reported in the database are not accidents that involve
chemicals. Also, when the.chemicals are reported, it is difficult to ascertain if the injury
from the accident was a direct result of the chemical that is listed in the record. For
example, if a maintenance person cleans the inside of a storage tank and is asphyxiated by
a nitrogen-rich environment, this death is not the result of an "accidental release" of a
chemical from an operation.
DATA ELEMENTS
The following key categories are included in IMIS:
name of establishment inspected
status of hazard
nature of injury
environmental factor
(e.g., earthquake, chemical reaction)
description of accident
number of employees exposed to hazard
information on person(s) injured
source of injury
event type
hazardous substance
ACCESS
Availability
Conditions
of Use
OSHA Contact Line The IMIS database and information about IMIS are available by
contacting the OSHA contact person. An OSHA staff person will assess the query and
supply the requested information. The information in IMIS is usually free, but there may
be a cost, usually under fifty dollars, if there is extensive analysis or data formatting
involved.
CD-ROM OSHA is considering making the IMIS database available to the public on CD-
ROM. ' .
Published Information There is an annual report, prepared by OSHA for Congress,
specific to released hazardous substances.
The information in the database is not considered confidential, however, the database
screens the names of the persons that have been injured.
HELPFUL HINTS
Search the hazardous substance field to identify the less than 300 major hazardous substance
releases. To further -identify those records that directly relate the hazardous substance release with
a consequence (e.g., death, injury), search the event type data field for fire, explosion, gas release,
etc. The search could be focused on records in the petroleum and chemical industry. For the
records identified through the initial screening, the requestor might have to read through each
description paragraph and determine whether the consequences are linked to a hazardous
substance release.
-3.4-
-------
Acronym:
Database Name:
Agency Oftice:
Primary Contact:
Contact Address:
Contact Phone:
Pmfite
HSEES
Hazardous Substances Emergency Events
^Surveillance
Agency for Toxic Substances and Bisease Registry
HSEES Manager
Agency for Toxic Substances and Disease Registry
Public Health Service
Atlanta, Georgia 30333
(404) 639-6203
GENERAL DESCRIPTION
The Hazardous Substances Emergency Events Surveillance (HSEES) system is an Agency for
Toxic Substances and Disease Registry (ATSDR) database that describes the release or threatened
release of hazardous substances and the resulting public health consequences (e.g., death, injuries,
evacuations). The primary focus is acute effects. The database was developed because ATSDR
determined that the public health consequences of hazardous substance releases have not been
adequately characterized by other databases. The database, implemented in 1990, is based on;
state-collected data. As of January 1, 1995, 14 state health departments collect data for HSEES,
by documenting the total number of hazardous substance emergencies that occur within their
respective states. During 1990-1992, 3,125 events were reported from participating states. The
HSEES's primary purpose is to determine the distribution of hazardous substance emergencies, to
identify the morbidity and mortality experienced by employees, responders, and the general public,
to identify risk factors associated with the morbidity and mortality, and to establish prevention
strategies.
CHARACTERISTICS OF DATA .
Source
Scope
Once a hazardous substance emergency has occurred within a participating state, the state
agency notifies the health department within 48 hours. The state health department then
.collects information about_the emergency on a data collection form and enters it into a
dBase IV program. The data collection forms, designed by ATSDR, include information
on the event, chemicals, victims, injuries, and evacuations. State health departments use a
variety of data sources, such as records or personnel from state environmental protection
agencies, police or fire departments, or hospitals. On a quarterly basis, the state health
departments send electronic data to ATSDR.
Hazardous substance emergency events are defined as uncontrolled or illegal releases or .
threatened releases of chemicals, or their hazardous by-products. The reportable
chemicals include all hazardous substances except petroleum products.
Events are included in the database when the amount of product released needs to be
removed, cleaned up, or neutralized according to federal, state, or local law; or when there
is only a threatened release of one of the chemicals listed above, but this threat leads to
an action (e.g., evacuation). Victims are defined as those individuals who suffer at least
-35-
-------
HSEES (continued) fc
one injury as a consequence of the event. HSEES includes data on hazardous substance
emergencies for both transportation and fixed facility events.
Data Quality/ The information from the data collection is considered reliable because it is an active
Limitations state-based system that collects data in a timely fashion. Data completeness is assessed
quarterly through error-checking programs, and system sensitivity is assessed in
comparison with events reported to national databases. Consistency of data reporting
between states is ensured by training manuals, case studies, and a newsletter clarifying
questions from participating states.
DATA ELEMENTS
The following key categories are included in the Hazardous Substances Emergency Event
Surveillance: . '
event identification and notification
morbidity and mortality
types of injuries (e.g., trauma, nausea)
evacuation and in-place sheltering
substance, chemical, or trade name
exposure or potential exposure population within
specified radii of the event
demographic characteristics of victims
ACCESS
Availability
The HSEES database is not intended to be directly available to the public or other
interested parties. Instead, the information is available through requested searches and
published results.
Federal Government Requests Personnel from Federal agencies should contact the HSEES
Manager at (404) 639-6203.
Published Information' There is an annual report called the Hazardous Substances
Emergency Events Surveillance Annual Report. To request a copy of the report, contact
the HSEES Manager at (404) 639-6203. Summaries of analyses are published periodically
in journal articles. Publications include:
Hall HI, Dhara VR, Kaye WE, Price-Green, PA., "Surveillance of Hazardous
Substance Releases and Related Health Effects". Archives of Environmental
Health. January/February 1994, Volume 49(1); pages 45-48.
Hall HI, Dhara VR, Price-Green, PA, Kaye WE., "Surveillance for Emergency
Events Involving Hazardous Substances - United States 1990-1992", MMWR.
Center for Disease Control Surveillance Summaries. July 22, 1994, Volume 43, No.
SS-2.
-36-
-------
Short Descriptions of Additional Federal Release Information/Databases
The following databases and information sources were not featured as profiles, but they do contain
certain chemical release information. They were developed to meet federal agency goals and to satisfy
regulatory requirements.
1. Coast Guard Marine Safety Information System (MSIS): DOT
The Marine Safety Information System (MSIS), maintained by the United States Coast Guard,
gathers information on about 12,000 fixed facilities and transportation accidents per year. Chemicals
covered include petroleum, and CERCLA and non-CERCLA substances.
MSIS automates critical Coast Guard data gathering activities to provide support to overall
mission performance. The data includes vessels' history, waterfront facilities, involved parties, and vessel
owners and operators. The information is used to prioritize boardings to maximize use of Coast Guard
resources for prevention, response, investigations, ship inspections, and pollution response.
MSIS is accessed by Coast Guard Marine Safety Offices throughout the United States, district
offices, and headquarters. MSIS captures the majority of the data that the Office of Marine Safety,
Security and Environmental Protection uses to carry out its missions.
2. Acute Hazardous Events (AHE) Database: EPA
The Acute Hazardous Events database, developed by EPA, provides a historical perspective on the
magnitude of chemical accidents in the United States in response to the Bhopal, India disaster. The
database contains about 6,200 records that represent information on roughly 11,000 incidents that occurred
primarily between 1982 and 1986. Data on the events were collected from a variety of sources including
the United Press International (UPI), Associated Press (AP), 26 daily newspapers, EPA Region VII office
files, six offices of five state governments, and from spill reports to the National Response Center (NRC).
The data collection was only intended to provide a "snapshot" of the number of chemical accidents
occurring at fixed facilities and transportation, fire and explosion events, toxic releases, and the degree of
deaths, injuries, evacuations and environmental damage associated with these kinds of incidents in the
United States. The data is provided by secondary sources and has not been thoroughly verified.
Therefore, caution should be used when interpreting certain findings.
3. Pollution Reports (POLREPS): EPA/Coast Guard
POLREPS are files and reports from follow-up removal actions of reportable quantity (RQ)
events, as required by 40 CFR 300.135(m). The U.S. Coast Guard On Scene Coordinator (OSC) submits
pollution reports (POLREPS) to USCG District Commanders, and to the Director, Emergency Response
Division of EPA for the purpose of communicating CERCLA response and fund obligation data to EPA
POLREPS provide factual operational data relating to a release, specifically, a site description, incident
description, preliminary assessment results, response activities, and project cost information. The initial
POLREP will be sent within 24 hours of initiating a response action, if information is available. Once the
initial report is completed, POLREPS would be sent on a routine basis (daily, or as significant
developments warrant). When the Regional Response Team (RRT) is activated for a specific incident, the
RRT shall submit POLREPS to the NRC in a timely manner as significant developments occur (but not
later than 1600 local time on each day of operation). '
-37-
-------
4. CERCLIS: EPA
EPA's Office of Emergency and Remedial Response maintains CERCLIS, a national computerized
program management and inventory system for sites reported to Superfund for potential remediation.
CERCLIS contains information on all aspects of potential hazardous waste sites from initial discovery to
listing on the National Priorities List (NPL). Data provided in CERCLIS include site names, geographic
location, remedial actions taken or proposed under the Superfund program, and major events in site
cleanup. CERCLIS operates on the EPA mainframe computer. Regional program offices and, to a
limited extent, the U.S. Corps ,of Engineers enter new facility reporting data directly into the system and
update old data periodically. CERCLIS use is restricted to EPA and other government agencies. Reports
and tapes containing the site inventory and site assessment activity information are available from NTIS.
5. OSC/NRT Reports: EPA/Coast Guard
Current CERCLA regulations require the submission of OSC reports within one year of
completion of removal actions, or when requested by the Regional Response Team. The original purpose
of these reports was to summarize activities at the site, communicate lessons learned, discuss any problems
encountered in the response, and recommend improvements that need to be shared throughout the
response community. OSC reports should cover all of the topics listed at 40 CFR 300.165(b), and
reference other information sources such as the administrative record, the pollution reports, the site log
book, and the OSC log book. On October 22, 1993, EPA proposed in the Federal Register to delete the
current requirement in ง300.165 to prepare OSC reports for all responses to major discharges or releases.
In revising the National Contingency Plan, EPA has recognized that OSCs have extensive responsibilities
and that responding to discharges is a higher priority than drafting the OSC report. As requested by the
NRT or RRT on a case-by-case basis, however, the OSC or remedial project manager (RPM) shall submit
to the NRT or RRT a complete report on the removal operations and the actions taken. These new
regulations went into effect in October 1994 (30 days after publication of the final rale in the Federal
Register on September 15, 1994).
6. Toxic Release Inventory (TRI): EPA
The Toxic Release Inventory (TRI) is a publicly available database that contains information on
routine emissions and accidental releases of specific toxic chemicals from manufacturing facilities
throughout the United States. This inventory was established under the Emergency Planning and
Community Right-to-Know Act of 1986 (EPCRA), which Congress passed to promote planning for
chemical emergencies and to provide information to the public about the presence and release of toxic and
hazardous chemicals in their communities. Following passage of the Pollution Prevention Act of 1990, the
TRI was expanded to include mandatory reporting of additional waste management and pollution
prevention activities, and the list of substances was expanded from about 300 to nearly 600 for the 1995
reporting year. The chemical-specific and facility-specific information collected under these laws can be
used by the public to identify facilities and release patterns that warrant further study and analysis.
Combined with hazard and exposure information, TRI has been used for risk identification. As of 1992,
the TRI included over 80,000 reports from approximately 23,000 facilities each year. However, it captures
only a portion of all toxic chemical releases nationwide. Facilities that have fewer than 10 employees, do
not meet chemical thresholds, of are non-manufacturers are not required to file TRI reports.
-38-
-------
7. Occurrence Reporting and Processing System (ORPS): DOE
The Occurrence Reporting and Processing System database provides the Department of Energy
(DOE) with a readily accessible database containing information about occurrences1 at DOE facilities,
causes of those occurrences, and corrective actions. This information can.be used to identify and analyze
trends in occurrences. The database resides on a host computer at the Idaho National Engineering
Laboratory in Idaho Falls, Idaho, and can be accessed from any DOE site via computer 24 hours a day.
Since September 1, 1990, approximately 6,000 to 8,000 occurrence reports have been entered annually.
8. Natural Gas Pipeline Incidents: DOT
Release information on natural gas pipelines is collected in a reporting system by DOT's Office of
Pipeline Safety. This system contains the number of natural gas pipeline fatalities, injuries, dollar amount
of property damage, location and time of incident, cause, and where/what part of the system failed. The
database contains over 2,400 records since data was collected in 1984.
9. National Fire Incident Reporting System/FEMA (NFIRS): USFA
The National Fire Incident Reporting System (NFIRS), maintained by the U.S. Fire
Administration (USFA), is a data collection system with information on fires. NFIRS gathers data from
41 states. In 1990, data on hazardous materials incidents began to be collected in the NFIRS System. In
the first year, information was collected from only five or six states and approximately 85 incidents were
recorded. The first full year that data were collected using this system was 1991; however, only a small
number of states were involved. In 1992, states representing approximately 210 fire departments were
supplying data. For the first half of 1992, over 600 hazardous materials incidents were reported. Among
the data fields used in this system are the type of site (fixed or transportation), the chemical involved, and
the injuries and deaths resulting from the incident. NFIRS has been used to analyze factors involved in
fire incidents and, in some cases, has brought about changes leading to increased safety. -
Under DOE Order 5000.3A, occurrences are defined as all events or conditions that could: (1)
affect the health and safety of the-public; (2) seriously impact the intended purpose of DOE
facilities; (3) have a noticeable adverse effect on the environment; or (4) endanger the health and
safety of workers. Occurrences are categorized by their seriousness to ensure the more serious
occurrences are highlighted to management. The categories are defined in DOE Order 5000.3A
-39-
-------
-------
IV. QUICK CROSS REFERENCE TO DATABASES
Quick cross references to the federal accident release databases enable the user to compare
databases and determine which ones provide relevant information. While a detailed description of each
database is valuable, users should review cross references and summary data. Such review is especially
useful if users are unsure which database will meet his or her needs or if users want a quick comparison of
the information in the databases. The following four exhibits in this section serve as cross references: '
Exhibit 4: Quick reference on scope of databases
Exhibit 5: Comparison of data elements in databases
Exhibit 6: Specific database information contained in each data element
Exhibit?: Top five chemicals Or substances (non-petroleum) found in each-database
Users who are largely unfamiliar with the databases may need to start with Exhibit 4 to decide which
databases are most appropriate for their analyses. Users may wish to consult Exhibits 5, 6, and 7 to
further match a database to their specific informational demands. Users who.already have a detailed list of
informational requirements may wish to start with Exhibits 5 and 6.
Exhibit 4 briefly reviews the scope of each of the seven federal accident release databases and
includes Such information as the government agency providing the database, chemicals covered, number of
records, and selection criteria. The exhibit also comments on data limitations and quality issues such as
the degree of verification, whether the information is based on notifications, and whether there are missing
data. From the exhibit, the user can gain a quick comparison of and "feel for" the databases and can
screen the databases for the general types of releases included.
Exhibit 5 provides a comparison of the data elements in the seven databases. Data elements (e.g.,
date gf release, primary release cause) are grouped into Seven broader data categories: event reporting
information, facility/release location, release information, release cause, damages, cleanup action, and
general remarks. A check mark indicates if a data element is addressed in a particular database, though.
data elements may not be in the same format (e.g., coded, text). Users will benefit most from this exhibit
once they have already defined the types of data elements to be included in their information request of
analysis. Also, a reference page number is provided for each data element that refers the user tq more
detailed information in Exhibit 6.
Exhibit 6 includes a description of the types of database information contained within each data
element of the databases. This exhibit is helpful when the user's proposed data search or analysis demands
a close look at the way the database covers specific; types of information under each data element. For
example, if the analysis requires the distinction between employee injuries and public injuries, the user
should consult this exhibit to identify databases that make this distinction.
Exhibit 7 lists the five most frequently reported chemicals or substances (non-petroleum) in each
database. The chemicals that are reported are indicated with a check mark. Users will find this exhibit
helpful in attempting to determine which databases have the most information on particular chemicals
(e.g., ammonia). ~
-41-
-------
EXHIBIT 4
QUICK REFERENCE: SCOPE OF DATABASES
DATABASE SCOPE
Government agency
Chemicals covered
Industries covered
Transportation-related?
Fixed facility-related?
Number of records
FEDERAL DATABASES
IRIS
NRC
CERCLA
hazardous
substances, oil
products, and
other substances
All
Yes
Yes
-33,000 per
year/330,000
since 1982
ERNS
EPA
CERCLA
hazardous
substances, oil
products, and
other substances
All
Yes
Yes
-42,000 per
year/~300,000
since 1986
ARIP
EPA
CERCLA and
EPCRA listed
chemicals
All
No
Yes
, -4,800
HMIRS
DOT
EHMTL
chemicals; also
CERCLA
hazardous
substances,
petroleum,
explosives,
pesticides,
others
Hazardous
materials
carriers and
shippers
Yes
No
15,000 reports
per year/
-220,000 total
HLPAD
DOT
20 chemicals
covered as ,
petroleum and
toxic products
Pipeline
carriers of
hazardous
liquids
Yes
No
-200 per
year/ป2,000 total
IMIS
OSHA
All hazardous
. substances,
liquids, dust
particles,
petroleum
products, gases,
flammable
liquids
All
Possible
Possible
-120,000
inspections per
year
HSEES
ATSDR
All hazardous
substances
except
petroleum
products
All
Yes
Yes
3,125 records
from 1990-92
-42-
-------
EXHIBIT 4 (continued)
QUICK REFERENCE: SCOPE OF DATABASES
DATABASE SCOPE
Criteria for selecting
releases ,
... r . . . .
.''
Limitations/Quality:
1) Information
Verified?
2) Notification
Information?
3) Missing data?
:" 4) Comment '
: : " '." "
r- . - .-. ,.-...:.
t
Years collected
FEDERAL DATABASES
IRIS
1) Release
above
reportable
quantity (RQ);
2) oil release
violates water
standards,
causes a film,
sheen, or
sludge; 3) other
chemical release
meets HMTA
or pipeline
safety criteria
Sortie
Yes
Yes
Impacts may
not be related
to chemical
release; some
inaccuracies
because data
source is only
initial
notification
1974 - present
: ERNS
1) CERCLA
release above
reportable
quantity (RQ);
2) oil release
violates water
standards, causes
a film, sheen, or
sludge; 3) other
chemical release
meets HMTA or
pipeline safety
criteria
Most not
.Yes
!.' Yes .
Impacts may not
be related to
chemical release;
some
inaccuracies
because data
source is only
initial
notification ,
1986 - present
ARIP
Subset of ERNS
releases and
meets one of
four ARIP
criteria:
1) causes
death/injury;
2) multiple of .
RQ; 3) repeat
release; 4) EHS
'
Yes
. No
" ' No -. '
Only most
severe accidents;
criteria and
ARIP,
questionnaire
has changed
over time,
therefore, not
all data are
consistent or
comparable
1986 - present
HMIRS
Any
unintentional
release of
hazardous
material during
the course of
transportation
Yes
Yes with follow-
UP
Yes ,
Sometimes
chemical
information
provided as
category (e.g.,
flammables) ,
rather than
individual
chemical name
1971 - present
HLPAD
Explosion/fire,
or loss of 50 or
more barrels of
liquid, or release
of more than
five barrels per
day of liquified
gas, or death, or
property damage
of at least
$50,000 :..''
1
: Yes
Yes with follow-
up
'. N'o
Not all liquid
pipeline'
accidents are
reported in
database
1985 - present
IMIS
No release
trigger, incidents
-selected if
involves 3
injuries
-requiring
hospitalization
...
' '
Yes
Yes with follow-
UP /
, No
Injuries or
, deaths may not
be related to
chemicalrelease
, .
,;!, . .. .
1972 - present
HSEES
All hazardous
substance
releases except
petroleum
.products
occurring in the
participating
states are
.included
,
.
Yes
Largely not
No
Current '
information in
database is
collected from
14 state health
departments
" ' .
1990 -present
-43-
-------
EXHIBITS
COMPARISON OF DATA ELEMENTS IN FEDERAL HAZARDOUS SUBSTANCE RELEASE DATABASES
DATA CATEGORY
Event reporting information
Facility/release location
Release information
Release cause
DATA ELEMENT
Reporting party
Date and time reported
Facility name and address
Release location
Date and time of release
Transportation release
Facility release
Substance involved
Quantity/concentration
Affected medium
'End result/type of release
Primary cause
Secondary cause
Packaging/equipment
information
FEDERAL DATABASES
IRIS
/
/
/
/
/
/
/
/
/
/
/ .
/
ERNS
/
/
/
/
/
/
. /
/
/
/
/
/
ARE?
/
/
/
/
/
/
/
/
/
/
/
/
HMDRS
/
/
/
/
/
/
/
/
/
/
/
HLPAD
/
/
/
/
/
/
/
/
/
/
/
IMIS
/
/
/
/
/
/
/
/
/
/
HSEES
/
/
/
/
/
REFERENCE
PAGE FOR
MORE INFO.
47
47
48
48
49
49
49
49
'49
50
50
51
51
51
-44-
-------
EXHIBIT 5 (continued)
COMPARISON OF DATA ELEMENTS IN FEDERAL HAZARDOUS SUBSTANCE RELEASE DATABASES
DATA CATEGORY
Damages
Cleanup action
General remarks
DATA ELEMENT
Deaths
Injuries
Evacuation
Property damage
Environmental damage
Stabilization and control
measures
Notification
Prevention/repairs
General remarks
FEDERAL DATABASES
IRIS
/
/
/
' / ' ,
/
/
/
/
ERNS
/
/
/
/
/
/
/
/
/
ARIP
/
/
/
/
/
/
/
/
HMIRS
/
/
/
/
/
/
/
HLPAD
/
/
/
-
/
/
IMIS
/
/
/
HSEES
/
/
/
;,
REFERENCE
PAGE FOR
MORE INFO.
52
' 52
52 ."
52 ',
'. 52 .
53
53
53
53
-45-
-------
-------
; EXHIBITS
DATABASE INFORMATION CONTAINED IN EACH DATA ELEMENT
DATA CATEGORY: EVENT REPORTING INFORMATION
DATA ELEMENT
Reporting party
Date and time reported
FEDERAL
DATABASES
IRIS
ERNS-
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
DATABASE INFORMATION
Individual/company, address , ,
Individual/company, address
Questionnaire respondent
Individual/company, address
Operator information "
Accident compliance officer .
Date, time
Date, time
,
Date, time
Date, time -
Date
.'"'-,- : ''. "' '
-47-
-------
EXHIBIT 6 (continued)
DATABASE INFORMATION CONTAINED IN EACH DATA ELEMENT
DATA CATEGORY: FACILITY/RELEASE LOCATION
DATA ELEMENT
Facility name and address
Release location
FEDERAL
DATABASES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
DATABASE INFORMATION
Company, address, city, county, state
Company; address, city, county, state, Dunn and Bradstreet number
Facility name, facility address, owner name, owner address, Dunn and
Bradstreet number
Carrier, address, city, state
Company name .
Facility name, address, city, state
.
Spill location, city, county, region
Spill location, city, county, region, longitude/latitude, address in
comment field
Location of release within facility, longitude/latitude
Location of incident (city, county, state, route)
Spill location (city, county, state, offshore coordinates)
Same as facility name and address
-48-
-------
EXHIBIT 6 (continued)
DATABASE INFORMATION CONTAINED IN EACH DATA ELEMENT
DATA CATEGORY: RELEASE
DATA ELEMENT
Date and time of release
^
Transportation release
- '' - ' ' - '
. -'
Facility operations and
release
Substance involved
-
- ' '
: INFORMATION
FEDERAL
DATABASES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
;IRIS .
ERNS
ARIP
HMIRS
HLPAD
IMIS .
HSEES
IRIS
, ERNS '
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
DATABASE INFORMATION
Date, time
Date, time ,
Date, time release occurred; date, time release ceased
Date, time ."..'
Date, time .
Sometimes provided in general comment field " . .-
Date, time . ' ,
Transportation mode, vessel/vehicle number .: . . ' '
Transportation mode, vehicle number, indicates if release caused by
transportation accident - .
' " " " ' - -'""-'. ~ ,
Mode of transport, shipment information,, type of vehicle
Year equipment installed, above/below ground pipeline '
' . ' ' " --.-""
-Indicates transportation release . "
Capacity of facility
Capacity of facility, indicates if fixed facility release
Year operations began, SIC code, primary product, status of operations at time
of release, current status of operations , " . ', . .
,
Sometimes provided in comment field: SIC code, facility violations
Indicates fixed facility release
CHRIS code, material name
CHRIS code, material name, CAS number
Chemical name, CAS number, physical state
Shipping name, trade name, hazard class_
Commodity spilled
Hazardous substance code
Chemicals (grouped by categories)- can record several chemicals per release
-49-
-------
EXHIBIT 6 (continued)
DATABASE INFORMATION CONTAINED IN EACH DATA ELEMENT
DATA CATEGORY: RELEASE INFORMATION
DATA ELEMENT
Quantity/concentration
Affected medium
End resuItAype of release
FEDERAL
DATABASES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
DATABASE INFORMATION
Quantity, quantity in water, units
Quantity, quantity in water, units
Quantity, units, concentration, method/source of information
Quantity, units . ' '
Amount spilled in barrels
Medium type (air, groundwater, land, water), waterway affected
Medium (air, groundwater, land, water, within facility, codes for specific
water/land body affected (e.g., canal), name of waterway)
Quantity released to each media (air, water, land, treatment facility), unit,
method/source of information
Spill, vapor release, fire, explosion, etc.
Spill, vapor release, fire, explosion, etc.
Fire, explosion .
Some information in source of injury codes (fire, pressure)
-
-50-
-------
EXHIBIT 6 (continued)
DATABASE INFORMATION CONTAINED IN EACH DATA ELEMENT
DATA CATEGORY: RELEASE CAUSE ,
DATA ELEMENT
Primary cause
Secondary cause
Packaging/equipment
information
FEDERAL
DATABASES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
- HSEES
DATABASE INFORMATION
Transportation accident, equipment failure, operator error, etc.;
description of cause
Transportation accident, equipment failure, operator error, etc.
Equipment failure, operator error, upset condition, 'etc.
General cause
Corrosion, failed weld, operator error, etc.
Human and environmental (e.g., earthquakes) factor codes
-..'--
Recently added 50 secondary cause codes
Same as for primary cause .-...
Container type ,
Container type, source of release
Condition of releasing equipment at time of release
Nature of packaging failure, packaging information
Place of release (e.g., valve, tank), system involved (line pump, tank
farm), pipe tests
Sometimes provided in comment field
-51-
-------
EXHIBIT 6 (continued)
DATABASE INFORMATION CONTAINED IN EACH DATA ELEMENT
DATA CATEGORY: DAMAGES
DATA ELEMENT
Deaths
Injuries
Evacuation
Property damage
Environmental damage
FEDERAL
DATABASES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS.
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
IRIS
ERNS
ARIP
HMIRS
, HLPAD
IMIS
HSEES
DATABASE INFORMATION
Number, sometimes additional information in comment field
Number, sometimes additional information in comment field
Yes/no; number among facility employees, general public, contractor, responder
Number
Number of total deaths, employee deaths, non-employee deaths
Information on person(s) killed
Deaths of employees, responders, public; age and gender profile
Number, sometimes additional information in comment field
Number, sometimes additional information in comment field
Number injured and number hospitalized among facility employees, general public,
contractor, responder
Number of minor and major injuries
Number of total injuries, employee injuries, non-employee injuries
Hospitalized, non-hospitalized, type (burn), body part injured
Number and type of injuries (trauma) for employees, responders, public; age and gender
profile
Yes/no, number evacuated, sometimes additional information in comment field
Yes/no, number evacuated, sometimes additional information in comment field
Number of facility employees, public, contractors, responders evacuated or sheltered;
date and time
Number evacuated
Evacuation and in-place sheltering
Yes/no, dollar amount, sometimes additional information in comment field
Yes/no;' dollar amount, sometimes additional information in comment field
Recently added" facility costs, public costs
Dollar estimate
Dollar estimate
-.
Air pollution, sewage, water quality, sometimes additional information in comment field
Release threat (drinking water contamination, ecological damage, soil contamination,
wetlands contamination, etc.), sometimes additional information in comment field
Yes/no (fishkills, vegetation damage, groundwater contamination, etc.)
Yes/no
Contributing environmental factors
-52-
-------
EXHIBIT 6 (continued)
DATABASE INFORMATION CONTAINED IN EACH DATA ELEMENT
DATA CATEGORY: CLEANUP ACTION .
DATA ELEMENT
Stabilization and control
measures
Notification
Prevention/repairs
FEDERAL
DATABASES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS-
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS '
HSEES
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
HSEES
DATABASE INFORMATION
Description , . ;
Description . .
Yes/no cleanup, party responsible, date cleanup ceased, completion date, immediate
response activities
. - , - - . ,
-'"'. : . .
Notification of federal (e.g., OSHA, FEMA, DOD, EPA) and state authorities, caller
notifications
Notification of federal (e.g., OSHA, FEMA, DOD, EPA) and state authorities, caller
notifications
Notification of federal,' state, and local authorities, general public; time; persons
Organizations contacted, caller notifications
Telephone report, time
Actions taken to correct or mitigate incident (comment field)
Actions taken to correct or mitigate incident (comment field)
Prevention practices and policies when release occurred, equipment repairs and/or
replacements, preventive measures, hazard evaluations, training - '
Existence of damage prevention program
Use of personal protection equipment
DATA CATEGORY: GENERAL REMARKS -
DATA ELEMENT
General remarks
FEDERAL
DATABASES
IRIS
ERNS
ARIP
HMIRS
HLPAD ,
IMIS.
HSEES
DATABASE INFORMATION
Miscellaneous information ' .
Miscellaneous information
Miscellaneous information
Summary of incident
-53-
-------
-------
, EXHIBIT?
TOP FIVE CHEMICALS OR SUBSTANCES (NON-PETROLEUM) IN EACH FEDERAL ACCIDENTAL RELEASE DATABASE
CHEMICAL/
SUBSTANCE
Acids
Ammonia
Ammonium nitrate
fertilizer
Carbon dioxide
Chlorine
Compound cleaning
liquid corrosive
Corrosive liquid nos
Ethykne glycol
Flammable liquid nos
Herbicides
Hydrogen suffide
Metals
Methylene chloride
Pofychlorinated
JSiphenyls
Resin solution
Sulfur dioxide
Sutfuric add
Volatile organic
compounds
ote: Data based on cumu
1HLPAD contains primaril
FEDERAL DATABASES
HUS
/
/
y
/
/ ' "
ERNS
/
/
/
,
'" S ,
/
ative reports lor iKls, JiKJNtJ, AK1F, 1
y petroleum-related data; four chemical
ARIP
V
!.
V
/
/
^
HMIRS
/
/
/
/
/
HLPAD1
/
/
/
/
IMIS
/
'/
/
/
/
/' .
" i
HSEES
/
/
/
/
/ - ''
VliS, and HSEiiS, and on Iyy3 reports lor hlMlKS. ,
s are reported in the database. ; . ' '
-55-
-------
-------
V. LOOKING TO THE FUTURE - LINKING DATABASES
Most analyses of accidental releases are addressed within the scope of a single database. Although
within the family of federal accidental release databases considerably larger" numbers of incidents can be
found and in most cases more extensive and accurate information on incidents exist, few. users have ever
searched using more than a single database. This is because it is difficult and cumbersome to link an
incident from one database to the same incident in another database since most federal accidental release
databases lack comparability. Given the importance of the information that has been collected and the
value of being able to assemble this information and gain a better understanding of various accidental
releases as well as a more complete national (as well as regional, state or local) picture of the types of
releases that are taking place, this chapter begins to address the issue of database linkages by discussing
the value of linking the databases, general approaches for performing various types of linkages, and future
opportunities for conducting comprehensive searches on linked databases.
Value of Linking Databases
Many users of this guide, including federal, state, and local officials, industry, environmental
groups, and the public, are interested in conducting comprehensive searches and analyses that span several
different databases. Described below are ways that linked databases can benefit such users.
Support Public Policy and Regulatory Analyses and Decisions. A comprehensive analysis of the
"accident problem" by examining multiple accident databases may be necessary for certain policy and
regulatory decisions. The absence of comparable databases slows any analyses of accident data and limits
the information available for public policy analyses and decisions. Policy issues and regulatory analyses
whose scope extends beyond one or two databases are candidates for database linkage. Efforts to link
databases are time-consuming and require careful planning. If such linkages were already established,
more thorough comprehensive analyses could be applied to public policy .decisions.
Enhance Enforcement/Inspection/Accident Investigation. Easy access to linked databases may help
federal and state officials set priority for enforcement and inspections of facilities. Linked data may also
directly point to a lack of compliance in reporting. For example, HMIRS is'periodically linked to the
railroad and highway accident databases to compare records and to identify incidents that should have
been reported to HMIRS by the carrier or responsible party. The linked information may also provide
additional background for the facility visit/accident investigation and may point to certain problems and
potential release prevention measures.
Support Special Studies. Special studies such as the Report to Congress on Hydrogen Fluoride
would have benefitted from comparable federal accidental release databases. The Hydrogen Fluoride (HF)
study examined separately the ARIP, HMIRS, and ERNS databases: Conclusions about HF releases were
provided for each database. In addition, a linked database was necessary to provide a few overall findings.
Combining the databases for this specific study proved a time-consuming, costly, and difficult task.
Support Coordination of Accident Analyses among Government Agencies. Promoting comparable
databases would encourage coordination among government agencies. Agencies might share insights,
skills, and accident analyses. For example, regular meetings of an existing multi-federal agency accident
work group provides a forum for the agency representatives who maintain the accident databases to .learn
and discuss database coordination issues. Other forums to encourage database coordination include
conferences, regular meetings through the National Response Team, an interagency task force, and
newsletters. .
-57-
-------
Enhance International Cooperation. International cooperation and information exchange .is
becoming increasingly important with growing concerns about hazardous substance use, past catastrophic
accidental releases, and the potential for cross-border accidents. Information exchange on releases of
hazardous substance incidents can build trust and international support fo prepare for, prevent, and
respond lo such incidents. Coordination of accidental release databases in the United States could provide
important, comprehensive information and analyses to be shared with other countries. For example, as a
delegate to the Group of Experts on Chemical Accidents sponsored by the Organization for Economic Co-
operation and Development (OECD), the United States and other countries have agreed to complete an
accident form if an incident meets certain criteria. To decide if the incident meets the criteria and to
complete the form, the U.S. will need to rely on several different databases. Linked databases that are
updated periodically can provide a centralized resource for one federal agency to complete the accident
form efficiently within the required two week period after a major release event.
Linking Databases .
What is meant by linking databases? Linking can mean several different things. It could mean
that connections or bridges are-established among the databases through common release identifiers (e.g.,
release date, facility name) to enable the user to access various database information on a particular
incident. This linkage basically establishes a pointer system which allows quick identification .of release
information in the individual databases, but preserves the integrity of each. For example, a linkage would
enable a user to search for a release on October 1, 1992 at Facility X in any of the databases and access
particular release information contained in each database. This linkage is valuable if specific release
information, not aggregate analysis, is desired.
Linking can also refer to the combination of several databases into one. A combined database
enables more comprehensive aggregate analysis but leaves data gaps (because different information is
contained in different databases). Such a linkage also requires difficult choices when discrepancies in
information exist among databases to be combined. Decisions must also be made about whether an
information category in one database (e.g., release quantity to water) is truly the same category of
information in another database (e.g., release quantity to navigable waterway).
A third kind of linkage*could result in a smaller scale combined database. This linkage would
combine only data elements (information types) that are common to most databases. The purpose is to
increase the number of release records .available (after eliminating duplicates) for the analysis without
including unique information from individual databases (e.g., environmental damage) that would
complicate a linkage. This linkage eliminates data gaps and enables core aggregate analysis (e.g., number
of releases per year in the U.S.) to be conducted.
One possible use of a smaller scale combined database would be to perform an analysis on a
specific chemical. For example, selected data elements on hydrogen chloride releases in ARIP could be
directly appended to the hydrogen chloride data elements from HMIRS because the databases have
different scopes (e.g., ARIP covers fixed facility and HMIRS covers transportation releases). Then, the
common data elements "number of major/hospitalized injuries" and "quantity released" could be analyzed
to determine, for example, the relationship between release size of hydrogen chloride and number of
injuries. Even with this relatively simple linkage and analysis, there is at least one issue to resolve. The
ARIP database has separate data elements that pertain to hospitalization of facility employees, contractors,
responders, and the public. The numbers will have to be totalled and placed in a new data element which
can then be appended to the HMIRS data element on the "number of major/hospitalized injuries".
-58-
-------
Basis of the Linkage.-Common Data Elements
Data elements refer to the specific type of information contained in the database. Examples
include time and date of release, substance and quantity released, and number of injuries. A requirement
for performing any of the above database linkages is to identify key common data elements which can be
used to establish linkages. Data elements in one database are common to data elements in another
database if the information contained in them is similar. For example, "release quantity" from one
database could be considered common to "spilled quantity" in another database. However, the precise
definition of the data elements, which often differs among databases, should be acquired and evaluated
before data elements are considered common.
Common data elements do not mean that the data are always directly comparable. For example,
release quantities may still be common even though one database may list the release quantity in pounds
and the other database lists it in gallons. Also, "chemical released" is considered a common data element
though one database may provide the information as a formal name and another may list it as a CAS
number. In addition, common data elements usually have.different computer formats for the information
(e.g., field width, field type as character or numeric). Differences such as those listed above can be
adjusted for consistency.
A side-by-side comparison was performed of the seven, federal accidental release databases
featured in this user's guide to identify common data elements. The data elements that are common to at
least five of these databases include:
Facility name/address
Release quantity/concentration
Chemical released
Release state
Release city
Time/date of release
Primary cause
NRC number
Packaging/equipment information
Number of deaths
Number of injuries
Number of evacuees-
Reporting party
Property damage ' , - -
Type of release (transportation, facility)
Although the data elements are common, the precise way the information is expressed and the computer
format may differ from database to database.
Most common data elements are not useful for linking databases because they are not release
specific (e.g., chemical name) or do not contain easily matched information (e.g., release quantity). There
are only a few data elements that are common to most databases and could potentially link databases by
matching release records. These data elements include release date, facility name, and release state, city,
and NRC number. The advantages and disadvantages of using these data elements are considered below.
Release date, facility name, release city, release state. Release date can be-used with facility or other
release-specific information to match release records from one database with release records from another
database. However, these common elements release date, facility name, release city, release state are
not without foreseeable problems. Exhibit 7 lists the different formats of these data elements and
indicates the need to standardize these formats for field type (e.g., text, numbers, date) and field width.
Most databases contain release date in a consistent format (morith/day/year), but some reports have an
uncertain date. The facility name is subject to misspelling, varied versions, or confusion with the name of
the parent company. The release city can be subject to misspellings and misinterpretation. The release
state is the most consistently accurate, as all databases use the two letter abbreviation. Several format
-59-
-------
widths were changed in the ARIP database to be consistent with the format widths for most of the other
databases. These changes in the ARIP database are already reflected in Exhibit 7.
EXHIBIT 7
COMPUTER FORMATS FOR KEY COMMON DATA ELEMENTS
Agency
NRC
EPA '
EPA
DOT
DOT
OSHA
Data-
base
IRIS
ERNS
ARIP
HMIRS
HLPAD
IMIS
Common Data Elements
Release Date
Type
date
date
date
date
date
text
Width
10
10
10
10
10
>200
Facility Name
Type
text
text
text -
text
text
text
Width
30
30
30
30
50
-
Release City
Type
text
text
text
text
text
num
Width
20
20
25
25
25
4
Release State
Type
text
text
text
text
. text
text
Width
2
2.
.2 .
2
2
2
NRC Number
Type
num
num
num
num
num
-
Width*
6
6
6
6
6
-
* The following databases provide additional blank spaces over and above the six digits currently needed to accommodate
the NRC number: IRIS (1 additional space), ERNS and HMIRS and HLPAD (6 additional spaces).
National Response Center Identification Number. Another suggestion is to use a single
identification number that can refer to one release or notification in all of the federal accident databases. .
Because five of the seven databases (i.e., IRIS, ERNS, ARIP, HMIRS, and HLPAD) featured in this guide
originate with the National Response Center's (NRC) database (IRIS), perhaps an NRC identification
number can eventually be assigned to the databases to link them. When the NRC receives a call
concerning a release, the call is given a six digit NRC number. This number is already associated with
ERNS, HMIRS, ARIP, and HLPAD. '
However, several problems accompany this approach. First, the NRC identification numbers
pertain to notification reports to the NRC, not to actual releases. Also, multiple notifications about a
single release create several different NRC numbers. According to the NRC, around 20 percent of NRC
records are estimated to be duplicates of individual releases.. This duplication creates a problem if
matching the databases are based on a release. Also, for such a matching system to work, federal agencies
would have to take responsibility for including the NRC identification number in their databases. HMIRS
and HLPAD database managers do not include the NRC number in their databases, but they could
retrieve it. However, only a small number of incidents in HMIRS and HLPAD require reporting to the
NRC and have NRC numbers.
Efforts to Support Database Linkage
In addition to efforts by individual federal agencies to place databases (e.g., ERNS, ARIP) on
electronic bulletin boards, the NRT has outlined and is considering a pilot project to link databases to
determine the utility of database linkage.
The NRT is considering a pilot project to produce a publication of summary statistics on accidents
in the United States. The publication would be based on a synthesis of a year's worth of data (e.g., 1994)
-60-
-------
from all of the databases featured in this user's guide. The intention is to develop a "snap shot" of the
release data for a national picture. The effort would include merging fifteen or fewer common data
elements (listed on page 59) into a single combined database so that aggregate analysis could be,
performed. The procedures to link the data would also be documented. The entire effort to produce a
"temporary working database" might demand significant resources to conduct and document the linkage of
databases and therefore, might only be performed once! Because many of the databases are huge, the
NRT may consider a scaled-down effort by perhaps limiting the number of merged release records to a .,
subset - those that meet a release quantity threshold (e.g., ,a 100 gallons), impact trigger (e.g., causes
death, injury, environmental damage), or some other screening criterion. Much of the resources for a
second version and a follow-up publication on the accident picture would be borne in the first year
because the procedure to link the databases and the database structure would have already been
established and the initial problems would have been resolved.
In an additional optional effort, the NRT could compare the temporary working database to
accidental release data from up to three select states. This data would be compared for accuracy and
completeness against the nationally collected data. The merging of state data with the accidental release
data collected nationally could add depth to the accident picture for the state(s) involved. Additional
publications could feature compreliensive summary statistics on selected states or comparison of state
accidental release pictures.
The NRT would assess the costs of arid response to the publication on the accidental release
picture to determine if annual updates of the publication or release of the raw data are warranted. The
publications that feature statistics on national and state-enhanced data could be available through some
agreed upon mechanism (e.g., NTIS, electronic bulletin boards).
Further study of the benefits, the technical complications, and the resource requirements of this
pilot project is necessary before the NRT can proceed.
-61-
-------
-------
User's Guide Appendices
Appendix A:
Examples of Completed Accident Report Forms for Federal
Release Databases
Appendix B: Datafield Dictionaries of Federal Release Databases
-------
-------
Appendix A
Examples of Completed Accident Report Forms for Federal Release Databases
-------
-------
IRIS Accident Report Form
-------
-------
OS:Ol AM EOT 05/23/95
rage 1 ' Bi
INFORMATION SHOWN ON THIS FORM IS SUBJECT TO MINOR CHANGES.
OFFICIAL NRC REPORTS ARE SENT TO VNTSC ON A DAILY BASIS.
From: National Response"Center
USCG HQ Washington, D..C.
1-800-H2H-8802
To: PO LEWIS
MSO HONOLULU
Incident Report #292103
INCIDENT DESCRIPTION
*Report taken by MST3 BRIGHT at 05s 47. -on 22-MAY-95
Incident Type: MARINE
Incident Cause: UNKNOWN
Affected Area: PEARL HARBOR ,
The incident was discovered on 21-MAY-95 at 21: 45 local time.
Affected Medium: WATER . \
REPORTING PARTY
l"-r" --T-rr U-.--I ..___. , . ., ._ .
Name:
Job Title:
Organization:
Address:
called for the responsible party.
Day Phonei
Type of Organization: ' ,~
SUSPECTED RESPONSIBLE PARTY
Name:
Job Title:
Organization:
Address:
Day Phone:
Type of Organization:
BERTH A6
PEARL HARBOR, HI 96673^1036
INCIDENT LOCATION
County: OAHU
RELEASED MATERIALfSl
CHRIS Code: OLB OIL, MISC: LUBRICATING __
Qty Released? 50 GAL(S) . Qty in Water: 50 GAL(S)
~~ ' ~~ SOURCE/CAUSE OF INCIDENT
USS NAVAJO/WASTE LUBE OIL TANK OVERFLOW
DAMAGE
Injuries: Fatalities: Evacuations: Damages:
Air Close: Road Close:
N N
REMEDIAL ACTIONS
BOOMS DEPLOYED
NOTIFICATIONS BY CALLER
EPA: STATE: CG: Y OTHER: DESC: HONMS
-------
oa.-oi AH tui
rage
as
INFORMATION SHOWN ON THIS FORM IS SUBJECT TO MINOR CHANGES.
OFFICIAL NRC REPORTS ARE SENT TO VNTSC ON A DAILY BASIS,
From: National Response Center
USCG HQ Washington, D. C.
i-Boo-424-8802
To: PO LEWIS
MSO HONOLULU
Incident Report * 292403
INCIDENT DESCRIPTION
*Report taken by MST3 BRIGHT at 05:47 on 22-MAY-95
NOTIFICATIONS BY NRC
MSO HONOLULU PO LEWIS
2E-MAY-95 05: 54
ADDITIONAL INFORMATION
SHEEN SIZE:230' X 10'
***** END OF REPORT # 292403 *****
-------
ERNS Accident Report Form
-------
-------
,ERNS INCIDENT NOTIFICATION REPORT
Regional Case Number:_
Reported (nrnfddtw):
Time
Recorded Byt\\^
Mulbpfe fteportt" | |~ j Regional Time
Multiple RegionalCase Number:^,,.., ...
TJttbugh NR% f| { ;
NRC Case Number:
SSI Report:
CR Number:
By
i st:
Discovery Date (mmrdd/yy):
Spill Date (mnVdd/yy):
Spill Time (HH/MMj:
Material Type: (Check One) [~J Unknown [~~| Oil QHazSub | j Other
Material Name,
CHRIS. CAS No.
UN DOT No. Quantity
Units (Cirde One) Quantity In Water
Ib bill dan unk
gal' ton oth
Ib bbl drm unit
gal ton oth
lit tib! drat uo*
gat tot eth
Source of Spill: (Cheek Any) |"""| Highway
I I Air Transport
B Railway,
Vessel
B Pipeline
Offshore
UST
I AST
B
Fixed Facility [~1 Other
Unknown
Number Q{ Tanks;
Tank Capacity^
Tank Units: (Circle One)
Ib Mtf drm unk
gal ton oth
Medium Affected: (Check Any)
None
Air
Land
Water
Groundwater
I Within Facility
Other
Unknown
Reported Cause; (Check Any)
Equipment Failure
B
Natural Phenomenon
Dumping . | [Other
Unknown . ..
No. of Injuries: _
| | None
No. of Deaths:
None
Evacuation: ) f I Response Actions Taken:
Property Damage>$50,000: ' | ]
ICallet Has Notified;
State/Local j j DJschatger Q USCG Q O<|rt8r ED Unknown
I Agency Name:
I Comments:
Hespiwise- Comments;
Agency- Name:
Qstete D Dfecharger Q ?**ซ* Q pA Q Q^fter
Agency-Namec
U3C9I
Q Pederat Q EPA
Unknown
Agency Nantec
| J toca( Qstate.
Federat Q ERA Q other
Unknown
[^-Critical Data For Datk Qual'cty
CALLER INFORMATION
Fcxm Version 08/91
-------
REGION 2 INCIDENT NOTIFICATION REPORT Regional Case Number:.
Stale Case #; > \ ,"
Caller Has Notified: cchซ*.Oftซป f " ? ^ -"" IT EPAy. s' f~l NRC
Drill; F~l
Prevention Codefs):
Responsibility: (QhockOr*)
,, Q EPJU>|~]ซUSC.G, ,- f~j Other
SPCC latter;
CVS/&308 Spill Letter: | | H 5\
Tributary Tpi' *
RQ(arral;
POHL0W-UP',
Update Date; {mn/ddtyy) , \x ,> 5
Updated By;
Dun&SradsfreetNo,:^ --", x,s // "' '"^^T^"^^^-^^-"^
' ""^.^--^v-^ %% ^" * f^ * f^,_, < ' '"f'/^f f ^
'^ฃ ;;-.', > It
. '?,< 'y r "f
-*\ < *,
Ov %> , ,
I",
rr^-Crifcjl DMป For Data Quality
FOLLOW-UP INFORMATION
Form Version 08/91
-------
ARIP Accident Report Form
-------
-------
OMB #: 2050-0065
-.'' Expires: September 30,1995
. U.S. ENVIRONMENTAL PROTECTION AGENCY
ACCIDENTAL RELEASE INFORMATION PROGRAM ,
VERIFICATION AND INFORMATION SUPPLEMENT
INSTRUCTIONS
GENERAL INSTRUCTIONS -
The Accidental Release Information.Program (ARIP) is administered by the
U.S. Environmental Protection Agency (EPA). The purpose of this program is to
learn more about the causes and consequences of accidental releases of
hazardous substances from fixed facilities and the actions that have been or-'
could have been effective in. preventing them from occurring. The collected
information will serve to support a range of chemical accident'prevention and
preparedness efforts involving industry, local and state government, and EPA
regions and headquarters.
Please read the instructions before you verify the information or answer
the questions. If you need further assistance, please contact the person
identified in the cover letter. .
ORGANIZATION
There are two parts to this survey.
all questions must be answered.
Both parts must be completed and
PART A.
Emergency Response Notification System - Verification
The Emergency Response Notification System'(ERNS) is a national computer
database and retrieval system that is used to store information on releases of
oil and hazardous substances. ERNS provides a mechanism for documenting and
verifying incident.notification information as initially reported to the
National Response Center (NRG), EPA, and/or the U.S. Coast Guard. This part
of the survey includes an ERNS printout of available information pertaining
your particular release event. - It is important that you verify this
information, make corrections as needed, and provide any missing information.
Please note the identification numbers for your reported event at the
top of this section. These numbers are the ERNS database number and/or the
NRC report number'* Make sure that you IDENTIFY ALL PAGES WITH AT LEAST ONE OF
THESE NUMBERS.
PART B.
Accidental Release Prevention - Supplemental Information
This part of the .survey questionnaire requests information to supplement
reports you may have submitted to the National Response Center (NRC) and other
federal, state, or local authorities. The questionnaire is divided into three
sections: . ''.' ' -
Section I - Facility Profile
This section asks several questions about your facility, e.g.," location,
product, and current status of operations.
Section II - Hazardous Substance Release Profile
This section asks, several key questions concerning the reported release.
It is important,that you respond as accurately as you can based on the
-------
information available to you. If more space or 'comments to clarify your
response are needed, please use additional pages.
Section III - Prevention Profile .
This section asks you to provide an assessment of prevention plans and
technologies at your facility and any changes that will be initiated
because of the release incident. Additional space for alternate answer's
and/or details is provided. Please attach additional pages if
necessary.
AGENCY DISCLOSURE OF ESTIMATED BURDEN
Public reporting burden for this collection of information is estimated
to average 24.5 hours, including time for reviewing instructions, searching
existing data sources, gathering and maintaining data needed, and .completing
and reviewing the collection of information. Send comments regarding the
estimated burden or any other aspect of this collection of information,
including suggestions for reducing the burden, to Director, Regulatory
Information Division, Mail Code 2136, U.S. Environmental Protection Agency,
401 M St., S.W., Washington, D.C. 20460; and to Paperwork Reduction Project
(OMB $ 2050-0065), Office of Information and Regulatory Affairs, Office of
Management and Budget, Washington, D.C.20503.
DEFINITIONS
Please refer to the definitions below to clarify the precise meaning and
use of the terms in the questionnaire.
By-pass: A piping system designed to provide an alternate pathway for gas or
liquid streams that detours around a normal pathway. A by-pass condition
refers to a system's operation using available bypass systems. Certain
instrument control alarms and interlocks may also be "by-passed" during
abnormal operating conditions.
Cause-Consequence Analysis1: A diagram display of the interrelationships
between accident outcomes and their basic causes. This analysis is a blend of
the Fault Tree and Event .Tree analysis.
Containment System: Dikes, curbs, vaults, ponds, and the like that serve to
collect and temporarily hold spilled materials until such time as they are
removed, disposed of, or transferred to a secure storage vessel.
Dow and Mond Indices1: A method for relative ranking of the risks at a
chemical process plant. This method assigns penalties to process materials
and conditions, that can contribute to an accident. Credits are assigned to
plant safety procedures that can mitigate the effects of an accident.
Equipment (Mechanical) Failure: Failure of process or storage vessels,
valves, piping, pumps or other equipment connecting vessels in a process that
allows a loss of containment.
-------
Event Tree Analysis1: Considers operator response or safety system response;
to an initiating event in determining accident outcome. This analysis results
in accident sequences. -
Facility Boundary:
facility.
.Fence line or property line marking the perimeter of a
Failure Modes/Effects Analysis1: A method fo'r tabulating the system/plant
equipment and their respective failure modes (description of how the equipment"
or -system fails) . The tabulation includes the effects of .each "failure mode on
the system/plant and a critical ranking of them.
Fault Tree Analysis1:. A deductive technique that focuses on determining the
causes of one particular accident event. The causes are determined using" the
fault tree - a graphic model that displays the various combinations of
equipment faults and failures that can result in an accident event. '
Federal Authority: Any federal government official delegated the '
responsibility under the Superfund statute for activities related to hazardous
substance releases (e.g., National Response Center, U.S. Environmental
Protection Agency and its regional offices).
General Public: Persons not present within the facility boundaries at the
time the .release occurred and/or with no business association to the facility
owner (e.g.,. residents near the facility).
Hazard Assessment1: Formal procedures employed to identify potential risks .
that could lead to an accidental release (e.g., Fault Tree analysis).
Hazard and Operability Studies (HAZOP)
1.
Formal team brainstorming to
systematically identify hazards and operability problems throughout an entire
facility. Certain.guide-words such as "no flow" and "no cooling" are used.
The consequences of credible deviations associated with the guide-words are
identified and assessed.
Hazardous Substance: Any element, compound, mixture, solution,- or'substance
designated under section 102 of the Comprehensive Environmental Response, :
Compensation, and Liability Act (CERCLA) or section 3001 of the Solid Waste
Disposal Act. -
Human Error Analysis1 (also know as Human Factors Analysis): A systematic
evaluation of the factors that irifluence the performance, procedures, rand
techniques of human operators, maintenance staff, and other personnel.' It
will identify errors and likely situations that' can cause an accident.'. .. *
Immediate Response1: Application of equipment, systems,'and procedures to
capture, neutralize, or destroy a hazardous substance before it is released to
the-environment (e. g., scrubber) . !.
Local Authority: Any local government official responsible for remedial or
related activities connected with a hazardous substance release (e.g., Local
Emergency Response Committee (LEPC), fire-department).
Loss of Containment: '-Accidental release of hazardous substances from" a
process or storage vessel, interconnecting equipment, and/or control equipment
to the environment. - -
-------
Migration: The movement of a substance from one place to another in air,
water, soil, or other media.
Operator Error: A mistake (e.g., leaving a valve open, failure to respond to
process alarms, failure to maintain process variables or conditions at set .
point) made during operation of a process by the operator resulting in a
release or loss of containment.
Owner: The legally designated individual, partnership, or parties that own
the facility. '
POTW: Publicly Owned Treatment Works. "
Probabilistic Risk Assessment*: The overall measure of risk determined
through numerical evaluation of both accidental .consequences and
probabilities. This method is used to assess comparative risk where
alternative designs exist.
Process Control and. Monitoring*: Control and detection equipments that
provide information on the process status, standard operating conditions or
parameters, and possible or imminent releases- (e.g., pressure sensprs,
temperature sensors, chemical detectors on process lines).
Process Design*: Design of process equipment and systems to limit the
potential for accidental releases (e.g., redundant systems').
Process Vessel: A tank, reactor, vat, or other piece of equipment- in which
substances are blended to form a mixture or are reacted to convert them to
some other product or form.
Release: Any unintentional or accidental spilling,- leaking, flowing, pumping,
pouring, emitting, emptying, discharging, injecting, escaping, leaching,
dumping, or disposing of a hazardous substance into the environment from a
storage or process vessel. -
Responding Official: Person responsible for the finalreview of the
information provided in the survey questionnaire for completeness and accuracy
(e.g., facility safety officer, environmental engineer, plant manager).
Response*: Application of equipment, systems, and procedures to capture,
neutralize, or destroy a hazardous substance after it is released to the
environment (e.g., cleanup).'
Standard Industrial Classification: The federal government categories of -
business activity. See Standard Industrial Classification Manual, Office of
Management and Budget, U.S. Government Printing Office, Washington, D.C.
State Authority: Any state government official responsible for remedial or
related activities connected with a hazardous substance release (e.g., State
Emergency Response- Commission (SERC), state transportation office).
Storage Vessel: Any container (e.g., tank, drum, bottle, tank car, cylinder)
used to hold a ra"w or input material, a product, or a by-product at ambient
conditions or at an elevated or reduced temperature or pressure.
-------
Upset: Process deviation from standard conditions because of a malfunction or
failure of process controls, alarms, or backup systems. These condition's
could result from operator error, mechanical or equipment failure, or from
unexpected events such as fire, explosion, power loss, or water loss.
What If Analysis1:' Considers consequences, associated with events that occur
as a result of failures involving equipment, design, or procedures. All
.possible system failures are collected in a list and evaluated (e.g., "what if
the feed pump fails"). This method requires a basic understanding of what is
intended and the ability to combine possible deviations and to reject
incredible situations. - "".."-'
1. Definition derived from Guidelines for Hazard Evaluation Procedures,
AICHE, 1985, and from the Review of Emergency Systems, EPA, June, 1988.
-------
-------
PART A.
OMB #: 2050-0065
Expires:
U.S. ENVIRONMENTAL PROTECTION AGENCY
ACCIDENTAL RELEASE INFORMATION PROGRAM
EMERGENCY RESPONSE NOTIFICATION SYSTEM - VERIFICATION
Information regarding.an accidental release incident in your facility
has been recorded in the Emergency Response Notification System (ERNS). Below
is the information available in ERNS regarding this release. Please verify
the information, by making any corrections and/or by.providing any missing
information in the spaces provided (attach additional pages as necessary).
1. Facility:
Dun & Bradstreet Number
Street
City
County
State
Telephone (
. Zip
2. Spill. Location: (
Street
City
Caunty
State
Telephone (
Check here if same as Facility Address)
Zip
Latitude (Deg/Min)
Longitude
,3. Primary Chemical Released:
4. ERNS Reporting Date/Time:
(mm/dd/yy)
(24-hr clock)
5. Reported through NRC?
Yes
No
-------
ERNS/REGIONAL CASE #
/ NRG #
6. Federal, State, and Local Authorities Notified:
(e.g., NRC, "EPA Regional Office, SERC, DNR, LEPC, Police, and others.
Show dates as mm/dd/yy; times in 24 hour clock.)
Agency
Date
Time
Person Contacted
7. Responding Agencies:
8. Response Action(s):
-------
ERNS/REGIONAL CASE #
/ NRG #
PART B. ACCIDENTAL RELEASE PREVENTION - SUPPLEMENTAL INFORMATION
SECTION I. FACILITY PROFILE
1. Plant Manager/Facility Owner:
2. Responding Official:
Title:
Address:
Telephone: (
Signature:
Date:
3. Please provide the four-digit Standard Industrial Classification (SIC)'
codes that best describe your facility operations: -
SIC code(s): , ,
(Primary)
Primary product or service:
4. Indicate the total number of employees typically at the facility
(include all full-time and part time employees, all employees on sick
leave, paid .holidays, paid vacations, managers and corporate officers at
the facility, and contractors):
Number of Employees: - -'
-------
ERNS/REGIONAL CASE #
/ NRG #
SECTION II. HAZARDOUS SPBSTANCE RELEASE PROFILE
For the following section, if exact responses cannot be provided' please
provide estimates using your best professional judgment.
5. Date/Time Release Began:
(month/day/year) (24-hr clock)
Ended:
(month/day/year) (24-hr clock)
In the table below, provide .release estimates for the primary chemical
released (in Ibs, only) to each media. Quantities released to each
media should add up to the total quantity released. For solutions,
adjust the quantity of the chemical released for chemical concentration
(e.g., report 1,000 Ibs of 50% sulfuric acid released as 500 Ibs
sulfuric acid). For multiple chemicals attach additional pages as
necessary. ~
Chemical Name:
CAS Number:
Concentration (wt%):
Physical State at time of release:
Released To: Quantity (Ibs)
Air
Surface Water
Land
Treatment Facility
Total Quantity Released:
Check the item below that best describes when the release occurred:
b.
c.
During routine operation
During routine startup
While in process of shutting down operations
d. While unit was shutdown for maintenance/product changeover, etc.
e. During special test, or non-standard, trial run conditions
f. During startup of new construction, new equipment
g. Other (please describe): . ' .
-------
EKNS/REGIOKAL CASE #
/ MRC #
8. ' Check the item below that best describes the status of the- facility,
unit, or process line as a result of the. release: . 1
b.
c.
d.
_ No interruption; continued operations .
_ Restarted after release
_ Shut down for repairs; with plans to restart'
_ Permanently closed ''-
Other (please describe) : . : -.-:' .
Check the one item below that best describes the location of'the loss of
containment in the specified area: '" .
a. Process Vessel:
b. Storage vessel: ___
c. Valve: ___ flange,
d. Piping: flange
Pump: flange,
wall,
wall,
seal, _
_ joint,
seal,
overflow,
overflow,
body
- elbow,
body
_ _ _ _
f. Other process equipment (please describe) :
vent,
vent,
wall
drain'
drain
10.
How was the release first discovered? (check as many as apply)
a.
b.
c.
d.
e.
f.
_ Process control-device indication
_ Chemical specific detector, alarm
_ Observation by employee(s)
_ Explosion/fire '
_ Third party notification
_ Other (please describe):
11. Check one item below that best describes what initiated the release:
a. . Equipment, failure - " . .
b. Operator error . - .-- .
-------
ERNS/REGIONAL CASE #
/ NRG #
12.
Indicate other factors that contributed to. the equipment failure or
operator error (check as .many as- apply ,and .elaborate below) :
a.
b.
c.
d.
e.
f.
g-
h.
i.
"Upset" condition
"By-pass" condition * - . .
Maintenance .activity , .
Training deficiencies
Inappropriate operating procedures
Faulty process design
Unsuitable equipment
Unusual weather Conditions
Other (please describe):
13.
Provide a brief chronological description of the events that led up to
and contributed to the release event (if helpful, include a sketch).
Briefly discuss the results of your investigation. Use additional pages
as necessary. . .
14. Check all items that describe the end effects of the release.event:
a. Spill , . . - - .
b. Vapor release .
c. Explosion
d. Fire
e. Other (describe):
-------
ERtfS/REGIONAL CASE #
/ me ,#
15. Was the-general public notified?
Yes
No
If yes, indicate the type of.communication technologies used* to alert
and notify the public to evacu_ate or take other safety measures. Check
as many items as apply:
a.
b.
c.
d.
e.
f.
g-
h.
i.
j.
k.
Door-to-door notification
Loudspeakers/public access, system
Tone alert radio/pagers
Siren/alarms \
Modulated power lines - '-...
Aircraft . - .
Radio .
Television -
Cable override
Telephone
Other (please describe):
16. Indicate the numbervof persons injured, hospitalised (as opposed to
treated and released) and fatalities that occurred as -a result of the
release (indicate with NA if not known) : ""-.
Injuries
Hospitalized
Fatalities
Facility employees
Contractors
General public
Responders
17. Indicate the number of persons evacuated and/or sheltered-in-place as a
-. result of the release" (indicate with NA if not known) :
Evacuated
Sheltered in Place
Facility employees
Contractors
General public
-------
ERNS/REGIONAL CASE #
/ NEC #
18. Describe the immediate response activities taken to mitigate the release
(capture, neutralize or destroy a toxic chemical before it is released
into the environment). Check as many as apply.
b.
c.
d.
e.
f.
g..
h.
i.
j-
k.
Reduce system pressure/temperature
Apply spray scrubber/curtain
Transfer contents from failed equipment
Dilute and/or neutralize
Containment
Plant/process shutdown
Divert release to treatment
Vacuum/release recovery
Incineration/flares
None
Other (describe):
19.
Indicate the environmental effects that occurred as a result of the
release: .
a.
b.
c.
d.
e.
f.
g-
Fish Kills
Vegetation damage
Soil contamination
Groundwater contamination
Wildlife kills
None
Other (please describe):
20. Estimate the financial impact of the accidental release for the facility
(e.g., cleanup cost, outside contractors cost, hours/wages diverted to
cleanup or lost to shutdown, loss of production) and for,the general
public (e.g., damage to natural resources, public and private
properties). An aggregate figure may be provided if a breakdown is not
available.
b.
Facility Costs:
General Public Costs:
$
$
Total Costs:
-------
ERNS/REGIONAL CASE #
/ NRG..#'
SECTION III. PREVENTION PROFILE
21a. What formalized hazard evaluation'was performed prior to this release at
the process or storage area within your facility where the accident
occurred? When was it last conducted? How frequently is this
evaluation conducted (e.g. every 2 years)? Indicate frequency in years
and date last conducted as mm/dd/yy. .
Last
Conducted
a.
b.
c.
d.
e.
f.
g-
h.
i.
j-
k.
Frequency
Cause-Consequence analyses , - '
Dow and Mond Hazard Indices - . ^^_
Event Tree analyses ' ' ^_^
Failure Modes/Effects analyses ,' - __-_
'Fault. Tree analyses ^ '
HAZOP Studies
Human Error analyses " ' __^_^
Probabilistic Risk Assessments .
What If analyses -
No evaluation ever done for this area
Other evaluation (describe, indicate frequency, date done):
21b.
Was the hazard evaluation performed effective in predicting this release
event? Why or why not? "
-------
ERNS/REGIONAL CASE #
/ NRG #
22a. Identify the training-, procedures, and/or management practices used at
this facility prior to this release to prevent accidental releases.
Check all that apply.
a.
b.
c.
d.
e.
f.
g.
h.
i.
Preventive Maintenance/Inspections
Accident Investigations
Audits '
Inventory/capacity reductions
Employee safety training
Standard operating procedures
Emergency response training
None
Other (please describe):
22b. Describe any changes to existing training, procedures and management
practices, or what new types of training, procedures and management
practices are or will be implemented as a result of this release?
23a.
What engineering systems or controls were in use prior to the release at
the process or storage area within your facility where the accident :
occurred? Check all that apply. .
a.
b.
c.
d.
e.
f.
g.
h.
Backup/Redundant systems
Automatic Shut-offs
Bypass/Surge systems
Manual Overrides
Controls for operations monitoring and warning
Interlocks
None
Other (please describe):
10
-------
EKNS/REGIONAL CASE #
/ NRC #
23b. Describe any changes to the existing-engineering systems or controls,
and any new types of engineering systems/controls that are or will be
implemented as a result-of this release:
11
-------
-------
HMIRS Accident Report Form
-------
-------
DEPARTMENT OF TRANSPORTATION ,
HAZARDOUS MATERIALS INCIDENT REPORT
Form Approved OMB-Ho. 2137-OO39
INSTRUCTIONS: Submit-this report in duplicate to the Information Systems Manager, Office of Hazardous Materials Transportation, DHM-63, Research and
Special Programs Administration, U.S. Department of Transportation, Washington, D.C. 20590. If space provided for any item is inadequate, complete that
item under Section IX, keying to the entry number being completed. Copies of this form, in limited quantities, may be obtained from the Information Systems
Manager, Office of Hazardous Materials Transportation. Additional copies in this prescribed format may be reproduced and used, if on the same size and kind '
of paper. _ . ' ' ; .
J. MODE. DATE. AND LOCATION OF INCIDENT
1. MODEOFTRANSPORATION:
,D AIR
HIGHWAY
Q RAIL
D WATER
OTHER
2. DATE AND TIME OF INCIDENT
(Use Military Time. e.g. 8:30am = 0830.
noon = 1200. 6pm = 1800. midnight = 2400).
Date:
7.
1995
TIME:
3. LOCATION OF INCIDENT (Include airport name in ROUTE/STREET if incident occurs at an airport.)
CITY: Belvoir
COUNTY: _
STATE:
ROUTE/STREET: _JJS_RQUte_L.
II. DESCRIPTION OF CARRIER. COMPANY, OR INDIVIDUAL REPORTING
4. FULL NAME
ABC Trucking Company
5. ADDRESS (Principal place of business)
1492 Columbus Avenue
Richmond-, VA 23021
6. LIST YOUR OMC MOTOR CARRIER CENSUS NUMBER, REPORTING RAILROAD ALPHABETIC
CODE. MERCHANT VESSEL NAME AND ID NUMBER OR OTHER REPORTING CODE OR NUMBER.
MC 654321
III. SHIPMENT INFORMATION (From Shipping Paper or Packaging)
7. SHIPPER NAME AND ADDRESS (Principal place of business)
.Scientific Division - American Hotel Supply
1101 South Peachtree Street
Atlanta, GA 30303
8. CONSIGNEE NAME AND ADDRESS ( Principal place of business)
J & J Chemicals ,,
9801 Sluice Parkway
Newark, NJ 07101
9. ORIGIN ADDRESS (If different from Shipper address)
N/A
10. DESTINATION ADDRESS (If different from Consignee address)
1506 Wayne Stteet
Alexandria, VA 22301
11, SHIPPING PAPER/WAYBILL IDENTIFICATION NO.
Carrier's PRO 98765
IV. HAZARDOUS MATERIAL(S) SPILLED (NOTE: REFERENCE 49CFR SECTION 172.101.
12. PROPER SHIPPING NAME
Acetone
13. CHEMICAL/TRADE NAME
N/A. .
14. HAZARD CLASS
Flammable Liquid
15. IDENTIFICATION NUMBER
(e.g. UN 2764. NA 2020)
. UN 1090
16. IS MATERIAL A HAZARDOUS SUBSTANCE? gYES Q No
17. WAS THE RQ MET?
ID YES
NO
V. CONSEQUENCES OF INCIDENT. DUE TO THE HAZARDOUS MATERIAL.
18. ESTIMATED QUANTITY
HAZARDOUS MATERIAL
RELEASED (Include
units of measurement)
45 Gallons
22. NUMBER OF PEOPLE EVACUATED
None
19. FATALITIES
None
20. HOSPITALIZED
INJURIES
None
21. NON-HOSPITALIZED
INJURIES
23. ESTIMATED DOLLAR AMOUNT OF LOSS AND/OR PROPERTY DAMAGE. INCLUDING COST OF DECONTAMINATION OR CLEANUP (Round off in dollars)
A. PRODUCT LOSS
$90.00
B. CARRIER DAMAGE
N/A
C. PUBLIC/PRIVATE
PROPERTY DAMAGE
N/A
D. DECONTAMINATION/
CLEANUP
$100.00
E OTHER
N/A
24. CONSEQUENCES ASSOCIATED WITH THE INCIDENT:
C? SPILLAGE D FIRE D EXPLOSION
D VAPOR (GAS) DISPERSION
D ENVIRONMENTAL DAMAGE
D MATERIAL ENTERED WATERWAY/SEWER
CD NONE D OTHER: !__
VI. TRANSPORT ENVIRONMENT
25. INDICATE TYPE(S) OF VEHICLE(S) INVOLVED: Q CARGO TANK
D TANK CAR D RAIL CAR D TOFC/COFC D AIRCRAFT
g VAN TRUCK/TRAILER
CD BARGE
D FLAT BED TRUCK-TRAILER
D SHIP D OTHER:
26. TRANSPORTATION PHASE DURING WHICH INCIDENT OCCURRED OR WAS DISCOVERED:
K3 EN ROUTE BETWEEN ORIGIN/DESTINATION ' D LOADING - Q UNLOADING D TEMPORARY STORAGE/TERMINAL
27. LAND USE AT INCIDENT SITE: D INDUSTRIAL Q COMMERCIAL PRESIDENTIAL D AGRICULTURAL D UNDEVELOPED
28. COMMUNITY TYPE AT SITE:
D URBAN
CS SUBURBAN
D RURAL
29. WAS THE"SPILL THE RESULT OF A VEHICLE ACCIDENT/DERAILMENT?
IF, YES AND APPLICABLE. ANSWER PARTS A THRU C. '
YES D NO -
A, ^ESTIMATED SPEED:
25 mph
B. HIGHWAY TYPE:
XH DIVIDED/LIMITED ACCESS
D UNDIVIDED '
FORM DOT F 5800.1
-------
VII. PACKAGING INFORMATION: If the package is overpacked (consists'of several packages, e.g. glass jars within a fibarboard box), begin with Column A
lor information on the innermost package. , -
ITEM
30 TYPE OF PACKAGING, INCLUDING INNER
RECEPTACLES (eg. Steel drum, tank car)
31 CAPACITY OR WEIGHT PER UNIT PACKAGE
(e o 55 gallons. 65 IDS,)
32 NUMBER OF PACKAGES OF SAME TYPE WHICH
FAILED IN IDENTICAL MANNER
33 NUMBER OF PACKAGES OF SAME TYPE IN
SHIPMENT
34 PACKAGE SPECIFICATION IDENTIFICATION
(e g DOT 17E. DOT 105A100. UN 1A1 or none)
35 ANY OTHER PACKAGING MARKINGS
(e g STC. 18/16.55-88. Y1. 4/150/87)
36 NAME AND ADDRESS. SYMBOL OR REGISTRATION
NUMBER OF PACKAGING MANUFACTURER
37 SERIAL NUMBER OF CYLINDERS. PORTABLE TANKS.
CARGO TANKS. TANK CARS
38 TYPE OF LABELING OR PLACARDING APPLIED
39
IF RECONDITIONED
OR REQUALIFIED
A. REGISTRATION
NUMBER OR SYMBOL
B. DATE OF LAST
TEST OR- INSPECTION
40 EXEMPTION/APPROVAL/COMPETENT AUTHORITY
NUMBER. IF APPLICABLE (e.g. DOT E1012)
A (.Inner; -B (.Uuter;
Plastic Liner Steel Drum
-55 Gallons
1
12
DOT 2SL
55-rl2-93
AAA - Toledo
N/A
None
N/A
N/A
N/A
. 55 Gallons
.1
12
DOT 17H
STC 18/16-55-92
,.-OH FUBAR - Flint, MI
N/A
Flammable Liquid
DOT 51000
2/94
. N/A
C
-
-
. '
VIII. DESCRIPTION OF PACKAGING FAILURE: Check all applicable boxes for the packaga(s) identified above.
<ป ACTION CONTRIBUTING TO PACKAGING FAILURE
A, ft S. ABC
ป S) Q: D TRANSPORT VEHICLE COLLISION j. ง0 B D CC
b. D O D TRANSPORT VEHICLE OVERTURN k. D D D ME
C. O D D OVERLOADING/OVERFILLING I. D D D FR
d, D D O LOOSE FITTINGS. VALVES m. D D D Fll
e D D D DEFECTIVE FITTINGS. VALVES n. ID D D FH
t D D D DROPPED 0. D ,D D'VE
0 BSD STRUCK/RAMMED p. D D D VA
h: D D D IMPROPER LOADING q. D D D IN
i, D D: D IMPROPER BLOCKING r. D D D OT
(3 HOW PACKAGED) FAILED
A. 1 Q.
a H H D PUNCTURED
b D D D CRACKED
C, D D D BURST/INTERNAL PRESSURE
d, D D D RIPPED
0. D H D CRUSHED
1, D D D RUBBED/ABRADED
g. D D D RUPTURED
h. O D D OTHER
44. PACKAGE AREA Tf
ABC
a. n n n EN
b. n D n EN
c. n n n su
d. n n n sit
e. D D D TO
(. n D n BO
g. S H D CE
h. n n n OT
IRROSION
HAL FATIGUE
ICTION/RUBBING
IE/HEAT
EEZING
NTING
NDALISM
COMPATIBLE MATERIALS
HER
1AT FAILED
D. FORWARD
D. REAR
)E. RIGHT
)E. LEFT
P
TTOM
NTER
HER
42. OBJECT C*
A B
a. SO*
b. n n
c. n n
d. n n
e. D D
i. n n
g. n n
n. n n
i. n n
USING FAILURE
Q ,
D OTHER FREIGHT
D FORKLIFT
D NAIL/PROTRUSION
D OTHER TRANSPORT VEHICLE
D WATER/OTHER LIQUID
D GROUND/FLOOR/ROADWAY
D ROADSIDE OBSTACLE
D NONE
D OTHER
45. WHAT FAILED ON PACKAGE(S)
A B ,!'C
a. H D D BASIC PACKAGE MATERIAL
. b. D D D FITTING/VALVE .
c. D D D CLOSURE
d. D H D CHIME
e. D D D WELD/SEAM
f. D D D HOSE/PIPING
g. D H D INNER LINER
h. D D D 'OTHER
IX. DESCRIPTION OF EVENTS: Describe the sequence of events that lad to incident, action taken at time discovered, nnd action takan to prevent future
incidents. Include any recommendations to improve packaging, handling, or transportation of hazardous materials. Photographs and diagrams should
be submitted when necessary for clarification. ATTACH A COPY OF THE HAZARDOUS WASTE MANIFEST FOR INCIDENTS INVOLVING
HAZARDOUS WASTE. Continue on additional sheets if necessary.
Our vehicle was involved in a minor traffic accident which caused the load to shift and
puncture one of the drums. The leaking drum -and all of the spilled Acetone was removed
for disposal by Hazmat Cleanup Service Inc. to their site at 9987 Old Town Road, March,
VA. The vehicle was taken to our Alexandria terminal and cleaned (washed and steamed) .
A Highway Patrolman on the scene had some of the spilled liquid splash on, his hand.
He received first aid at the scene for his skin irritation.
IB NAME OF PERSON RESPONSIBLE FOR PREPARING REPORT
Gonzalez
18 TITLE OF PERSON RESPONSIBLE FOR PREPARING REPORT
Traffic Safety Coordinator
47. SIGNATURE
49. TELEPHONE NUMBER (Area Code)
(703) 666-4321
SO. DATE REPORT SIGNED
April 5, 1995
-------
HLPAD Accident Report Form
-------
-------
OMB No. 2137-0047
Report Date
ACCIDENT REPORT-HAZARDOUS LIQUID PIPELINE
7000-1
0J07J
PART AOPERATOR INFORMATION
1.) Name of operator -First
2.) Principal business address _
Pipeline Company
One* Tenley
Anytdwn", PA
Valo P
3.)' Is pipeline interstate? B yes
. . (zip code)
O no
PART BTIME AND LOCATION OF ACCIDENT
1.) Date: (month) May
2.)
. a.)
4.)
(day)
(year)
1995'
Hour (24 hour clock) 2010
If onshore give State (including Puerto Sico and W
and county or city. Jeff ergon 'Co.-, Any
If offshore, give offshore coordinates
Did- accident occur on Federal Land?
. D.C.),
, Pa r
no
D yes
ISee instructions for definition of Federal Ldnd.J
6.) Specific location (If location is near offshore platforms, buildings, or other landmarks, such as highways, waterways, or
railroads', attach a sketch or drawing showing relationshp of accident location to these landmarks)
3 miles West of '^Main S t . Thence 3 miles South of HWY .9 -on. ..Coker- Road.,
'thence 300' West of Coker Road a-h Dance Creek. '
PART CORIGIN OF RELEASE OF LIQUID OR VAPOR. | ~ ~" :
1.) Part'of system involved:'
S line pipe D tank farm O pump station
2.) Item Involved: IS pipe D valve d scraper trap O pump
D welding' fitting D girth weld D tank
O bolted fitting O longitudial weld '
(specify) ;v ; ';" '
(Check all applicable items)
. 3.) Yean hem installed 1949
PART DCAUSE OF ACCIDENT |' : ! ' ~~ *~
D corrosion D failed weld . O incorrect operation by operator personnel
D failed pipe D outside'force damage . . . . '
O malfunction of control or relief equipment. '
H ofaer(specify) Pip^l-rpg was puncttjred by rifle bullet.
PART EDEATH OR INJURY |
1.) Number of persons killed..
- ' ' Operator employees .
2.) Number of persons Injured. Q
-0
. Non-employees
. Operator employees.
.Non-employees
PART FESTIMATED TOTAL PROPERTY DAMAGE
$ 2'5fonn. '
PART GCOMMODITY SPILLED |
Gasoline
1.( Name of commodity spilled: _
2.) Classification of commodity spilled: .
. C3 Petroleum Petroleum product O HVL .or S Non-HVL
3.) Estimated amount of commodity Involved
5QQ Barrels spilled -6 Barrels recoverc*
4.) Was there an explosion?
Q yes a no '
5.) Was there a Fire?
Oyes ^ fl no .
US-16
-------
INSTRUCTIONS: Answer sections H. I. or J only H it applies to the particular accident being reported.
PART HOCCURRED IN LINE PIPE~T
1.)
Nominal diameter (Inches)'. ป" ' 2.) Wall thickness (inches) Q 322 .
SMYS (psi) 35,000 4.) Type of joint: H welded O flanged D threaded
Pipe was D Below ground
O coupled
12 Above ground
O otheY
; t
.v6.)
7.
8.)
"ง.)
10.)-
1,1.)
Maximum operating pressure (psig) j 700
'Pressure at time arid location o( accident (psig) 4.5
Had there been a pressure test on.system? .
. D yes K'no '. ' '
Duration of test (firs) ' '
*, Maximum test pressure (psig) '
Date of latest test
PART I CAUSED BY CORROSION
1. Location of corros
~ BnHtemal
2. Facitty coated? '
O yes ' D no
3. Facilty under cathodic protection?
^O yes D no
4; Type of corrosion
D galvanic D other (Specify) .
PART JCAUSED BY OUTSIDE FORCE |
1. O Damage by operator or its contractor
H Damage by others
O Damage by natural forces
O Landslide
O Subsidence
D Washout
O Frostheave
* O Earthquake '
D Ship anchor '
CJ Mudslide , .
O Fishing Operations
Olhaf Ri-Flo gyrlTp.^
2.
3.
4.
5.
Was a damage prevention program in effect
S yes . D no '
If yes, was the program
ฎ "one-call" ' D other _
Did excavator call?
Dyes D no
Was pipeline location temporarily marked for the excavator?
D yes D no N/A
PART KACCOUNT OF ACCIDENT~r~ ' '.
5/5/95 " . . '
Police Dept. Reported leak to us.
Pressure loss indicated that we had leak.
.One mile area: around leak site'evacuated.
Damaged pipe was under water because of heavy rain.
Valve on-North side of leak site closed.
Valve on South side of .leak site'closed.
2010
2015
2044
2100
2117
2130
5/9/95 .
0400 Water receded arid wooden peg was driven into bullet hole.
0645 Installed temporary repair clamp. ' "
NAME AND TITLE OF OPERATOR OFFICIAL FILING THIS REPORT.
John Smith, 'Manager, Pipeline 'Operations
(999) 123-4567
Telephone no. (Including area code)
10, 1995
Date
DOT Fotm 7000-1 (4-85)
US-17
-------
IMIS Accident Report Form
-------
-------
2/11/92 NONUNION
Activity Number: 10S2S4944 SIC 2421 . Open Date:
**** ACCIDENT DATA **** , '
SUMMARY # 793224 -DATE: 2-11-92 .
DESCRIP:CAUGHT BETWEEN STATIONARY BEAM AND MOVING MACHINE PART
ABSTRACT: ON FEBRUARY 11,1992 AT 9 AM EMPLOYEE 1 SUFFERED FATAL HEAD
INJURIES WHEN HE WAS CAUGHT BETWEEN A ROTATING ARM ON THE LUMBER STACKER
AND VERTICAL '.!' BEAM. HE WAS THE LUMBER STACKER OPERATOR AND WAS
INJURED. WHILE IN THE AREA BELOW THE MACHINE.''HE HAD STOPPED THE STACKER
BECAUSE OF- AN INTERRUPTION IN THE FLOW OF LUMBER FROM THE SORTER. HE
AND A STICKERMAN HAD LEFT THE STACKER AND GONE TO ASSIST TWO OTHER
WORKERS. A SECOND STICKERMAN AND RELIEF STACKER OPERATOR REMAINED AT
THE STACKER CONTROLS TO OPERATE THE LUMBER.TRANSFER CHAINS. WHEN THE
PROBLEM WAS CORRECTED, EMPLOYEE 1 DID NOT RETURN TO HIS OPERATING
POSITION AND THE RELIEF OPERATOR/STICKERMAN STARTED THE MACHINE. THE '"'
STACKER COMPLETED. A PARTIAL CYCLE AND STOPPED AND IN THE COURSE OF
INVESTIGATING THIS MALFUNCTION, THE CO-WORKERS DISCOVERED THAT EMPLOYEE
1 WAS CAUGHT IN THE MACHINE. -
VICTIM: 001
DISPOSITION :
INJ NATURE :
INJ SOURCE :
PART-OF-BODY:
AGE: 54
FATALITY
FRACTURE
MACHINE
HEAD
SEX: M
EVENT-TYPE :
ENVIR FACTOR:
HUMAN FACTOR:
CAUGHT IN OR BETWEEN
PINCH POINT ACTION
LOCKOUT/TAGOUT PROCED MALFUNC
HAZ SUBSTNCE: NO SUBSTANCE IMPLICATED
* ป* *****ป***ปป* 1
Activity Number 109362046 SIC 2421 Open Date 2/19/92 NONUNION
**** ACCIDENT DATA ****
SUMMARY # 14330567 DATE: 2-18-92
DESCRIP:WOOD CHIPPER OBSTRUCTED, BLEW APART, STRUCK OPERATOR
ABSTRACT: EMPLOYEE HAD STARTED WOOD CHIPPER, HEARD CLICKING NOISE,
OBSERVED CHIPPER (SHORT TIME APPROXIMATELY 30 SECONDS) INTERNAL PROBLEMS
CAUSED DAMAGED TO ONE KNIFE AND PADDLES. PADDLES SHEARED THE MOUNTING
BOLTS AND, BLEW UPPER HOUSING OFF OF THE MACHINE. METAL PARTS STRUCK
EMPLOYEE RESULTING IN FATAL HEAD INJURIES. EMPLOYEE (VICTIM) WAS 3' TO
5' FROM THE MORBARK, MODEL 58, CHIPPER.
VICTIM: 001 AGE: 38 SEX: M
DISPOSITION : FATALITY
INJ NATURE : BRUISE/CONTUS/ABRAS
INJ SOURCE : MACHINE
PART-OF-BODY: HEAD
EVENT-TYPE :
ENVIR FACTOR:
HUMAN FACTOR:
HAZ SUBSTNCE:
STRUCK BY
FLYING OBJECT ACTION
OTHER
NO SUBSTANCE
2
-------
-------
HSEES Accident Report Form
-------
-------
HSEES is not directly accessible to the public; therefore, the report form is unavailable.
-------
-------
Appendix B
Datafield Dictionaries of Federal Release Databases
-------
-------
IRIS Datafield Dictionary
-------
-------
TABLE
ADDRESS
ADDRESS
ADDRESS
.>
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
ADDRESS
v''
ADDRESS
ADDRESS
ADDRESS
ADDRESS
COLUMN
ADDRDAT&
ADDRESS
ADDRESSTYPE
AREACQDE1
AREACODE2
CITY
COMPANYNAME
CONFIDENTIAL
COUNTY
EXTENSION1&2
FIRSTNAME
HAZMAT
LASTNAME
MI
ORGANIZATIONTYPE
PHONENUMBER1&2
RESPONSIBLEPARTY
SEQNOS
STATE
STREET1
STREET2
TITLE
ZIP -
ZIPEXT
TYPE
DATE (7)
CHAR(25)
CHAR(1)
NUMBER(3)
NUMBER(3)
CHAR(20)
CHAR(25)
CHAR(1)
CHAR(25)
CHAR(4)
CHAR(16)
CHAR(1)
CHAR(25)
CHAR(l)
CHAR(2)
NUMBER(7)
CHAR(1)
NUMBER(7)
CHAR(2)
CHAR(25)
CHAR(25)
CHAR(20)
CHAR(5)
CHAR(4)
IRIS
Address
hidden field
City .
Company
Confidential (Y/N)
City
First Name
Where Materials
Released (Y/N)?
Last Name
MI
OrgType
Phone
Calling for
Responsible Party
(Y/N)?-
Call#
State
Postion
Zip
EXPLANATION
Only used in continuous
release reports
Address of the caller or
discharger line 1
'A'-Additional Information
'D'-Discharger
Information
'C'-Caller
Information
Areacode of the caller or
discharger line 1
Areacode of the caller or
discharger line 2
City of the caller or
discharger
Company of the caller or
discarger
Reporting Party
confidentiality
City of the caller or
discharger
Phone number extension
First Name of the caller or
discharger
Were Materials Released
Last Name of the caller or
discharger
Middle Initial
Type of Organization of the
caller or discharger
Phone number for the caller
or discharger ~'
Is the calling on behalf the
responsible party?
NRC report number
State of the caller or
discharger
Address of caller or
discharger line 2
Address of caller or
discharger line 3
The postion of the caller or
discharger
Zip code of the caller or
discharger
Zip code extension
-------
TABLE
ADDITIONALINFO
ADDITIONALINFO
ADDITIONALINFO
ADDITIONALINFO"
COLUMN
SEQNOS
ADDINFOTYPE
SPECIFIC
SPECIFIC2
TYPE
NUMBER(7)
CHAR(1)
CHAR(71) ,
CHAR(71)
IRIS
Call*
hidden field
Source and/or Cause of
Incident
Actions Taken to Correct
or Mitigate Incident
Any Information About
the Incident not Recorded
Elsewhere in the Report
Source and/or Cause of
Incident
Actions Taken to Correct
or Mitigate Incident
Any Information About
the Incident not Recorded
Elsewhere in the Report
EXPLANATION
NRC report number
'A'-Additional Info
'D'-Source/Cause
'R' -Remedial Action
Line 1
Line 2
-------
TABLE
CALLERNOTIFY
CALLERNOTIFY
CALLERNOTIFY
CALLERNOTIFY
CALLERNOTIFY
" " . '
CALLERNOTIFY
COLUMN
SEQNOS
EPA
STATE
USCG
OTHER
ORGDESC
,
TYPE
NUMBER(7)
CHAR(1) ;
CHAR(1)
CHAR(1)
CHAR(1)
CHAR(35)
-.
IRIS
EPA
STATE
USCG
OTHER
DESC
EXPLANATION
NRC call number
Caller notified EPA
organization
Caller notified State
organization ;
Caller notified a
USCG organization
Caller notified an
organization not
listed above
The description of
the organization the
caller notified
-------
TABLE
CALLS
CALLS
CALLS
CALLS
CALLS
CALLS
CALLS
CALLS
COLUMN
SEQNOS
CALLTYPE
CALLDATE
STARTTIME
ENDTIME
MENUNUMBER
USERID
MARK
-
TYPE
NUMBER(7)
CHAR(3)
DATE
DATE
DATE
NUMBER(2)
CHAR(16)
CHAR(1)
IRIS
Date/Time Received
Date/Time Received
EXPLANATION
NRC report number
Type of call
The date the call
was received
The time the call
was received
The time the call
ended
The number chosen
off the calls menu
The NRC
watchstander who
took the call
Whether the report
was reviewed or not
-------
TABLE
DERAILED
DERAILED
DERAILED
DERAILED
COLUMN
SEQNOS
TRAINUMBER
CARNUMBER
CARGO
TYPE
NUMBER(7)
CHAR(10)
CHAR(10)
CHAR(50)
IRIS
Train Number
Car
Cargo
EXPLANATION
NRC call number
The train number of the derailed cars
The derailed car number
"The derailed cargo
-------
TABLE
IMPACT
IMPACT
IMPACT
IMPACT
IMPACT
IMPACT
IMPACT
IMPACT
IMPACT
IMPACT
IMPACT
COLUMN .
SEQNOS
.
AIRCLOSE
ROADCLOSE
EVACUATIONS
NOOFEVACUATIONS
DAMAGES
bOLLARAMOUNT
NOOFINJURIES
NOOFFATALITIES
MEDIUMTYPE ,
MEDIUMDESCREPTON
TYPE
NUMBER(7)
CHAR(1)
CHAR(1)
CHAR(1)
NUMBER(5)
CHAR(1)
NUMBER(9,2)
NUMBERC3),
NUMBER(3)
CHAR(1)
CHAR(41)
t
IRIS
Call*
Any Air
Corridor Closed
(Y/N/U)?
Any Roads
Closed
(Y/N/U)?
Were there
Evacuations
(Y/N/U)?
Number
Evacuated
Was there Any
Damage
(Y/N/U)?
Damage in
Dollars:
Number of
Injuries?
Number of
Fatalities?
Medium
Affected
More
Information
about Medium
EXPLANATIO
N
NRCcall
number
Air corridor
closure
Road closure
Evacuations
Number of
Evacuations
Damages
Cost of
: Damages
Injuries
Fatalities
What the
discharge
affected
Additional
Information
about the
Medium
Affected
-------
TABLE
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
INCIDENT
COLUMN
SEQNOS
INCIDENTDATE
INCIDENTDTG
INCIDENTTYPE
OFHCIALNUMBER
CAUSE
FRAHOT
RELEASETYPE
RELEASENUMBER
SDAY
SMON
SYR
SMI
SHR
TYPE
NUMBER(7)
DATE
CHAR(1)
CHAR(2)
CHAR(20)
CHAR(1)
CHAR(1)
CHAR(1)
NUMBER(7)
CHAR(2)
CHAR(3)
CHAR(2)
CHAR(2)
CHAR(2)
IRIS
Date
DTG
.. '
Type
Vessel or Vehicle
Number
Cause
RRHot(Y/N)?
Continuous Release
type
Continuous Release
*
EXPLANATION
NRC report number
Date of the incident
DATE TIME
GROUP
Type of Incident
Vessel or Vehicle
Number
Cause of the
Incident
Did the call come
over the RR hot line
For continuous
release reports
NRC original
number for the
continuous release
report
Incident day
Incident month
Incident year
Incident minute
Incident hour
-------
TABLE
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
LOCATION
COLUMN
SEQNOS
CITYDISTANCE
CITYDISTANCEUNITS
CITYDIRECTION
MILEPOST
LATTTUDEDEG
LAirrUDEMtNUTES
LATTTUDESECONDS
LONGirUDEDEG
LONGITUDEMINUTES
LONGrrUDESECONDS
LATQ
LONQ
FIELDID
BLOCKID
ADDRESS
STREET1
STREET2
CITY
COUNTY
STATE
ZIP
ZIPEXT
SECTION
TOWNSHIP
RANGE
CONTAINERTYPE
TANKCAPACITY
TANKUNITS
FACiLrrYCAPAcrrY
FACiLrrYUNrrs
TYPE
NUMBER
NUMBER(4,1)
CHAR(2)
CHAR(3)
CHAR(5)
NUMBER(2)
NUMBER(2)
NUMBER(2)
NUMBER(3)
NUMBER(2)
NUMBER(2)
CHAR(1)
CHAR(1)
CHAR(25)
CHAR(5)
CHAR(25)
CHAR(25)
CHAR(25)
CHAR(20)
CHAR(25)
CHAR(2)
CHAR(5)
CHAR(4)
CHAR(10)
CHAR(20)
CHAR(10)
CHAR(1)
NUMBER(8)
CHAR(3)
NUMBER(8)
CHAR(3)
IRIS
Distance from City
Units
Direction from City
Milepost
Latitude Degrees
Minutes
Seconds
Longitude Degrees
Minutes
Seconds
Latitude Quadrant
Longitude Quadrant
Area ID
Block ID
Incident
Address/Location
Line 1
Incident
Address/Location
Line 2
Incident
Address/Location
Line 3
Nearest City
County
State
Zip
Section
Township
Range
Container Type
Tank Cap.
Units
Facility Cap.
Units
EXPLANATION
NRC report
number
-------
TABLE
MATERIALINVOLVED
MATERIALINVOLVED
MATERIALINVOLVED
-
MATERIALINVOLVED
MATERIALINVOLVED
MATERIALINVOLVED
MATERIALINVOLVED
MATERIALINVOLVED
MATERIALINVOLVED
COLUMN
SEQNOS
CHRISCODE
SPILLEDQTY
SPILLEDUNIT
WATERQTY
WATERUNIT
MATERIALNAME
CASNUMBER
DOTNUMBER
TYPE
NUMBER(7)
CHAR(3)
NUMBER(8,2)
CHAR(3)
NUMBER(8,2)
CHAR(3)
CHAR(50)
CHAR(7)
CHAR(7)
IRIS
Call*
CHRIS Code
Released Quantity
Unit of Measure
Quantity in Water
Unit of Measure
Released Material
EXPLANATION
NRC report number
Chemical
Abbreviation Code
Amount of
material released
Unit of Measure
used for released
material
Amount of
material released
that went into
water
Unit of Measure
used for quantity
in water
Released Material
Chemical
identification code
Chemical
identification code
-------
TABLE
NOTIFICATION
NOTIFICATION
NOTIFICATION
NOTIFICATION
NOTIFICATION
NOTIFICATION
NOTIFICATION
NOTIFICATION
NOTIFICATION
NOTIFICATION
NOTIFICATION
.
NOTIFICATION
NOTIFICATION
COLUMN
SEQNOS
DATENTERED
TIMENTERED
UNTTID
PERSONOTIFffiD
AREACODECALLED
PHONENUMBERCALLED
ORGANIZATION
TIMECALLED
USERID
LASTNAME
CASENUMBER
NOTMCATIONTYPE
TYPE
NUMBER(7)
DATE
DATE
CHAR(7)
CHAR(25)
NUMBER(3)
NUMBER(7)
CHAR(35)
DATE ,
CHAR(16)
CHAR(25)
CHAR(5)
CHAR(1)
IRIS
Call*
EXPLANATION
NRC report .
number
Date of
Notification
Time of
Notification
Abbreviation of the
organizations the
NRCnotifies
Person the NRC
notified
Areacodeof the
notification phone
number
Phone number of
the notification
Organization the
NRC notified
NRC watchstander
who made the
notification
Lastnameofthe
NRC watchstander
who made the
notification
Classify types of
notifications
-------
TABLE
RAILROAD
RAILROAD
RAILROAD
RAILROAD
RAILROAD
COLUMN
SEQNOS
RADLROADNAME
TRAINUMBER
TRAINDERAILED
NOOFCARSDERAELED
TYPE
NUMBER(7)
CHAR(25)
CHAR(10)
CHAR(1)
NUMBER(3)
IRIS
Call*
Name of Railroad
Train Number
Was Train
Derailed?(Y/N/U)
Number of Cars
Derailed
EXPLANATION
NRC report
number
Name of the
Railroad involved
Number of cars
derailed
-------
-------
ERNS Datafield Dictionary
-------
-------
Emergency Response Notification
System Data Dictionary
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
April 14, 1994
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY 1
WHATISERNS?
The Emergency Response Notification System (ERNS) is a computer data base containing information on release
notifications of oil and hazardous substances that have occurred :throughout the United States and have been
reported to the National Response Center (NRC),, the ten EPA Regions, or the U.S. Coast Guard. The initial
notification data may be updated with information from various Federal, State, and local response authorities as
appropriate. ERNS data can be used to analyze release notifications, support emergency planning efforts,.and to
assist decision makers in developing spill prevention programs.
DATA LIMITATIONS
Because ERNS is a data base of initial notifications and not incidents, there are several limitations to the data.
ERNS primarily contains initial accounts of releases, made during or immediately after an incident, when exact
details are often unknown. These data are usually not updated unless an EPA Region is involved in the response
action. In addition, there may be multiple reports for a single incident. (This occurs when the caller makes a
second report to update original data, or a private observer reports a release that has already been reported by the
facility.) Because reports are taken over the phone, transcription errors (e.g., misspellings of discharger or
location information) occasionally limit the quality of some data.
STRUCTURE OF THE ERNS DATA BASE
The structure of the ERNS data base was recently upgraded to a relational structure. There are three data sets
which contain information regarding the release reports, TELE, MATERIAL and DISCHRGR. The TELE data
set contains general information about the release. For each report to ERNS there is an initial record in the TELE
data set. When these data are updated, a "most up to date" record is then added. Information about the
discharger and the material released are located in the DISCHRGR and MATERIAL data sets respectively. Each
TELE record is associated with as many MATERIAL records as there were materials reported.
TELE
DISCHRGR
MATERIAL
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY 2
HOW TO USE THE DATA DICTIONARY
The data dictionary is a complete list of the available fields hi ERNS at the time of the most recent upgrade to the
ERNS system, which occurred in January 1994. Provided below is a brief description of the type, of information
that is available hi the data dictionary.
Field Name
Abbreviation
Definition
Data Code
This column provides the name of the field as it appears in the ERNS data base.
This column provides the abbreviation that is used and accepted by the ERNS system.
This column provides an explanation of the information that may be found within that
field. In addition, this column may specify the location of the data field and the dates
that the field is present hi the ERNS data base. It should be assumed that the field is
located in the TELE data set unless otherwise stated.
This column contains a one-letter code which indicates the data collecting organizations
that use the field:
T = Volpe National Transportation System Center
N = National Response Center _
R = One of the ten U.S. EPA Regions
COMMONLY USED ACRONYMS IN THE DATA DICTIONARY
CERCLA Comprehensive Environmental Response, Compensation, and Liability Act of 1980
DOT Department of Transportation
EPA Environmental Protection Agency
ERNS Emergency Response Notification System
HMIS Hazardous Material Information System
NRC National Response Center
OSC On-Scene Coordinator
PRP Potentially Responsible Party
RQ Reportable Quantity
USCG United States Coast Guard
VNTSC Volpe National Transportation System Center
-------
EMERGENCY RESPONSE NOTEFTCATTON SYSTEM (ERNS) DATA DICTIONARY
Field Name
ACTION MEMO APPROVED
ACTION MEMO DATE
ACTION TEXT
AGENCIES NOTIFIED BY NRC
BLOCK ID
Abbreviation
ACTMEMAPPR
ACTMEMDATE
ATEXT
AGENC
BID
CALLER NOTIFIED
CALLER SAME AS DISCHARGER
CAS
CAUSE CODE
Definition
Indicates if an action memo was approved. An
action memo is required prior to expenditure of
Superfund money. (1992-present)
The action memo approval date. An action memo
is required prior to expenditure of Superfund
money.. (1992-present) .
Description of response actions taken as a result of
a notification. (1987-present)
Agencies notified of the release by the NRC.
(1987-present)
Part of a grid system of areas and blocks used in
the Gulf of Mexico by the United States Coast
Guard (USCG) to determine platform locations as-
well as sheen sightings (used in conjunction with
FIELDJD). (1991:present)
Authorities that the individual reporting the release
notified. (1987-present)
Indicates whether the person reporting the release is
the person responsible for the release. (1987-
present)-
The Chemical Abstracts Service (CAS) Registry
Number for the substance released. ERNS stores
information on up to three substances for each
report. This field is located in the MATERIAL
data set. (1987-present)
N ;
CAUSE_CODE Code used to describe the cause of the incident.
(1992-present)
AA = Overturning
AB = Collision
AC = Fire
AD = Explosion '
AE = Grounding
AF = Sinking
AG = Derailment
AH = Pipeline Blowout
BA = Broken Containers
BB = Tank or Container
BC = Valve
BD = Flange
BE =Hose
BF = Fitting
BG = Alarm
BH = Automatic Shutoff
Data
code
TR
TR
TNR
TN
TN
CNOTIF
SPLR
CAS
TNR
T
TR
TR
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
Field Name
CAUSE_CODE (cont.)
Abbreviation
CAUSE CODE
Definition
CGJJNIT
CHEMID
CGU
CID
CHEMTREC
CHEMTREC
BI = Dike
BJ = Pump
BK = Hull
BL = Well Head
BM = Flow Line
BN = Pipeline
BO = Manifold
BP = Structural
BQ = Weld
BR = Container Leak
BS = Lact Upset"
BT = Treater Upset
BU = Power Failure -
BV = Power Oil Line
CA = Improper Maintenance
CB = Improper Operation
CC = Improper Hose Connection
CD = Improper Secured Flange
CE = Improper Storage/Handling
CF = Improper Design
CG = Improper Training
CH = Improper Communication
CI = Improper Valve Handling
CJ = Overflow
CK = Failure to Shutdown
DA = Flooding
DB = Freezing
DC = Wind
DD = Natural Seepage
DE = Rain or Snow
DF .= Lightning
.EA = Improper Disposal
EB = Deliberate
FA = Unknown
GA = Vandalism
GB = Sabotage
The USCG unit that received the release
notification from the NRC. (1987-present)
Volpe National Transportation System Center
(VNTSC) generated identifier used to speed cross
referencing to the Agency chemical data base. This
field is located in the MATERIAL data set. (1987-
present)
Indicates if the Chemical Transportation
Emergency Center (CHEMTREC), an emergency
information center sponsored by the chemical
industry, was notified of the release by the agency
Data
code
TR
TN
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
Field Name
CHRIS_CODE
CITYJJNITS
COMPASSJKEADING
CONFIDENTIAL
CONTAINER TYPE
Abbreviation
CC
CUNITS
COMP
CONFID
CTYPE
CR NUMBER
CR TYPE
CR NO
CR TYPE
DAMAGES
DATE_CANCEL_LETTER
DATE HARDCOPY
DAM
DCANL
DHC
Definition
receiving the release notification. (1987-present)
The Chemical Hazards Response Information
System (CHRIS) code of the substance released.
This field is located in the MATERIAL data set.
(1987-present)
The units of distance used in the "
"DISTANCE_fFROM_CITY" field. (1991 -present)
KM = Kilometers
MI = Miles
The location of the nearest city to the release,
expressed in compass directions. (1991-present)
Indicates if the caller information is confidential.
(1987-present)
Describes the type of container from which the
release occurred. (1991-present)
A = Above Ground Container
B = Below Ground Container
U = Unknown
The continuous release, number associated with this
report, if applicable. An initial CR number is
assigned by the NRC. See CR_TYPE. (1990-
present)
The type of continuous release being reported; A
continuous release is one that occurs without
interruption or abatement or that is routine,
anticipated, and intermittent and incidental to
normal operations or treatment processes. Once an
initial continuous release is reported only certain
types of changes are required to be. reported. See
CERCLA section 103(f)(2). (1990-present)
A = Annual Change
B = Baseline Change
C = Change in Source or Composition
I = Initial Report of Continuous Release
S = Statistically Significant Increase in
Release
Indicates if damages were incurred as a result of the
release. (1987-present)
The date on the cancellation letter. This letter is
sent by the individual responsible for the release,
and states that the release did not meet or exceed
mandated reporting requirements. (1987-present)
The date the hard copy of the release report was
Data
code
TNR
TN
T
TNR
TN
TNR
TNR
TNR
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
Field Name
DATE_SPILL
DC
DD
DE
DEATHS
DESCRIPTIONJTEXT
D1SCH ORG TYPE
DISCHARGER ADDRESS
DISCHARGER CITY
DISCHARGER COUNTY
DISCHARGER ID
DISCHARGER NAME
Abbreviation Definition
received by VNTSC. (1987-present)
DASPI The date the release was reported to have occurred.
(1987-present)
DC Used by VNTSC to indicate the date that the latest
change to the report was made by the U.S. EPA
Region. This field is located in the MATERIAL
and DISCHRGR data sets. (1987-present)
DD The date that the report was deleted from the
system. This field is located in the MATERIAL
and DISCHRGR data sets. (1987-present)
DE The date that the report was entered into the
system. This field is located in the MATERIAL
and DISCHRGR data sets. (1987-present)
DBA The number of fatalities resulting from the release.
These fatalities may either be the result of the
accident causing the release, or from exposure to
the substance released., (1987-present)
DTEXT Descriptive text offering information on the
release. (1987-present)
DORGT The type of organization with which the Potentially
' Responsible Party (PRP) is affiliated. This field is
located in the DISCHRGR data set. (1987rpresent)
FG = Federal Government
LG = Local Government
PC = Private Citizen
PE = Private Enterprise
PU = Public Utility
SG = State Government
UN = Unknown.
DADD The street address where the PRP is located. This
field is located in the DISCHRGR data set. (1987-'
present)
DCITY The city where the PRP is located. This field is
located hi the DISCHRGR data set. (1987-present)
DCOUNTY The county where the PRP is located. This field is
located in the DISCHRGR data set. (1987-present)
DID A unique number assigned to each report used in
mapping reports to the discharger data set. This
field is located in the DISCHRGR data set. (1992-
present)
DNAME The name of the person considered to be the PRP
for the release. This field is located in the
Data
code
TNR
T
TNR
TNR
TNR
TNR
TNR
TNR
T
TNR
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
Field Name
DISCHARGER_ORG
DISCHARGERJPHONE
DISCHARGER_STATE
DISCHARGER_ZIP
DISCOVERYJDATE
DISTANCE_FROM_CITY
DOTJFAA
DOTJFRA
DOT_OMCS
DUMPING
DUN BRADSTREET
DUTY OFFICER
Abbreviation
DORG
DPH(1,2)
DST
DZIP
DDATE
DIST
DOT_FAA
DOT_FRA
DOT_OMCS
DUMP
DUNS
DO
ENFORCEMENT_ACTIVITY_CODES ENFOR ACT
Definition Data
code
DISCHRGR data set. (1987-present)
The name of the organization considered to be the TN
PRP for the release. This field is located in the
DISCHRGR data set. (1987-present)
The telephone number, including area code, of the TNR
PRP. A single report may have up to two
telephone numbers stored in ERNS. This field is
located hi the DISCHRGR data set. (1987-present)
The State where the PRP is located. This field is . TNR
located in the DISCHRGR data set. (1987-present)
The five- or nine-digit postal zip code of the area TNR
where the PRP is located. This field is located in
ฃhe DISCHRGR data set. (1987-present)
The date the reporting individual discovered the TR
release. (1992-present)
The distance of the release from the nearest city. TN
(1991-present)
Indicates if the Federal Aviation Administration TN
(FAA) was notified of the release by the agency
receiving the release notification. (1987-present)
Indicates if the Federal. Railway Administration TN
(FRA) was notified of the release by the agency
receiving the release notification. (1987-present)
Indicates if the Office of Motor Carrier Safety TN
(OMCS) was notified of the release by the agency
receiving the release notification. (1987rpresent)
Indicates if the release was caused by dumping. TNR
This field is one of a group of seven logical cause
fields hi ERNS including DUMPING,
EQUIPJFAILURE, NATURAL_
PHENOMENON, OPERATORJERROR,
OTHER_CAUSE, TRANS_ACCIDENT, and
UNKNOWN, (1987-present) .
The Dun and Bradstreet number assigned to the TR
organization responsible for the release. (1992- :
present)
The name of the NRC duty officer who received TNR
the report. (1987-present)
The enforcement activity codes associated with the TR
incident. A single report may have up to 5 codes
stored in ERNS. (1992-present)
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
8
Field Name
Abbreviation
Definition
Data
code
ENFORCEMENT_ACTIVITY_CODES ENFOR_ACT
(cont.)
AC =
AN =
AV =
CA =
CB =
CD =
CL =
DD =
DL =
FA =
FC =
FI =
FN =
FU =
IL =
JG =
NB =
NE =
NI =
NS =
NW=
PC =
PI =
RN
RP =
SN =
sv =
sx =
TE =
UA
Administrative Order on Consent
RD/RA Negotiations
Administrative/Voluntary Cost
Recovery
Consent Agreement
Claim on Bankruptcy Proceeding
Consent Decree
Section 106/107 Litigation
Issue Cost Recovery Decision
Document Not to Sue
Issue Demand Letters
Federal Memorandum of Agreement
Federal Compliance Agreement
Federal Interagency Agreement
RI/FS Negotiations
Federal Memorandum of
Understanding
Issue Information Request Letters
(104E)
Judgement
Non-binding Allocation of
Responsibility
Cost Recovery Negotiations
Issue Notice Letters
NPLRP Search
Issue Notice of s!22 Waiver
Prepare Cost Documentation
Package
Preliminary Injunction
= Removal Negotiations
= Non-NPL Removal RP Search
=.Issue Special Notice
= Section 107 Litigation
= Section 106 Litigation
= Temporary Restraining Order
=Unilateral Administrative Order
TR
EPA
EPA REGION
EPA REPORTING NAME
EPA REPORTING SOURCE
EPA
EPAR
RNAME
RSOURCE
Indicates if the U.S. EPA was notified of the
release by the person reporting the release. (1987-
present)
The U.S. EPA Region which (1) directly received
the initial report, or (2) was notified of the incident
bytheNRC. (1987-present)
The name of the agency which was first to receive
the report. (1993-present)
The type of agency from which the report was
received. (1993-present)
TN
TN
TR
TR
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
Field Name
Abbreviation
EPAJJNIQUEJDENTIFIER
EQUIPJFAILURE
TRANSNUMB
EQUIP
ER_ACTVTY
ERAJDATE
ERA_OSC
ERROR_CODE
EVACUATIONS
FACILITY_CAPACITY
FACILITY UNITS
ER_ACTVTY
ERA_DATE
ERA_OSC
ERRC
EVAC
FCAP
FUNITS
FIELD ID
FID
Definition
C
E
F
M
N
$
= USCG
= EPA Region
= Other Federal agency
News media
= NRC
= State agency
Data
code
A unique number generated by the system to
identify the report. This field is hidden from the
user. (1987-present)
Indicates if the release was caused by equipment
failure. This field is one of a group of seven
logical cause fields in ERNS including DUMPING,
EQUnVFAILURE, NATURAL_
PHENOMENON, OPERATOR_ERROR,
OTHER_CAUSE, TRANS_ACCIDENT, and
UNKNOWN, (1987-present)
Indicates if the emergency response activity was
defined by the Superfund Comprehensive
Accomplishments Plan (SCAP). (1992-present)
The date emergency response activity began.
(1992-present)
The name of the OSC who responded to the
release. (1992-present)
An internal code used by Hazardous Material
Information System (HMIS) to indicate a failure in
. either uploading or translating the data. (1987- .
present)
Indicates if people were evacuated as a result of the
release. (1987-present)
The capacity of the facility involved in the release.
(1991-present)
The units of measure used in the
"FACILITY_CAPACITY" field: (1991-present)
BBL = Barrels
GAL = Gallons
LBS = Pounds -
TON = Tons
. UNK= Unknown
Part of a grid system of areas and blocks used in
the Gulf of Mexico by the USCG to determine
platform locations as well as sheen sightings, (used
in conjunction with BLOCK_ID). (1991-present)
TR
TNR
TR
TR
TR
T
TNR
TN
TN
TN
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
10
Field Name
FLIGHT_PATTERN
FOLLOWNUM
FOLLOWUP CODES
ID
INCIDENT STAT
INITJRPT
INJURIES
JURISDICTION
LATITUDE_DEGREES
LATITUDE_MINUTES
LATITUDE_SECONDS
LOCATION_TEXT
LONGITUDE DEGREES
Abbreviation
FLIGHT
FOLLOWNUM
FOLLOWUP
ID
ISTAT
INIT
INJ
JURI
LATD
LATM
LATS
LTEXT
LONGD
Definition Data
code
Indicates if the operational flight pattern or routine TN
of an aircraft was altered because of the release.
(1992-present)
The number of times that the report has been TR
updated. This number is hidden to the user.
(1993-present)
The type of update that was made, if an update has TR
been made to the original report (e.g.,
typographical correction, data correction, or
information resulting from an EPA response
action). (1993-present)
A unique sequential number assigned by the T
computer to each report in the material data set.
This field is located in the MATERIAL data set.
(1987-present)
Codes detailing the incident status. (1992-present) TR
CL = Classic Incident
CR = Critical Incident .
FS = Field Simulation
NA = No Further Action
NC = Non-critical Incident
RA = Remedial Action
Indicates if the release report in ERNS is an initial T
report. (1992-present)
The number of injuries resulting from the release. TNR
These injuries may either be the result of the
accident causing the release, or from exposure to
the substances released. (1987-present)
The U.S. EPA Region that has jurisdiction if the T
release occurred hi an area overlapping two U.S.
EPA Regions. (1987-present)
The geographic location of the release as expressed TN
hi degrees latitude. (1990-present)
The geographic location of the release as expressed TN
hi minutes latitude. (1990-present)
The geographic location of the release as expressed TN
hi seconds latitude. (1990-present)
Miscellaneous location information on the release. TNR
(1987-present)
The geographic location of the release, as expressed TN
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY 11
Field Name
LONGITUDE_MINUTES
LONGITUDEJSECONDS
MATERIALS_RELEASED
MATERIALS_SPILLED
MCASEJD
MED_AIR
MEDJFACILITY
MED_GROUND WATER
\
MED_LAND
MED_OTHER
MED_WATER
MEDCODE
Abbreviation
LONGM
LONGS
MATS
MATSP
MCASEJD
MAIR
MFAC
MGRD
MLAND
MOTH
MWATER
MEDCODE
Definition D_ata
code
in degrees longitude. (1990-present)
The geographic location of the release, as expressed TN
hi minutes longitude. (1990-present)
The geographic location of the release, as expressed TN
in seconds longitude. (1990-present)
Indicates if any substances were actually released. TN
This field is located in the MATERIAL data set.
(1991-present)
The name of the.substance or substances released. TNR
This field is located hi the MATERIAL data set.
(1987-present)
The multiple case identification number in the U.S. TR
EPA Region. (1992-present)
Indicates if the release affected the air. This field TNR
is one of a group of six logical medium fields in
ERNS. (1987-present)
Indicates if the release is contained within the fixed TR
facility. This field is one of a group of six logical
medium fields hi ERNS.'(1987-present)'
Indicates if the release affected groundwater. This TNR
field is one of a group of six logical medium fields
in ERNS. (1987-present)
Indicates if the release affected land. This field is TNR
one of a group of six logical medium fields in ' '
ERNS. (1987-present)
Indicates if media, other than those listed TR
specifically hi ERNS, were affected. This field is
one of a group of six logical medium fields in
ERNS. (1987-present)
Indicates if the release affected water. This field is TNR
one of a group of six logical medium fields hi
ERNS. (1987-present)
The code describing the medium to which the
substance(s) was released. (1992-present)
AA = Explosion
AB = Evaporation
AC = Sublimation
AD = Spray
BA = Ground
BB = Roadway
BC = Parking Lot
BD = Concrete
TR
-------
EMERGENCY RESPONSE NOTIFIGATION SYSTEM (ERNS) DATA DICTIONARY
12
Field Name
MILEPOST
MISC_ATSDR
MISC_DOD
MISCJDOE
MISCJFEMA
MISC_NRC
MISC_OSHA
MISCELLANEOUS TEXT
Abbreviation Definition Data
code
BE = Beach Water -
CA = Stream
CB = River
CC = Sewer
- CD = Lake
CE = Pond
CF = Ditch
CG =. Reservoir
CH = Canal
CI = Ocean
CJ = Estuary
. CK = Inlet
CL = Creek
CM = Irrigation
DA = Well
DB = Aquifer
EA = Within Building
EB = Within Processing System
EC = On Concrete or Asphalt
ED = On Ground
MILEPOST The highway or waterway mile marker number
where the release occurred. (1991-present)
MISC_ATSDR Indicates if the Agency for Toxic Substances and
Disease Registry (ATSDR) was notified of the
release by the agency receiving the release
notification. (1992-present)
MISC_DOD Indicates if the Department of Defense (DOD) wats
notified of the release by the agency receiving the
release notification. (1987-present)
MISC_DOE Indicates if the Department of Energy (DOE) was
notified of the release by the agency receiving the
release notification. (1987-present)
MISC_FEMA Indicates if the Federal Emergency Management
Agency (FEMA) was notified of the release by the
agency receiving the release notification. (1987-
present)
MISC_NRC Indicates if the Nuclear Regulatory Commission
(NRC) was notified of the release by the agency
receiving the release notification. (1987-present)
MISC_OSHA Indicates if the Occupational Safety and Health
Administration (OSHA) was notified of the release
by the agency receiving the release notification.
(1992-present)
MTEXT Miscellaneous information on the release. (1987- TNR
TN
TN
TN
TN
TN
TN
TN
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
13
Field Name
1 -
MOST_UP_TO_DATE
MREPT_CNT
MULTIPLE
MULTIPLE_CASE_NO
N_DISCHARGER
Abbreviation
MUD
MREPT_CNT
MULT
MCASE .
DIS
Definition
present)
Indicates if the report is the most recently updated
version. (1992-present)
Count of the multiple reports received for a release.
(1992-present)
Indicates if a particular report is part of a multiple
report group. (1992-present)
The Regional case number initially assigned by the
U.S. EPA Region. (1992-present)
Indicates if the person responsible for the release
Data
code
T
TR
TR
TR
T
N OTHER
N UNKNOWN
NATURAL PHENOMENON
NEW_CODE
NO_OF_EVACUATIONS
NUM ON REGIONAL REPORT
NOTH
NUNK
NATL
CODE
EVACS
RNO2
NTSB HIGH
NTSB PIPE
NTSB HIGH
NTSB PIPE
was notified by the agency receiving the release
notification. (1987-present)
Indicates if agencies, other than those specifically TN
listed in ERNS,-were notified of the release by the
person reporting the release. (1987-present)
Indicates if it is unknown who was notified of the T
release. (1987-present)
Indicates if the release was caused by a natural TNR
phenomenon. This field is one of a group Of seven
logical cause fields in ERNS including DUMPING,
EQUIP_FAILURE, NATURAL_
PHENOMENON; OPERATOR_ERROR,
OTHER_CAUSE, TRANS_ACCIDENT, and
UNKNOWN. (1987-present)
An internal code used by HMIS. (1987-present) T
Count of the number of people evacuated because TNR
of the release. (1991-present)
The original report number when a report TR
originally received by the NRC is updated by an
EPA Region. If a report has not been updated, this
field is left blank. See REPORTJSTUMBER.
(1992-present).
Indicates if the National Transportation Safety TN
Board (NTSB) was notified of the release by the
agency receiving the release notification. (1992-
present) " '
Indicates if the National Transportation Safety _ TN
Board (NTSB) or the Office of Pipeline Safety was
notified of the release by the agency receiving the
release notification. (1987-present)
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
14
Field Name
NTSB RAIL
ON SCENE MONITORING
OPERATOR ERROR
ONSCEN_MON
OPP
OTHER CAUSE
OC
OWN ID
POLLUTION REPORT ISSUED DATE POL R DATE
PROPERTY DAMAGE
QUA_IN_LBS
QUADJLAT
QUADJLONG
QUANTITY_IN_WATER
QUANTITY_SPILLED
Abbreviation Definition
NTSBJRAIL Indicates if the National Transportation Safety
Board (NTSB) or the Federal Railway
Administration was notified of the release by the
agency receiving the release notification. (1987-
present)
Indicates if the release required on-scene
monitoring. (1992-present)
Indicates if the release was caused by operator
error. This field is one of a group of seven logical
cause fields in ERNS including DUMPING,
EQUIPJFAILURE, NATURAL_
PHENOMENON, OPERATOR_ERROR,
OTHER_CAUSE, TRANS_ACCIDENT, and
UNKNOWN. (1987-present)
Indicates if the release was due to a cause other
than those specifically listed in ERNS. This field
is one of a group of seven logical cause fields in
ERNS including DUMPING, EQUIP_FAILURE,
NATURALJPHENOMENON, OPERATOR^
ERROR, OTHER_CAUSE, TRANS_ACCIDENT,
and UNKNOWN. (1987-present)
OWN_ID . A unique sequential number, assigned by the
computer, to each report. (1987-present)
The date that a pollution report (POLREP) was
issued by the Federal OSC, if a POLREP was
issued. (1992-present)
The estimated cost of the property damages
resulting from the release. (1987-present)
The quantity of the substance'released, converted
into pounds. This conversion is done so that the
substance released can be readily compared to
standard RQ levels. This field is located in the
MATERIAL data set. (1987-present)
QUADJLA The quadrant of latitude where the release
occurred. (1990-present)
QUAD_LO The quadrant of longitude where the release
occurred. (1990-present)
QUAW The amount of the substance released into the
water. This field is located in the MATERIAL
data set. (1987-present)
QUA The total quantity of the substance released. This
field is located in the MATERIAL data set. (1987-
Data
code
TN
TR
TNR
PROP
LBS
TNR
T
TR
TN
TR
TN
TN
TNR
TNR
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY 15
Field Name
RANGE
RELEASE INVESTIGATION
REPORT DATE
REPORT NUMBER
REPORT TIME
REPORTABLE
RESPONDING AGENCY
RESPONDING AGENCY CODE
ROAD CLOSURE
RSPA OHM
Abbreviation Definition D_ata
code
present)
RANGE" The geographic survey description used in some TN
. states, expressed in geographic range. (1991-
present)
RELJNVEST Indicates if a U.S. EPA release investigation has TR
taken place. (1992-present)
RDATE The date when the report was received by the NRC TNR
or an EPA Region. (1987-present)
RNO The number assigned by the agency who received TNR
the request. (1987-present)
RTIME . The local time the report was received by the NRC TNR
(Eastern Time), or the U.S. EPA Region, based on
24 hour military time. (1987-present)
RPT Indicates if the spill met the:reporting requirements TN
of the DOT'S Office of Hazardous Materials Safety
(OHMS) for all transportation related reports.
(1987-present)
E = Enforcement Action Required
L = Cancellation Letter Filed
W = Met Reporting Requirements
The agency responding to the release. ERNS stores - TR
information on multiple agencies for each release.
A single report may have the names of up to three
agencies stored hi ERNS. (1989-present)
The code used to describe the agency responding to TR
the release. ERNS stores information on multiple
agencies for each release. A single report may
have up to three agency codes stored in ERNS.
(1989-present)
_. D = Discharger
E = U.S. EPA
F = Federal
L = Local' --" '-.':...
O = Other
S = State ,
U = Unknown.
ROAD Indicates if the incident forced one or more major T
transportation arteries to be closed for one or more
hours. (1992-present)
RSPA_OHM Indicates if the Research and Special Programs TN
Administration (RSPA) or the Office of Hazardous
, Materials (OHM) was notified of the release by the
agency receiving the notification. (1987-present)
R_NAME(1,2,3)
RAGE(1,2,3)
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
16
Field Name
RSPA OPS
SECTION
SOURCE AGENCY
SOURCE CODE
Abbreviation Definition
RSPA_OPS Indicates if the Research and Special Programs
Administration (RSPA) or the Office of Pipeline
Safety (OPS) was notified of the release by the
agency receiving the notification. (1987-present)
SECT The geographic survey description used in some
states, as expressed in geographic section. (1991-
- present)
SRC Indicates if the NRC, U.S. EPA, or the Marine
Safety Information System (MSIS) received the
initial report. (1987-present)
SOURCE Code describing the source of the release. (1992-
present)
AA = Dry Cargo
AB = Liquid Cargo
AC = Vehicle Fuel Tank
BA = Pick Up
BB = Platform
BC = Van or Panel
BD = Dump
. . BE = Tractor Trailer
BF = Tank
CA = Airplane Fuel Tank
CB = Airplane Cargo
DA = Locomotive Fuel Tank
DB = Tank Car
DC = Flat Car
DD = Hopper Car
DE = Refrigerator Car
DF = Dry Cargo
DG = Liquid Cargo
EA = Dry Cargo
EB = Liquid Cargo
EC = Vessel Fuel Tank
FA = Private Boat
FB = Commercial
FC = Tow Board
FD = Tug Boat
FE = Roro
FF = Containerized
FG = Tanker
FH = Barge
GA = Plant
GB = Distributor
GC = Plant Piping
GD = Production
GE = Refining
GF = Power Plant
Data
code
TN
TN
TR
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
17
Field Name
Abbreviation
SQURCE_CODE (cont.)
SOURCE
SPILL_CITY
SPILL_COUNTY
SPILL DTG TYPE
SPILL_REGION
SPILL SAME LOG
SPILLJSTATE
SPILLJZIP
STATE_LOC
TANK CAPACITY
SCITY
SCOUNTY
DTG
EPAR2
SAMEL
SST
SZIP
STLOC
TCAP
Definition
GG = Hazardous Waste Site
GH = Transformer .
GI - Railroad Yard
GJ = Consumer
GK = Underground Storage Tank
GL = Gasoline Station
GM = Water Treatment .
HA = Lines
HB = Pumping Station
HC = Inlet
HD = Outlet
HE = Valve or Fitting ' . - -
IA = Production
IB = Storage
1C = Transport (to Shore Only)
ID = Equipment
JA = Air Release
The city where the release occurred. (1987-
preserit)
The county where the release occurred, (1987-
present)
A code that indicates if the release occurred, was
planned, or was discovered. (1987-present)
D = Discovered
O = Occurred
P = Planned
Blank = Other
The U.S. EPA Region where the spill occurred.
(1990-present)
Indicates if the release occurred in the same
location as the caller or the discharger. (1987-
present) ' '
A = Caller
B = Discharger
The State where the release occurred. (1987-
present)
The five- or nine-digit zip code of the area where
the release occurred. -
Indicates if any State or local authorities were
notified of the release by the person reporting the
release. (1987-present)
The capacity of the storage tank involved in the .
release, if a storage tank was involved. (1991-
Data
code
TR
TNR
TNR
TN
T
TN
TNR
TNR
TN
TNR
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
18
Field Name
TANK_COUNT
TANK UNITS
TECHNICAL_DIRECTION
DOCUMENT NUMBER
TELEPHONE ASSISTANCE
THREAT CODES
TDD NUMBER
TELE ASSIS
THREATS
TIME CO
TIME EPA
TIME OTHER
Abbreviation Definition
present)
TANK_CT The number of storage tanks at the facility where
the release occurred. (1992-present)
TUNITS The units of measure used in the
"TANK_CAPACITY" field. (1991-present)
BBL = Barrels
GAL = Gallons
LBS = Pounds
TON = Tons
UNK= Unknown '
The technical direction document number that
corresponds to the work conducted by the
Technical Assistance Team (TAT) at the incident
location. (1992-present)
Indicates if the U.S. EPA provided any form of
guidance to an outside agency of discharger over
the phone. (1992-present)
A code which indicates if the release has caused, or
has the potential to cause, threats of harm to public
health, property, or the environment. A single
report may have up to five codes stored in ERNS.
(1992-present)
AC = Air Contamination
DS = Direct Contact: Skin
DG = Direct Contact: Ingestion
DH = Direct Contact: Inhalation
DU = Direct Contact: Non-Specific
DW = Drinking Water Contamination
EC = Ecological Damage
FE = Fire/Explosion Hazard
. GW = Groundwater Contamination
SC = Soil Contamination
SW = Surface Water Contamination
WC = Wetlands Contamination
OH = Other
TIME_CG The local time that the NRC (Eastern Time) passed
the report to the USCG, based on 24 hour military
time. (1987-present)
TIME_EPA The local time that the NRC (Eastern Time) passed
the report on to the U.S. EPA, based on 24 hour
military time. (1987-present)
TIME_OTHER The local time that the NRC (Eastern Time) passed
the report on to other agencies, based on 24 hour
military time. (1987-present)
Data
code
TR
TNR
TR
TR
TR
TN
TN
TN
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
19
Field Name
TIME_SPILL
TOWNSHIP
TRANS ACCIDENT
Abbreviation
TMSPI
TOWN
TRANS
TRANSPORT MODE
MODE
UNDOT
UNDOT
UNITS
UNITS
Definition
The local time the incident occurred, based on 24
hour military time. (1987-present)
The geographic survey description used in'some
states, expressed in geographic townships. (1990-
present)
Indicates if the release was caused by a
transportation-related accident. This field is one of
a group of seven logical cause fields hi ERNS
including DUMPING, EQUIP_FAILURE,
NATURALJPHENOMENON, OPERATOR_
ERROR, ,OTHER_CAUSE, TRANS_ACCIDENT,
and UNKNOWN. (1987-present)
A code indicating the type of transportation
involved with the release. A single report may
have up to two codes stored hi ERNS. (1987-
present) . -
A = Air Transport Related
F = Fixed Facility
G = Rail/Highway Crossing
H = Highway Related
M= Marine - released from a marine
vessel to inland waterway. (NRC)
O= Offshore - spilled off the coast
P = Pipeline Related
R = Railroad
S = Underground Storage Tank
T = Above Ground Storage Tank
U = Unknown (EPA Regions)
V = Marine Vessel (EPA Regions)
X = Unknown (NRC)
Code issued by the U.S. DOT to be displayed on
vehicles transporting hazardous substances. These
codes are used to identify substances in case of a
spill. This field is located in the MATERIAL data
set. (1987-present)
The units-of measure used in the
"QUANTITY_SPILLED" field. This field is
located in the MATERIAL data set. (1987-present)
BBL = Barrels
GAL = Gallons
LBS = Pounds
NON=None
OTH = Other
TON = Tons
UNK= Unknown
Data
code
TNR
TN
TNR
TNR
TR
TNR
-------
EMERGENCY RESPONSE NOTIFICATION SYSTEM (ERNS) DATA DICTIONARY
20
Field Name
UNITS IN WATER
Abbreviation
UNITSW
UNKNOWN
UNK
USCG
VEHICLEJD
WATERWAY AFFECTED
USCG
VID
WWY
Definition Data
code
The units of measure used in the TNR
"QUANTITY_IN_WATER" field. This field is
located hi the MATERIAL data set. (1987-present)
BBL = Barrels
GAL = Gallons
LBS = Pounds
NON = None
OTH = Other
TON = Tons
UNK = Unknown
Indicates if the release was due to an unknown TNR
cause. This field is one of a group of seven logical
cause fields in ERNS including DUMPING,
EQUIP_FAILURE, NATURAL_
PHENOMENON, OPERATOR_ERROR,
OTHER_CAUSE, TRANS_ACCIDENT, and
UNKNOWN. (1987-present)
Indicates if the USCG was notified of the release. TN
(1987-present)
The vehicle identification number of the vehicle TNR
involved in the incident, if the incident was
transportation related. (1987-present)
The name of the waterway, or body of water, that TR
was affected by the release. (1987-present).
-------
ARIP Datafield Dictionary
-------
-------
APPENDIX G . DATA DICTIONARY FOR ARIP91 DATABASE
'iTJBS
Question
No.
PART A
1
2
4
5
6
7
======
Data Field Name
ERNS-
NRC
REGION
LOGNO
FACNAME
DUNBRAD
FACSTR
FACCITY
FACCO
FACSTATE
FACZIP
FACPHONE
SPILLOC
SPILSTR
SPILCITY
SPILCO
SPILSTATE
SPDLZIP
SPILPHONE
LAT
LONG
ERNSDAT
ERNSTIME
FEDNOTIF
FEDCODE
FEDDAT1
FEDTIM1
FEDDAT2
FEDTIM2
FEDDAT3
FEDTIM3
FEDNAME1
FEDNAME2
"FEDNAME3
STANOTIF
STACODE
STAAGENCY
STADAT
STATIM
STANAME
LOCNOTEF
LOCAGENCY
LOCDAT
LOCTIM
LOCNAME
PRIMRESP
SECRESP
Description
ERNS identification no.
NRC identification no. -
EPA Region
ARIP identification no.
Facility name
Facility Dun & Bradstreet no.
Facility address
Facility city " .--
Facility county ,
Facility state
Facility zip code (5-digit)
Facility phone
Spill location the same as Facility address (Y/N)
Spill location address
Spill location city
Spill location county
Spill location State
Spill location zip code (5-digit)
Spill location phone
Latitude
Longitude
ERNS reporting date
ERNS reporting time
Were Federal authorities notified? (Y/N)
Federal authority identification codes
Federal .reporting date no. 1
Federal reporting time no. 1
Federal reporting date ho. 2
Federal reporting tune no. 2
Federal reporting date no. 3
Federal reporting time no. 3
Federal authority contact name no. 1
Federal authority contact name no. 2
Federal authority contact name no. 3
Were State authorities notified? (Y/N)
State authority identification codes
State authority name
State reporting date
State reporting time
State authority contact name
Were local authorities notified? (Y/N)
Local authority name
Local reporting date
Local reporting time
Local authority contact name
Primary responding agency
Secondary responding agency
Type
G6
N6
C2
CS
C30
Cll
C30
C30
C30
C2
C5
C14
01
C30
C30
C30
C2
C5
C14 '
C5
C6
D8
C5
Cl
C3
D8
C5
D8
C5
D8
C5
C20
C20
C20
Cl
Cl
C30
D8
CS
C30
Cl
C30
D8
C5
C30
C30
C30
Status
NEW
NEW,
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
'
NEW
NEW
-------
APPENDIX G - DATA DICTIONARY FOR ARIP91 DATABASE (CONT.)
Question
No.
PARTB
1
2
3
4
5
6
7
8
9
10
11
12
14
15
16
Data Field Name
NNAME
RESNAME
RESTTTLE
RESAGENCY
RESSTR
RESCUY
RESSTATE
RESZEP
RESPHONE
SIGNATURE
QUESCOM
S1C1
SIC2
SIC3
PRODUCT
NUMEMPL
RELSTDAT
RELSTTIM
RELENDAT
RELENTIM
HAZMN1
CASN1
HAZC1
HAZS1
HAZMQA1
HAZMQS1
HAZMQL1
HAZMQT1
HAZMQ1TOT
SECCHEM
HAZMN2
CASN2
HAZC2
HAZS2
HAZMQA2
HAZMQS2
HAZMQL2
HAZMQT2
HAZMQ2TOT
STATREL
STATCUR
RELLOC
RELDISC
RELCAUSE
ADDCAUSE
ENDEFF
PUBNOTIF
COMMTEC
Description
Owner name
Responding official's name
Responding official's title
Responding official's agency name
Responding official's street address
Responding official's city
Responding official's state
Responding official's zip code (5-digit)
Responding official's phone
Signature on ARIP form (Y/N)
Signature/form date
Facility SIC code
Facility SIC code
Facility SIC code
Primary product
Number of employees
Date release began
Time release began
Date release ended
Time release ended
Release chemical name
Release chemical CAS no.
Release chemical concentration
Release chemical physical state
Amount released to air Ob)
Amount released to surface water (Ib)
Amount released to land (Ib)
Amount released to facility treatment (Ib)
Total amount released
Was a second chemical released?
Second release chemical name
Second release chemical CAS no.
Second release chemical concentration
Second release chemical physical state
Amount released to air (Ib)
Amount released to surface water (Ib)
Amount released to land (Ib)
Amount released to facility treatment Ob)
Total amount released
When the release occurred
Status of process line at time of spill
Location of the lost containment
How release was discovered
Cause of release
Secondary cause of release
End effects of release
Was general public notified? (Y/N)
Technologies used
Type
C30
C30
C30
C30
C30
C30
C2
C5
C14
Cl
D8
C4
C4
C4
C50
N6
D8
C5
D8
C5
C30
Nil
CIO
CIO
N11.2
N11.2
N11.2
N11.2
N11.2
Cl
C30
Nil
CIO
CIO
N11.2
N11.2
N11.2
N11.2
N11.2
C7
C5
Cl
C9
Cl
C9
C5
Cl
C12
Status
NEW
NEW
NEW
NEW
NEW
TRANS
TRANS
TRANS
TRANS
TRANS
TRANS
-------
APPENDIX G - DATA DICTIONARY FOR ARIP91 DATABASE (CONT.)
Question
No.
17
18
19
20
21a
**
21b
22a
22b
23a
23b
Data Field Name
INJFACNUM
HOSFACNUM
DTHFACNUM
INJCONNUM
HOSCONNUM
DTHCONNUM
INJPUBNUM
HOSPUBNUM
DTHPUBNUM
INJRESNUM
HOSRESNUM
DTHRESNUM
CONTEVAC
CONTSHEL
FACE VAC
FACSHEL
NUMEVAC
NUMSHEL
IMMRESP
EKVCODE
CGSTFAC
COSTPUB
COSTTOT
HAZASS1
HAZASS1DT
HAZASS2
'( HAZASS2DT
iHAZASSS
' HAZASS3DT
HAZASS4
HAZASS4DT
HAZASS5
HAZASS5DT
HAZASS6
HAZASS6DT
HAZASS7
HAZASS7DT
HAZASS8
HAZASS8DT
HAZASS9
HAZASS9DT
HAZASS10
HAZASS11
HAZASS11DT
OPINION
PREMANPRAC
PREVFUT
SYSPROC
ENGSYS
Description
No. of facility employees injured
No. of facility employees hospitalized
No. of facility employee deaths
No. of contractors injured
No. of contractors hospitalized
No. of contractor deaths
No. of general public injured
No. of general public hospitalized
No. of general public deaths
No. of responders -injured ' '" ' .
No. of responders hospitalized
No. of responder deaths
No. of contractors evacuated
No. of contractors sheltered-in-place
No. of employees evacuated
No. of employees sheltered-uvplace
No. of general public evacuated
No. of general public sheltered-in-place
Immediate response activities
Environmental effects ,
Facility cost
General public cost
Total cost
Frequency of Cause-Consequence
Date last conducted
Frequency of Dow and Mond Hazard
Date last conducted
Frequency of Event Tree analyses
Date last conducted
Frequency of Failure/Effects analyses
Date last conducted
Frequency of Fault Tree analyses
Date last conducted '
Frequency of HAZOP Studies ;
Date last conducted
Frequency of Human Error analyses
Date last conducted
Frequency of Probabilistic Risk
Date last conducted
Frequency of "What If ' analyses
Date last conducted
No evaluation
Other evaluation
Date last conducted
Effectiveness of hazard evaluation
Procedures/practices used before spill
Procedures/practices used after spill
Systems and controls used before spill
Systems and controls used after spill
Type
' N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
N6
Cll
C7
N8.2
N8.2
.N9.2
N8.3
D8
N8.3
D8
N8.3
D8
N8.3
D8
N8.3
D8
N8.3
D8
N8.3
D8
N8.3
D8
N8.3
D8
N8.3
N8.3
D8
Cl
C13
C13
C13
C13
Status
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
TRANS
Note: NEW =-new field; TRANS = translated field; C = character; N = numeric; D = date; Type number = length.
-------
-------
HMIRS Datafield Dictionary
-------
-------
DATASET DESCRIPTIONS
DATABASE: [$TEMP]
DATASET: HAZMAT
DIRECTORY: INCIDENTS
This dataset contains information corresponding to the data fields on the front of the incident report
form that answers the questions when, what, where and how of the incident. This data is used to
generate various^ummary statistics. This dataset can be used to map to the HA2CON and HAZRMK
datasets.
DATASET: HAZMAT
FIELD NAME
REPORTJMUMBER
MULT!PLE_CODE
MODEJDFJRANSPORT
MODE_OTHER_DESC
DATE OF INCIDENT or
INCIDENT_DATE
TIMEJDFJNCIDENT
INCIDENT_CITY
INCIDENT_COUNTY
INCIDENT_STATE
INCIDENT_ROUTE
CARRIERJD
ABBREV
RPTNO
MTPL
MODE
MODEO
IDATE -
ITIME
ICITY
ICOUN
1ST
IROUT
CARID
TYPE
Text
Text
Int
Text
Date
Time
Text
Text
Text
Text
Text
DIRECTORY: INCIDENTS
SIZE
8
1 ,
3
16
10
5
25
22
2
30
9
DESCRIPTION
8-digrt code which contains the
year, month and sequence the
incident report was received.
Uniquely identifies each report.
Alphabetical code which appears
to the right of the report number
describing the type of incident.
Describes the mode of
transportation in which the
incident occurred. Taken from
Section!, #1. . /
Description of the other
transportation mode. Taken from
Section I, #1.
Date the incident occurred. Taken
from Section I, #2.
Time the incident occurred. Taken
from Section I, #2.
City in which the incident
occurred. Taken from Section I,
#3. .
County in which the incident
occurred. Taken from Section I,
#3.
State in which the incident
occurred. Taken from Section I,
#3.
Street location on which the
incident occurred. Taken from
Section I, #3.
9-digit code used to identify the
carrier.
-------
DATASET: HAZMAT
FIELD NAME
CARR1ER_NAME
CARR!ER_ADDRESS
CARRIER_CITY
CARRIER_STATE
CARRIER_ZIP
CARRIER_REPORTING_NO
SHIPPERJD
SHIPPER_NAME
SHIPPER_ADDRESS
SHIPPER_CITY
SHIPPER_STATE
SHIPPER_ZIP
CONSIGNEEJD
CONS!GNEE_NAME
CONSIGNEE_ADDRESS
CONSIGNEE_CITY
CONSIGNEE_STATE
CONSIGNEE_2IP
ABBREV
CARRI
CARAD
CACIT
CARST .
CAZIP
CRPNO
SHPID
SHIPR
SHPAD
SHCIT
SHPST
SHZIP
CONID
CONS1
CONAD
COCIT
CONST
COZIP
TYPE
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
DIRECTORY: INCIDENTS
SIZE
30
30
25
2
9
12
9
30
30
25
2
9
9
30
30
25
2
9
DESCRIPTION
Name of the company responsible
for transport of the product. Taken
from Section II, #4.
Street address of the carrier.
Taken from Section II, #5.
City the carrier resides in. Taken
from Section II, #5.
State the carrier resides in. Taken
from Section II, #5.
Zip code of the carrier location.
Taken from Section II, #5.
Modal carrier identifier number or
code. Taken from. Section II, #6.
9-digit code used to identify the
shipper.
Name of the company shipping a
product. Taken from Section III,
#7.
Street address of the shipper.
Taken from Section III, #7.
City the shipper resides in. Taken
from Section III, #7.
State the shipper resides in. Taken
from Section III, #7.
Zip code of the shipper's location.
Taken from Section III, #7.
9-digit code used to identify the
consignee.
Name of the company product is
to be delivered to. Taken from
Section III, #8.
Street address of the consignee.
Taken from Section III, #8.
City the consignee resides in.
Taken from Section III, #8. .
State the consignee resides in.
Taken from Section III, #8.
Zip code of the consignee
location. Taken from Section III,
#8.
-------
DATASET: HAZMAT
FIELDNAME
ORIGIN_SAME_AS_SHIPPER
. ORIGIN_ADDRESS
ORIGIN_CITY
ORIGIN_STATE
ORIGIN_ZIP
DESTINATION SAME AS
CONSIG ~
DESTINATION_ADDRESS
DESTINATION_CITY
DESTINATION_STATE
DESTINATION_ZIP
SHIPPING_PAPER_NO -
COMMODITY_eODE
ABBREV
ORSHP
ORIAD
OGITY
OST
OZIP
DECON
DESAD
DCITY
DST
DZIP
SHPNO
CMCD
TYPE
Logi
Text
Text
Text
Text
Logi
Text
Text
Text
Text
Text
Text
DIRECTORY: INCIDENTS
SIZE
1
30
25
2
9
1
30
25
2
9
16
5
DESCRIPTION
Identifies if the origin location of
delivery is the same as the shipper
location.
Street. address where the
shipment of the hazardous
material originated. Taken from
Section III, #9.
City where shipment of the
hazardous material originated.
Taken from Section III, #9.
State where shipment of the -
hazardous material originated.
Taken from Section III, #9.
Zip code of state where shipment
of the hazardous materials
originated. Taken from Section III,
#9.
Identifies if the destination location
of the shipment of the hazardous
materials is the same as the
consignee location.
Street address where shipment of
the hazardous materials is
destined. Taken from Section III, ,
#10. '
City where shipment of the
hazardous materials is destined.
Taken from Section III, #1 0.
State where shipment of , the
hazardous materials is destined.
Taken from Section III, #1 0.
Zip code of state where shipment
of the hazardous materials is
destined. Taken from Section III,
#10.
Identification number of papers
used to identify shipment of
hazardous materials being
transported. Taken from Section
III, #11.
5-digit office generated code used
to identify and standardize the
commodity being shipped.
-------
DATASET: HAZMAT
FIELD NAME
COMMODITY SHIPPING
NAME
COMMODITY_TRADE_NAME
COMMODITY_CLASS
UN_NUMBER
HAZARDOUS_SUBSTANCE
RQ_MET
QUANTITY_RELEASED
QUANTITY RELEASED
CODE
UNITS OF QUANT
RELEASED
DEATHS
MAJORJNJURIES
MINORJNJURIES
ABBREV
COMOD
TRADE
CMCL
UNNUM
HAZSUB
RQMET
RQUAN
RCODE
RUNIT
DEAD
MJINJ
MNINJ
(
TYPE
Text
Text
Text
Text
Logi
Log!
Real
Int
Text
Int
Int
Int
DIRECTORY: INCIDENTS
SIZE
25
20
2
6
1
1
9
1
3
2
3
3
DESCRIPTION
Name of the product being
transported. Taken from Section
IV, #12.
Commonly used name of the
product being transported. Taken
from Section IV, #13.
2-digit code to identify the hazard
class of the product being
transported. Taken from Section
IV, #14.
United Nations identification
number of the product being
transported. Taken from Section
IV, #15.
Identifies whether the material
being transported is listed as a
hazardous substance. Taken from
Section IV, #16.
Identifies whether the reportable
quantity of the material being
transported was met. Taken from
Section IV, #17.
Amount of material released.
Taken from Section V, #1 8.
Code that indicates that the
quantity was provided by the
report preparer.
Units (gal./lbs./cfts.) of the amount
, of transported material released.
Taken from Section V, #18.
Number of deaths that occurred
.due to the hazardous material
released during transportation.
Taken from Section V, #19.
Number of serious injuries that
occurred due to the hazardous
materials released during
transportation. Taken from Section
V, #20.
Number of minor injuries that
occurred due to the hazardous
materials released during
transportation. Taken from Section
V, #21.
-------
DATASET: HAZMAT .
FIELD NAME
NUMBER_EVACUATED
PRODUCT_LOSS
PRODUCT_LOSS_CODE
CARRIERJDAMAGE
CARRIER_DAMAGE_CODE
PUB_PRI_DAMAGE
PUB_PRI_DAMAGE_CODE
DECON^DAMAGE .
DECON_DAMAGE_CODE
OTHER_DAMAGE
OTHER_DAMAGE_CODE
REPORT_DAMAGE
REPORT_DAMAGE_CODE
ABBREV
NEVAC
PLDAM
PLDCD
CADAM
CADCD
PPDAM
PPDCD
DCDAM
DCDCD
OTDAM
OTDGD
RPDAM
RPDCD
t t
TYPE
Int
Int
Text
Int
Text
Int
Text
Int
Text
Int
Text
Int
Text
DIRECTORY: INCIDENTS
SIZE
6
8
1
8
1
8
1
8
1
8 :
1
8
1
DESCRIPTION
Number of people evacuated from
an area because of the hazardous
materials released during
transportation. Taken from Section
V, #22.
Dollar value of the product lost.
Taken from Section V, #23A.
A code that indicates that the
dollar value was provided by the
report preparer.
Dollar value of the damage
substained by the carrier. Taken
from Section V, #23B.
A code that indicates that the
dollar value was provided by the
report preparer.
Dollar value of the damage
substained to public or private
property. Taken' from Section V,
#23C. ' ,
Code that indicates that the dollar
value of damage to public or
private property was provided by
the report preparer.
Dollar value of the cleanup effort
or decontaminating the area
involved in the product spillage.
Taken from Section V, #23D.
Code that indicates that the dollar
value of the cleanup effort or
decontaminating the area involved
in the incident was provided by
the report preparer.
Dollar value of the damage or
efforts not already mentioned in
the incident. Taken from Section
V, #23E.
Code that indicates that the dollar
value of OTHER_DAMAGE was
provided by the report preparer.
Total dollar value of fields 23A thru
23E of the report.
Code that indicates that the report
total was provided by the report
preparer.
-------
DATASET: HAZMAT
FIELD NAME
INCIDENT_DAMAGE
DAMAGE_CODE
RESULT.VAPOR
RESULT_SEWER
RESULT_SPILL
RESULT_FIRE
RESULT_EXPLO
RESULT_ENVIR
RESULT_NONE
RESULT_OTHER
RESULT_OTHER_DESC
VEHICLE_CARGO
VEHICLE_VAN
VEHICLE_FLAT
VEHICLE_TANK_CAR
VEHICLE_RAIL_CAR
ABBREV
DAMAG
DAMCD
VAPOR
SEWER
SPILL
FIRE
EXPLO
ENVIR
RNONE
ROTH ,
ROTHD
CARGO
VANTR
FLATT
TCAR
RCAR
TYPE
Int
Text
Log!
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Text
Logi
Logi
Logi
Logi
Logi
DIRECTORY: INCIDENTS
SIZE
8
1
1
1
1
1
1
1
1
1
16
1
1
1
1
1
DESCRIPTION
Total damage value for an
incident. (Not in use.)
Code that indicates that the total
dollar value was provided by the
report preparer.
Identifies whether vapor being
released was a consequence of
the incident.
Identifies whether the commodity
entering a waterway or sewer
system was a consequence of the
incident.
Identifies whether the commodity
released as a consequence of the
incident.
Identifies whether a fire occurred
as a consequence of the incident.
Identifies whether an explosion
occurred as a consequence of the
incident.
Identifies whether environmental
damage occurred as a
consequence of the incident.
Identifies if there were no
consequences of the incident.
Identifies whether there were other
consequences of the incident. See
RESULT_OTHER.
Description of the other
consequences of the incident.
Identifies that a cargo tank was
the vehicle involved in the
incident.
Identifies that either a van, truck,
or trailer was the vehicle involved
in the incident.
Identifies that a flatbed truck or
trailer was the vehicle involved in
the incident.
Identifies that a tank car was the
vehicle involved in the incident.
Identifies that a rail car was the
vehicle involved in the incident.
-------
DATASET: HAZMAT
FIELD NAME
VEHICLE_TOFC
VEHICLE_AIRCRAFT
VEHICLE_BARGE
VEHICLE_SHIP
VEHICLE_OTHER
VEHICLE_OTHER_DESC
TRANSPORTATION_PHASE
LAND_USE
COMMUNITY_TYPE
ACCIDENT_OR_DERAIL
ESTIMAJED_SPEED
HIGHWAYJTYPE
HIGHWAY_LANES
GENERAL_CAUSE
MISCELLANEOUSJNFOJ
MISCELLANEOUSJNFOJ
ATTACHMENTS
ABBREV
TOFC
PLANE
BARGE
SHIP '
VOTH
VOTHD
PHASE
LUSE
CTYPE
ACCDR
SPEED
HTYPE
LANES
CAUSE
MISC1
MISC2
ATTACH
TYPE
Logi
Logi
Logi
Logi
Logi
Text
Int
Int
Int
Logi
Int
Int
Int
Int
Int
Int
Logi
DIRECTORY: INCIDENTS
SIZE
1
1
i
1
1
16
3
3
3
1
3
3
1
3
3
3
1
DESCRIPTION
Identifies that a trailer or container
on a flat car was the vehicle
involved in the incident.
Identifies that an aircraft was the
vehicle involved in the incident.
Identifies that a barge was the
vehicle that was involved in the
incident. ,
Identifies that a ship was the
vehicle that was involved in the
incident.
Identifies that an unlisted vehicle
type was involved in the incident.
Description of other types of
vehicles involved in the incident.
Transportation phase when the
incident occurred.
Type of land use where the
incident occurred.
Type of community'where the
incident occurred.
Identifies if the incident occurred
because of a vehicle accident or
derailment. - :
Speed of vehicle when the
incident occurred.
Type of highway where the
incident occurred.
Number of lanes on the highway
where the incident occurred.
Code that states whether the
incident was caused by human
error, vehicle accident, package
failure or another reason.
Code that states important factors
concerning the incident.
.Code that states important factors
concerning the incident.
Identifies whether there are
attachments received with the , :
original form.
-------
DATASET: HAZMAT
FIELD NAME
RECOMMENDATIONS
REPORTERS NAME
REPORTERS TITLE
REPORTERS_PHONE
REPORT_DATE
DATE_ADDED_TO_DATA_
SET or
DATE OF ENTRY
DATE OF LAST CHANGE
or DATE OF CHANGE
INTEGERJDFJD
ABBREV
RECOM
RNAME
RTITL
PHONE
RDATE
DOE
DOC
INTID
TYPE
Logi
Text
Text
Text
Date
Date
Date
Int
DIRECTORY: INCIDENTS
SIZE
1
25
25
12
10
10
10
10
DESCRIPTION
Identifies whether comments are
given in Section IX of the incident
form suggesting
recommendations.
Name of incident report preparer.
Title of incident report preparer.
Phone number of the incident
report preparer.
Date the incident report was filled
out.
Date the incident report was
added to the dataset.
Date the last change was made to
the incident report.
System generated number that is
used to match the same report in
other datasets.
-------
DATABASE: [$TEMP]
DATASET: HAZCON
DIRECTORY: INCIDENTS
This dataset stores the packaging information reported on the back of the incident form for a
hazardous materials incident: type of packaging, how many failed and the reason why it failed. This
dataset can be used to map to the HAZMAT dataset.
DATASET: HAZCON
FIELD NAME
REPORT_NUMBER
MULTIPLE_CODE
CONTAINER_SEQUENCE
TYPE_OF_CONTAINER
CAPACITY_CONTAINER
CAPACITY CONTAINER
CODE
CAPACITY_UNITS
NUMBER_FAILED
NUMBER_FAILED_CODE
NUMBER_IN_SHIPMENT
NUMBER IN SHIPMENT
CODE
GAUGE_OF_CONTAINER
MANUFACTURERSJD
MANUFACTURERSJMAME
ABBREV
RPTNO
MTPL '..
SEQ
CTYPE or
CNAME
CCAP
CAPCD
CUNIT
NFAIL
NFLCD
NSHIP
NSPCD
GAUGE
MFGID
MANUF
TYPE
Text
Text
Int
Text
Real
Text
Text
Int
Text
Int
Text
Text
Text
Text
DIRECTORY: INCIDENTS
SIZE
8
1
1
8
9
1
3
5
1.
5
1
12
9*
30
DESCRIPTION
8-digrt code which contains the
year, month and sequence the
incident report was received.
Uniquely identifies each report.
Alphabetical code which appears
to the right of the report number
describing the number of reports
for an incident.
.Sequential ordering from the inner
to outermost container.
Packaging name.
Indicates the size of the package.
Code that indicates that the
capacity value was provided by
the report preparer.
Identifies the units (gals./lbs./cfts.)
of the container.
Number of packages releasing
material in the incident.
Code that indicates that the figure
was provided by the preparer of
the report.
Number of packages being
transported.
Code that indicates that the
number being transported was
provided by the report preparer.
Identifies package markings or
other information.
9-digit code used to standardize
and identify the container
manufacturer's name.
Name of the company that
manufactures the packaging as
taken from Section VII, #36.
-------
DATASET: HAZCON
FIELD NAME
MANUFACTURERS_CITY
MANUFACTURERS_STATE
TANK_SER!AL_NO
LABEL_OR_PLACARD
REGISTRATION_NO
INSPECTION_DATE
EXEMPT1ON_NO
VEHICLE_COLUSION
VEHICLE_OVERTURN
OVERLOAD_OVERFILL
LOOSE_FITTING
DEFECTIVEJTTTING
DROPPED
STRUCK_RAMMED
IMPROPER_LOADING
IMPROPER_BLOCKING
CORROSION
ABBREV
MCITY
MST
TKID
LRP
RNUM
INSP
ENUM
VCOLL
VOVER
OLOAD
LOOSE .
DEFCT
DROPD
STRCK
ILOAD
BLOCK
CORRO
TYPE
Text
Text
Text
Text
Text
Date
Text
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Logi
DIRECTORY: INCIDENTS
SIZE
25
2
.10
7
6
10
10
1
1
1
1
1
1
1
1
1
1
DESCRIPTION
City the manufacturer resides as
taken from Section VII, #35.
State the manufacturer resides as
taken from Section VII, #35.
Gives the packaging serial
number.
Color-coded sign that states the
class of the product dependent
upon the size of the package.
Registration code assigned to a
container if 'it has been
reconditioned or requalified.
Last date the package was
inspected.
Number that states whether a
company is exempt from a
particular regulation.
Identifies whether a vehicle
collision occurred.
Identifies whether a vehicle '
overturned or derailed.
Identifies whether a container was
overfilled.
Identifies whether loss of product
occurred because of a loose fitting
or closure.
Identifies whether loss of product
occurred due to a defective fitting.
Indicates the package involved
has been dropped causing
product loss.
Indicates the package involved
has been struck causing product
loss.
Indicates the package has been
loaded incorrectly, i.e. heavy
packages on top.
Indicates the package has been
blocked incorrectly, i.e. package
has not been tied down.
Indicates package has corroded
causing product loss.
-------
DATASET: HAZCON
FIELDNAME
METAL_FATIGUE
FRICTION_RUBBING
FIRE_HEAT
FREEZING
VENTING
VANDALISM
INCOMPATIBLE_MATERIAL
CONTRIBUTING JDTHER
CONTRIBUTING OTHER
DESC .
OTHER_FREIGHT
FORKLIFT
NAIL_PROTRUSION
OTHER_VEHICLE
WATER
GROUND_FLOOR_ROAD-WAY
ABBREV
FATIG
FRICT
FIRE
FREEZ
VENT
VANDL
INCOM
COTH
COTHD
FRGHT
FLIFT
NAIL
VEHCL
FLOOR
TYPE
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Text
Logi
Logi
Logi
Logi
Logi
Logi
DIRECTORY: INCIDENTS
SIZE
1
1
1
1
.1
1
1
1
16
1
1
1
1
1
1
DESCRIPTION
Indicates the packaging has
weakened due to overuse or
defects in the manufacture of the
package.
Indicates that the package failed
due to contact with its
surroundings.
Indicates that fire or heat caused
defects in the packaging allowing
product loss.
Indicates that freezing cold or ice
contributed to product loss.
Indicates product was released
through closures because of
pressure.
Indicates product was released
from packaging because of
vandalism.
Indicates two materials should not
be in contact with one another.
Indicates there was another
reason contributing to package
failure. See
CONTRIBUTING OTHER DES-
CRIPTION.
Explanation as to what contributed
to the package failure.
Indicates whether another form of
freight was responsible for
package failure.
Indicates whether a forklift was
responsible for the package
failure.
Indicates whether a hail or another
type of protrusion is responsible
for package failure.
Indicates whether another vehicle.
is responsible for package failure.
Indicates whether water is
responsible for package failure.
Indicates whether package failure
was due to contact with ground,
floor, or roadway.
-------
DATASET: HAZCON
FIELD NAME
ROADSIDEJDBSTACLE
NO_OBJECT
OBJECT_OTHER
OBJECT_OTHER_DESC
PUNCTURED
CRACKED
BURSTJNTL_PRESSURE
RIPPED
CRUSHED
RUBBED_ABRADED
RUPTURED
HOW_FA1LED_OTHER
HOW_FAILED_OTHER_DESC
END_FORWARD
END_REAR
SIDE_RIGHT
SIDE_LEFT
TOP
ABBREV
OBSTC
NONE
OOTH
OOTHD
PUNCT
CRACK
BURST
RIPPD
CRUSH
ABRAD
RUPTD
HOTH
HOTHD
FORWD
REAR
RIGHT
LEFT
TYPE
Logi
Logi
Logi
Text
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Text
Logi
Logi
Logi
Logi
Logi
DIRECTORY: INCIDENTS
SIZE
1
1
1
16
1
1
1
1
1
1
1
1
16
1
1
1
1
1
DESCRIPTION
Indicates whether a roadside
obstacle was the reason for the
package failure.
Identifies that no object caused
the package failure.
Identifies that another object
caused the package failure. See
OBJECT_OTHER_DESCRIPTION.
Explanation as to what object
caused the package failure.
Indicates that a puncture caused
the package failure.
Indicates that a crack caused the
package failure.
Indicates that internal pressure
caused the package failure.
Indicates that a rip caused
package failure.
Indicates the package failed
because the package was
crushed.
Indicates the package failed
because the package was rubbed
or abraded.
Indicates that the package failed
because it ruptured.
Identifies another cause for the
package failure. See HOW
FAILED_OTHER_DESC.
Explanation as to how the
package failed.
Identifies whether the front of the
package failed.
Identifies whether the back of the
package failed.
Identifies whether the right side of
the package failed.
Identifies whetHer the left side of
the package failed.
Identifies whether the top of the
package failed.
-------
DATASET: HAZCON
FIELDNAME
-BOTTOM
CENTER
AREA_OTHER
AREA_OTHER_DESC
PACKAGE_MATERIAL
FITTING_VALVE
CLOSURE
CHIME
WELD_SEAM
HOSE_PIPING
INNER_LINING
WHAT_FAILED_OTHER
WHAT FAILED OTHER
DESC
DATE ADDED TO DATA
BASE or
DATE OF ENTRY
DATE_OF_LAST_CHANGE
or
DATE OF CHANGE
INTEGER_OF_ID
ABBREV
BOTTM
CENT
AOTH
AOTHD
MATRL
VALVE
CLOSE
WELD
HOSE
INLIN
WOTH
WOTHD
DOE
DOC
INTID
TYPE
Logi
Logi
Logi
Text
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Logi
Text
Date
Date
Int
DIRECTORY: INCIDENTS
SIZE
1
1
1
16
,1
1
1
1
1
1
1
1
16
10
10
10
DESCRIPTION
Identifies whether the bottom of
the package failed.
Identifies whether the center of the
package failed.
Identifies that there was another
area on the package that failed.
See AREA OTHER DESCRIP-
TION.
Explanation of where the package
failed.
Identifies that the package material
failed.
Identifies whether a fitting or valve
on the package failed.
Identifies whether the closure
on the package failed.
Identifies whether a chime
on the package failed.
Identifies whether a seam or weld
on the package failed.
Identifies whether a hose or piping
on the package failed.
Identifies whether the inner lining
on the package failed.
Indicates there was something
else that failed on the package.
See WHAT FAILED OTHER
DESC.
Explanation of the area that failed
on the package.
System-generated field which
indicates the date a record was
added to the dataset.
System-generated field which
indicates the date a change was
made to a record.
Number that is used to match the -
same report in other datasets.
DATABASE: [$TEMP]
-------
DATASET: HAZRMK
DIRECTORY: INCIDENTS
This dataset contains the comments from the hazardous materials incident report. These comments
have also been taken from attachments that may be sent with the incident report.
DATASET: HAZRMK
FIELD NAME
REPORTJMUMBER
SEQUENCE_NUMBER
REMARKS
DATE_OF_CHANGE
DATE_OF_ENTRY
ABBREV
RPTNO
SEQ
REM
DOC
DOE
TYPE
Text
Int
Text
Date
Date
DIRECTORY: INCIDENTS
SIZE
8
3
75
10
10
DESCRIPTION
8-digrt code which contains the
year, month and sequence the
incident report was received.
Uniquely identifies each report.
Sequential number used to sort
the remarks in the proper order.
Comments taken from the incident
report that are written by the
report preparer.
System-generated field which
indicates the date a change was
made to a record.
System-generated field which
indicates the date a record was
added to the dataset.
-------
HLPAD Datafield Dictionary
-------
-------
DATASET NAME: LIQLCK.DMS
This dataset contains the information from the liquid accident
report Form RSPA F 7000-1 (4-85).
FIELD NAME
REPORT_YEAR
REPORT_NUHBER
REPORT_ID
OPERATOR_CODE
OPERATOR_NAHE
INTERSTATE_PIPELINE
INCIDENT_DATE
INCIDENT_HOUR
INCIDENT_STATE
INCIDENT_COUNTY
INCIDENT_CITY
OF FSHORE_COORDINATES
INCIDENT_ON_FEDERAL_LAND
SPECIFICJ.OCATION
CARRIER SYSTEM INVOLVED
ORIGIN OF RELEASE
ORIGIN_OF_RELEASE_OTHER
YEAR_ITEM_INSTALLED, *
ACCIDENT CAUSE
ABBREV
.YR
LOG
RPTID
OPID
NAME
INTER
I DATE
DTHH
ACCST
ACCNT
ACCTY
COOR
IFED
SPLOC
CSYS
ORGLK
ORGLO
ITMYR
CAUS
TYPE SIZE
INT 2
INT 4
INT 6
INT 5
TEXT 50
INT 2
DATE 10
INT 4
TEXT 2
TEXT 25
TEXT 25
TEXT 25
TEXT. 2
TEXT 160
INT 1
INT 2
TEXT 25
INT 4
INT 1
ACCIDENT CAUSE OTHER
CAUSO
TEXT 25
DESCRIPTION
Year of report YY.
Unique identi-fier assigned by OPS.
DOT assigned Id number for report..
Part A-1. - DOT assigned number for the operator.
Part A-1.-- Name of the operator or company.
Part A-3. - Is pipeline interstate?
0 - No data
1 - Yes
2 - No
Part B-1. - Hour accident took place.
Part B-2. - Hour accident took place.
Part B-3. - State where accident took place.
Part B-3. - County where accident took place.
Part B-3. - -City at or near where accident took place.
Part B-4. - If offshore, offshore coordinates.
Part B-5. -
0 - No Data
1 - Yes
2 - No . -
Part B-6. - Description of the Specific location where
incident occurred.
Part C-1. - Part of system involved
0 - No data .
1 - line pipe
2 - tank farm . ...
3 - pump station
Part C-2. - Origin of release of liquid or vapor.
0 - No data
1 - pipe
2 - valve '.':-'
3 - scraper trap
4 - pump
5 - welding fitting
6 - girth
7 - tank
8 - bolted fitting
9 - longitudinal weld
10 - other -
Part C-2. - Text for choice 10 above.
Part C-3. - Year item was installed.
Part D, -- Cause of accident. '".'-
1 - coTosion
2 - f ailed weld
3 - incorrect operation by operator personnel
4 - failed pipe .
5 - outside force damage
6 - malfunction of control or relief equipment
7 - other
Part D. - Text for choice 7 above.
-------
tOTAL_FATALlTIES
EHPtOYEE_FATALITIES
NON_EMPLOYEE_FATALmES
TOTAL_INJt}RIES
EHPLOYEE_IHJURIES
NON_EซPLOYEE_INJURIES
PROPERTY_DAMAGE
COHHODITYJTRANSPORTED
COHHOblTY_TRANSPORTED_ID
CLASSIFICATION OF COKMOD
EST1HATEO_LOSS_BARREL
EST1MATED_RECOVฃR_BARREL
F1RE_CAUSED
EXPLOSION
HOHIHALJJIAHETER
THICKNES3_UALL
SYSTEH-HAX_YIELD_STRGTH
JOINT TYPE
PIPE_ABOVE_GROUND
PRESSUREJJESIGH
PRESSURE_ACCIDENT
PRESSUREJTEST
DURATIONJDFJTEST
HAX_TEST_PRESSURE
LATEST_TEST_HOHTH
UTEST TEST YEAR
TFAT
EFAT
NFAT
TINJ
EINJ
NINJ
PRPTY
COHH
COHID
CLASS
LOSS
RECOV
FIRE
EXP
NMD IA
THK
SMYS
JNT
GRND
DSPRS
ACPRS
PRTST
DUR
MXPRS
TSTMM
TSTYY
INT 3 Part E-1. - Number of persons killed.
INT 3 . Part E-1. - Number of operator employees killed.
INT 3 Part E-1. - Number of non-employees killed.
INT 3 Part E-2. - Number of persons injured.
INT 3 Part E-2. - Number of operator employees injured.
INT 3 Part E-2. - Number of non-employees injured.
INT 8 Part F. - Dollar amount.
TEXT 3,0 Part G-1. - Name of commodity spilled. Found in dataset
STCC.
INT 7 Part G-1. - ID of commodity spilled. (Coded on form).
INT 1 Part G-2. - Classification of commodity spilled.
0 - No data
1 - Petroleum
2 - Petroleum product HVL
3 - Petroleum product non-HVL
INT 6 Part G-3. - Estimated amount of barrels spilled.
INT 6 Part G-3. - Estimated number of barrels recovered.
INT "2 Part G:5. - Was there a fire?
0 - No data
1 - Yes
2 - No
INT 2 Part G-4. - Was there an explosion?
0 - No data
1 - Yes .
2 - No
REAL 6 - Part.H-1. - Nominal Diameter (inches).
REAL 6 Part H-2. - Wall thickness (inches).
INT 7 Part H-3. - Maximum yield strength of systems (psi).
INT 1 Part H-4. - Type of joint.
0 - No data
1 - Welded
2 - Flanged
3 - Threaded
4 - Coupled
5 - Other
INT 2 Part H-.5..- Level of pipe.
1 - Below ground
2 - Above ground
INT 4 Part H-6. - Maximum operating pressure (psig).
INT 4 Part H-7. - Pressure at time'and location of accident
(psig).
INT 2 Part H-8. - Had there been a pressure test on the system?
0 - No data
1 - Yes
2 - No
INT 3 Part H-9. - Duration of test (hrs).
INT 4 Part H-10. - Maximum test pressure (psig).
INT 2 Part H-11. - Month of latest test.
INT 2 Part H-11. - Year of latest test.
-------
CORROSION LOCATION
FACILITY COATED
FAC_CATHODICALLY_PROT
CORROSION TYPE
CORROSION_TYPE_OTHER
PRIMARY CAUSE
PRIHARY_CAUSE_OTHER
DAMAGE_PREVENT_PRbGRAM
ONE_CALL
ONE_CALL_OTHER
EXCAVATOR_CALL
TEMPORARILY" MARKED
REPORTING_OFFICIALS_NAME,
PREPARERS_PHONE_NUMBER
NO_REPORTABLE
TELEPHONICS_REPORT_NO
TELEPHONES ID
CORLC
FACTD
FACAT
CORR
CORRO
CAULK
CAULO
PREVT
ONECL
ONEOT
EXCAL
TMPMK
RNAME
PHONE
NORPT .
TELRN
TELID
INT 2
INT 2
INT 2
INT 2
TEXT 25
INT 2
TEXT 25
INT 2
INT 2
TEXT 25
INT 2
INT 2
TEXT 60
TEXT 10
TEXT 1
TEXT 10
INT 5
Part 1-1. - Location of corrosion.
0 - No data
1 - Internal
2 External
Part 1-2. - Facility coated?
0 - No data
.1 - Yes
2 - No
Part 1-3. - Facility under cathodie protection?
0 -. No data
1 - Yes
2, - No .
Part 1-4. - Type of corrosion.
0 - No data
1 - Galvanic
2 - Other .
Part 1-4. - Text for choice 2 above.
Part J-1. - If spilled was caused by outside force, then
primary cause of spill.
0 - No, data . .--..
1 - Damage by operator or its contractor
2 - Damage by others .
3 - Damage by natural forces
4 - Landslide
5 - Subsidence,
6 - Washout
7 - Frostheave
8 - Earthquake
9 - Ship anchor
10 - Mudslide
11 - Fishing Operations - ' '
12 - Other . .
Part J-1. - Text for choice 12-above.
Part J-2. - Was a damage prevention program in effect?
0 - No data
1 - Yes
,2 - No . .
Part J-3. - If Yes-above, was the program "one-call" or
other? .
0 - No data
1 - "One-call11
2 - Other '
Part J-3. - Text for choice 2 above.
Part J-4. - Did excavator call?
0 - No data
1 - Yes
2 - No
Part J-5. - Was pipeline location temporarily marked for
the excavator?
0 - No data
1 - Yes
2 - No
Name and title of operator official, filing report.
Phone number of operator official filing report.
Entered if report does not meet reporting requirements.
Report number of matching telephonic report (RNO
in Telephonies database).
' f"
ID number of matching telephonic report (ID in Telephonies
database).
-------
DATE_OF_RECEIVED_AT_DOT
DATE_OF_ENTRY
DATE_OF_CHAHGE
DOR
DOE
DOC
DATE 10 Date report was received at DOT. Stamped on report by DOT:
DATE 10 System generated date for data entry.
DATE 10 ' System generated date for any change in the data entry.
These are the cause codes and cause descriptions for the liquid
accidents dataset.
1. Corrosion
2. Failed Weld
3. Incorrect Operation by Operator Personnel
4. Failed Pipe'
5. Outside Force Damage
6. Malfunction of Control or Relief Equipment
7. Other
0. Ho data
These are the commodity codes and descriptions for the liquid
accident dataset.
2815154 ALKYLATE
2819815 ANHYDROUS AMMONIA
4905706 BUTANE
2813320 CARBON DIOXIDE
2911976 CONDENSATE
1311110 CRUDE OIL . -
2911315 DIESEL FUEL
2871244 FERTILIZER, AMMONIUM NITRATE
2911715 FUEL OIL
2911135 GASOLINE
2911130 JET FUEL
2911230 KEROSENE
4905711 L.P.G., PROPANE, ETHANE
4908176 NATURAL GAS LIQUID, BUTANE
2911190 OIL AND GASOLINE
4905781 PROPANE
2814167 TOLUENE
2911735 TRANSMIX (PART. REFINED PETRO)
2911225 TURBINE FUEL
2814170 XYLENE
-------
IMIS Datafield Dictionary
-------
-------
IMIS Derived File field Definitions
The following is a brief definition of the data elements comprising the IMIS derived file fields. The field names in the
first column correspond to the COBOL include module, DRSSINSP. Note that unused numeric fields, including dates,
are set to spaces. -
<>'
Fixed Stem portion - first 269 characters of the record.
Field Name
Continuation-Flag
History-Flag
OSHA1-MOD-PROC
State-Flag
Prev-Act-Type
Prev-Act-Nr
Activity-Mr
Report-ID
Region
Area-Code
Office-Code
CSHO-ID
Job-Title
Opt-Rpt-Nr
Description
Indicates whether record is a continuation of the
previous record (occurs for records with more than
99 violations - less than 20)
Identifies record as MIS or IMIS
Latest date record was modified.
Indicates whether record is federal or state( 1 8b)
Indicates if previous OSHA activity occurred at
Location inspected and the type of activity
Activity number for previous OSHA Activity
Unique pre-printed or generated (MIS) number that
identifies the OSHA- 1 and in the derived file is the
record identifier
7 -digit identification code of each OSHA and State
(1 8b) office, uniquely identifying office conducting
inspection.
DOL region code(first 2 digits of Report-ID)
Area office code (next 3 digits of Report-ID)
Code identifying Federal district or state sub-office
{last 2 digits of Report- ID)
CSHO number of compliance officer who
conducted inspection.
Job classification of CSHO who conducted
inspection
Option report number (used for identifier in MIS
system)
Values/format
b (blank) = No
X = Yes
H = Historical (7/72- 3/84)
b= IMIS (After 3/84)
X/T = Entered on-line
p= Entered on I V-Phase
YYMMDD
b = federal
S = state
b = NoActivity
A = Accident I = Inspection
C = Complaint R = Referral
Appendix B of code manual has all codes
values 01-10
values 11 1-578
.<500 = Federal Office
>500 = State Office
values 00-99
A = Area Director
C * Safety Officer
I - Health Officer
L = Safety Trainee
M ป Health Trainee
S = Supervisor
V = Discrimination Invest.
.W = Regional Mgt
X ป Regional FSO
Y = Regional Tech Supp
-------
Field Name
Sue-Info
Estab-Name
Site-Street
Site-State
Site-ZIP
Stte-City-Code
Site-Cntv-Code
Duns-Nr
Owner
Owner-Code
Adv-Notice
Open-TDate
Close-Conf-Date
S-H
SIC
SIC-Guide
SIC-Inspd
Inspection-Type
Inspection-Scope
Nr-In-Estab
Nr-Covered
Nr-Cb-Empr
Walk-Around
Description
Next 7 fields give the site location of the inspection
Name of the firm inspected
Street location
State
ZIP
4 digit city code from GSA geographical location
codes
3 digit FIPS county code
Duns Number
Ownership designation
Agency Code for Federal Agency inspections
Advance notice given
Date of opening conference or entry or attempted
entrv into the site
Date of closing conference held before issuing
citations or exit from inspection site
Safety or Health inspection
Primary SIC code for firm's activity
Secondary SIC
SIC inspected if different from primary SIC (18b
States only)
Type of Inspection
Types A, B, C, D, E, F, G, and J are
unprogrammed.
Types R I. and K are programmed.
Scope or coverage of the Inspection
Maximum number of employees at the inspected
site during the last 12 months.
Number of employees covered by inspection
Number of employees controlled by the employer
nationally
Employee representative present during the
inspection ,
Values/format
"
2 character alpha postal abbreviation
5 digit ZIP in packed format
Binary format
Packed format
Binary format
A = Private sector
B = Local Government
C = State Government
D ~ Federal Government
Packed format
X = Yes b = No
YYMMDD
YYMMDD
S = Safety
H = Health
AsFat/Cat E=Variance
B=Complaint F=Follow-up
C=Referral GsUnProgRclated
D=Monitoring J=UnProgOther
H=Planned K-ProgOther
I=ProgRelated L=Other
A ป Comprehensive B = Partial
C ป Records Only
D ซ No Inspection
X-Yes b = No
-------
Field Name
Empl-Inter
Union
Close-Case
Why-No-INSP
Close-Case-Date
Safety-pg-man
Safety-pg-con
Safety-pg-rnar
Health-pg-man
Health-pg-con
Health-pg-mar
Local
Spec-pgm
Migrant
Antic-Served
First-Denial-Date
Last-Reenter-Date
BLS-LWDI-Rate
Dept-Collection
Pen-Due-Date
FTA-Due-Date
Due-Date-SRC
Insp-Disc-Hours
PA-Prep
PA-Travel
PA-On-Site
PA-Tech-Supp
Description
Employees interviewed during inspection (J8b
States only)
Employees represented by a Union
Safety planned inspection in manufacturing
Safety planned inspection in construction
Safety planned inspection in maritime
Health planned inspection in manufacturing
Health planned inspection in construction
Health planned inspection in maritime
Local emphasis program
Special emphasis program
Warrant served or subpoena obtained prior to the
start of the inspection
Date of initial denial of entry
Date CSHO re-entered firm for inspection after
first or second denial of entry
Lost Work day injury rate for inspected site
Next three data elements are used to track the debt
collection process
Date Penalties are due
Date Failure to Abate penalties are due
Source of Penalty Due Date
Total hours reported for this inspection by category
- next 9 fields
Time spent preparing for this inspection
Time spent traveling to and from this inspection
Time spent in the firm or at the job site
Time spent providing employer abatement
assistance
Values/format
X = Yes b = No
X = Yes b = No
'
X = Yes b = No
X = Yes b = No
X = Yes b = No
X = Yes b = No
X = Yes b = No
X = Yes b = No
X = Yes b*No
YYMMDD
YYMMDD
YYMMDD
b-No Due Date
N-Date 9/1/85 by National Office
D-Date oo Fora OSHA 167-1
R-Event Cede on OSHA 167-1, Penalty Due
Date Final Order Date plus 60 Days
J-Event code on OSHA 167-1, Penalty Due
Date Final Order Date plus 90 Diyi
F-Final order Date on OSHA 167-1
I-CiUlion bounce Date * 20 Days
A-Informal Settlement Date plia 20 Dayi
- '
-------
Field Name
PA-Rpt-Prep
PA-Other-conf
PA-LitiRation
PA-Denial
PA-Sum-Hrs
Denved-Info
Earliest-Coniest -
Date
Remitted-Pen-
Amt
Tot-Penalties
Tot-FTA
Total- Violations
Total-Ser-Viols
Block-Counts
Nr-Relative
Nr-Optinfo
Nr-Debt
Nr-Viols
Nr-Event
Nr-Hazsub
Nr-Accid
Nr-Adm-Pav
Seg-Relative
Rel-Item-Nr
Rel-Type
Rel-Act-Nr
Rel-Safety
Description
Time spent researching and completing the case
file"
Time spent in all off-site case-related conferences
Time spent preparing case for court and testifying
Time spent on all denial of entry activity from
initial denial to re-entrv or closing of case
Sum of all inspection activity hours reported
Next seven fields are calculated or selected for the
data blocks
Earliest Date of Contest received
Total penalty dollars remitted
Sum of current penalties issued
Sum of Failure to abate penalties issued
Total number of violations issued
Total number of serious, wilful, or repeat violations
issued
Count for the number of data blocks appended to
the record stem
Number of related activity blocks
Number of Optional information blocks
Number of Debt information blocks
Number of violation blocks
Number of penalty/failure to abate event blocks
Number of Hazardous substance blocks
Number of accident blocks
Number of administrative pay blocks
End of Stem portion of record
Relative Activity Block
Related Activity item number
Type of Related Activity
Activity number of related activity
All safety hazards for complaint/referral are
satisfied
Values/format
YYMMDD or b for non-contested
inspection
acceptable range for number of blocks:
(0-10)
(0-10)
(0-226)
(0-10)
(0-10)
(0-10)
9 characters
A = Accident 1 '* Inspection
C ป Complaint R = Referral
-------
1 Field Name
Rel-Health
Seg-Optinfo
Opt-Type
Opt-ID
Opt- Value
Seg-Debt
Debt-Type
Debt-Pen-FTA
Waived
Waived-Reason
Ref-Date
te
DLO
DCA-Send-Date
DCA-Ret-Date
DCA-Recommend
DCA-Litig-Amt
DCA-Fee-Amt
Archived
DCA-Int
DCA-DLQ
DFO-Send-Date
DFO-Ret-Date .
DFO-Recommend
AO-Send-Date
CB-Send-Date
IRS-Send-Date
1 CB-Ret-Date
Description
All health hazards for complaint/referral are
.satisfied
-
Optional Information Block
Office level requesting the entry of Information
C*
Preassigned number identifying the information
entered
Data
Debt information Block
Sets the type of data in this block
Following define block for T in Debt-Type
-
,:
Values/format
1 5 characters
N = National Office
R = Regional Office
A = Area Office .
S = State
72 characters
P = Debt-Pen
F = Debt-FTA
M = Debt-Misc
Packed -4
Packed - 5, 2 decimal places
Packed - 5, 2 decimal places
Packed - 4
Packed - 4
Packed - 5, 2 decimal places
Packed - 5, 2' decimal places
Packed - 5, 2 decimal places
Packed - 5, 2 decimal places
Packed -4
Packed, 4
Packed -4
Packed -4
Packed -4
Packed -4
-------
Field Name
Debt-Misc
Next-Install-Date
Last-lnstall-Date
SQL-Date
SQL-Reason
Case-Hold
Viol-Rec
Delele-Flag
Issuance-Date
Viol-Key
Emphasis
Gravity
Current-Penalty
Initial-penalty
Viol-Type
Inilial-Viol-Type
STD
Abate-Date
Mr-Instances
Rec
Nr-Exposed
Abate-Complete
Pen-Contesl-Data
Earl-Cont-Date
Viol-Contest
Pen-Contest
Abate-Empr-Contest
Abate-Empe-contest
Description
Followine define block for 'M' m Debt-Type
Violation Block
Violation deleted for reason other than error in
submission of data
Date citation issued bv Area Director
Unique identifier for each violation issued as a
result of this inspection. Identifies citation number
and violation number
Current penalty amount reflecting any changes or
modifications to the initial penalty
Initial assessed penalty amount
Type of violation (reflects any changes or
modifications)
Initial type of violation
Standard cited
Abatement date for this violation
Number of instances of this violation
Related event code
Number of employees exposed to hazard violated
Code indicating status of hazard
Penalty Violation Abatement contest data
Contest date
Violation contest
Penalty contest
Abatement Employer Contest
Abatement Employee Contest
Values/format
Packed -4
Packed - 4
Packed - 4
97 characters
b - violation not deleted
YYMMDD
S = Serious R = Repeat
W = Wilful O = Other
S = Serious R s Repeat
W = Wilful Q^Other
complete reference to 29 CFR
YYMMDD
,
A = Accident C - Complaint
I ซ Imminent Danger
R.= Related Event
V = Variance
Codes in Forms Manual
YYMMDD
X = Yes b = No
X^Yes b = No
X = Yes b = No
X^Yes b = No
-------
Field Name
Final-Order-Date
Events
PMA
Amended
ISA
Disp-Event
-/
FTA-Data
FTA-Insp-Nr
FTA-Penaltv
FTA-Issuance-Date
FTA-Contest
FTA-Amended
FTA-ISA
FTA-Disp-Eveni
Seg-Event
Hist-Type
Hist-Cit-ID
Pen-Historv
Pen-Hist-Date
Pen-Hist-Event .
Pen-Hist-Penaltv
Pen-Hist-Abate
Pen-Hist-Vtype
Pen-Hist-Action
FTA-Historv ,
Description _
Date contest settlement and penalties become
receivable
Petition to modify abatement approved
Citation amended prior to contest
Informal settlement agreement
Disposition of contested violation
Failure-to-abate data
Acuvity number of inspection on which FT A was
issued
Additional penalties issued for FT A
Issue date for FTA
FTA violation contest date
FTA citation amended prior to contest
Informal Settlement Agreement for FTA violation
Disposition of contested FTA violation
History Information Block
Defines data contained in block
. ; '
Values/format
YYMMDD
X = Yes b = No
X = Yes b = No
X = Yes b = No
W = Employer withdrew
D = Govt Dismissed
L s St Settlement
Y = St Decision
F * Formal settlement
J = ALJ Decision
R = Review commission
1 = St Lower court
2 = Appeals court
3 = Supreme court
YYMMDD
X = Yes b = No
X^Yes b = No
Codes in Forms Manual
24 characters
P-Pen-Hist
F-FTA-Hist
YYMMDD packed
Packed - 5 - 2 decimals
YYMMDD packed
-------
Field Name
FTA-Hisl-Insp-Nr
FTA-Hist-Date
FTA-Hist-Event
FTA-Hisl-Penaltv
FTA-Hist-Action
Seg-Hazsub
Haz-Kev
Hazsubl-HazsubS
Seg-Accident
Name
Rel-msp-Nr
Sex
Age
Degree-of-Inj
Nature-of-Inj
Pan-of-Body
Src-of-Inj
Event-Type
Env-Factor
Hum-Factor
Task-Assigned
Hazsub
Occ-Code
Description
Hazardous Substance Block
Viol-Key for violation these substances relate
Up to 5 hazardous substances with exposure levels
above the allowable limits that resutlted in the
violation. If more than 5 are involved then the 5
with the highest severity
Accident block
Name of the victim
Related inspection activity number
Gender of victim
Age of victim
Extent of injury
Nature of type of injury
Pan of body injured ,
Source of injury
Event type
Contributing environmental factor
Contributing human factor
Task working on at time of incident
Hazardous substance contributing to incident
Occupation Code for 1 8b state use only
Values/format
binary
YYMMDD packed
Packed - 5 - 2 decimals
27 characters
4 character OSHA substance codes;
Codes are listed in Appendix E Forms
Manual
49 characters
M - Male F = Female
1 ป Fatality 2 = Hospitalized Injury
3 = Nonhospitalized injury
Codes are listed in Appendix G Forms
Manual
Codes are listed in Appendix G Forms
Manual
Codes are listed in Appendix G Forms
Manual
Codes are listed in Appendix G Forms
Manual
Codes are listed in Appendix G Forms
Manual
Codes are listed in Appendix G Forms
Manual
A=Regularly assigned task
B=Task other than regularly assigned
Codes are listed in Appendix E Forms
Manual
Codes are listed in Appendix H Forms
Manual
-------
Field Name
Seg-Adm-Pay
AP-Type ,
Adm-Info
Adm-Date
Adm-Amt
AP-Type
Pay-Info
Pav-Date
Pay-Pen-Amt
Pay-FTA-Amt
Description
Admin/Pay Segment"
"Administrative and payment data blocks have a
common description and length. Both block types
can be present in a record. The value of the field
AP-TYPE determines the content of the block.
Alternate field names are given to be used
dependent on the type of data present
Administrative segment (from OSHA- 1 671)
' Type of Administrative payment data
Administrative cost data
Action date for activity
Administrative assessment applied to record
Payment Segment (from OSHA-163)
Type of payment
Payment Collection data
Date payment received and form completed
Amount of payment received for assessed penalties
Amount of payment received for failure-to-abate
charge
Values/format
1 5 characters
1-9 "Dunning letter
I = Interest fees
D = Delinquent fees
YYMMDD
P = Payment R = Refund
U * Unhonored check C = Court
,
YYMMDD
-------
-------
OSHA Instruction ADM 1-1, 12B
December 29, 1989
Office of Management Data Systems
Appendix E
INVESTIGATION SUMMARY CODES
Table E-l
NATURE OF INJURY CODES
01 Amputation
02 Asphyxia
03 Bruise/Contusion/Abrasion
04 Burn (Chemical)
05 -Burn/Scald (Heat)
06 Concussion ,
07 Cut/Laceration
08 Dermatitis
09 Dislocation
10 Electric Shock
11 Foreign Body in Eye
12 Fracture
13 Freezing Frost Bite
14 Hearing Loss
15 Heat Exhaustion
16 Hernia
17 Poisoning (Systemic)
18 Puncture
19 Radiation Effects
20 Strain/Sprain
21 Other
22 Cancer
Table E-2.
PART OF BODY CODES
01 Abdomen
02 Arm(s) Multiple.
03 Back v
04 Body System
05 Chest
06 Ear (s) -
07 Elbows(s)
0 8 Eye(s) ~
09 Face
10 Finger(s)
11 Foot/Feet/Toe(s)/Ankle(s)
12 Hand(s)
13 Head
14 Hip(s^)
15 Knee(s)
16 Leg(s)
17
18
19
20
21
22
23
24
.25
26
27
28
29
30
31
Lower Arm(s)
Lower Leg(s)
Multiple
Neck
Shoulders
Upper Arm(s)
Upper Leg(s)
Wrist(s)
Blood
Kidney
Liver .
Lung .
Nervous System
Reproductive System
Other Body System
-------
Table .E-3
SOURCE OF INJURY CODES
01 Aircraft
02 Air Pressure
03 Animal/Insect/Bird/Reptile/Fish
04 Boat
05 Bodily Motion
06 Boiler/Pressure
07 Boxes/Barrels, etc.
08 Buildings/Structures
09 Chemical Liquids/Vapors
10 Cleaning Compound
11 Cold (Environmental/Mechanical)
12 Dirt/Sand/Stone
13 Drugs/Alcohol
14 Dust/Particles/Chips
15 Electrical Apparatus/Wiring
16 Fire/Smoke
17 Food
18 Furniture/Furnishings
19 Gases
20 Glass
21 Hand Tool (Powered)
22 Hand Tool (Manual)
23 Heat (Environmental/
Mechanical)
24 ,Hoisting Apparatus
25 Ladder
26 Machine
27 Materials Handling
Equipment
28 Metal Products
29 Motor Vehicle (Highway)
30 Motor Vehicle
(Industrial),
31 .Motorcycle
32 Windstorm/Lighting, etc
33 Firearm
34 Person
35 Petroleum Products
36 Pump/Prime Mower
37 Radiation
38 Train/Railroad
Equipment
39 Vegetation
40 .Waste Products
41 Water
42 Working Surface
43 Other
44 Fume
45 Mists
46 Vibration"
47 Noise
48 Biological Agent
Table E-4
EVENT TYPE CODES
01 Struck By
02 Caught In or Between
03 Bite/Sting/Scratch
04 Fall (Same Level)
05 Fall (From Elevation)
06 Struck Against
07 Rubbed/Abraded
08 Inhalation
09
10..
11
12
13
14
Ingestion
Absorption
Repeated Motion/
Pressure
Cardio-Vascular/
Respiratory System
Failure
Shock
Other
-------
Table E-5 '-'.'.. '
ENVIRONMENTAL .FACTOR CODES
01 Pinch Point Action : '
.02 Catch Point /Puncture Action
03 Shear Point Action
04 Squeeze Point Action .
'05 Flying object Action
06 Overhead Moving and/or Falling Object Action
07 .Gas/Vapor/Mist/Fume/Smoke/Dust/Cqndition .
08 .Materials Handling Equipment/Method
09 Chemical Action/Reaction Exposure
10 Flammable Liquid/Solid Exposure
11 ' Temperature Above or Below Tolerance Level
12 Radiation Condition
13 Working Surface/Facility Layout Condition
14 Illumination
15 Overpressure/Underpressure 'Condition.
16 Sound Level .
17 Weather/Earthquake, etc. Condition . '
18 Other ' . .
Table E-6
N
" HUMAN FACTOR CODES .
01 Misjudgment of Hazardous Situation
04 Malfunction of Procedure for Securing Operation
or Warning of Hazardous Situation
05 Distracting Actions by Others
06 Equipment in Use Not Appropriate for Operation
07 Malfunction of Neuro-Muscular System
08 Malfunction of Perception System with Respect to
Task Environment ' "- .
09 Safety Devices Removed or Inoperative
10 Operational Position not Appropriate for Task
11 Procedure for Handling Materials Not Appropriate
for Task .
12 Defective Equipment: Knowingly Used
13 Malfunction of Procedure for Lock-Out or Tag-Out
14 Other
15 ' Insufficient or Lack of Housekeeping Program
16- Insufficient or Lack of Exposure or Biological
Monitoring
17 Insufficient or Lack of Engineering Controls
18 Insufficient or Lack of Written Work Practices
Program - .
19 Insufficient or Lack of Respiratory Protection
20 Insufficient or Lack of Protective Work Clothing
and Equipment '
-------
HSEES Datafield Dictionary
-------
HSEES is not directly accessible to the public; therefore, the datafield dictionary is unavailable.
-------
------- |