Recreational abalone fishing dates set for WA summer
Summarised from 2 outlets · Updated 20 Nov, 18:13 · Archive
Licensed recreational fishers in Western Australia will have four opportunities to catch Roe's abalone this summer. The sessions are scheduled for 12 December, 9 January and 6 and 20 February between 7am and 8am, subject to weather and ocean conditions. All sessions will take place in the Western Zone between Busselton Jetty and the Greenough River mouth, south of Geraldton.
About 23 tonnes of Roe's abalone are available for recreational fishing this season, according to scientific assessments. Fishers must follow a bag limit of 15 abalone per session and a minimum size limit of 60mm. Fisheries Minister Jackie Jarvis said WA has one of the few remaining sustainable wild-stock abalone fisheries close to a major metropolitan area.
Safety officials are emphasising the dangers of abalone fishing. Surf Life Saving WA will provide hazardous surf forecast assessments ahead of each session and conduct safety patrols. The organisation received $417,000 from the State Government last year for abalone fishing safety services until 2028. Several lives have been lost while abalone fishing since 2012. If poor weather or dangerous seas lead to a session being cancelled, another may be added later in the season.

How it is being reported
- WA abalone fishing dates announced for summer seasonAbout 23 tonnes of Roe’s abalone are available for recreational fishing this season.Perth Now · 20 Nov, 18:00
- Western Zone abalone 2026-27 summer fishing dates announcedFour dates have been announced for licensed recreational fishers to catch Roe’s abalone along the WA coast this summer.The West Australian · 20 Nov, 02:37
In this story: Western Australia · Department of Primary Industries and Regional Development · Jackie Jarvis · Surf Life Saving WA · Busselton Jetty · Greenough River
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)