Top Qs
Timeline
Chat
Perspective
2024–25 Australian region cyclone season
Cyclone season in Australia From Wikipedia, the free encyclopedia
Remove ads
The 2024–25 Australian region cyclone season was the most active, and first above-average season in the Australian region since 2005–06. This season also had the highest amount of severe tropical cyclones since 2005-06, as well as being the first non-below average season since 2018–19. The season recorded an average amount of tropical cyclones, an above average amount of tropical lows. It was also the third consecutive season with at least five severe tropical cyclones. The season officially started on 1 November 2024 and ended on 30 April 2025, however, a tropical cyclone could form at any time between 1 July 2024 and 30 June 2025 and would count towards the season total. During the season, tropical cyclones are officially monitored by one of the three tropical cyclone warning centres (TCWCs) for the region which are operated by the Australian Bureau of Meteorology, National Weather Service of Papua New Guinea and the Indonesian Agency for Meteorology, Climatology and Geophysics. The United States Joint Typhoon Warning Center (JTWC) and other national meteorological services including Météo-France and the Fiji Meteorological Service will also monitor the basin during the season.
Remove ads
Season forecasts
Summarize
Perspective
Ahead of the season officially starting on 1 November, the Australian Bureau of Meteorology (BoM) and New Zealand's National Institute of Water and Atmospheric Research (NIWA) both issued a tropical cyclone outlook that discussed the upcoming season.[2][3] These outlooks took into account a variety of factors such as a developing weak to moderate La Niña event and what had happened in previous seasons such as 1983–84, 1995–96, 2005–06 and 2017–18.[2][3] The Southwest Pacific tropical cyclone outlook issued by New Zealand's National Institute of Water and Atmospheric Research (NIWA) in conjunction with MetService, the BoM and various other Pacific meteorological services, predicted that six to ten tropical cyclones would occur over the South Pacific Ocean between 135°E and 120°W.[3] The outlook also predicted that three to four of these tropical cyclones would intensify further and become either a Category three, four or five severe tropical cyclone on the Australian tropical cyclone intensity scale.[3] In addition to contributing towards the Southwest Pacific tropical cyclone outlook, the BoM predicted that tropical cyclone activity within the whole region between 90°E – 160°E and each of its self-defined subregions would be near normal.[2] They also warned that the likelihood of a severe tropical cyclone was higher than average because of the warmer than average ocean temperatures that had been forecast for the region.[2]
Remove ads
Season summary
Summarize
Perspective
Early season activity
The season officially started on 1 November, 2024. On 14 November, the Bureau of Meteorology (BoM) noted that a tropical low may form west of Sumatra.[4] A westerly wind shear enhanced the disturbance's development. Despite moderate to high wind shear displacing deep convection, the tropical low further developed and the Joint Typhoon Warning Center (JTWC) issued a tropical cyclone formation alert. [5] On 28 November, the BoM named Tropical Cyclone Robyn.[6] The storm officially peaked as a high-end tropical storm before increasing wind shear caused the storm to dissipate. On 4 December, Tropical Low 04U formed off the coast of Java and headed west before dissipating on 11 December. Unfortunately, the disturbance caused landslides and floods, killing eleven people and leaving seven missing.[7][8] The rest of December had Tropical Lows 02U, 06U, 07U, and 08U. Tropical Low 07U formed southeast of the Cocos Islands and JTWC designated it as a tropical storm. 08U later became Category 3 Cyclone Dikeledi in the Southwest Indian Ocean.
Peak season activity
The first half of January had Tropical Cyclone 09U and Tropical Low 10U.[9] The latter half had Sean, 13U, Taliah, and Vince. On 17 January, the BoM designated Tropical Low 11U, which absorbed 10U, and later named Sean on 19 January. A day later, the storm rapidly intensified to a Category 4 major cyclone on the Australian cyclone scale, possessing a distinct eye and intense winds. Sean dissipated a couple days later.[10] The cyclone caused heavy rainfall and gale-force winds across portions of Western Australia. A record amount of rain fell in Karratha, with 274.4 mm recorded within 24 hours on 20 January.[11] Tropical Low 13U briefly tracked along the coast of Queensland and flooding killed a 63 year old woman.[12] On 31 January, the BoM designated Tropical Lows 14U and 15U, which were later named Taliah and Vince. After dealing with moderate wind shear, on 3 February, Taliah peaked as a Category 3 severe tropical cyclone on the Australian cyclone scale and Category 2 on the SSHWS scale. Taliah exited the basin on 12 February.[13] Vince was named on 2 February and also intensified to a Category 3 on the Australian cyclone scale before exiting BoM area of responsibility on 4 February.[14] February started with Tropical Lows 16U and 19U, though both disturbances exited the basin and entered the Fiji Meteorological Service area of responsibility. Meanwhile, the BoM designated Tropical Low 18U on 7 February, which was named Zelia on 11 February. Two days later, Zelia underwent rapid intensification due to warm sea surface temperatures and relatively low wind shear. At 00:00 UTC 13 February, Zelia intensified to a Category 4 severe tropical cyclone and later to Category 5 intensity.[15] Afterward, the cyclone stalled and underwent an eyewall replacement cycle (EWRC), which ended its rapid intensification phase.[16] Radar imagery showed an EWRC, which was later completed before landfall near De Grey, northeast of Port Hedland.[17] On 18 February, the Bureau of Meteorology designated Tropical Low 21U in the eastern side of the Indian Ocean. BOM later named the system Tropical Cyclone Bianca. On 20 February, a tropical low was spotted by the Bureau of Meteorology in the Coral Sea. The disturbance, initially designated by the agency as 22U, was noted to likely develop into a tropical cyclone over the next several days. Two days later, BOM upgraded the system to a category 1, with the name Alfred being assigned to it. On 25 February, Bianca peaked as a Category 4 severe tropical cyclone on the Australian cyclone scale and Category 3 on the SSHWS scale. Afterward, increasing wind shear and cooler sea surface temperatures caused the storm to rapidly weaken, dissipating on 27 February.[18] Over the next couple of days, Alfred continued to gradually move to the east, and was upgraded to a Category 2 tropical cyclone in the Australian scale at 16:00 AEST on 24 February. As Alfred turned south, it intensified to Category 3 status on 26 February at 22:00 AEST. The next day, the BOM further upgraded Alfred to a Category 4 cyclone, with a small eye appearing on visible satellite imagery. Later that night, an eyewall replacement cycle (ERC) occurred, prompting Alfred to fluctuate between Categories 3 and 4 on 1 March, before further weakening down to a Category 1 the following day. The cyclone then restrengthened slightly to Category 2 status by 3 March, before being downgraded to Category 1 intensity on 8 March. Alfred made landfall at Moreton Island on 01:00 AEST March 8 as a Category 1 tropical cyclone, and was downgraded to a tropical low five hours later.[19]
Late season activity
Tropical Low 23U formed on 4 March before exiting the basin on 8 March. The system later intensified into Tropical Storm Ivone in the South-West Indian Ocean. Tropical Cyclone 25U formed on 17 March before dissipating on 21 March.[1] Tropical Low 27U formed on 22 March and strengthened into Tropical Cyclone Courtney three days later. Afterward, Courtney intensified to a Category 5 cyclone on the Australian cyclone scale before entering the South-West Indian Ocean on 29 March.[20] Tropical Cyclone Dianne formed near North Australia on 28 March and made landfall near Derby on 29 March.[21] On 8 April, Tropical Low 29U formed in the Arafura Sea. Three days later, JTWC designated Tropical Cyclone 29S. Later on 15 April, 29S was designated as Errol by BoM. Shortly after the designation, the cyclone explosively intensified to a powerful Category 5 severe tropical cyclone cyclone.[22] Tropical Low 30U formed in the Arafura Sea on 16 April.[1] On 18 April, JTWC designated 30U as 31P. It was expected to strengthen, but wind shear soon caused it to dissipate on 23 April.
Off-season
On 9 May 2025, Tropical Low 33U formed near Papua New Guinea. During 11 May, this system was upgraded to a tropical storm by the JTWC and designated 32P. 33U dissipated the next day.[1] On 14 May, Tropical Low 34U formed near the Solomon Islands. It meandered around the southern Solomon Sea but dissipated the next day.
Remove ads
Systems
Summarize
Perspective
Tropical Cyclone Robyn
On 14 November, the Bureau of Meteorology (BoM) noted that a tropical low could form west of Sumatra, Indonesia.[4] Several days later, they noted that the tropical low was developing.[23] Further consolidation due to a westerly wind burst, which also spawned a twin cyclone, prompted the Joint Typhoon Warning Center (JTWC) to first track it on 23 November.[5] Despite deep convection being displaced due to moderate to high wind shear, the system's circulation became increasingly defined, prompting the JTWC to issue a tropical cyclone formation alert (TCFA) on the disturbance.[24] The JTWC then upgraded the system into a tropical storm, designating it as 03S.[25] By 28 November, the BoM reported that it intensified into a tropical cyclone, being named Robyn, before reaching peak intensity late in the same day, with winds of 55 knots (102 km/h; 63 mph). However, strong wind shear and dry air made the system to rapidly weaken, becoming a gale-force tropical low by 29 November.[6]
Tropical Low 04U
Tropical Low 04U formed to the north of the Cocos (Keeling) Islands on 7 December.[26] After heading westward for most of its lifetime, it dissipated on 11 December. The storm caused floods and landslides in Sukabumi Regency, West Java, killing eight people and leaving seven others missing, with one home destroyed and 39 others damaged in the regency.[7] Flooding also killed three people in Lebak Regency, Banten.[8]
Tropical Low 02U
On 9 December, the BoM reported that Tropical Low 02U formed to the north of the Pilbara coast.[26] It dissipated on 12 December.
Tropical Low 06U
At 9 a.m. on December 21, a low pressure system formed in the Coral Sea, and the Joint Typhoon Warning Center labeled the disturbance 96P. At 8 p.m. on December 21, the Australian Bureau of Meteorology upgraded it to a tropical depression and labeled it 06U. 06U dissipated on 23 December.
Tropical Low 07U
Late on 23 December, the JTWC began to monitor an area of convection approximately 99 nautical miles (183 km) southeast of the Cocos (Keeling) Islands. At the time, it had a weakly-defined centre, and was within an environment of warm sea surface temperatures, low vertical wind shear, and good dual-channel divergence aloft.[27] The BoM subsequently started to monitor it, designating it as 07U.[1] Over the next few days, the tropical low began to organize as it moved westwards, with persistent convection over its consolidating centre as shear began to increase.[28] As a result, the JTWC issued a TCFA on 07U by 26 December.[29] Late on the same day, the BoM began to issue advisories on 07U, as gale-force winds developed to the west of the system, but did not meet their naming criteria.[30] Nonetheless, the JTWC upgraded the system to a tropical storm early on 27 December, designating it as 05S.[31] Moving east-southeast, the system began to weaken, as increasing wind shear led to its centre becoming exposed, separating from its deep convection.[32][33] By the next day, deep convection was redeveloping in its ill-defined centre,[34] before becoming fully exposed once again, prompting the JTWC to issue its final advisory six hours later.[35] The BoM, however, continued to track 07U as it moved southward,[36] before issuing their final advisory early on 29 December.[37] The tropical low was last noted at 31 December, when it moved outside the Australian area of responsibility.[1]
Tropical Low 08U (Dikeledi)
Dikeledi formed south of Java, Indonesia as a tropical low on 30 December 2024, traversing the southern Indian Ocean before entering the South-West Indian Ocean basin on 4 January.[citation needed]
Tropical Cyclone 09U
On 8 January, the BoM reported that Tropical Low 09U had formed to the south of Christmas Island, within an environment of warm sea surface temperatures and moderate easterly shear.[9] As it moved southwestward, it began to organize as wind shear decreased, with persistent convection to the south of its centre.[38] By 10 January, an ASCAT pass showed the low had developed gale-force winds extending halfway to its centre, prompting the BoM to upgrade 09U to a category 1 tropical cyclone; operationally, it was not named, with gale-force winds estimated only at its southwest quadrant.[9][39] At the same time, the JTWC issued a TCFA on the system, noting deep convection building over its centre.[40] However, increasing northwesterly shear and a dry air intrusion caused the system to rapidly weaken below tropical cyclone status,[9][41] leading to the BoM issuing its final advisory and the JTWC cancelling its TCFA late on the same day.[42][43] The remnants of the system continued westwards, being last noted on 13 January.[9]
Tropical Low 10U
Tropical Low 10U formed on 13 January, and whilst initially forecasted by many forecast models to become a Severe Tropical Cyclone, it never intensified, and was instead absorbed by the tropical low which would become Severe Tropical Cyclone Sean on 17 January near the Western Australian coast.
Severe Tropical Cyclone Sean
On 16 January, the JTWC began to monitor an area of convection that had formed to the west of the Kimberley coast, aided by an equatorial Rossby wave passing to the north of Australia.[10][44] At the time, it had a partially exposed centre, with deep convection wrapping to the south of the system.[44] As it moved generally southwestward, its centre began to consolidate within an environment of record warm sea surface temperatures, low vertical wind shear, and moderate poleward outflow aloft,[10][45] prompting the JTWC to issue a TCFA late on the next day,[46] before designating the system as Tropical Cyclone 10S by 18 January, noting its rapid development as it merged with Tropical Low 10U.[47] The BoM followed suit soon after, designating the low as 11U.[48] Continuing to organize, gale-force winds soon extended halfway to its centre, prompting the BoM to upgrade 11U to a category 1 tropical cyclone early on the next day, naming it Sean.[10][49]
Sean then began to rapidly intensify, as it developed a 15 nmi (28 km) pinhole eye, becoming a category 3 severe tropical cyclone in the Australian scale and a category 1-equivalent tropical cyclone on the Saffir-Simpson scale respectively by 12:00 UTC that same day.[10][50] By 20 January, the BoM upgraded Sean to a category 4 severe tropical cyclone,[51] with the JTWC following suit and upgrading Sean into a category 3-equivalent tropical cyclone.[52] Sean then reached peak intensity at 12:00 UTC that same day.[53][54]
Moving into cooler sea surface temperatures, Sean immediately began to weaken, with the BoM downgrading the system to a category 3 severe tropical cyclone.[55] The JTWC followed suit and downgraded Sean to a category 2-equivalent tropical cyclone by 21 January, as a dry air entrainment eroded the system's convection.[56] Six hours later, it further weakened into a category 1-equivalent tropical cyclone.[57] By 12:00 UTC that same day, the BoM had downgraded Sean to a category 2 tropical cyclone, as it continued to weaken.[58] The JTWC soon followed suit, downgrading Sean to a tropical storm.[59] The system then further weakened into a category 1 tropical cyclone by 22 January,[60] before the BoM stopped advisories six hours later, as Sean became a cold-core low.[10][61] The JTWC continued to track Sean, as it further weakened within an environment of high vertical wind shear, low sea surface temperatures and dry air.[62] By the next day, the JTWC stopped monitoring Sean, as its centre became further elongated.[63]
Cyclone Sean caused a record amount of rain to fall in Karratha, with 274.4 mm recorded in the 24 hours until 9:00 AM local time on January 20.[11] Roads and homes were inundated, power grids were damaged, and ports were closed.[64]
Tropical Low 13U
Tropical Low 13U formed on 28 January, tracked along the coast of Queensland, before dissipating on 1 February.[65] It caused major flooding in Northern Queensland which killed a 63 year old woman.[12] Cardwell Range recorded weekly rainfall totals of 1,697 millimetres (66.8 in), with 626 millimetres (24.6 in) in a day.[66]
Severe Tropical Cyclone Taliah
A strong Madden-Julian Oscillation (MJO) pulse, combined with the eastward-moving equatorial Rossby wave that spawned Severe Tropical Cyclone Sean, spawned a weak tropical low within a monsoon trough approximately 350 nautical miles (650 km) north-northwest of Broome on 31 January.[13][67] As it moved westward within an environment of warm sea surface temperatures, low to moderate vertical wind shear, and moderate dual channel outflow aloft, the low quickly organized, with its centre becoming embedded within deep convection,[68] prompting the JTWC to issue a TCFA by the next day.[69] On 2 February, the system intensified into a category 1 tropical cyclone, with the BoM giving the name Taliah.[13] The JTWC subsequently followed suit and upgraded Taliah to a tropical storm.[70]
12 hours later, Taliah intensified into a category 2 tropical cyclone,[71] with the JTWC upgrading the system to a Category 1-equivalent tropical cyclone late on the same day, as it formed a banding eye.[72] Taliah's intensification then stalled as wind shear increased,[13][73] before deep curved banding improved rapidly around the system, becoming a category 3 severe tropical cyclone at 12:00 UTC on 3 February.[13] By the next day, Taliah reached its peak intensity, with the JTWC upgrading Taliah to a category 2-equivalent tropical cyclone.[13][74]
Following its peak intensity, increasing wind shear and a dry air entrainment into the core of Taliah led to its weakening,[13] prompting the JTWC to downgrade Taliah to a category 1-equivalent tropical cyclone late on the same day.[75] By early 5 February, Taliah had weakened to a category 2 tropical cyclone.[13] Throughout the day, the system struggled, with its centre becoming partially exposed due to the high easterly wind shear.[76] As a result, the JTWC downgraded Taliah to a tropical storm late on the same day, as its centre became elongated.[77] Taliah then further weakened to a category 1 tropical cyclone at 06:00 UTC on 6 February, before becoming a tropical low by the next day, although gale-force winds persisted but not halfway through the system.[13]
Over the next few days, wind shear slowly decreased as Taliah continued westward,[78] and by 10 February, Taliah had re-intensified into a category 1 tropical cyclone, with tighter spiral bands of convection evident near the system's centre.[79][80] The system then further intensified into a category 2 tropical cyclone by the next day, based on synthetic-aperture radar.[13][81] As a large, ragged eye soon formed, the JTWC upgraded Taliah to a category 1-equivalent tropical cyclone once again on 12 February,[82] before it exited the Australian area of responsibility by 12:00 UTC that same day.[13][83]
Severe Tropical Cyclone Vince
On 31 January, both the BoM and JTWC reported that Tropical Low 15U had formed, aided by the MJO that also spawned Severe Tropical Cyclone Taliah, approximately 243 nautical miles (450 km) to the south-southeast of Christmas Island.[14][84] Within an environment of warm sea surface temperatures, low to moderate vertical wind shear, and good poleward aloft, the system gradually organized, with deep convection forming near its centre, prompting the JTWC to issue a TCFA on 1 February.[85] Late on the same day, the JTWC upgraded the system to a tropical storm, with an ASCAT pass indicating it had developed gale-force winds.[86] The BoM would not follow suit until 12:00 UTC the next day, as gale-force winds extended more than halfway of its centre, becoming a category 1 tropical cyclone; however, it would not be named Vince until 3 February, when it already intensified into a category 2 tropical cyclone.[14][87]
After it got named, Vince began to rapidly intensify, becoming a category 3 severe tropical cyclone by 12:00 UTC that same day,[14] before it formed a pinhole eye by 4 February, prompting the JTWC to upgrade the system to a category 3-equivalent tropical cyclone.[88] It then subsequently exited the Australian area of responsibility that same day.[14][89]
Severe Tropical Cyclone Zelia
Tropical Low 18U formed on 8 February.[17] It began tracking west-southwest, and was upgraded to a Category 1 system, named Zelia on 11 February.[90] The storm then steadily intensified to become a Category 2 by the next morning.[91] That night, the storm slowed, and began rapid intensification,[17] to reach Category 4 status by 06:00 AWST on 13 February,[15] and Category 5 status by 12:00 AWST that day. The storm then stalled and began an eyewall replacement cycle as shown by radar imagery, causing the rapid intensification phase to end.[16] Increasing wind shear and the eyewall replacement cycle caused Zelia to peak with 10-minute sustained winds of 215 km/h (130 mph); a Category 5 on the Australian scale.[1] On 14 February, Severe Tropical Cyclone Zelia made landfall at around 12:30 AWST in the afternoon near the De Grey River mouth, northeast of Port Hedland at Category 4 intensity.[17] Zelia quickly weakened after landfall, and it dropped below tropical cyclone intensity later that day.[92]
Severe Tropical Cyclone Bianca
On 18 February, both the BoM and the JTWC reported that Tropical Low 21U had formed, associated with a trough, approximately 167 nautical miles (309 km) to the northwest of Darwin.[18][93] Over the next few days, the low struggled to organize due to moderate to strong easterly vertical wind shear disrupting its structure, with scatterometer passes showing an elongated system.[18] By 02:00 UTC on 23 February, the JTWC issued a TCFA on the system, as deep curved banding wrapped to the north of its consolidating centre.[94] The low soon intensified into a category 1 tropical cyclone, with the BoM naming it as Bianca,[18] and the JTWC designating it as 20S.[95]
On the next day, the BoM reported that Bianca had further intensified into a category 2 tropical cyclone,[96] with the JTWC upgrading the system to a category 1-equivalent tropical cyclone six hours later, as a cloud-filled ragged eye formed.[97] Soon after, Bianca became a category 3 severe tropical cyclone, as its ragged eye soon cleared.[98] The JTWC soon followed suit and upgraded Bianca to a category 2-equivalent tropical cyclone late on the same day.[99] By 25 February, Bianca reached its peak intensity, as it became a category 4 severe tropical cyclone,[18] with the JTWC estimating the system as a category 3-equivalent tropical cyclone.[100]
After its peak intensity, wind shear soon increased as Bianca moved into lowering sea surface temperatures combined with a dry air intrusion, leading to its weakening to a category 3 severe tropical cyclone.[101] The JTWC subsequently downgraded it to a category 2-equivalent tropical cyclone that same day, as the system increasingly became vertically misaligned.[102] At 00:00 UTC on the next day, the BoM reported that Bianca had weakened to a category 2 tropical cyclone,[103] with the JTWC following suit six hours later and downgrading the system to a tropical storm, as its centre became fully exposed.[104] Bianca then further weakened into a category 1 tropical cyclone,[105] before both the BoM and JTWC issued their final advisories on the system late on the same day, as it weakened below tropical cyclone intensity.[106][107] Bianca then fully dissipated by 27 February, as it was absorbed into a broader southeasterly front.[18]
Severe Tropical Cyclone Alfred
On 20 February, the BoM began to monitor Tropical Low 22U in the Coral Sea, and was noted to likely develop into a tropical cyclone over the next several days.[108] Two days later, the JTWC upgraded the system to a tropical storm.[109] Initially, the BoM did not immediately follow suit and kept it as a tropical low;[110] however, at 06:00 UTC on 23 February, the BoM upgraded the system to a category 1, with the name Alfred being assigned to it.[111]
Over the next couple of days, the storm continued to gradually move to the east, and was upgraded to a category 2 tropical cyclone in the Australian scale at 06:00 UTC on 24 February.[112] As Alfred then turned south, it also continued to intensify, attaining category 3 status by 12:00 UTC on 26 February.[113] The next day, the BoM further upgraded Alfred to a category 4 cyclone as a small eye appeared on visible satellite imagery.[114] Later that night, its eye collapsed due to upwelling of cool water,[115] prompting Alfred to fluctuate between Categories 3 and 4 on 28 February,[116][117][118] before further weakening down to a Category 2 the following day.[119] The cyclone then weakened to a category 1 tropical cyclone by 2 March,[120] before restrengthening slightly to category 2 status late on the same day.[121] On 3rd of March, Alfred showed signs of transitioning into a subtropical storm. Despite this, the cyclone still retained its status of tropical storm.[122] Alfred then weakened to a Category 1 on 7 March.[123] The cyclone then subsequently made landfall at Moreton Island,[124] and was downgraded to a tropical low at 20:00 UTC that same day.[125]
Beginning on 3 March, watches and warnings were issued in South East Queensland (SEQ) – including Brisbane – as Alfred posed a notable risk to the area, with all major forecast models having predicted an SEQ landfall between 6 and 8 March. A Cyclone Watch was issued between Sandy Cape, and Grafton, including Brisbane – the first for the city since a watch was briefly issued for Cyclone Oma in 2019.[126][127] The northeastern part of New South Wales (NSW) is also expected to be under a cyclone warning in preparation for the storm.[128][129] Alfred caused an estimated US$1.18-billion economic loss.[130]
Tropical Low 23U (Ivone)
On 5 March, both the BoM and TCWC Jakarta reported that Tropical Low 23U had formed, approximately 750 kilometres (470 mi) to the northwest of the Cocos (Keeling) Islands.[131][132] The disturbance later exited the basin and entered the South-West Indian Ocean basin late on 6 March,[133] where it was named Ivone by Météo-France on 8 March.[134]
Tropical Cyclone 25U
On 16 March, the BoM reported that Tropical Low 25U was forming in the Indian Ocean, between the Cocos (Keeling) Islands and Christmas Island.[135] Over the next few days, the low steadily organized as it moved westward within an environment of warm sea surface temperatures, low vertical wind shear, and good poleward outflow aloft,[136] prompting the JTWC to issue a TCFA by 18:00 UTC on 18 March.[137] Three hours later, the JTWC upgraded the low to a tropical storm, designating it as 26S.[138] The BoM did not follow suit however, as gales were only extending halfway of the system;[139] upon reanalysis, 25U briefly became a category 1 tropical cyclone on the next day.[1][140] 25U then struggled as easterly wind shear caused by a mid-to-upper level ridge soon increased,[141] with its centre becoming exposed and its convection being displaced to the west by 20 March.[142] As a result, both the BoM and JTWC issued their final advisories on 25U late on the same day.[143][144]
Severe Tropical Cyclone Courtney
During the second half of March, an active phase of the MJO affected Western Australian longitudes.[20] Combined with a monsoon trough extending from the eastern Indian Ocean across northern Australia,[145] it led to the BoM noting that a tropical low could form to the northwest of the Pilbara region in the next 7 days on 16 March, pre-designating it as 27U.[146] This came into fruition six days later, when both the BoM and JTWC reported that the low had formed approximately 530 nautical miles (980 km) to the north of Learmonth.[20][147] Within an environment of warm sea surface temperatures, low to moderate vertical wind shear, and moderate poleward outflow, the low gradually organized,[148] prompting the JTWC to issue a TCFA late on 23 March.[149] By the next day, the JTWC upgraded 27U into a tropical storm, although convection was sheared to the west of the system's centre.[150] The BoM did not follow suit, however, as gales were only confined in the southwest quadrant.[151] Late on 25 March, the BoM reported that it had intensified into a category 1 tropical cyclone, earning the name Courtney.[152]
By the next day, Courtney intensified into a category 2 tropical cyclone as wind shear decreased,[153] before both the BoM and JTWC reported that Courtney had further intensified into a category 3 severe tropical cyclone and a category 1-equivalent tropical cyclone, respectively, late on the same day.[154][155] Courtney's intensification then slowed by 27 March,[156] before the JTWC reported that Courtney had became a category 2-equivalent tropical cyclone late on the same day.[157] By the next day, Courtney began rapidly intensifying, as it formed a pinhole eye, prompting the JTWC to upgrade the system to a category 3-equivalent tropical cyclone,[158] before further intensifying to a category 4 severe tropical cyclone late on the same day.[20][159] It then reached its peak intensity as a category 5 severe tropical cyclone at 12:00 UTC on 29 March, before subsequently exiting the Australian area of responsibility.[20][160]
Tropical Cyclone Dianne
On 25 March, the BoM began to note that a tropical low, pre-designated as 28U, could form off the northwest coast of the Kimberley region, associated with the active MJO and within the monsoon trough that also spawned Severe Tropical Cyclone Courtney.[21][161] Aided by the passage of an equatorial Rossby wave, the tropical low then formed late on 26 March,[21] with the JTWC issuing a TCFA on the low by 05:00 UTC on the next day, as very intense deep convection was being sheared to the west of the system's centre.[162] Within an environment of warm sea surface temperatures and low vertical wind shear, the convection gradually wrapped into the system's centre, becoming Tropical Cyclone Dianne by 28 March.[163][21] Turning south, Dianne quickly strengthened into a category 2 tropical cyclone, before making landfall near Koolan Island late on the same day at the same intensity.[21] As a result, the JTWC issued their final advisory on the system.[164] Dianne subsequently weakened into a tropical low by the next day, before completely dissipating by 30 March.[21]
130 mm of rain fell in Derby, causing street flooding. However, there were no reports of significant damage.[165]
Severe Tropical Cyclone Errol
.jpg)
Errol formed on 9 April as Tropical Low 29U,[22] and intensified into a category 1 tropical cyclone on 15 April.[166] Starting late on 15 April, Errol began a period of explosive deepening; 1-minute sustained winds increased from 100 km/h (65 mph) to 260 km/h (160 mph) in 24 hours and 120 km/h (75 mph) to 220 km/h (140 mph) in 12 hours, and the JTWC described it as 'explosive and extreme rapid intensification'.[167] On 16 April, it reached its peak intensity as a Category 5 equivalent tropical cyclone, with 1-minute sustained winds of 260 km/h (160 mph), according to JTWC, while the BOM estimated 10-minute sustained winds of 205 km/h (125 mph) which made it a Category 5 severe tropical cyclone.[167][1] On 17 April, as Errol took a sharp turn east-southeast, wind shear soon increased, causing Errol to weaken.[168] It made landfall south of Kuri Bay on 18 April as a tropical low. After landfall, the BoM ceased advisories on the system as it fell below warning criteria.[169]
Errol was a small tropical cyclone that brought heavy rain to the Northern Kimberley coast including Derby and Kalumburu on 18 and 19 April.[170] Kalumburu received 160.8 millimetres (6.33 in) of rainfall in 24 hours. Errol is the latest tropical cyclone to form or move into the Australian region since Cyclone Karim which formed on 7 May 2022.[171]
Tropical Low 30U
On 11 April, the BoM began to note that a tropical low may form between the Arafura Sea and the Gulf of Carpentaria, and pre-designated it as 30U.[172] This came into fruition five days later, when both the BoM and the JTWC reported that the low had formed approximately 337 nautical miles (624 km) to the northeast of Darwin.[173][174] Within an increasingly favorable environment of warm sea surface temperatures, lowering vertical wind shear and increasing poleward outflow, its centre began to consolidate,[175][176] prompting the JTWC to issue a TCFA late on 17 April,[177] before upgrading the system to a tropical storm on the next day.[178] The BoM did not follow suit, however, as gales were only extending halfway of the system.[1] 30U then weakened to a tropical depression late on the same day, as its centre became partially exposed due to increasing wind shear and a dry air intrusion.[179] Moving westward, the system remained weak,[180] before the JTWC briefly upgraded 30U to a tropical storm once again on 21 March.[181] It subsequently weakened to a tropical depression once again, as its centre became fully exposed.[182] The JTWC then issued their final advisory on 30U by the next day, as the system further deteriorated.[183] The BoM subsequently followed suit and stopped monitoring the system late on the same day.[184]
Tropical Low 33U
On 8 May, the JTWC reported that an area of convection had formed approximately 228 nautical miles (422 km) to the north of Weipa. At the time, it had a broad but organizing centre, and was within a marginal environment of warm sea surface temperatures, low vertical wind shear, and good poleward outflow offset by its proximity near land.[185] By the next day, the BoM designated the low as 33U.[1] The system then slowly organized as it moved southwestward,[186] with the JTWC issuing a TCFA late on 10 March.[187] By the next day, the JTWC upgraded 33U into a tropical storm;[188] however, the BoM did not follow suit, as gale-force winds did not extend halfway through the system.[1][189] The system then began to weaken, as its centre became tilted, along with a dry air intrusion.[190] As a result, the JTWC issued their final advisory on 33U by 12 May,[191] with the BoM subsequently following suit six hours later.[192]
Other systems
- Tropical Low 16U formed on February 2,as a low pressure system in the northwest of Vanuatu, and the Joint Typhoon Warning Center (JTWC) assigned it a disturbance number of 92P. At 8 pm, the Australian Bureau of Meteorology upgraded it to a tropical depression and assigned it the number 16U. The system exited the basin on 4 February, while strengthening.[66]
- On February 6, a low pressure system formed along the coast of Queensland, with the Joint Typhoon Warning Center numbering it 95P. At 9 a.m. on February 7, the Australian Bureau of Meteorology upgraded it to a tropical depression and numbered it 19U. The low strengthened and exited the basin on 11 February.
- Tropical Low 20U formed on 10 February along a monsoon trough in the Gulf of Carpentaria, bringing heavy rainfalls to parts of the Cape York Peninsula before dissipating on 13 February.[193]
- On May 9, a disturbance formed near the Solomon Islands, and the Joint Typhoon Warning Center designated it 94P. At 10 a.m. on May 11, the Australian Bureau of Meteorology upgraded it to a tropical depression and designated it 34U. At 4 p.m. on May 14, the Australian Bureau of Meteorology stopped tracking the disturbance because it had dissipated.[194]
Remove ads
Storm names
Summarize
Perspective
Bureau of Meteorology
The Australian Bureau of Meteorology (TCWC Melbourne) monitors all tropical cyclones that form within the Australian region, including any within the areas of responsibility of TCWC Jakarta or TCWC Port Moresby.[195] Should a tropical low reach tropical cyclone strength within the BoM's area of responsibility, it will be assigned the next name from the following naming list. The names that will be used for the 2024–25 season are listed below:
Originally, the name Anthony was scheduled to be used, but was switched with Alfred from the next list of names in February 2025 to avoid confusion with Anthony Albanese, the Prime Minister of Australia at the time.[196]
TCWC Jakarta
TCWC Jakarta monitors Tropical Cyclones from the Equator to 10°S and from 90°E to 145°E. Should a Tropical Depression reach Tropical Cyclone strength within TCWC Jakarta's Area of Responsibility then it will be assigned the next name from the following list.[195]
|
|
|
TCWC Port Moresby
Tropical cyclones that develop north of 10°S between 151°E and 160°E are assigned names by the Tropical Cyclone Warning Centre in Port Moresby, Papua New Guinea. Tropical cyclone formation in this area is extremely rare, with no cyclones being named in it since 2007.[197] As names are assigned in a random order, the whole list is shown below:
|
|
Remove ads
Season effects
Summarize
Perspective
This table lists all of the tropical cyclones and subtropical cyclones that were monitored during the 2024–2025 Australian region cyclone season. Information on their intensity, duration, name, areas affected, primarily comes from the BoM. Death and damage reports come from either press reports or the relevant national disaster management agency while the damage totals are given in 2024 or 2025 USD.
Remove ads
See also
- Weather of 2024 and 2025
- List of Southern Hemisphere cyclone seasons
- Tropical cyclones in 2024, 2025
- Atlantic hurricane seasons: 2024, 2025
- Pacific hurricane seasons: 2024, 2025
- Pacific typhoon seasons: 2024, 2025
- North Indian Ocean cyclone seasons: 2024, 2025
- 2024–25 South-West Indian Ocean cyclone season
- 2024–25 South Pacific cyclone season
References
External links
Wikiwand - on
Seamless Wikipedia browsing. On steroids.
Remove ads