Make sure your PLB and EPIRB registrations are up to date

Help us to help you! Please make sure that your personal locator beacon (PLB) and/or emergency positioning indication radio beacon (EPIRB) registrations are up to date.

Indeed, now could be as good a time as any for some admin work and to check that your information is up to date. Register, for free, click here.

We remind you of this in light of an incident we attended to on 4 May, which involved a search for a 9m sailing vessel after an EPIRB was activated near Teignmouth.

The HM Coastguard helicopter from St Athan, Exmouth and Teignmouth Coastguard Rescue Teams, Exmouth and Teignmouth lifeboats, and Avon and Somerset Police were all sent to search for the vessel from just before 2pm to past 8.30pm.

The EPIRB had been registered but the owner’s contact details were out of date as the associated vessel had been sold on several times.

All of the subsequent owners of the vessel were contacted and, thankfully, the current owner was found safe and well on land and the vessel was moored safely in a marina.

However, the EPIRB was no longer with the vessel. A decision was subsequently made to stand down following a thorough search.


Phil Norman, Duty Controller for HM Coastguard, said: “When an emergency beacon is activated we have to assume the worst, that a vessel is in difficulty and people are in need of urgent help.

“The search involved a significant amount of resources, not only Coastguard assets but police ones too. If the emergency beacon had the most recent owner’s contact details, or if it had been disposed of correctly this could have easily been avoided.

“PLBs and EPIRBs are a really effective tool in an emergency, but even more so if they are registered, so help us to help you, and register today.”

Popular posts from this blog

Dad recalls moment he 'could have lost one or more' of his kids when paddleboarding trip went wrong

Fisherman survives overboard ordeal with personal locator beacon lighting the way for the coastguard rescue

Hunterston Terminal incident update