Loading AI tools
From Wikipedia, the free encyclopedia
The 2023–24 Australian region cyclone season was the fifth consecutive season to have below-average activity in terms of named storms. Despite this, it was the second in a row to have at least five severe tropical cyclones, including Australia's wettest tropical cyclone on record. The season officially started on 1 November 2023 and ended on 30 April 2024, however, a tropical cyclone could form at any time between 1 July 2023 and 30 June 2024 and would count towards the season total. During the season, tropical cyclones were 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.
| 2023–24 Australian region cyclone season | |
|---|---|
Season summary map | |
| Seasonal boundaries | |
| First system formed | 4 December 2023 |
| Last system dissipated | 5 May 2024 |
| Strongest storm | |
| Name | Jasper |
| • Maximum winds | 215 km/h (130 mph) (10-minute sustained) |
| • Lowest pressure | 926 hPa (mbar) |
| Seasonal statistics | |
| Tropical lows | 13 |
| Tropical cyclones | 8 |
| Severe tropical cyclones | 6 |
| Total fatalities | 1 total |
| Total damage | $675 million (2023 USD) |
| Related articles | |
| Source/Record | Tropical Cyclone |
Severe Tropical Cyclone |
Ref | |
|---|---|---|---|---|
| Record high: | 21 | 12 | [1] | |
| Record low: | 3 | 0 | [1] | |
| Average (1969–70 – 2023–24): | 11 | — | [2] | |
| Region | Chance of less |
Average number |
Ref | |
| Whole (90°E–160°E) | 80% | 11 | [2] | |
| Western (90°E–125°E) | 72% | 7 | [2] | |
| North-Western (105°E–130°E) | 75% | 5 | [2] | |
| Northern (125°E–142.5°E) | 61% | 3 | [2] | |
| Eastern (142.5°E–160°E) | 76% | 4 | [2] | |
| Western South Pacific (142.5°E—165°E) | 68% | 4 | [3] | |
| Eastern South Pacific (165°E—120°W) | 40% | 6 | [3] | |
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][4] These outlooks took into account a variety of factors such as a developing El Niño event and what had happened in previous seasons such as 1972–73, 1982–83, 1997–98, 2009–10 and 2015–16.[2][4] Within their seasonal outlook for the Australian region, the BoM suggested that there was an 80% chance, that the whole region between 90°E – 160°E, would be below average, having less than the long term average of 11 tropical cyclones.[2] They also suggested that each of their self-defined Western, Northern, North-western and Eastern regions would see a below-average amount of tropical cyclone activity.[2]
The BoM also issued a seasonal forecast that discussed tropical cyclone activity over the South Pacific Ocean for their self-defined eastern and western regions of the South Pacific Ocean.[3] Within this forecast, they predicted that their western region between 142.5°E and 165°E would have a below average amount of activity, while their eastern region between 165°E and 120°W had a 60% chance of seeing activity above its average of 6 tropical cyclones.[3] Along with other Pacific Meteorological Services, the BoM contributed to NIWA's Southwest Pacific tropical cyclone outlook, which predicted that nine and fourteen tropical cyclones would occur between 135°E and 120°W.[4] At least four to eight of these systems were expected to intensify further and become either a Category 3, 4 or 5 severe tropical cyclone on the Australian tropical cyclone intensity scale.[2]
The season officially started on 1 November, however the first system, Cyclone Jasper, would not be active until 4 December, when it crossed into the basin as a tropical low from the South Pacific. The low became a named storm on 5 December, receiving the name Jasper,[5] and intensified into the season's first severe tropical cyclone the next day.[6] Jasper made landfall in Far North Queensland as a Category 2 tropical cyclone on 13 December.[7]
After a significant lull in activity, Tropical Cyclone Anggrek and Tropical Low 03U formed on 10 and 11 January respectively,[8][9] with the latter dissipating on 23 January.[10] The next day, Cyclone Kirrily formed.[11] Tropical Low 06U formed on 30 January, dancing out of basin the next day and waltzing back in on 5 February.[1][12] Tropical Cyclone Lincoln formed on 16 February and made landfall on the Gulf of Carpentaria coast.[13] Severe Tropical Cyclone Neville formed north of the Cocos Islands[14] on 1 March and left the basin 20 days later.[15] Severe Tropical Cyclone Megan formed on 13 March from a tropical low over the coast of the Gulf of Carpentaria.[16] Short-lived Tropical Low 10U formed and weakened within the same day of 14 March.[17] Severe Tropical Cyclone Olga formed within a monsoon trough south of Sumba[18][19] on 4 April. Tropical Cyclone Paul formed 5 days later over the Louisiade Archipelago.[20] Tropical Low 12U formed on 12 April and remained traceable.[21]
The season ended with Tropical Low 16U, formed on 4 May and weakened the next day.[22]
| Category 5 severe tropical cyclone (Australian scale) | |
| Category 4 tropical cyclone (SSHWS) | |
  | |
| Duration | 4 December (Entered basin) – 18 December |
|---|---|
| Peak intensity | 215 km/h (130 mph) (10-min); 926 hPa (mbar) |
On 2 December, the Australian Bureau of Meteorology (BoM) reported that Tropical Disturbance 03F, which was re-designated as Tropical Low 02U, had formed in the South Pacific Ocean in Fiji's area of responsibility.[23] Two days later, on 00:00 UTC of 4 December, the system would enter the Australian area of responsibility.[24][25] The Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert (TCFA) later that day, projecting a high likelihood of a significant tropical cyclone developing.[26] Later the next day, the JTWC subsequently initiated advisories on the system and classified it as Tropical Cyclone 03P.[27] The BoM subsequently followed suit and upgraded it to a Category 1 tropical cyclone, naming it Jasper.[5] Jasper started to track southward under the steering influence of a near equatorial ridge to the east.[28] During the next day, the cyclone's centre continued to organise, with deep convective bands starting to wrap around the centre, prompting the JTWC to upgrade the system to a Category 1 hurricane.[29] Jasper rapidly intensified into a Category 3 severe tropical cyclone,[6] due to being in an environment with warm sea surface temperatures and low wind shear. The next day, it further intensified, becoming a Category 5 severe tropical cyclone.[30] Operationally, the BoM classified Jasper as a high-end Category 4 severe tropical cyclone with winds of 195 km/h (120 mph), but during post-cyclone reanalysis concluded a peak wind speed of 215 km/h (130 mph) based on Synthetic-aperture radar measurements.[1][31] Shortly thereafter, Jasper began weakening, with its eye becoming cloud-filled and the deep convection eroding due to dry air entrainment.[32] Jasper would reintensify, and at 12:00 UTC on 13 December, made landfall as a Category 2 tropical cyclone in Wujal Wujal, Queensland.[7] After making landfall, the JTWC discontinue warnings on the system later that day.[33] By 14:00 UTC that day, the BoM reported that Jasper had weakened to a tropical low.[34] However, Jasper remained traceable, and the BoM would give the tropical low a moderate chance of redeveloping into a tropical cyclone on 15 December.[35] However, they would soon downgrade its chances of re-developing into a very low as the storm turned southeast further inland, causing the tropical low to rapidly weaken, and on 18 December, Jasper was last noted over the Cape York Peninsula.[36]
Jasper produced torrential rainfall, peaking at 2,252 mm (88.7 in) at Bairds near the Daintree River, making the wettest tropical cyclone in Australian history, beating the previous record of Cyclone Peter in 1979.[37][38] The Insurance Council of Australia estimated that Jasper caused AU$1 billion (US$675 million) in damages.[39]
| Category 3 severe tropical cyclone (Australian scale) | |
| Category 1 tropical cyclone (SSHWS) | |
  | |
| Duration | 10 January – 25 January (Exited basin) |
|---|---|
| Peak intensity | 140 km/h (85 mph) (10-min); 973 hPa (mbar) |
On 9 January, the BoM noted that a tropical low could form in the Indian Ocean, designating it as 04U.[40] Later the next day, the BoM reported that it had formed to the northwest of the Cocos Islands.[41] On 11 January, the JTWC followed suit in monitoring the system, after convection had significantly consolidated around the circulation.[42] Three days later, the agency issued a TCFA, for the disturbance as it was situated in an environment of warm waters, low shear, and good outflow.[43] By 15 January, the JTWC began issuing advisories, recognising it as Tropical Cyclone 06S after its circulation had improved,[44] with the BoM subsequently followed suit and upgraded it to a Category 1 tropical cyclone.[45] Since the cyclone was within their area of responsibility, Meteorology, Climatology, and Geophysical Agency (BMKG) named the system Anggrek.[46] It tracked southeast before changing direction and tracking west.[47] Anggrek remained nearly stationary due to weak steering ridges to the north and southwest, the system generated upwelling, causing sea surface temperatures to decrease.[48] Despite that, Anggrek steadily re-intensified,[49] and after entering favourable conditions on 24 January, became a Category 3 severe tropical cyclone, with estimated maximum 10-minute sustained winds of 150 km/h (90 mph), and a central barometric pressure of 968 hPa (28.59 inHg).[50][51] while the system's depiction showed that tightly circulating around a ragged eye.[52] The next day, the system exited the basin towards the South West Indian Ocean.[53]
On 7 January, the BoM noted the possibility of a tropical low forming near the north Kimberley, as a monsoon trough was expected to develop along the Top End. It was predesignated as 03U.[54] This came to fruition 4 days later, when the BoM reported that it was developing over the southern Joseph Bonaparte Gulf within the trough.[9] As the tropical low tracked overland, the system maintained a robust outflow channel in the upper troposphere.[55] The BoM continued to monitor the low as it moved slowly southeast,[56] then turning west towards Western Australia by 20 January,[57] until they determined that it would not develop into a tropical cyclone on 23 January.[58][59]
The low and its associated monsoon brought heavy rainfall to the Northern Territory, resulting in the BoM issuing flood watches and warnings throughout the Top End and central Northern Territory.[60] Wadeye received 661 mm (26.0 in) of rainfall.[61]
The BoM noted the possibility of a tropical low forming within the monsoon trough over the Gulf of Carpentaria on 9 January, designating it as 05U.[62] Three days later, the BoM reported that it was developing over the eastern portion of the gulf.[63] By 17 January, the JTWC began monitoring the low.[64] Two days later, the JTWC issued a TCFA for the system.[65] By 21 January, the BoM started issuing warnings on the system.[66] By 23 January, the JTWC followed suit, recognising it as Tropical Cyclone 07P.[67] The next day, the BoM upgraded the low into a Category 1 tropical cyclone, naming it Kirrily.[68] Deep convection shifted to the western side of Kirrily's circulation, though its centre remained well defined.[69] It subsequently intensified to a Category 3 severe tropical cyclone,[70] the JTWC followed suit the system and upgraded it to a Category 1 hurricane,[71] prior to landfall over Townsville, Australia on 25 January.[72] Shortly after the landfall, the JTWC discontinued warnings on the system.[72] The next day, the BoM discontinued warnings.[73] However, Kirrily remained traceable, as it moved westwards towards the Queensland region throughout the rest of January.[74] The JTWC began monitoring the remnants of Kirrily for potential regeneration as the system developed a partially exposed low-level circulation centre (LLCC).[75] Early the next day, they issued a TCFA for the remnants.[76] The disturbance later regenerated into a tropical cyclone; the system showed a consolidating LLCC with convective banding and a central dense overcast (CDO).[77] Since the system only produced near-gale-force winds in the Gulf of Carpentaria, the BoM determined that the low was not expected to redevelop into a tropical cyclone.[78] By 2 February, the JTWC discontinued their advisories again, as the storm accelerated inland with the rainbands unraveling and warming cloud tops,[79] until it was last noted on the BoM tropical cyclone outlooks by the next day.[80]
Before the storm made landfall on 24 January, the BoM issued cyclone warnings for Townsville, Mackay, Bowen, the Whitsunday Islands, which extended inland to Charters Towers.[81] As the storm impacted Queensland, locally intense rainfall up to 300 mm (12 in) was recorded.[82]
| Tropical low (Australian scale) | |
  | |
| Duration | 30 January – 7 February (Exited basin) (Out of basin from 1–4 February) |
|---|---|
| Peak intensity | 55 km/h (35 mph) (10-min); 997 hPa (mbar) |
On 29 January, the BoM noted that a subtropical low was expected to form off the coast of Eastern Australia in a few days, designating it as 06U.[83] The next day, the BoM began monitoring the low as it was developing in the eastern portion of the basin, about 125 km (80 mi) to the northeast of Kgari in Queensland, Australia.[1][84][85] Over the next couple of days, the system moved north-eastwards and moved into the South Pacific basin during 1 February, where it was classified as Tropical Disturbance 05F by the Fiji Meteorological Service.[1][12] At this stage, the system was located in an area of moderate vertical wind shear and good upper-level divergence about 675 km (420 mi) to the northwest of Nouméa in New Caledonia, while atmospheric convection persisted over the system's LLCC.[12] After meandering outside the basin for several days, the system re-entered the basin as a tropical low.[86] Environmental conditions were assessed as being marginally conducive for tropical cyclogenesis, with warm sea surface temperatures near 29–30 °C (84–86 °F) and low vertical wind shear.[87] It again exited the basin on 7 February, as the storm was struggling due to moderate wind shear.[88]
During February 2024, the presence of the Madden–Julian Oscillation and an equatorial Indian Ocean in the Australian region contributed to the formation of Tropical Low 07U in the monsoon trough over the western Gulf of Carpentaria,[89][90][91] approximately 419 km (260 mi) to the east-southeast of Darwin in the Northern Territory during 14 February.[92][90] Initially located in an favourable environment for intensification, the tropical low began to encounter somewhat improved conditions.[93] As the tropical low tracked slowly moving towards the coast, consolidating LLCC with convection started to develop and was wrapping toward the centre.[94] By 15 February, at 14:30 UTC, the JTWC issued a TCFA, noting that the system was in a favourable environment with low wind shear and sea surface temperatures exceeding 29–30 °C (84–86 °F).[95] The agency later issued its first warning on the system, classifying it as Tropical Cyclone 14P.[96] The BoM followed suit—officially upgrading the system to a Category 1 tropical cyclone and assigning the name Lincoln.[97] Lincoln had a partially exposed LLCC with core convection confined to the western edge of the cyclone.[98] Lincoln made landfall on the Gulf of Carpentaria coast between Port McArthur and the Northern Territory—Queensland border just after 06:00 UTC on 16 February.[99] Shortly after the landfall, the JTWC discontinued warnings on the system.[100] Later that day, the BoM followed suit and released its last advisory as the system degenerated into a tropical low.[101] However, Lincoln remained traceable, and the BoM would give the system a high chance of redeveloping into a tropical cyclone on 18 February.[102] The following day, the tropical low continued moving west-southwest, aided by a ridge to the south, across inland parts of the Northern Territory.[89] By 21 February, the remnants of Lincoln turned westward into the offshore of the Kimberley coast and began to re-organise, resulting deep convection to the north.[103] The JTWC re-issued a TCFA for the system at 07:30 UTC as the formative convective banding was wrapping into a defined circulation.[104] With an increase in convective banding on the southern of the cyclone's circulation,[105] the JTWC re-initiated advisories on the storm approximately 446 km (275 mi) northeast of Learmonth at 03:00 UTC on 22 February.[106] Turning northwest as it approached Western Australia, the storm failed to organised its deep convection.[107] By 24 February, the JTWC subsequently issued their final advisory on the system, as its circulation became exposed.[108] The storm then crossed just south of Coral Bay on the Australian northwestern coastline just after 12:00 UTC that day, before moving inland across Gascoyne and dissipating shortly afterward.[109][110] Tropical Cyclone Lincoln was the first tropical cyclone to form in the Gulf of the Carpentaria since Tropical Cyclone Alfred in February 2017.[111]
| Category 4 severe tropical cyclone (Australian scale) | |
| Category 4 tropical cyclone (SSHWS) | |
  | |
| Duration | 4 March – 24 March (Exited basin) |
|---|---|
| Peak intensity | 185 km/h (115 mph) (10-min); 948 hPa (mbar) |
On 1 March, the BoM started to monitor a possible tropical low to the north of the Cocos Islands within the monsoon trough, designating it as 08U.[112] An increased monsoon flow over the Indian Ocean towards Indonesia prompted the agency to report that the tropical low was forming on 4 March, within an unfavourable environment for further development.[113][114] By 10 March, the JTWC issued a TCFA for the tropical low after noting that its deep convection continued to build in the southern and central regions over the system's LLCC, and the next day, it recognised the system as Tropical Cyclone 18S.[115][116] Afterwards, subsidence and high vertical wind shear caused the system to struggle to intensify, leaving the LLLC exposed.[117][118] Although convection continued to fluctuate in the system, deep convection continued to improve near the centre.[119] By 18 March, the JTWC subsequently issued their final advisory on the system, as its structure was to be disorganised.[120] During the next day, the tropical low began to displace to the south of the LLLC, the JTWC resumed monitoring the system.[121] The LLCC started to re–develop with deep convective bands wrapping into it, the JTWC re-initiated advisories approximately 341 km (210 mi) northwest of Learmonth at 03:00 UTC on 20 March.[122] Later that day, the BoM reported that the tropical low had developed into a Category 1 tropical cyclone and named it Neville.[123] Neville intensified shortly after, with an eye forming on microwave imagery.[124] A pinhole eye briefly emerged on infrared and visible satellite imagery as a ragged feature at the cyclone's centre, surrounded by well-defined rainbands.[125] Neville reached peak intensity at 06:00 UTC the following day as a high-end Category 4 severe tropical cyclone, with ten-minute sustained winds estimated at 175 km/h (110 mph), and a central barometric pressure of 952 hPa (28.11 inHg).[126][127] The JTWC estimated that the system was generating one-minute sustained winds of 215 km/h (130 mph), equivalent to a low-end Category 4 major hurricane.[128] Afterward, the storm's eye becoming cloud-filled caused Neville to gradually weaken as its track shifted west-southwestward.[129] Neville's eye disappeared from satellite imagery and the cloud tops of the central dense overcast warming.[130] Not long afterward, the storm began to deteriorate due to cooler waters, increasing vertical wind, and dry air entrainment. The BoM downgraded the storm to a vigorous gale-force tropical low on 24 March.[131][132] Around this time, Ex-Tropical Cyclone Neville assumed a more consistent course towards the southwest, and crossed over the 90th meridian east into the South-West Indian Ocean.[133]
Throughout its existence, Neville remained far from major landmasses; however, it brought near-gale-force gusts, as reported at Cocos Islands Airport, with winds reaching 42 km/h (26 mph), causing significant structural damage at the resort on the island.[134]
On 4 March, the BoM noted the formation of a tropical low over south of Indonesia's Sumatra or Java, designating it as 09U.[135] Over the next couple of days, the BoM reported that it was developing over the western Timor Sea within the trough.[136] Analysis from the JTWC indicated that the disturbance was in a favourable environment for development—featuring sea surface temperatures of 29 to 31 °C (84 to 88 °F), and low to moderate wind shear.[137] By 15 March, the JTWC issued a TCFA on the tropical low and warned that there was a high potential for the disturbance to develop into a tropical cyclone.[138] The tropical low moved into the Gulf of Carpentaria,[139] whereupon it gradually organised and began to intensify.[140] The same day, the JTWC upgraded the system to Tropical Cyclone 19S, approximately 367 km (230 mi) east of Darwin, Northern Territory.[141] Later the next day, the BoM reported that the tropical low had developed into a Category 1 tropical cyclone and assigned the name Megan.[142] Rapid intensification began the same day, with Megan reaching Category 2 tropical cyclone.[143] The BoM upgraded the storm to a Category 4 severe tropical cyclone at 12:00 UTC,[144] Operationally, the BoM classified Megan a Category 3 severe tropical cyclone with winds of 155 km/h (100 mph), but during post-cyclone reanalysis concluded a peak wind speed of 165 km/h (105 mph) based on Synthetic-aperture radar measurements.[145][146] Gradually approaching the southwestern coast of the Gulf of Carpentaria,[147] the JTWC indicated that one-minute sustained winds had reached 185 km/h (115 mph), equivalent to a Category 3 major hurricane on the SSHWS.[148] Megan made landfall on the southwestern Gulf of Carpentaria coast just after 06:00 UTC on 18 March.[149] Shortly after the landfall, the JTWC discontinued warnings on the system.[150] After moving ashore, the cyclone turned generally southeast and tracked along the inland of Borroloola.[151][152] The following day, the system was downgraded to a tropical low by the BoM as it approached the inland coast of the Gulf of Carpentaria.[153] Ex-Tropical Cyclone Megan moved inland, tracking across the Northern Territory, before the BoM stopped monitoring the low on 21 March.[154][155]
A planned evacuation in Borroloola was cancelled as planes were not able to land. Groote Eylandt got 600 mm (25 in) of rain.[156]
On 12 March, the BoM started to monitor a possible tropical low within the monsoon trough off the eastern Top End in the Gulf of Carpentaria, designating it as 10U.[157] Over the next couple of days, the tropical low remained poorly organised.[158] By 14 March, the BoM reported that a tropical low had developed within a monsoon trough east of Cape York Peninsula.[159] Later that day, the BoM stopped monitoring the low, as it moved southeast off the coast while continuing to weaken.[160]
On 4 April, the BoM reported that Tropical Low 11U had developed within a monsoonal trough over the south of Indonesia's Sumba.[161][162] The JTWC assessed environmental conditions as being favourable for tropical cyclogenesis, with good poleward outflow and sea surface temperatures near 30 to 31 °C (86 to 88 °F) being offset by the effects of low to moderate vertical wind shear.[163] Convective activity began organising into a symmetrical circulation, which prompted the JTWC to issue a TCFA on the disturbance as it tracked southwestwards into a favourable environment.[164][165] By 5 April, the JTWC initiated advisories on the system and classified it as Tropical Cyclone 21S, about 642 km (400 mi) northwest of Learmonth, Western Australia.[166] Later the next day, the BoM reported that the tropical low had developed into a Category 1 tropical cyclone and assigned the name Olga as its deep convection had organised significantly along with improved curvature of its bands.[167][168] The system developed a central dense overcast and a weak-developing eye.[169] The same day, Olga intensified into a Category 3 severe tropical cyclone, while the JTWC upgraded Olga to the equivalent of a low-end Category 1 hurricane with winds of 120 km/h (75 mph).[170][171] By the following day, the storm had undergone rapid intensification to attain its peak strength with sustained winds of 205 km/h (125 mph)—equivalent to a Category 5 severe tropical cyclone—and an estimated central pressure of 933 hPa (27.55 inHg).[172][173] The JTWC estimated one-minute sustained winds at this time to have been 220 km/h (140 mph)—equivalent to a Category 4 major hurricane.[174] Operationally, the BoM classified Olga as a high-end Category 4 severe tropical cyclone with winds of 185 km/h (115 mph), but during post-cyclone reanalysis concluded a peak wind speed of 205 km/h (125 mph) based on Dvorak technique measurements.[1][31] Upon reaching its peak, Olga entered a phase of steady weakening, whereby its eye disappeared from satellite imagery.[175] By 8 April, the cyclone began to encounter increasing west-northwesterly shear coupled with dry air entrainment.[176] Deep convection becoming displaced to the southeast of an increasingly-exposed LLLC.[177] Olga was re-classified as a tropical low by the BoM at 18:00 UTC on 9 April, despite still producing gale-force winds.[178][179] By the following day, the JTWC subsequently issued their final advisory on the system, as its gale-force winds soon became confined to the southern quadrant as the low became devoid of deep convection, leaving the LLLC exposed.[180] Shortly after, the BoM stopped monitoring the low, as it moved southwest while continuing to weaken.[181]
On 9 April, the BoM reported that a Tropical Low 13U had formed over the Louisiade Archipelago.[182] The tropical low depicted flaring consolidated convection to the LLLC.[183] The same day, the JTWC issued a TCFA, noting a deep convective banding wrapping into a circulation centre.[184] Shortly after, the BoM reported that the tropical low had developed into a Category 1 tropical cyclone and assigned the name Paul.[185] The JTWC followed suit, initiated advisories on the system, and classified it as Tropical Cyclone 22S.[186] Paul featured a ragged central dense overcast and soon became sufficiently organised, obscuring the LLCC, with the BoM upgrading the storm to a Category 2 tropical cyclone.[187] Paul then peaked at 12:00 UTC on 11 April, with 10-minute sustained winds of 95 km/h (60 mph), and a central barometric pressure of 994 hPa (29.35 inHg).[188][189] Flaring deep convection became disorganised into a weakly-defined centre due to increasing westerly wind shear.[190] The system was downgraded to a tropical low by the BoM at 00:00 UTC on 12 April.[191] The JTWC subsequently issued their final advisory on the system, as its circulation became disorganised.[192] The circulation of Paul had dissipated on the same day.[193][194]
On 4 April, the BoM noted that a weak tropical low could form in the Arafura Sea, designating it as 12U.[195] It remained traceable, and the BoM would give the developing tropical low an increased chance of developing into a tropical cyclone.[196] By 11 April, the BoM reported that the probability of becoming a tropical cyclogenesis had decreased due to model guidance.[197] As the system continued to move westwards, it organized further, prompting the tropical low to develop a weak circulation.[198] By 14 April, the BoM stopped monitoring the low as it moved westwards near East Timor while continuing to weaken.[199]
Towards the end of the Australian season, the BoM noted that a tropical low was expected to form north of the Australian Region and also gave the system a 15% chance of tropical cyclogenesis within a few days, designating it as 16U.[200] On 4 May, the BoM reported that it was developing over the Banda Sea.[201] At this stage, the system was located in an area of low vertical wind shear and good upper-level divergence to the northwest of Gove Airport in Australia, while atmospheric isolated convection persisted over the system before the BoM stopped monitoring the tropical low.[202][203]
The United States' Joint Typhoon Warning Center (JTWC) reported that Cyclone Djoungou entered the Australian region after crossing the 90th meridian east from the South-West Indian Ocean basin at 18:00 UTC on 19 February, located approximately 1,271 kilometres (790 mi) to the west-southwest of Learmonth, Western Australia.[204] Upon entering the region, the Météo-France (MFR) issued its last advisory on Djoungou as it transitioned into a post-tropical depression.[205] The system had commenced upon entering the region due to the effects of hostile vertical wind shear of 35–40 kn (65–74 km/h).[206] At this time, the JTWC assessed the system as a subtropical cyclone, with maximum one-minute sustained winds of 55 km/h (35 mph). The JTWC subsequently issued its final advisory on Djoungou, as its circulation became fully exposed.[204]
The Australian Bureau of Meteorology (BoM) indicated that a potential tropical low was expected to form north of Vanuatu in a few days on 12 April, designating it as 14U.[207] The potential tropical low was assessed as having a low probability of developing into a tropical cyclogenesis.[208] Once formed, the low may contribute to a strengthening of the southeasterly winds to the south that will extend towards the southern Queensland coast, until they determine that it will not develop into a tropical cyclogenesis on 18 April.[209][210]
On 15 April, the BoM started highlighting the chances of the development of a tropical low offshore the Top End and also gave the system a 30% chance of tropical cyclogenesis within a few days, designating it as 15U.[211][212] On 19 April, the BoM also reported that a potential tropical low was starting to form in the eastern Arafura Sea.[213] Shortly after, the BoM stopped monitoring the potential low, as its probability of becoming a tropical cyclogenesis had decreased.[214]
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.[215] Should a tropical low intensify into a tropical cyclone within the BoM's area of responsibility, it will be assigned the next name from the following naming list. The names Lincoln and Megan were used for the first (and only time, in case of Megan) time this season, after replacing Laurence and Magda respectively, from the 2009–10 season. The names that will be used for the 2023–24 season are listed below:
|
Later in 2024, the World Meteorological Organisations RA V Tropical Cyclone Committee retired the names Jasper, Kirrily and Megan, replacing them with the names Julian, Kima and Merryn respectively, due to the damage caused by systems in Western Australia and the South Pacific. [216]
TCWC Jakarta monitors all tropical cyclones active from the Equator to 11S and from 90E to 145E. Should a tropical depression intensify into a tropical cyclone within TCWC Jakarta's Area of Responsibility, it will be assigned the next name from the following list.[215]
|
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 extremely rare, with no cyclones being named in it since 2007.[217] As names are assigned in a random order, the whole list is shown below:
|
|
This table lists all of the tropical cyclones and subtropical cyclones that were monitored during the 2023–2024 Australian region cyclone season. Information on their intensity, duration, name, areas affected, primarily comes from TCWC Melbourne. Death and damage reports come from either press reports or the relevant national disaster management agency while the damage totals are given in 2023 or 2024 USD.
| Name | Dates | Peak intensity | Areas affected | Damage (US$) |
Deaths | |||
|---|---|---|---|---|---|---|---|---|
| Category | Wind speed (km/h (mph)) |
Pressure (hPa) | ||||||
| Jasper | 4–18 Dec | Category 5 severe tropical cyclone | 215 (130) | 926 | Solomon Islands, Queensland | 675 million | 1 | [218] |
| Anggrek | 10–25 Jan | Category 3 severe tropical cyclone | 140 (85) | 973 | None | None | 0 | |
| 03U | 11–23 Jan | Tropical low | Not specified | 991 | Northern Territory, Western Australia | None | 0 | |
| Kirrily | 12 Jan – 3 Feb | Category 3 severe tropical cyclone | 120 (75) | 978 | Queensland, Northern Territory, South Australia, New South Wales | Unknown | 0 | |
| 06U | 30 Jan – 7 Feb | Tropical low | 55 (35) | 997 | None | None | 0 | |
| Lincoln | 14–25 Feb | Category 1 tropical cyclone | 85 (50) | 990 | Northern Territory, Queensland, Western Australia | None | 0 | |
| Neville | 4–24 Mar | Category 4 severe tropical cyclone | 185 (115) | 948 | Cocos Islands, Christmas Island | None | 0 | |
| Megan | 13–21 Mar | Category 4 severe tropical cyclone | 165 (105) | 955 | Northern Territory, Queensland | None | 0 | |
| 10U | 14 Mar | Tropical low | Not specified | 1003 | Cape York Peninsula | None | 0 | |
| Olga | 3–11 Apr | Category 5 severe tropical cyclone | 205 (125) | 933 | Lesser Sunda Islands, Western Australia | None | 0 | |
| Paul | 9–12 Apr | Category 2 tropical cyclone | 95 (60) | 994 | Louisiade Archipelago | None | 0 | |
| 12U | 12–14 Apr | Tropical low | Not specified | 1006 | Lesser Sunda Islands, East Timor | None | 0 | |
| 16U | 4–5 May | Tropical low | Not specified | 1004 | None | None | 0 | |
| Season aggregates | ||||||||
| 13 systems | 4 Dec – 5 May | 205 (125) | 933 | 675 million | 1 | |||
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
.jpg)
