When documenting an abnormal system fault in the BCC logbook, which elements must be included?

• A. Time of the incident, symptoms, affected systems, actions taken, escalation steps, and notification to supervision.
• B. Time of the incident and which operator found it.
• C. Only the affected systems and actions taken.
• D. A brief note with no specifics.

Answer: (A)

When documenting an abnormal system fault, you need a complete, time-stamped record that communicates what happened, what was affected, and how it was handled. Start with the exact time of the incident so you can place it in the sequence of events and correlate it with other data. Include the symptoms or error indicators observed to describe how the fault manifested. Note which systems or components were affected to define the scope of impact. Record the actions taken to respond—what diagnostics were run, what corrective steps were taken, and any temporary workarounds implemented. Include escalation steps to show the response path, such as who was notified and when, and confirm notification to supervision so oversight is documented. This full set ensures the log supports later review, accountability, and learning from the incident.

Other options miss essential pieces: one only mentions time and who found it, which doesn’t describe the fault or the response; another only lists affected systems and actions, missing timing, symptoms, escalation, and supervision notification; a brief note with no specifics lacks the detail needed for investigation and learning.