Because of our name and the work that we do, we have many people who share with us videos of members of the public disentangling whales and other marine life including the recent video of a young man jumping into the water to free an entangled humpback whale. These videos have all of the elements of an amazing story- danger, bravery, and hopefully success. Yet, we rarely share these videos, and for good reason. While the stories are compelling, the unintended consequences of these actions can be devastating.
While we don’t doubt the good intention to do right thing and save the whales, a lot more is at stake than the life of the one whale who inspires someone to take action. Accidental entanglement in fishing gear is a worldwide issue and is the leading cause of death for many different species of whales and dolphins. It also affects sea turtles, seals, and many other species of marine life. In fact, we even saw an entangled shark this summer.
As someone who works to protect these animals at Whale and Dolphin Conservation and as someone who has experienced the heart-breaking discovery of a whale entangled in fishing gear, I am conflicted when I see videos of people who have not been trained in disentanglement taking on this dangerous role. I’m obviously happy when the stories have a happy ending: a freed whale, an uninjured rescuer, and a raised profile about a threat to whales. Yet, at the same time, I can’t help but experience an immense amount of anxiety as I fear these actions will encourage others to literally “jump in” to help a whale. Whether they are motivated by a passion for whales, the exhilaration of the risk, or the hope to become the next internet sensation, there are so many problems with ad hoc entanglements.
As the name implies, ad hoc entanglements happen without a plan…. and without training or authorization from the federal government. The common thread between permitted and ad hoc entanglements is compassion for a suffering whale and the hope for a good outcome. The differences, however, can be life and death for the whale and the would-be rescuers. There are definitely heroes in the disentanglement world and they rarely get attention or are featured in viral videos, but their work is life-saving.
I would like to introduce you to my whale-saving heroes, the trained members of the federally authorized disentanglement teams.
These individuals make incredible sacrifices to do what they do. They dedicate their lives and careers to saving these whales from life-threatening entanglements. Only after intensive trainings and apprenticeships, which sometimes can take years to complete, do they take on the challenge to risk their lives to save whales. When I think of their day-to-day lives, I’m still amazed that they can stay positive. Without hazard or on-call pay, they are available 24/7 to respond to entangled animals. The ping of a text or chime of a call brings on the dreadful adrenal rush which may be their only nourishment for the next 12 to 24 hours as they pack their sharp tool kit and head out to sea in search of a scared and wounded wild whale who does not know they are there to help.
To do this once is amazing in itself. To do this day after day makes them superheroes.
Dedication and passion may drive them, but their training and pre-planned rescue attempts are what keep them alive. Disentangling a whale can be life-threatening to both the rescuer and the whale. While we have all heard the feel-good stories about whales helping in their rescue, or thanking their rescuers for freeing them, the reality is not a fairy tale. After a short conversation with any disentanglement team member, you will politely receive a reality check. The whales are in pain, scared, and evade rescue efforts. They react defensively, and sometimes respond with a flick of a tail or flipper which is instantly lethal to anyone on the receiving end. Each approach can further agitate an already anxious whale, further decreasing the odds of success.
Unlike what is seen in the feel-good videos are the tragic realities of disentanglement attemps. A distressed and entangled whale led to the death of a New Zealand diver in 2003, who attempted an in-water disentanglement. Even boat-based disentanglements can be life threatening. Just last year, Joe Howlett, a seasoned and trained rescuer, was tragically killed during a right whale disentanglement when the whale’s tail rose above the water’s surface and came down on the front of the boat where he was stationed. Even with experience and training, the risk to the would-be rescuers is all too real.
As is the risk to the whales themselves. Unfortunately, even the best intentions can threaten more whales than just the one in front of you. Both the Canadian and US governments temporarily suspended all authorizations to disentangle whales when Mr. Howlett was killed last year. While the US government phased in authorizations within weeks, it took months for Canada to allow disentanglements to once again take place. Whales, however, continued to get entangled during the suspension when trained rescuers were not able to respond. If a member of the public is killed, the suspensions may be permanent, leaving countless whales to die.
Even for those whales who appear to be saved, the happy ending may end with the story, as the reality may be very different. If you ask those familiar with disentangling whales they will tell you that entanglements are typically complicated wraps of rope through the whale’s mouth or around a submerged flipper, none of which is easily visible from the surface. It is a rare case to have only a single rope going across the back of a whale requiring only a single cut to shed the gear. Without the right tools, equipment, and experience, the random single cut of a line could further constrict another wrap, hastening the whale’s suffering as the remaining line cuts into the flesh, and eventually sawing through the bone of the whale hailed as “saved”.
Would-be disentanglers should all be required to visit the exhibit of Spinnaker at the Center for Coastal Studies in Provincetown, MA. Spinnaker, a once beloved and vibrant humpback whale, was disentangled on three separate occasions – two of these entanglements were extremely complex and undoubtedly life-threatening. The team spent many hours with Spinnaker, trying to get her out of trouble, as they strategically made cuts through the rope that restricted her. Yet, only a short time after their last attempt to free her, she was found dead. The necropsy (animal autopsy) showed that the fishing gear from her earlier entanglement remained embedded in tissue and bone of the roof of her mouth, undoubtedly causing immense pain. She had never been freed from her entanglement. Spinnaker’s skeleton, complete with the piece of fishing gear which contributed to her death, hangs in display at the Center for Coastal Studies as a reminder of the agonizing deaths whales experience due to entanglements and that disentanglement is not a long term solution to this threat.
Solving entanglements requires a huge community of scientists, disentanglement teams, whale watchers, captains, fishermen, policy makers and AND members of the public. Each has their role but only trained and permitted members of disentanglement teams should take on the role of removing gear from whales. Working together to prevent entanglements will keep whales and rescuers safe and leave the viral videos to the kittens and puppies.
What You Can Do:
Call your regional disentanglement hotline or the USCG on VHF 16.
West Coast:1-877-SOS-WHALE (1-877-767-9425)
East Coast: 1-866-755-NOAA (6622)
Alaska: (877) 925-7773
Hawaii: (888) 256-9840
Stand by the whale if possible. If you can’t stand by, report the last location (lat/long) of the whale and his or her direction of travel.
Take photographs or video to document the whale and the gear on the whale. If you don’t have a camera, sketch a picture and note the location and color of the line and any buoys you see associated with the entanglement.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies. However you may visit Cookie Settings to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__RequestVerificationToken
session
This cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks.
_abck
1 year
This cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
_GRECAPTCHA
5 months 27 days
This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks.
AWSALBCORS
7 days
This cookie is managed by Amazon Web Services and is used for load balancing.
bm_sz
4 hours
This cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
CookieLawInfoConsent
1 year
Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie.
crumb
session
Squarespace sets this cookie to prevent cross-site request forgery (CSRF).
datadome
session
This is a security cookie set by Force24 to detect BOTS and malicious traffic.
JSESSIONID
session
The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
MS0
30 minutes
This cookie is set by Microsoft to identify a particular session.
MSFPC
1 year
This cookie is set by Microsoft to recognize unique web browsers that visit Microsoft sites. It is used for advertising, site analytics, and other operational purposes.
PHPSESSID
session
This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
viewed_cookie_policy
1 year
The cookie is set by the GDPR Cookie Consent plugin to store whether or not the user has consented to the use of cookies. It does not store any personal data.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
__Host-GAPS
2 years
This cookie allows the website to identify a user and provide enhanced functionality and personalisation.
_fbp
3 months
This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
ANONCHK
10 minutes
The ANONCHK cookie, set by Bing, is used to store a user's session ID and also verify the clicks from ads on the Bing search engine. The cookie helps in reporting and personalization as well.
fr
3 months
Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE
1 year 24 days
Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
muc_ads
1 year 1 month 4 days
Twitter set this cookie to collect visitor navigation data to optimise ad relevance.
MUID
1 year 24 days
Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations.
NID
6 months
NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.
personalization_id
1 year 1 month 4 days
Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting.
test_cookie
15 minutes
The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
ttwid
1 year
TikTok sets this cookie to keep track of how embedded services are being used.
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devices
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-id
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextId
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requests
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gat_UA-*
1 minute
Google Analytics sets this cookie for user behaviour tracking.
_gcl_au
3 months
Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid
1 day
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
_hjAbsoluteSessionInProgress
30 minutes
Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjFirstSeen
30 minutes
Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user.
_hjRecordingEnabled
never
Hotjar sets this cookie when a Recording starts and is read when the recording module is initialized, to see if the user is already in a recording in a particular session.
_hjRecordingLastActivity
never
Hotjar sets this cookie when a user recording starts and when data is sent through the WebSocket.
ai_session
30 minutes
This is a unique anonymous session identifier cookie set by Microsoft Application Insights software to gather statistical usage and telemetry data for apps built on the Azure cloud platform.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
CONSENT
2 years
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
MicrosoftApplicationsTelemetryDeviceId
1 year
Microsoft sets this cookie to install a unique device ID that is used to track how users behave and interact with the Microsoft application on the device.
MR
7 days
This cookie, set by Bing, is used to collect user information for analytics purposes.
SM
session
Microsoft Clarity cookie set this cookie for synchronizing the MUID across Microsoft domains.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
__cf_bm
30 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
S
1 hour
Used by Yahoo to provide ads, content or analytics.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Cookie
Duration
Description
AWSALB
7 days
AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.
SRM_B
1 year 24 days
Used by Microsoft Advertising as a unique ID for visitors.