F-Gas on Yachts: Traceability, Risks and Best Practices
F-Gas compliance is not just an administrative matter: poor refrigerant traceability slows down diagnostics, increases the risk of unplanned downtime, and complicates relationships with contractors — and sometimes with insurers and managers. Here is a simple method for keeping a log that is clear, consistent and actually usable.
On a yacht, refrigeration and HVAC are mission-critical systems. When a chiller or air handling unit trips out in the middle of summer, the diagnosis needs to be fast. Without a clear history of refrigerant handling — type, quantities, interventions — time is lost, assumptions multiply and the risk of costly decisions rises sharply.
- Faster diagnosis: knowing whether a performance drop followed a recent top-up, or whether a slow leak is likely.
- Better contractor oversight: avoiding work carried out on gut feel (top-ups without a leak search, missing data).
- Fewer unplanned stops: scheduling actions (leak search, parts, dockside windows) instead of reacting to them.
Operational risks
- Unplanned trips (HP/LP alarms), reduced capacity, short cycling.
- Insufficient cooling during the day → discomfort and humidity on board.
- Time wasted reconstructing history (who did what, when, how much).
Contractual & reputational risks
- Disputes over work quality when measurements and records are absent.
- Difficulty comparing quotes and solutions without baseline data.
- Increased complexity during refit or pre-purchase (incomplete technical file).
Safety & environmental risks
- Interventions without appropriate controls (pressure, leak detection, space ventilation).
- Untreated leaks → environmental impact and additional cost.
- Repeated circuit openings increase the probability of handling errors.
Insurance risks (indirect)
- An incident file is harder to defend when no evidence of tracking or maintenance exists.
- Unclear chronology of events (top-up, fault, leak, repair).
- Corrective actions that were taken but not documented.
Without building a complex system, aim for a simple and consistent log (spreadsheet or shared folder) with standardised fields. The goal: find any piece of information in under 30 seconds.
- Equipment: chiller ID, refrigeration unit, galley/cold room + location on board.
- Refrigerant: type (e.g. R-xxx) + nominal charge (nameplate) + quantity added or recovered.
- Date & port: where the intervention took place + conditions (dockside / under way).
- Reason: scheduled maintenance, fault, top-up, leak search, component replacement.
- Measurements: pressures and temperatures (HP/LP) + findings.
- Action taken: what was done (with parts where applicable).
- Outcome: final test + status (OK / monitor) + next step.
- Contractor: name, company, contact + work order or quote reference.
- Attachments: photos of nameplate, reports, work orders, data logs.
Tip: one equipment sheet per unit + a single chronological work journal (all interventions across all systems) is usually sufficient.
A) Standardise your fields
- Always use the same equipment identifiers (e.g. “CH-01”, “CH-02”).
- Record quantities consistently with units (kg / g).
- Add a “probable cause” field and a “next action” field.
B) Require a measured end-of-work test
- A final check: stable operation, no alarms, setpoint reached where possible.
- If a top-up was done: record why (suspected leak?).
- If a leak was found: record the detection method, location and fix.
C) Keep evidence (without overcomplicating it)
- Photo of nameplate + refrigerant label + instrumentation where possible.
- PDF or work order attached to the log entry.
- One shared folder: “HVAC_Refrigeration/Logs”.
D) Prepare the pre-purchase / refit file
- Major recent interventions + incidents + parts replaced.
- Equipment list + refrigerant types + nominal charges.
- Watchpoints and recommended work.
“A well-maintained log takes no more than 10 minutes a month to keep up — and can save several hours at the next diagnostic.”
- Equipment identifier + location + refrigerant type + nominal charge.
- Reason for intervention + observed symptoms.
- Initial measurements (HP/LP, temperatures, active alarms) where accessible.
- Action carried out (recovery / vacuum pull / top-up / component replacement).
- Quantity recovered / added / final charge + method where applicable.
- Leak search: method used + location found + repair + verification.
- Final test + observations + recommendations.
- This month’s interventions: all entries complete + PDFs attached.
- Equipment under watch: drifts, suspected slow leaks.
- Parts and consumables to plan (dockside window, refit).
- Gaps: missing information → follow up with the contractor.
- Repeated top-ups without a leak search: this masks the problem and accumulates cost.
- Fragmented records (emails, WhatsApp messages, ungrouped photos): impossible to use in an emergency.
- Inconsistent equipment names: “salon chiller”, “CH1”, “unit 1” in the same file guarantees confusion.
- No end-of-work test: the unit “restarts” but performance is never validated.
- No baseline values: without normal operating data, identifying a drift is guesswork.
What log format works best?
A simple spreadsheet combined with a shared folder of PDFs and photos with consistent naming. The most important factors are standardised fields and the discipline to update the log after every intervention.
When does traceability become truly critical?
As soon as you have intermittent faults, a performance drop, or a history of repeated top-ups. It is also essential in a pre-purchase context or before a refit.
Does it genuinely help with diagnosis?
Yes: if performance drops after a recent intervention, if top-ups keep recurring, or if the refrigerant type or charge is uncertain, a good log immediately points towards the cause — leak, heat exchanger, controls, and so on.
RivierX Engineering can set up a simple logging framework and check the critical points on board.