When a CSOSS procedure is not fully green due to a fault, what is the required approach?

• A. Continue with the normal sequence while noting the fault.
• B. Switch to the applicable casualty or degraded mode procedures per CSOSS to maintain safe operation and continue engagement using alternate paths.
• C. Shut down all systems.
• D. Call for external help.

Answer: (B)

When a CSOSS procedure isn’t fully green due to a fault, you shift to casualty or degraded mode procedures defined in CSOSS. These pre-planned modes are specifically designed to keep the ship safe and mission-capable even when part of the system isn’t functioning as intended. By changing to the casualty or degraded path, you use alternative equipment, configurations, or steps that bypass or compensate for the faulty element, allowing you to maintain safe operation and continue engagement using other routes or methods.

This approach is preferred over pressing ahead with the normal sequence while a fault is unresolved, because continuing as if everything were OK can escalate danger or lead to loss of control. Shutting down all systems is overly drastic and not required unless the fault creates an unsafe condition that cannot be managed within degraded or casualty procedures. Calling for external help is appropriate in some situations, but CSOSS provides internal procedures to handle the fault first, ensuring you maximize safety and operational continuity before escalating.

So, when a fault prevents a procedure from being fully green, you implement the applicable casualty or degraded mode procedures to preserve safe operation and maintain engagement through alternative paths.