A cargo ship under dark storm clouds at sea
X3 MaritimeGuide · how to fill it out

X3 Casualty,Field by Field.

Is it reportable? Is it a serious marine incident? The clocks, the CG-2692 and the fix.

The rules your operation answers to
  • 46 CFR 136-144Subchapter M towing vessels
  • 46 CFR 199.180Monthly drills
  • 46 CFR 10.301Medical certificates
  • 46 CFR 16.230Random testing — 50%
  • 29 CFR 1915.12Confined & enclosed spaces
  • 29 CFR 1917.50Crane certification
  • 33 CFR 105.220Security drills every 3 months
  • 33 CFR 155.1060Spill response exercises
  • 46 CFR 4.05-10CG-2692 within 5 days
  • 46 CFR 4.06-32-hour / 32-hour test clocks

Every record X3 Casualty keeps, the rule behind it, how often it comes due, and exactly what to type in each field — with where to find it on your own paperwork.

Casualties

46 CFR 4.05 / 4.06 · Each time it happens

Marine casualties: groundings, injuries, damage and other accidents. Many must be reported to the Coast Guard right away, followed by form CG-2692 within 5 days.

FieldWhat it isWhere to find itExample
OccurredWhen the casualty happened.Logbook entry.06/30/2027 03:40
What happenedWhat happened, in plain words.Master's report or logbook.Tow grounded at mile 182 in fog
A barge was involvedYes if a barge was involved. A CG-2692A is then needed.Master's report.Yes
Death, injury or missing personYes if anyone died, was hurt beyond first aid, or is missing.Master's report.No
Reportable (4.05-1)Whether it must be reported to the Coast Guard.Grounding, loss of propulsion or steering, injury needing professional treatment beyond first aid that leaves the person unfit for routine duties, or damage over $75,000.Yes
Serious marine incident (4.03-2)Whether it is a serious marine incident (SMI). An SMI triggers drug and alcohol testing.SMI: a death; an injury needing professional treatment beyond first aid that leaves the person unfit for routine duties; property damage over $200,000; total loss of an inspected vessel, or an uninspected vessel of 100 GT or more; 10,000 gallons or more of oil discharged; or a reportable quantity of a hazardous substance released (46 CFR 4.03-2).Yes
Coast Guard notified atWhen you told the Coast Guard (right away, once safety is under control).Call log: the Sector or MSU you called and who you spoke with.06/30/2027 04:15
CG-2692 filedThe date the CG-2692 was sent (within 5 days).Your copy of the email or fax to the Sector or MSU.07/02/2027
Alcohol tests completedWhen alcohol tests were done (within 2 hours of an SMI).Breath or saliva test forms.06/30/2027 05:20
Drug specimens collectedWhen drug specimens were collected (within 32 hours of an SMI).CCFs from the collection.06/30/2027 14:00
Why any test was late or not doneIf a test was late or not done, the reason. This also goes on the CG-2692 and CG-2692B.Master's notes.No collector reachable until 10:00
Evidence of alcohol or drug use (4.05-12)Whether there's evidence of drug or alcohol use.Test results or witness observations.None found
StatusOpen, Investigating or Closed.Close when the investigation and actions are done.Investigating

Corrective Actions

Company program · Each action

Fixes assigned after a casualty or near miss, with a named owner and a check that each fix worked.

FieldWhat it isWhere to find itExample
ActionWhat will be done.Investigation report.Add fog procedure to TSMS
DueWhen it must be done.Investigation report or your SMS deadline.07/31/2027
StatusOpen, Done - awaiting check, or Verified.Verified means someone checked the fix worked.Open

Near Misses

Company program · Each time it happens

Close calls where nothing was hurt or damaged. Reporting them helps prevent the real accident.

FieldWhat it isWhere to find itExample
DateThe date of the near miss.Crew report.06/30/2027
What almost happenedWhat almost happened.Crew report. Describe it without blame.Line parted near deckhand
What was doneWhat was done about it.Supervisor's notes.Replaced line, toolbox talk

Root Cause

Company program · Each casualty or serious near miss

Root cause analysis: finding out why something happened so it doesn't happen again. 'Human error' alone is not a root cause.

FieldWhat it isWhere to find itExample
MethodThe method used to find the root cause.Pick the method your team used.5 Whys
Root causeThe underlying reason it happened.Investigation findings. Name a cause you can fix, not just 'human error'.No fog procedure in the TSMS
Contributing factorsOther things that helped it happen.Investigation findings.Fatigue, radar not tuned
Lessons learned / bulletinWhat the fleet should learn from it.Your lessons-learned bulletin.Stop and hold in fog under 0.5 mile

Compliance information, not legal advice. Rules cited are current as we publish; confirm against the official eCFR.