A new cadet asks the chief mate why deck officers need to know about engine room operations when there are engineer officers responsible for propulsion. Explain the chief mate's management-level engineering knowledge requirement.

A. CHIEF MATE ENGINEERING KNOWLEDGE — WHY IT IS REQUIRED: STCW CODE A-II/2 AND MIN 653 S4 require chief mates to have knowledge of: (a) Operating principles of marine power plants; (b) Ships' auxiliary machinery; (c) Remote control systems for propulsion; (d) General knowledge of marine engineering terms. WHY DECK OFFICERS NEED THIS: (1) EMERGENCY DECISION MAKING: if the chief engineer is incapacitated, the master (and chief mate by extension) must make informed decisions about engine status, available power, and manoeuvring capability. Deciding whether a low starting air pressure allows departure requires engineering understanding; (2) BRIDGE-ENGINE INTERFACE: the bridge officer issues orders to the engine room. Effective communication requires understanding what is being requested and what the limitations are — a chief mate who orders "full ahead" when a cold main engine needs warming cannot be surprised by the engineer's response; (3) CASUALTY INVESTIGATION: a chief mate who cannot describe the propulsion system when questioned in an MCA formal inquiry is professionally embarrassed and legally exposed; (4) PILOT INFORMATION: the pilot card requires propulsion type, CPP/FPP, number of screws, engine type — the chief mate must be able to verify and provide this accurately; (5) PORT STATE CONTROL: PSC officers may ask deck officers about engineering equipment — MARPOL compliance (oily water separator, ORB) involves both departments. The standard is "general knowledge" not expert engineering knowledge — the chief mate need not be able to overhaul a turbocharger but must understand how propulsion systems function.

B. Deck officers do not need engineering knowledge. STCW separates deck and engineering certificates precisely because these are distinct specialisations — any overlap is informal and not examined.

C. Engineering knowledge is only required of the master, not the chief mate. The chief mate's competence is limited to cargo, stability and navigation.

D. Deck officers only need to know how to operate the bridge telegraph. The technical details of engine operation are irrelevant to deck officer duties.

A. BRIDGE ENGINE REMOTE CONTROL — PRINCIPLES AND TESTING: OPERATING PRINCIPLE: Modern vessels have a telegraph system that allows the bridge to command propulsion from three positions: (1) Bridge wing (port and starboard); (2) Bridge centre console (primary); (3) Engine room local control (manual override). The system typically uses an electronic or electro-pneumatic telegraph — the bridge moves the telegraph lever and the engine room control room (or automated system) responds with matching engine movement. REMOTE CONTROL TYPES: (a) Bridge full control: bridge moves engine telegraph → ECR or UMS system automatically adjusts fuel injection, ahead/astern valve, and RPM; (b) Telegraphed control: bridge signals intention, engine room carries out manually; (c) CPP (Controllable Pitch Propeller): blade pitch changes rather than engine RPM — bridge pitch lever directly adjusts thrust. PRE-DEPARTURE TEST: (1) Notify engine room of impending test; (2) Test both bridge wing controls and centre console — move telegraph full range ahead/stop/astern; (3) Confirm ECR repeater matches bridge telegraph position; (4) Test emergency stop function; (5) Confirm steering gear tested (SOLAS V/26 — 12 hours before departure); (6) Log all tests with times; (7) Confirm with chief engineer "engines ready for manoeuvring."

B. Bridge engine control is tested only at drydock. Between drydocks, the engineer officer of the watch is solely responsible for engine operations and the chief mate has no role in engine testing.

C. The bridge telegraph is advisory only. The engine room carries out all engine movements independently — the bridge telegraph is a communication tool, not a control system.

D. Engine testing before departure is done by increasing to full ahead for 5 minutes then stopping. Other tests are the chief engineer's responsibility and are covered by the SMS.

A. UMS ALARM — BRIDGE OOW/CHIEF MATE RESPONSIBILITIES: UMS BACKGROUND: SOLAS II-1/46-54 and the UMS Code (MSC/Circ.645) allow machinery spaces to be operated without continuous manning when the vessel meets prescribed equipment and alarm standards. The engineer is on call, not in the machinery space. OOW BRIDGE ACTIONS ON UMS ALARM: (1) ACKNOWLEDGE the alarm on the bridge alarm panel — this stops the audible alarm but keeps the visual; (2) RECORD: alarm type, time, and acknowledge time in the logbook; (3) CONTACT the duty engineer officer — give the alarm description and location; (4) MONITOR the alarm: if a second alarm follows rapidly (cascade alarms), or if a HIGH PRIORITY alarm activates (blackout, main engine shutdown, steering failure) — take immediate navigational action as appropriate; (5) DO NOT SILENCE AND IGNORE: the alarm system requires that alarms are responded to — an unresponded-to alarm triggers escalation to the next person on the call list; (6) HIGH PRIORITY ALARMS: main engine slowdown/shutdown → notify master, consider navigational implications (vessel now drifting or under reduced power); (7) Document all alarms, response times, and engineer actions taken in the UMS alarm log. CHIEF MATE UNDERSTANDING: must know which alarms require navigational response vs engineering response.

B. All UMS alarms are exclusively the duty engineer's responsibility. The bridge OOW should silence the alarm and wait for the engineer to respond — there is no bridge action required.

C. Wake the master for every UMS alarm. Only the master has authority to decide whether a UMS alarm requires action at night — the OOW should not make this assessment.

D. UMS alarms can be safely ignored for 30 minutes before escalation. The engineer's call response time is 30 minutes under SOLAS and the OOW should not contact the engineer before this period expires.