Professional Documents
Culture Documents
60.0501 Incident Investigation
60.0501 Incident Investigation
INCIDENT INVESTIGATION
(GUIDELINE)
PTS 60.0501
JUNE 2006
Rev 1
PTS 60.0501
JUNE 2006
2
PREFACE
PETRONAS Technical Standards (PTS) publications reflect the views, at the time of publication, of
PETRONAS Corporate.
They are based on the experience acquired during the involvement with the design, construction, operation and
maintenance of processing units and facilities. Where appropriate they are based on, or reference is made to,
national and international standards and codes of practice.
The objective is to set the recommended standard for good technical practice to be applied by PETRONAS'
OPUs in oil and gas production facilities, refineries, gas processing plants, chemical plants, marketing facilities
or any other such facility, and thereby to achieve maximum technical and economic benefit from
standardisation.
The information set forth in these publications is provided to users for their consideration and decision to
implement. This is of particular importance where PTS may not cover every requirement or diversity of
condition at each locality. The system of PTS is expected to be sufficiently flexible to allow individual
operating units to adapt the information set forth in PTS to their own environment and requirements.
When Contractors or Manufacturers/Suppliers use PTS they shall be solely responsible for the quality of work
and the attainment of the required design and engineering standards. In particular, for those requirements not
specifically covered, the Principal will expect them to follow those design and engineering practices which will
achieve the same level of integrity as reflected in the PTS. If in doubt, the Contractor or Manufacturer/Supplier
shall, without detracting from his own responsibility, consult the Principal or its technical advisor.
2) Other parties who are authorised to use PTS subject to appropriate contractual arrangements.
Subject to any particular terms and conditions as may be set forth in specific agreements with users,
PETRONAS disclaims any liability of whatsoever nature for any damage (including injury or death) suffered
by any company or person whomsoever as a result of or in connection with the use, application or
implementation of any PTS, combination of PTS or any part thereof. The benefit of this disclaimer shall inure
in all respects to PETRONAS and/or any company affiliated to PETRONAS that may issue PTS or require the
use of PTS.
Without prejudice to any specific terms in respect of confidentiality under relevant contractual arrangements,
PTS shall not, without the prior written consent of PETRONAS, be disclosed by users to any company or
person whomsoever and the PTS shall be used exclusively for the purpose they have been provided to the user.
They shall be returned after use, including any copies which shall only be made by users with the express prior
written consent of PETRONAS. The copyright of PTS vests in PETRONAS. Users shall arrange for PTS to be
held in safe custody and PETRONAS may at any time require information satisfactory to PETRONAS in order
to ascertain how users implement this requirement.
PTS 60.0501
JUNE 2006
3
PTS 60.0501
JUNE 2006
4
TABLE OF CONTENTS
1. INTRODUCTION 6
1.1 Objectives 6
1.2 Structure of the Guide 7
1.3 Link with other Document 7
1.4 Written Policy and Procedures 7
4. FOLLOW-UP 22
4.1 Communication of Investigation Findings 22
PTS 60.0501
JUNE 2006
5
PTS 60.0501
JUNE 2006
6
Appendix 1 DEFINITIONS 24
Appendix 2 - INCIDENT INVESTIGATION TREES 26
Appendix 3 INCIDENT INVESTIGATION REPORTS 30
PTS 60.0501
JUNE 2006
7
1. INTRODUCTION
This document provides guidelines on procedures for effective incident investigation
and analysis
1.1 Objectives
The objectives of this Guide are:
• to explain the incident investigation process and the relationship between the
available techniques and methodologies for analysis and recording,
PTS 60.0501
JUNE 2006
8
• Work Injuries
• Occupational illnesses
• Environmental damage
• Property damage
• Near Misses
• Security Breach
The procedure should specify the actions required at each stage in the investigation
process and indicate the action parties, routing of communications and reports, and
related deadlines. The procedures should be supplemented by guidelines on a number
of issues, including the following:
PTS 60.0501
JUNE 2006
9
measures
PTS 60.0501
JUNE 2006
10
PTS 60.0501
JUNE 2006
11
When an incident occurs the first action to be taken is to prevent further injury and
arrange for any necessary medical treatment as well as taking measures to prevent the
situation from escalating and causing further damage. Where possible, the site should
be left unchanged until the investigation team has inspected it. Where this is not
possible, photographs should be taken or sketches be made of the scene.
A preliminary assessment of the incident should be made to identify the extent of
injury or damage, and any potential for escalation.
• advise operations control (so that adjustment can be made to the plan of
operations)
Notification should be made via the senior person at the location or plant.
Notification should be routed to the line function and to other departments from
which assistance is sought and also to the HSE organisation. Routing should be
specified in the Company's Incident Investigation Procedures.
The notification should contain details of:
• assistance required
The notification report should be factual and avoid hearsay, assumptions and
preliminary conclusions. If the notification is made verbally via mobile phones, it
should be followed up by a written email, faxed or telexed confirmation.
Operating companies should set stringent, fast, but achievable deadlines for
PTS 60.0501
JUNE 2006
12
PTS 60.0501
JUNE 2006
13
3.1.1 General
The notification of an incident triggers the start of the investigation process, which
comprises the consecutive stages as indicated in Figure 1.
PTS 60.0501
JUNE 2006
14
3.2.1 General
The size and composition of an investigation team will depend on one or all of the
following factors:
• departments involved
• legal requirements
For many incidents the investigative skill and effort required may be within the
capability of one person, who, for minor incidents, could be the line supervisor.
PTS 60.0501
JUNE 2006
15
• to identify the root causes of the incident such that actions can be taken to
prevent recurrence of future incidents
• to establish the facts surrounding the incident for use in relation to potential
insurance claims or litigation
PTS 60.0501
JUNE 2006
16
This may necessitate review of aspects remote from the location and time of the
Incident.
3.3.2 Timing
An investigation should be carried out as soon as possible after an incident,
preferably within 24 hours as the quality of evidence can deteriorate rapidly with
time, and delayed investigations only add to the “uncertainties” surrounding the
investigation.
• location plans
• contractual requirements
• messages, directions etc., given from base/head office concerning the work.
Before proceeding out to the scene of the accident, the team leader will brief the team
the information available thus far relating to the incident in terms of the harm done
and actions taken. The team will draw up the preliminary Hazard – Event – Target
(HET) diagram as a guide for gathering information. Where the barriers and controls
can be identified they should be reflected to produce the preliminary “core” diagram
in the investigation process
• interviewing witnesses
PTS 60.0501
JUNE 2006
17
During the initial stages of every investigation, investigators should aim to gather and
record all the information which may be of interest in determining causes.
Investigators should keep an open mind and considering the full range of
possibilities.
Checklists can be very useful in the early stages to keep the full range of enquiry in
mind, but they cannot cover all possible aspects of an investigation, neither can they
follow all individual leads back to basic causal factors. When checklists are used,
their limitations should be clearly understood. Make use of the core diagram to act as
prompters on areas to look at, effectiveness of which could have prevented the
accident.
• people
• environment
• equipment
• procedures
• organisation
Conditions, actions or omissions for each of these may be identified, which could be
factors contributing to the incident or to subsequent injury, damage or loss.
A factor to consider during an investigation is recent change. In many cases it has
been found that some change occurred prior to an incident which, combining with
other causal factors already present, served to initiate the incident. Changes in
personnel, organisation, procedures, processes and equipment should be investigated,
particularly the hand-over of control and instructions, and the communication of
information about the change to those who needed to know.
PTS 60.0501
JUNE 2006
18
The effect of work cycles and work related stress could have an impact on
individuals' performance prior to an incident.
The impact of social and domestic pressures related to individuals' behaviour should
not be overlooked.
The initial stages of an investigation normally focus on conditions and activities close
to the incident and only immediate causes are usually identified at this stage.
However, the conditions underlying these causes may also need investigating.
Information should be verified wherever possible. Statements made by different
witnesses may conflict and supporting evidence may be needed.
To ensure that all the facts are uncovered, the broad questions of "who?, what?,
when?, where?, why? and how?" should be asked.
After fact finding / information gathering it should be possible to:
• identify what barriers in place did not work or should be in place but missing
PTS 60.0501
JUNE 2006
19
• make an inventory of all the consequences of the incident (injury, damage and
loss).
• the position of valves, spades, set points, recorders, override switches, etc.
PTS 60.0501
JUNE 2006
20
• accessibility/evidence of congestion
• state of house-keeping
• effects of weather
• presence of witnesses
• odours, discolouration
PTS 60.0501
JUNE 2006
21
PTS 60.0501
JUNE 2006
22
investigator(s) should shift the emphasis of their investigation and questioning to the
underlying causes and to the reasons for peoples' actions. This will allow for ease of
assessment when analysing the incident.
3.4.1 General
The approach of tabulating events and then ordering them by date, time and place is
an essential stage in establishing the sequence of events towards the Hazard – Event
– Target (HET) diagram for the accident. Identifying the respective failed barriers /
controls result in the establishment of the “core” diagram.
system for a long time, and their adverse consequences may only become evident
when they combine with other factors to breach the system defences. Detailed case
studies reveal that latent rather than active failures are the precursors of incidents.
Tripod classifies these latent failures into General Failure Types (GFTs) / Basic Risk
Factors (BRFs).
Identifying and correcting these latent failures rather than merely correcting the
active failures induced by them (symptoms), is more effective in meeting the ultimate
objective of the investigation, namely to improve the overall HSE performance.
Identification of underlying causes and latent failures need not necessarily involve
application of the full Tripod methodology, but should apply the causation theory as
proposed by Tripod (See Fig. 2), involving a brief consideration of the GFT/BRFs.
See Appendix 3 for a summary of the Tripod methodology.
Figure 2 Tripod Incident Causation Sequence
PTS 60.0501
JUNE 2006
24
I causal/trend analysis.
For this purpose a database such as the Group common system to be defined can be
used. AN OTHER is a computer-based system for use by Operating Units, which
can also be used to transfer data to the PETRONAS Group Companies.
Notification to PETRONAS Group Companies can be done by document transmittal
or, for some Operating Units, by diskette or direct computer data transfer.
4. FOLLOW-UP
PTS 60.0501
JUNE 2006
25
Hardware related items are normally easy to identify as having been completed, e.g.
when the modification has been effected or when the new equipment has been
received or installed. This is not always the case with items such as training, changes
to procedures or supervision and particularly when action is described as "ongoing".
A precise description of the action item is essential if it is to be effective.
It is suggested that a procedural action point is considered to have been completed
when:
I written instructions have been issued and circulated to all staff
concerned
PTS 60.0501
JUNE 2006
26
This analysis allows for better identification of the lessons learnt from individual
incidents and improves the ability to identify and correct weaknesses in HSE
management. In addition, the computer system can facilitate performance monitoring
of individual units, contractors, etc.
Statistical analysis of incidents is only able to reflect what has happened and is
therefore a reflection of past policies and their implementation. For statistical
analysis to be meaningful a significant number of entries is required in order to be
able to detect trends. As a company's safety performance improves, complete
recording and analysis of all incidents becomes increasingly more important.
PTS 60.0501
JUNE 2006
27
APPENDIX 1 - DEFINITIONS
ACCIDENT
An Accident is an Incident which has resulted in actual Injury or Illness and/or
Damage (Loss) to Assets, the Environment or Third Party(ies).
EMPLOYMENT
Employment means all work or activity performed in carrying out an assignment or
request of a Reporting Company or Reportable Contractor, including related
activities not specifically covered by the assignment or request.
Employment also includes activities, even outside working hours, where the
Reporting Company has the Prevailing Influence. Under certain circumstances
travel to and from work is also considered as being in the course of Employment.
INCIDENT
An Incident is an unplanned event or chain of events, which has or could have
caused Injury or Illness and/or Damage (Loss) to Assets, the Environment or Third
Party(ies).
OCCUPATIONAL ILLNESS
An Occupational Illness is any work-related abnormal condition or disorder, other
than one resulting from a Work Injury, caused by or mainly caused by exposures at
work.
The basic difference between an Injury and Illness is the single event concept. If the
event resulted from something that happened in one instant, it is an injury. If it
resulted from prolonged or multiple exposure to a hazardous substance or
environmental factor, it is an Illness.
REPORTABLE INCIDENT
A Reportable Incident is one that is required to be reported to the Regional Focal
Point for Safety and the Functional Safety Advisor in accordance with the special
reporting procedures that have been established in Section 3 of the Guide for Safety
Performance Reporting.
PTS 60.0501
JUNE 2006
28
WORK INJURY
A Work Injury is an injury or illness, regardless of severity, which arises from a
single event (or a number of events close together in time) in the course of
Employment.
In cases where this definition gives reasons for doubt, an injury should be treated as a
Work Injury.
Injuries in the course of Employment which are caused by wilful acts are, in general,
treated as Work Injuries.
Injuries caused by the deficiencies in equipment or management controls for which
the Reporting Company is responsible are treated as Work Injuries, even when they
occur outside working hours.
Occupational illnesses and death from natural causes are not considered as Work
Injuries for the purpose of this Guide.
PTS 60.0501
JUNE 2006
29
I component failure
.
. I a rain squall.
An "event" could be the start of a condition, e.g. a joint failure having created a
flammable atmosphere.
Not all of the events and the conditions described are faults. The full description of
the circumstances of an incident must include all normal factors so that decisions
made and actions taken can be seen in their correct context.
1. CONSTRUCTION OF TREES
The incident event is the starting-point for constructing an investigation tree. Starting
with the incident itself, identify the prior events or conditions which were necessary
for the incident to happen (essential factors). Each factor can then be traced back in a
similar way, identifying further essential factors. The process of tracing back should
be continued for each chain of events to a point where it is considered to be outside
the control or prevailing influence of the Company.
Validation should establish that only factors which had any bearing on the incident
are included in the tree diagram. "Factors A, B (and C) were all necessary for event
D to happen". These should be joined by an 'and' gate. If removal of a factor is seen
not to affect the outcome it cannot be considered an essential factor.
If several alternative factors could have contributed to the next event, then these
should be combined through an "or" gate and may highlight an area where further
investigation is required.
PTS 60.0501
JUNE 2006
30
Background
Four men had been assigned to clear a track for a water line between a new drilling
location and a nearby creek. The new location was across the creek from the
engineering base camp. To get to the worksite from base, crews could either cross the
creek by canoe or walk around via an upstream bridge, which would take them about
an hour and a half.
On the day of the accident, the four men had been able to get a local canoe to ferry
them across in the morning. At about 11.30, being hungry, they decided to return to
the camp for lunch. They waited a short while for a canoe to pass, but none came.
Their supervisor was not there, and they did not want to lose time by waiting, so they
decided to swim across the creek. The water was flowing quite fast, but the creek was
only six metres wide and they all had life-jackets.
Due to the current, they all experienced difficulty in swimming. Three men managed
to make it to the other bank, exhausted, but they could not locate their companion
(Mr. X). The creek was muddy and full of debris.
Mr.X's body was recovered by villagers some 24 hours later. It was found at the
bottom of the creek, some 50 metres downstream of the crossing point. His life-
jacket was still attached.
PTS 60.0501
JUNE 2006
31
.
. I The labour subcontractor was given a daily allowance to cover transport. He
did not provide a canoe on stand-by, but there were usually enough local
canoes passing for his crews to obtain lifts across the creek.
.
. I Life-jackets of local manufacture had been issued for use when working by
water. Due to recent rains, rivers and creeks were high. Instructions had been
given to wear life-jackets "at all times".
.
. I Life-jackets had been in use for about three months, but many were in poor
condition, with securing tapes broken or missing and polystyrene floatation
blocks broken/compressed.
.
. I Neither the Company nor the Contractors had prepared a river crossing
procedure.
.
. I There was no rule forbidding swimming; contractor management considered
that some swimming was unavoidable.
.
. I It was the understanding that all men could swim, but no swimming tests
had been held, so individual competence had not been verified.
.
. I The subcontractor's labour were paid on a piece-work basis.
.
. I Construction crews were split up into groups of 3 to 4 men, one supervisor
looking after 5 or 6 groups.
Further leads to follow in order to complete the investigation tree (refer to the
numbers on Figure 3).
1. Controls in piece work contract to make sure that safe working practices were
maintained.
PTS 60.0501
JUNE 2006
32
12. Suitability of life-jacket materials and fabric for daily rough usage.
PTS 60.0501
JUNE 2006
33
This appendix contains a brief description of the key elements of a written investigation
report. General recommendations to consider in preparing the report are:
. I where events or conditions are listed, that are not critical for the incident to
have occurred, this should be clearly indicated
.
. I the report should be readable as a stand alone document, references to other
documents not open to inspection by others i.e. the public, should be avoided
.
. I a papertrail of the documents relevant to the incident and the report should be
established.
PTS 60.0501
JUNE 2006
34
PTS 60.0501
JUNE 2006
35
Details of Damage
. I description of the extent of direct damage
.
. I estimate of loss value
.
. I estimate of consequential losses.
I environmental conditions
I activities of key persons prior to the day of the incident that could have
affected their actions.
PTS 60.0501
JUNE 2006
36
I working conditions
I survival aspects
Conclusions
This section should include the results of the analysis of the findings, identifying the
immediate and underlying causes and commenting on the effectiveness of rescue and
damage containment activities where appropriate.
Conclusions based on circumstantial evidence should be highlighted as such.
Appendices
Any other pertinent information considered necessary for the understanding of the report.
This should include photographs, maps and drawings to supplement and clarify the written
report.
PTS 60.0501
JUNE 2006
37
Many companies have a standard incident report form. A standard form is not essential but
can have the advantage of setting out the minimum reporting needs in a logical order.
However, standard forms can have disadvantages, some of them caused by form design. A
review of the way in which forms are completed may highlight areas where they are
deficient. It must also be borne in mind that in the case of complex incidents, a standard
form will seldom be adequate.
Many standard incident report forms do not differentiate sufficiently between the elements of
incident notification, investigation findings and recommendations. These elements could
well be completed by different people, and should be kept clearly segregated.
One approach is to have a short basic Accident Notification form, and a longer Investigation
Report containing detailed results of the investigation.
Not all forms are self-explanatory, and there should be clear guidelines available to ensure
common understanding of information requirements, e.g. clear differentiation between
"description of event" and "incident cause".
Allocation of space is a very critical part of form design, and insufficient space may lead to
lack of detail being recorded.
Whether a standard form is used or not, the investigation report with appropriate appendices
should "stand alone", i.e. it should contain all relevant information necessary for reviewing
the incident.
PTS 60.0501
JUNE 2006