COLREG Bridge Case #1: Crossing Situation | What Should the OOW Do?

COLREG Bridge Case #1 – Crossing Situation You are the Officer of the Watch. A power-driven vessel is approaching from your starboard side and the bearing is remaining nearly constant while the range decreases. Is there a risk of collision? Which vessel is required to keep out of the way? What action should the OOW take? This scenario-based COLREG training case examines the encounter step by step using the relevant International Regulations for Preventing Collisions at Sea. Rules covered: Rule 5 – Look-out Rule 7 – Risk of Collision Rule 8 – Action to Avoid Collision Rule 15 – Crossing Situation Rule 16 – Action by Give-way Vessel Rule 17 – Action by Stand-on Vessel The case covers: Detecting a developing collision risk Constant or nearly constant bearing with decreasing range Identifying the give-way and stand-on vessels Early and substantial avoiding action Why small alterations can be dangerous Responsibilities of the stand-on vessel When the stand-on vessel may and must take action Monitoring until both vessels are finally past and clear Bridge Takeaway: COLREGs should be applied as a connected decision-making system rather than individual rules considered in isolation. Scenario assumptions: Both vessels are power-driven vessels underway, are in sight of one another, and the encounter involves risk of collision. For educational and training purposes. Actual navigational decisions must account for the full circumstances and conditions of the encounter. COLREG Bridge Training Series – Case #1 #COLREG #Rule15 #OOW #BridgeWatchkeeping #CollisionAvoidance #MaritimeTraining #DeckCadet #MerchantNavy COLREG crossing situation, COLREG Rule 15, crossing situation at sea, give way vessel, stand on vessel, OOW training, bridge watchkeeping, collision avoidance, CPA TCPA, risk of collision, Rule 7 COLREG, Rule 8 COLREG, Rule 16 COLREG, Rule 17 COLREG, deck cadet training, merchant navy training, marine navigation, rules of the road, bridge simulator, maritime case study