2021–22 Australian region cyclone season

Category 1 tropical cyclone (Australian scale)
Tropical storm (SSHWS)
Duration	17 November – 23 November
Peak intensity	75 km/h (45 mph) (10-min); 994 hPa (mbar)

During 17 November, the Australian Bureau of Meteorology (BoM) reported that Tropical Low 02U had developed along a trough of low pressure, just to the west of Christmas Island.[1] Over the next couple of days, the system remained slow-moving near the island before it started to move south-eastwards.[18] On 21 November of 04:00 UTC, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert (TCFA) for Invest 90S which the agency was tracking very recently, noting that the system was well-structured, with convection and near gale-force winds wrapping into its consolidated low-level circulation center (LLCC).[19] The BoM did not upgrade the system into a tropical cyclone at that time, as its centre was still somewhat elongated, and the near gale-force winds were only present at its southern quadrant. At 00:00 UTC of 22 November, the BoM upgraded the system to a Category 1 tropical cyclone on the Australian scale, and named it Paddy, becoming the first named cyclone in the season.[1] The JTWC followed suit later that day at 09:00 UTC.[20]

At this time, it started to incline more southwards under the influence of an upper trough moving to the east and a subtropical ridge to its south strengthening, with its pressure bottoming to 997 mbar (29.44 inHg). Paddy also reached its eventual peak intensity, with maximum 10-minute sustained winds of 40 kn (75 km/h; 45 mph), according to scatterometer passes.[1] Sea surface temperatures around 28 °C (82 °F), low wind shear and favorable upper-level divergence were the factors behind Paddy's intensification.[21] Paddy then reacted quickly to increasing northwesterly shear, as its convection began to decrease at 12:00 UTC that same day,[22] and by early next day, the BoM reported that Paddy had become an ex-tropical cyclone. As it turned to the south-southwest as the ridge to its south strengthened further, the synoptic gradient between the two increased, letting the storm reintensify slightly that same day, though gale-force winds were not wrapping halfway of the system. The winds would later rapidly decrease, and by 24 November, the BoM discontinued monitoring Paddy.[1] The JTWC subsequently followed suit and issued its final warning on the storm.[23]

Paddy remained far from major landmasses throughout its existence; however, it brought prolonged rainfall to Christmas Island. During a five-day period from 17 to 21 November, the island saw 251.2 mm (9.89 in) of rain.[1]

Tropical low (Australian scale)
Duration	22 November – 28 November
Peak intensity	Winds not specified; 1006 hPa (mbar)

On 22 November, a weak tropical low formed north of the Western Region, which was designated as 03U.[24] By 24 November, the tropical low had entered the region and was located 560 kilometres (350 mi) west-northwest of the Cocos Islands.[25] 03U meandered near the Cocos Islands, before moving westwards and exited the basin on 28 November.[26]

Category 1 tropical cyclone (Australian scale)
Tropical storm (SSHWS)
Duration	28 November – 11 December
Peak intensity	75 km/h (45 mph) (10-min); 996 hPa (mbar)

On 28 November, the BoM reported that a low formed within a monsoon trough to the southwest of Sumatra.[2] They designated it as 05U by the next day.[27] At 23:30 UTC on 30 November, the JTWC issued a TCFA for the system as the agencies found that the convection in associated with the system had increased.[28] By the next day, the BoM briefly upgraded it to a Category 1 tropical cyclone on the Australian scale, and named it Teratai which was given by TCWC Jakarta.[2][29] Later, the JTWC upgraded Teratai to a tropical storm, as it briefly attained sufficient convection.[30] But at 18:00 UTC, the BoM downgraded to a tropical low as deep convection had become limited, with the LLCC displaced towards the south. This was caused due to the lack of sufficient outflow caused by the northerly strait line flow which inhibited the system from further intensifying, despite favorable conditions.[2][31] The JTWC followed suit two hours later.[31] During the next few days, the BoM monitored ex-Teratai for redevelopment as the system executed a clockwise loop.[32] By 6 December, the JTWC issued a TCFA,[33] and the next day it re-upgraded the system to a tropical storm.[34] However, by 09:00 UTC of 9 December, JTWC issued its final warning.[35] The BoM continued to track the system until 11 December.[2]

Category 2 tropical cyclone (Australian scale)
Category 1 tropical cyclone (SSHWS)
Duration	9 December – 13 December (Exited basin)
Peak intensity	110 km/h (70 mph) (10-min); 980 hPa (mbar)

On 6 December, the BoM predicted that a tropical low could form near the Solomon Sea.[36] Two days later, the tropical low formed, and the BoM designated it as 07U.[37][3] The JTWC later issued a TCFA.[38] The system's deep convection became more organized overnight in 10 December, and began to strengthen, with gale-force winds being reported on 11 December.[3] Late on the same day, the JTWC upgraded the system into a tropical storm.[39] By the next day, it was upgraded to a Category 1 tropical cyclone on the Australian scale, and the BoM named it as Ruby. Twelve hours later, the BoM upgraded Ruby into a Category 2 cyclone,[3] with the JTWC following suit and upgraded the system into a category 1-equivalent tropical cyclone.[40] By 13 December, Ruby reached its peak intensity,[3] before subsequently crossing into the South Pacific basin.[41]

Tropical low (Australian scale)
Duration	13 December – 15 December
Peak intensity	Winds not specified; 1007 hPa (mbar)

On 7 December, the BoM noted on a possibility of a weak tropical low developing over the northern part of the Arafura Sea.[42] The BoM designated the system as 06U.[43] By 13 December, the BoM stated that 06U was already forming.[44] The system was last noted on 15 December.[45]

Category 2 tropical cyclone (Australian scale)
Tropical storm (SSHWS)
Duration	23 December – 1 January
Peak intensity	100 km/h (65 mph) (10-min); 982 hPa (mbar)

On 21 December, the BoM started to monitor a possible tropical low near the Arafura Sea.[46] Two days later, the BoM designated the low as 08U.[47] The JTWC started to monitor the system on 24 December.[48] By that same day, BoM began issuing advisories on the system, predicting a Category 1 intensity before landfall,[49] while the JTWC issued a TCFA at 21:00 UTC on the same day.[50] However, the TCFA was cancelled at 18:00 UTC on 25 December, since the system moved inland,[51] and the BoM ceased issuing advisories as well.[52] However, the tropical low kept moving eastward, reaching the Gulf of Carpentaria, before moving over the Top End and entering the Coral Sea.[4] At 02:30 UTC on 30 December, the JTWC issued a TCFA again on the system; however, at 02:30 UTC on 31 December, the TCFA was cancelled, due to the system developing subtropical characteristics.[53][54] Around that same time, the BoM upgraded the low to a Category 1 tropical cyclone on the Australian scale and named it Seth.[4] At 15:00 UTC, the JTWC finally classified it as a tropical cyclone, designating the system with the identifier 04P.[55] The cyclone reached its peak intensity that day, with BoM estimating Seth as a category 2 tropical cyclone, with sustained winds of 110 km/h (70 mph), before subsequently downgrading the storm to a category 1 tropical cyclone at 18:00 UTC that same day. At 06:00 UTC on 1 January, the BoM reclassified Seth as an ex-tropical cyclone.[4] The JTWC issued their final warning three hours later.[56] On the next day, the BoM classified the system as a subtropical low.[4]

As a post-tropical cyclone, Seth killed 2 people; one in Queensland and the other in New South Wales.[57][58]

Category 2 tropical cyclone (Australian scale)
Category 1 tropical cyclone (SSHWS)
Duration	8 January – 12 January
Peak intensity	100 km/h (65 mph) (10-min); 988 hPa (mbar)

On 4 January, the BoM started to monitor a possible tropical low near the Coral Sea.[59] By 8 January, BoM began issuing advisories on Tropical Low 10U.[5][60] The JTWC later issued a TCFA on the system.[61] By the next day, the BoM upgraded it to a category 1 tropical cyclone, and named it Tiffany.[5] The JTWC subsequently followed suit and started issuing advisories on Tiffany.[62] Tiffany then rapidly intensified, peaking as a Category 2 tropical cyclone in the Australian scale and a Category 1-equivalent tropical cyclone in the Saffir-Simpson scale.[5][63] The storm then rapidly weakened and made landfall over the Cape York Peninsula as a category 1 tropical cyclone at 06:00 UTC on 10 January. Due to land interaction, it rapidly weakened overland and became a weak tropical low. The low entered into the Gulf of Carpentaria with that intensity by the same night.[5] Despite the moderate wind shear, Tiffany re-intensified, with the BoM upgrading the system into a category 2 tropical cyclone by 11 January.[64][5] On 00:00 UTC of 12 January, the storm made its final landfall over the Northern Territory region and was followed by rapid weakening.[5] The JTWC stopped issuing advisories by the same time.[65]

Tiffany brought gusty winds and heavy rainfall exceeding 100 mm (3.9 in) to the Top End. A house near Katherine suffered around A$50,000 (US$36,000) in damage from fallen trees.[66]

Tropical low (Australian scale)
Duration	13 January – 14 January
Peak intensity	Winds not specified; 1008 hPa (mbar)

On 6 January, the BoM first noted the possible formation of a weak tropical low.[67] By 13 January, 11U formed while moving west-southwestward, 11U dissipated by the next day.[68][69]

Tropical low (Australian scale)
Duration	28 January – 5 February
Peak intensity	Winds not specified; 1003 hPa (mbar)

On 26 January, the BoM noted that a tropical low may form within a monsoon trough over the Kimberley Region.[70] The agency then reported that the low was forming over the central parts of the Northern Territory on 28 January.[71] As it moved slowly west over the next few days,[72] by 1 February, the BoM designated the tropical low as 14U.[73] The low then weakened as it turned northwestwards,[74] before being last noted on 5 February, about 515 km (320 mi) north-northwest of Port Hedland.[75]

In Western Australia, prolific rains affected the Kimberley with some areas recording accumulations not seen in over a century. Country Downs measured 843 mm (33.2 in) by 2 February, including 652.2 mm (25.68 in) in a 24-hour span. The latter constituted the second-highest daily rainfall on record in the state. Flooding occurred along the Fitzroy River, covering roads, washing out topsoil, knocking down fences, and toppling trees. More than 80,000 lightning strikes were observed around Broome.[76] Rainfall in the city reached 352.8 mm (13.89 in) on 30 January, surpassing the total rainfall seeing during the entirety of 2021.[6]

Tropical low (Australian scale)
Tropical storm (SSHWS)
Duration	29 January – 3 February (Exited basin)
Peak intensity	65 km/h (40 mph) (10-min); 995 hPa (mbar)

On 28 January, the BoM noted that a tropical low may form within a monsoon trough over the Coral Sea over the next few days.[77] By the next day, the agency reported that the low was forming about 250 km (160 mi) to the northeast of Cairns.[78] On 30 January, the JTWC started to monitor the low and gave it a low chance of formation into a tropical cyclone.[79] Under a favorable environment of warm sea surface temperatures, lowering wind shear and good outflow aloft, the system continued to consolidate, prompting the JTWC to issue a TCFA by the next day,[80][81] before subsequently upgrading it to a tropical cyclone, and designated it as 09P.[82] By 1 February, the BoM designated the low as 16U.[83] However, 16U did not intensify further as a dry air entrainment hampered the system's intensification, while continuing to move east-southeast under a near-equatorial ridge positioned to the north and northeast.[84] The JTWC later downgraded 16U into a tropical depression.[85] On 3 February, 16U exited the basin and entered the South Pacific basin.[86][17]

Tropical low (Australian scale)
Duration	5 February – 14 February
Peak intensity	Winds not specified; 1001 hPa (mbar)

By 4 February, the BoM noted that a weak tropical low may form within the vicinity of Christmas Island, and predesignated it as 17U.[87] The low then subsequently formed by the next day, about 300 km (190 mi) west-southwest of Christmas Island.[88] By 7 February, the JTWC started to monitor 17U, and gave it a medium chance for development within the next 24 hours.[89] The BoM subsequently gave the system a low chance for development in the next 3 days.[90] Under an environmment of warm sea surface temperatures, lowering vertical wind shear and fair poleward outflow, the low started to organize, with deep convection wrapping to its low-level circulation center, prompting the JTWC to issue a TCFA by the next day.[91] However, as it moved south-southwest,[92] the wind shear started to increase, leading to its LLCC becoming exposed and the JTWC cancelling the TCFA on 10 February.[93] 17U continued westwards, and was last noted by the BoM on 13 February, before exiting the basin shortly thereafter.[94]

Tropical low (Australian scale)
Monsoon depression
Duration	13 February – 16 February (Exited basin)
Peak intensity	55 km/h (35 mph) (1-min); 999 hPa (mbar)

On 10 February, the BoM noted that a tropical low may form in the next few days to the southeast of Christmas Island, and was predesignated as 19U.[95] The tropical low then developed three days later, about 600 km (370 mi) southeast of the Cocos Islands.[96] 19U moved west-southwestwards,[97] before entering the South-West Indian Ocean basin on 16 February.[98]

Tropical low (Australian scale)
Duration	17 February – 18 February
Peak intensity	Winds not specified; 1003 hPa (mbar)

On 16 February, the BoM noted that a weak tropical low may form to the south of Papua New Guinea, and predesignated it as 20U.[99] The low then subsequently formed the next day, under an unfavorable environment.[100] 20U was last noted by 18 February.[101]

Category 4 severe tropical cyclone (Australian scale)
Category 3 tropical cyclone (SSHWS)
Duration	23 February – 26 February (Exited basin)
Peak intensity	185 km/h (115 mph) (10-min); 950 hPa (mbar)

On 23 February, the BoM reported that a tropical low had developed to the southwest of Christmas Island in the Indian Ocean, and designated it as 22U.[7][17] By the next day, the JTWC started to monitor the low, and gave it a low chance of formation into a tropical cyclone.[102] Under a favorable environment of warm sea surface temperatures, low wind shear, and increasing poleward outflow, the system organized further, prompting the JTWC to issue a TCFA at 14:00 UTC that same day.[103] At 00:00 UTC on 25 February, the low intensified into a category 1 tropical cyclone in the Australian scale, with the BoM naming it as Vernon.[7] The JTWC subsequently started to issue advisories.[104] Moving west-southwest along the northern periphery of a deep-layered subtropical ridge to the south, Vernon went on a rapid intensification phase over the day, with BoM and JTWC upgrading Vernon into a category 3 severe tropical cyclone in the Australian scale and a category 1-equivalent tropical cyclone in the Saffir-Simpson scale respectively 12 hours later, as it developed a pinhole eye.[7][105] Vernon then intensified to a category 4 severe tropical cyclone by the next day, as it started to move out of the basin and into the South-West Indian Ocean basin.[7]

Tropical low (Australian scale)
Duration	24 February – 27 February
Peak intensity	Winds not specified; 1001 hPa (mbar)

On 20 February, the BoM noted a possible formation of a tropical low over the Arafura Sea, as a trough over northern Australia was expected to be more active.[106] It was later predesignated as 21U.[107] By 23 February, the JTWC started to monitor the low, and gave a low chance of formation in the next 24 hours.[108] The BoM then reported the low was forming by the next day, near the Torres Strait, and gave a moderate chance of formation over the next 3 days.[109] As the system continued to move east-southeast,[110] it never organized further, prompting the JTWC to drop the system on their bulletins by 26 February.[111] 21U was last noted by the next day, moving east and exiting the basin.[112]

Category 2 tropical cyclone (Australian scale)
Tropical storm (SSHWS)
Duration	24 February – 3 March
Peak intensity	95 km/h (60 mph) (10-min); 978 hPa (mbar)

During 23 February, the BoM started to monitor an enhanced area of convection, that developed along a monsoon trough in the Timor Sea.[8] The JTWC started to track the area late on the same day, and gave a low chance of formation into a tropical cyclone.[113] By the next day, the convection organized into a tropical low, and the BoM designated it as 23U.[17] Under a favorable environment of warm sea surface temperatures and pronounced outflow being offset by high wind shear, the low continued to organize, with the JTWC issuing a TCFA late on 24 February.[114] At 15:00 UTC the next day, the low intensified into a category 1 tropical cyclone, with the BoM naming it as Anika.[8] The JTWC subsequently followed suit and upgraded the system into a tropical storm, noting deep and cold convection covering its low-level circulation center.[115] By 25 January, Anika intensified to a category 2 cyclone, before making landfall in the Kimberley coast, to the east of Kalumburu at 12:00 UTC that same day. As a result, the BoM downgraded Anika to an ex-tropical cyclone.[8] The JTWC subsequently issued their final advisory on the system.[116]

Anika then moved southeastwards, emerging to the Indian Ocean on 1 March. During this time, the system initially struggled to redevelop, as its mid-level circulation center was displaced significantly to the south.[8] The JTWC issued a TCFA on Anika that same day, before upgrading the system back into a tropical storm, as banding was wrapping to its center.[117][118] The BoM then re-upgraded Anika to a category 1 tropical cyclone at 06:00 UTC the next day, before briefly reintensifying to a category 2 tropical cyclone as it made its second landfall near Wallal.[8] The JTWC subsequently discontinued issuing advisories on Anika once again.[119] It weakened into a category 1 tropical cyclone as it moved further inland, before becoming a tropical low on 3 March. It dissipated by the next day.[8]

Anika caused trees to fall in Kimberley, and more than 260 mm of precipitation was recorded according to the BoM.[9]

Tropical low (Australian scale)
Tropical storm (SSHWS)
Duration	26 February (Entered basin) – 27 February (Exited basin)
Peak intensity	85 km/h (50 mph) (10-min); 996 hPa (mbar)

On 26 February, Moderate Tropical Storm 08 briefly moved into the western portion of the basin while undergoing a fujiwhara interaction with Severe Tropical Cyclone Vernon, and was designated by BoM as Tropical Low 25U.[120] 25U was last noted on 27 February where it moved back to the South-West Indian Ocean basin.[17]

Tropical low (Australian scale)
Tropical storm (SSHWS)
Duration	27 February – 4 March
Peak intensity	65 km/h (40 mph) (1-min); 1004 hPa (mbar)

On 27 February, the BoM reported that Tropical Low 26U had formed about 295 km (183 mi) to the east of Christmas Island, and gave a low chance of formation over the next 3 days.[121] The JTWC started to monitor the low the next day, and also gave a low chance of formation over the next 24 hours.[122] Under a marginal environment of warm sea surface temperatures and robust outflow aloft offset by high wind shear, the low started to consolidate, prompting the agency to issue a TCFA late on 1 March.[123] By the next day, the JTWC upgraded 26U to a tropical storm, designating it as 17S. At that time, the system was already disorganized, with flaring convection being sheared off to the west of its exposed, elongated low-level circulation center.[124] As its LLCC continued to become more exposed, and its central convection becoming more disorganized, the JTWC discontinued issuing advisories for 26U late on the same day.[125] The BoM stopped monitoring the low on 4 February, as it moved southeast while continuing to weaken.[126]

Category 2 tropical cyclone (Australian scale)
Tropical storm (SSHWS)
Duration	12 March – 16 March
Peak intensity	95 km/h (60 mph) (10-min); 988 hPa (mbar)

On 9 March, the BoM noted that a tropical low is expected to develop to the south of Java, Indonesia.[127] The low started to develop two days later, on 11 March.[128] Late on the same day, the JTWC started to monitor the low, and gave a low chance of formation as it started to organize.[129] Moving west-southwestward under an environment of warm sea surface temperatures, low to moderate vertical wind shear and strong radial outflow aloft,[130] the low continued to improve, prompting the JTWC to issue a TCFA on 13 March,[131] before initiating advisories on Tropical Cyclone 20S late on the same day.[132]

By 14 March, the BoM estimated the low, now designated as 27U, had reached tropical cyclone intensity; operationally, they did not upgrade the system.[10][133] 27U continued to intensify, reaching peak intensity late on the same day as a category 2 tropical cyclone on the Australian scale.[10] The JTWC estimated its peak intensity with 1-minute sustained winds of 60 knots (110 km/h; 69 mph), based on microwave imagery showing a well-formed eye.[134] On 15 March, the BoM gave 27U the name Billy,[135] before the system started to weaken due to a dry air entrainment, along with increasing wind shear.[136] By 16 March, the BoM declared Billy as an ex-tropical cyclone, as convection associated with the system became sheared to the southeast of its low-level circulation center.[10][137] The JTWC continued to issue advisories to the system as gale-force winds continued to prevail,[138] until the next day, when Billy weakened below gale-force.[139] The system dissipated on the same day.[10]

Category 4 severe tropical cyclone (Australian scale)
Category 2 tropical cyclone (SSHWS)
Duration	16 March – 23 March
Peak intensity	165 km/h (105 mph) (10-min); 956 hPa (mbar)

On 12 March, the BoM noted that a tropical low may form in the Arafura Sea in the next 3 days.[140] The low developed 3 days later, to the north of the Northern Territory.[141] As it moved westwards across Timor-Leste into the Indian Ocean,[11] the JTWC started to monitor the system on 18 March, with deep convection displaced to the west of its elongated low-level circulation center.[142] Under a favorable environment of warm sea surface temperatures, low vertical wind shear and good poleward outflow aided by the upper-level westerlies associated with a mid-latitude trough to the south,[143] the low started to consolidate, prompting the agency to issue a TCFA by the next day.[144] On 20 March, the BoM started to issue advisories on the low, and assigned the identifier 28U.[145] The JTWC subsequently followed suit, and upgraded the low into a tropical storm, designating it as 21S.[146] 28U reached tropical cyclone intensity afterwards, with the BoM naming it as Charlotte.[11]

By the next day, Charlotte started to rapidly intensify, reaching category 2 status in the Australian scale at 00:00 UTC.[11] Around 21:00 UTC, the storm developed a 6 nautical miles (11 km; 6.9 mi) clear eye, which made the cyclone achieve its peak intensity as a category 4 severe tropical cyclone, with 10-minute sustained winds of 90 knots (170 km/h; 100 mph).[11] The JTWC subsequently upgraded Charlotte to a Category 2-equivalent cyclone in the Saffir-Simpson scale on 22 March.[147] Charlotte then started to weaken, as shear began to increase.[148] The BoM and JTWC estimated Charlotte to have weakened to a category 3 severe tropical cyclone, and a category 1-equivalent tropical cyclone, respectively, late on the same day.[11][149] As its low-level circulation center became exposed on 23 March, the BoM downgraded Charlotte to a category 2 tropical cyclone at 12:00 UTC, before it weakened into a remnant low six hours later.[11] The JTWC subsequently downgraded the system to a tropical storm 3 hours later,[150] before discontinuing advisories by the next day.[151] The BoM continued to track Charlotte until 25 March.[11]

As it moved over Timor-Leste, it brought heavy rain towards the country, however there were no damages reported.[11]

Tropical low (Australian scale)
Duration	30 March – 1 April
Peak intensity	45 km/h (30 mph) (10-min); 1004 hPa (mbar)

On 30 March, the BoM reported that Tropical Low 30U was developing south of Christmas Island, near 810 km (500 mi) northwest of Exmouth.[12][152] The JTWC also started to monitor the system, giving a low chance of formation in the next 24 hours.[153] Although in a favorable environment of warm sea surface temperatures, low vertical wind shear and robust poleward outflow aloft,[154] the low failed to organize as shear started to increase, prompting the JTWC to drop the system on 1 April.[155] The cyclone transitioned to a subtropical low at the same day as it moved south, before dissipating near Kalbarri two days later.[12]

As the low approached the southern Western Australia coast, it brought heavy rainfall along the area, with 118.66 millimetres (4.672 in) of rain reported at Carnarvon. Localized flooding caused road disruptions including the closure of the North West Coastal Highway from south of Carnarvon to the Shark Bay road for two days. Flash flood impacts were reported in Carnarvon with minor inundation of some roads, commercial and residential buildings.[12]

Tropical low (Australian scale)
Duration	8 April – 9 April
Peak intensity	Winds not specified; 1005 hPa (mbar)

According to a bulletin released by the Bureau of Meteorology on the morning of 8 April, a new tropical low formed in Papua New Guinea.[156] It was designated as 32U. 32U lost its tropical characteristics on 9 April without affecting any habitable areas.[157]

Tropical low (Australian scale)
Duration	17 April – 19 April
Peak intensity	Winds not specified; 1005 hPa (mbar)

On 17 April, the BoM reported that Tropical Low 33U had formed, about 155 km (96 mi) to the northwest of the Gove Peninsula.[158] 33U slowly headed northwards, before the BoM stopped monitoring the low on 19 April.[13]

Tropical low (Australian scale)
Duration	24 April – 26 April
Peak intensity	75 km/h (45 mph) (10-min); 996 hPa (mbar)

A tropical low formed 420 km (260 mi) from Christmas Island, according to the Bureau Of Meteorology technical bulletin, and was designated 34U.[159] The cyclone intensified and the agency released unusual bulletins about the possibility of reaching Category 1, even though it did not pose a threat to any habitable areas.[14]

Upon post-analysis, the BoM found that another low-level circulation center formed on 25 April that was not part of 34U; hence, the earlier system was assigned the identifier 37U.[17]

Tropical low (Australian scale)
Tropical storm (SSHWS)
Duration	25 April – 29 April
Peak intensity	65 km/h (40 mph) (10-min); 998 hPa (mbar)

On 25 April, a new low-level circulation center formed from now-classified Tropical Low 37U and tracked away to the east. The BoM assigned the identifier 34U to the system. This low dissipated on 29 April.[17] The system was upgraded to a tropical storm by the JTWC in post-analysis.[160]

Category 2 tropical cyclone (Australian scale)
Tropical storm (SSHWS)
Duration	7 May (Entered basin) – 11 May
Peak intensity	110 km/h (70 mph) (10-min); 982 hPa (mbar)

On 7 May, Moderate Tropical Storm Karim entered the Australian region, and the BoM initiated advisories on the system as a Category 1 tropical cyclone on the Australian scale.[15][161] At the time, the system was intensifying, with deep central convection wrapping into the system.[162] By the next day, Karim further intensified into a category 2 tropical cyclone.[15] Late on the same day, the JTWC reported the system had reached its peak intensity.[163] As it moved steadily southwards within an environment of warm sea surface temperatures, moderate wind shear and strong poleward outflow, Karim maintained its intensity throughout 9 May, before the BoM reported that Karim reached its peak intensity by the next day, with 10-minute sustained winds of 60 kn (110 km/h; 69 mph).[15] The storm then started to weaken, as it turned south-southeastwards under the influence of a near-equatorial ridge to the northwest, into an unfavorable environment of cooler sea surface temperatures and high wind shear.[164] By 11 May, the BoM reclassified Karim as a subtropical low.[15] The JTWC subsequently issued their final advisory on the system as it was transitioning to an extratropical cyclone.[165]

Tropical low (Australian scale)
Subtropical storm (SSHWS)
Duration	28 May – 31 May
Peak intensity	65 km/h (40 mph) (1-min); 1004 hPa (mbar)

On 28 May, the BoM reported that a tropical low formed to the southwest of Christmas Island.[16] The JTWC classified the disturbance as subtropical in an unofficial bulletin and called it Invest 92S the next day.[166] On 30 May, the agency issued a short bulletin warning that the cyclone could directly hit the region of Pilbara in the west of the country.[167] However, the low started to weaken, and the BoM last noted the low on the next day.[168]

The BoM first noted the formation of a possible low-pressure system to the southwest of the island of Sumatra by 4 November.[169] This forecast was materialized when the bureau started to track a weak tropical low outside the Western Region on 9 November, while located at 400 kilometres (250 mi) to the north-northeast of the Cocos Islands.[170] It then entered the region by the next day while tracking slowly towards the island. Environmental conditions were analyzed to be unfavorable for further development and as such, the BoM only forecast a "very low" chance of the low becoming a tropical cyclone.[171] The tropical low then passed to the south of the archipelago before turning westwards and exiting the basin into the South-West Indian Ocean region by 14 November.[172][173][174]

On 26 December, a weak tropical low formed close to the Cocos Islands. It meandered over the same area and dissipated on 3 January.[175]

On 22 January, a weak tropical low formed north of the Timor Sea.[176] It was moving east before it changed to west. The system was last noted on 25 January.[177]

On 23 January, the BoM reported that a tropical low had formed in the northwestern portion of the basin.[178][179] The system moved in a westward direction until it was last tracked on 25 January, when it had exited the basin and moved into the South-West Indian Ocean.[180] At its peak intensity in the Australian region, the BoM estimated the system's minimum atmospheric pressure as 1003 hPa.[181] The MFR began tracking the system, with the system intensifying into Moderate Tropical Storm Batsirai on 27 January.[182][183]

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.[184] 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 was used for 2021–22 season is listed below:

TCWC Jakarta monitors Tropical Cyclones from the Equator to 11S and from 90E to 145E. 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.[184] The name that was used for 2021–22 season is listed below:

Tropical cyclones that develop north of 11°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 rare, with no cyclones being named in it since 2007.[185] As names are assigned in a random order, the whole list is shown below:

If a tropical cyclone enters the Australian basin from the Southwest Indian region basin (east of 90°E), it will retain the name assigned to it by the Météo-France (MFR). The following storms were named in this manner:

• Karim

Later in 2022, the Bureau of Meteorology retired the name Seth, replacing it with Stafford due to the damage caused by it in Queensland.