Near-Miss Reporting After a Maintenance Error
During a refueling outage, a technician installs a temporary blind flange on the wrong line. The error is caught 20 minutes later by a second technician doing an independent walkdown. No consequence occurred. The first technician, who has 15 years of experience, considers reporting but worries about being blamed; the site's last three event reports resulted in individual counseling and one disciplinary note. The supervisor learns of the error informally and says, 'Let's just fix it and move on-we're behind schedule.' The outage is four days behind, and contractor staff have been added rapidly with abbreviated onboarding. The site's corrective action program has a backlog of 300 open items, and the last human-performance investigation was closed as 'procedure not followed' with no further analysis.
1. Assess the safety-culture and human-reliability implications of the supervisor's response and the site's reporting history.
Read the worked answer
The supervisor's 'fix it and move on' response converts a free lesson into a hidden risk. A caught error with no consequence is the highest-value reporting opportunity a site gets, because it reveals a latent condition before it produces harm. Suppressing it means the wrong-line installation cause is never analyzed, so the same conditions-rushed outage work, abbreviated contractor onboarding, ambiguous line identification-remain in place. The reporting history explains the technician's hesitation: three reports produced individual counseling and a disciplinary note, which teaches the workforce that reporting is personally dangerous. That is a punitive, blame-oriented culture operating under a nominal 'just culture' label. The 300-item corrective action backlog signals that even reported issues do not get resolved, further eroding trust. Closing the last investigation as 'procedure not followed' is a stopping rule that terminates analysis at the individual, guaranteeing recurrence. The rapid contractor addition with abbreviated onboarding is a classic latent-error setup: unfamiliar people, high tempo, degraded barriers.
2. Recommend how the site should investigate this event and rebuild reporting, with concrete mechanisms.
Read the worked answer
Investigation: treat it as a learning event using a systems-oriented method (for example, event and causal factor or human-performance analysis) that maps the work as done-line identification practices, tag and blind lists, independent verification, time pressure, staffing mix, and onboarding content. Ask why the wrong line looked right: labeling, physical similarity, lighting, access. Ask why the independent check worked and how to make it robust. Do not close at 'procedure not followed'; that is a finding to explain, not a conclusion. Reporting: separate honest error from reckless or intentional violation in a written just-culture policy with defined outcomes, so workers can predict they will not be punished for reporting. Provide confidential and near-miss-only reporting channels. Give the supervisor coaching on response behavior, since first-line response determines whether others report. Reduce the corrective action backlog with triage and publish closure status so reporters see action. Address the outage conditions directly: restore adequate onboarding for added contractors, reassess schedule pressure, and add independent verification for safety-significant temporary installations. Track reporting rate and backlog as leading indicators, and review them with leadership.