Tanker fixed gas sampling system: monthly and yearly checks
EL-0193 · Knowledge · rating 0 · occurred 22 Oct 2022
Source: /cases/el-0193
Notes#
The fixed gas sampling system on an oil tanker needs monthly crew checks (visual inspection, alarm test, zero and span calibration) plus, as good practice, a yearly health check by an authorized service team. The system has sampling points in the pump room and in the ballast tanks; one important job is early warning if cargo oil leaks into the ballast tanks. This note is not tied to a particular maker or model.
Routine maintenance I follow:
- Work to the maker's planned maintenance schedule.
- Get an authorized service team on board once a year for a health check.
- Test the alarms at each sampling point in the pump room and in the ballast tanks.
- Clean the filters, or renew them when needed.
- Check the membranes in the sampling pumps. Renew them when needed.
- Calibrate the sensors.
- Check the sampling lines for blockage. Blow them through with air.
- Overhaul all solenoid valves in the system cabinet.
- Train both deck crew and engine crew to use the system.
Is a yearly calibration required?
- I don't know of any flag state or third-party rule that requires a yearly calibration of fixed gas sampling systems.
- As I understand it, the FSS Code (under SOLAS) gives the crew monthly tasks:
- a visual inspection;
- a test of the audible and visual alarms;
- zero and span calibration;
- any extra maintenance that the maker lists.
- Keep records of this monthly work on board.
- The yearly health check by an authorized service team finds faults that are not easy to see. I treat this as good practice, not as a stated rule.
Check before use. The FSS Code points above are my own summary; I don't have the chapter or paragraph number. Confirm the exact wording in the Code itself and in the maker's manual.
What this note doesn't cover: real fault cases, alarm set points, span gas type or concentration, intervals for renewing filters or membranes, and maker service letters or class notices.
Comments · 0
No comments yet.