2019 North Indian Ocean cyclone season

Cyclonic storm (IMD)
Tropical storm (SSHWS)
Duration	January 4 (Entered basin) – January 7
Peak intensity	85 km/h (50 mph) (3-min)  998 hPa (mbar)

Originally a tropical storm that formed over the South China Sea on January 1, Pabuk entered the Gulf of Thailand. Shortly afterward, Pabuk made landfall over southern Thailand on January 4 and crossed into the Andaman Sea. The IMD then initiated advisories on the storm, making Pabuk the earliest-forming cyclonic storm for this basin, surpassing Hibaru in 2005, as well as the first cyclonic storm with a name originally assigned by RSMC Tokyo.[5] Over the next few days, Pabuk continued moving west-northwestward, before weakening into a well-marked low on January 7. The system's remnant low then turned to the northeast, subsequently dissipating on January 8.

Extremely severe cyclonic storm (IMD)
Category 5 tropical cyclone (SSHWS)
Duration	April 26 – May 4
Peak intensity	215 km/h (130 mph) (3-min)  932 hPa (mbar)

On April 26, a depression formed to the west of Sumatra, with the IMD giving the storm the identifier BOB 02. The system slowly organized while curving towards the northeast. On April 27, at 00:00 UTC, the IMD upgraded the system to a deep depression.[6] Later that day, the system intensified into Cyclonic Storm Fani, while shifting to the northwest. Development of the system proceeded very slowly for several days, with the cyclone struggling to intensify against the influence of moderate vertical wind shear.[7] At 12:00 UTC on 29 April, Fani was upgraded to a severe cyclonic storm, with the system beginning to undergo rapid intensification.[8][9] Fani continued rapidly intensifying, becoming an extremely severe cyclonic storm at 17:00 UTC on April 30.[10] The Joint Typhoon Warning Center (JTWC) upgraded the system to a Category 4 tropical cyclone on the Saffir–Simpson scale at 06:00 UTC on May 2, following which, rapid intensification resumed. The pressure decreased to 932 hPa (27.52 inHg),[11] three-minute sustained winds increased to 215 km/h (130 mph), and one-minute sustained winds to 280 km/h (175 mph), making the system the equivalent of a Category 5 major hurricane.[12] On May 3, at 02:30 UTC (8:00 a.m. IST) Fani made landfall on Puri, in Odisha,[13][14] weakening to a Category 1-equivalent very severe cyclonic storm soon after landfall, subsequently weakening to a cyclonic storm several hours later.[15] On May 4, Fani weakened into a deep depression and moved into Bangladesh.[16] Later that day, Fani degenerated into a well-marked low,[17] before dissipating on the next day.

Very severe cyclonic storm (IMD)
Category 3 tropical cyclone (SSHWS)
Duration	June 10 – June 17
Peak intensity	150 km/h (90 mph) (3-min)  970 hPa (mbar)

In early June, a strong pulse of the Madden-Julian Oscillation (MJO) tracked eastwards into the tropical Indian Ocean, leading to increased cloudiness and rainfall across the region.[18] On June 9, the India Meteorological Department (IMD) noted the development of a low-pressure area over the southeastern Arabian Sea, to the north of the Maldives. Early on June 10, a depression formed in the Arabian Sea, just northwest of the Maldives, and the IMD gave the storm the identifier ARB 01. As the system moved northward, it gradually strengthened, becoming a deep depression, before intensifying further into Cyclonic Storm Vayu later that day. After being upgraded by the IMD to a severe cyclonic storm on June 11, and concurrently by the JTWC to a Category 1 tropical cyclone on the Saffir–Simpson hurricane wind scale (SSHWS), the system began a period of rapid intensification. Vayu strengthened into a very severe cyclonic storm soon afterward, and became a Category 2-equivalent very severe cyclonic storm on June 12. On June 13, the influence of a strengthening subtropical ridge over Saudi Arabia caused Vayu to gradually slow down and turn to the west, as it approached the coastline of the state of Gujarat in northwestern India.[19][20] Later that day, at 06:00 UTC, Vayu reached its peak intensity as a very severe tropical cyclone, with three-minute sustained winds of 150 km/h (90 mph) and a minimum pressure of 970 hPa (28.64 inHg).[21] On June 14, Vayu began to weaken, as it tracked slowly westward, away from the Gujarat coastline due to strong wind shear.[22] On June 16, an approaching mid-latitude trough weakened the areas of high pressure centered to the west and northeast,[23] which recurved Vayu sharply to the northeast.[24] Upon weakening further to a cyclonic storm, strong low-level southwesterly flow caused the system to accelerate northeastwards through the break in the blocking high-pressure ridge, back towards the Gujarat coast.[23][25] At 03:00 UTC on 17 June, Vayu weakened into a deep depression,[26][27] before weakening further to a depression six hours later.[28] Soon afterward, Vayu weakened into a well-marked low, just off the coast of Gujarat.[29] Very early on June 18, Vayu's remnants crossed over the Gujarat coast and moved inland for another day, before dissipating on June 19.

Deep depression (IMD)
Duration	August 6 – August 11
Peak intensity	55 km/h (35 mph) (3-min)  990 hPa (mbar)

On August 6, a depression formed over the northwestern Bay of Bengal, with the IMD giving the storm the identifier BOB 03. Soon afterward, the system intensified into a deep depression, while approaching the north Odisha coastline. On August 7, around 08:00–09:00 UTC, the deep depression made landfall along the north Odisha-West Bengal coastline. Early on August 11, it dissipated.

Heavy rains battered much of Odisha, with accumulations peaking at 382.6 mm (15.06 in) in Lanjigarh.[30] Flooding across the state killed three people, left two missing, and affected 130,000 others. A total of 2,081 homes suffered damage, and 14,332 people required evacuation.[31]

Very severe cyclonic storm (IMD)
Category 2 tropical cyclone (SSHWS)
Duration	September 22 – September 25
Peak intensity	140 km/h (85 mph) (3-min)  978 hPa (mbar)

A depression formed in the Arabian Sea and soon intensified into a cyclonic storm and was named Hikaa. The system gradually intensified into a severe cyclonic storm and then reached its peak intensity as a very severe cyclonic storm with 85 mph 3-min sustained wind speeds. Hikaa weakened due to dry air intrusions and made landfall on Oman as a severe tropical cyclone. Hikaa quickly weakened after moving inland and later dissipated.

One person went missing after his boat sank off Duqm.[32] Off the Omani coast, a boat carried 11 Indian fishermen sank due to Hikaa. As of October 17, six of them were confirmed dead, and the other five remained missing.[33]

Depression (IMD)
Duration	September 29 – October 1
Peak intensity	45 km/h (30 mph) (3-min)  1002 hPa (mbar)

A depression formed over Gulf of Kutch and neighborhood Gujarat coast close to Kandla on September 30.[34][35] It weakened into a well-marked low pressure system with an eye visible on satellite at 00:00 UTC on October 1.[36]

Super cyclonic storm (IMD)
Category 4 tropical cyclone (SSHWS)
Duration	October 24 – November 1
Peak intensity	240 km/h (150 mph) (3-min)  922 hPa (mbar)

A depression formed in the Arabian Sea on October 24, with IMD giving it the identifier ARB 03, later intensifying into a deep depression before JTWC recognized it as Tropical Cyclone 04A. It further intensified and became a cyclonic storm, receiving the name Kyarr from IMD as the fifth cyclonic storm of the season. On October 25, owing to high sea surface temperatures, low shear and a moist environment, Kyarr began a period of rapid intensification and strengthened into a very severe cyclonic storm. Three hours later, Kyarr became an extremely severe cyclonic storm. Early on October 27, Kyarr intensified into a super cyclonic storm, becoming the first one in the basin since Gonu in 2007. The system continued to intensify, attaining maximum three-minute sustained winds of 240 km/h (150 mph) and a minimum barometric pressure of 922 hPa (27.23 inHg), Kyarr began slowly weakening on October 29 as it headed southwest towards the direction of Somalia. Kyarr dissipated off the coast of Somalia on November 1.

Extremely severe cyclonic storm (IMD)
Category 3 tropical cyclone (SSHWS)
Duration	October 30 – November 7
Peak intensity	185 km/h (115 mph) (3-min)  956 hPa (mbar)

A well-marked low pressure area strengthened into a depression on October 30.[37] The depression continued strengthening as it entered a more favorable environment and was upgraded into a Cyclonic Storm on November 1. Maha continued to intensify, fluctuating in intensity for the next 2 days as it moved along the Indian coast, producing rough surf and moderate coastal flooding along the way before becoming a Very Severe Cyclonic Storm on November 3 and then into an Extremely Severe Cyclonic Storm the next day as it moved parallel to the Indian coast. Maha then began to stall in the Arabian Sea as it reached peak intensity due to a lack of steering currents. Upwelling began to take its toll on the storm, and it weakened back to a Cyclonic Storm as it approached Gujarat. It then made landfall near Gujarat as a tropical depression and quickly weakened afterwards.

In preparation of Maha's impacts, orange alert was issued in four districts of Kerala.[38]

Very severe cyclonic storm (IMD)
Category 3 tropical cyclone (SSHWS)
Duration	November 6 – November 11
Peak intensity	140 km/h (85 mph) (3-min)  976 hPa (mbar)

On November 6, the remnants of Severe Tropical Storm Matmo traversed into the Bay of Bengal and developed into Cyclonic Storm Bulbul. The system quickly intensified into a Severe Cyclonic Storm over the next day. As it continued north, it then strengthened into a Very Severe Cyclonic Storm as the IMD issued coastal warnings for West Bengal.

Bulbul then underwent rapid intensification, becoming a very severe cyclonic storm on November 8.[39]

It was the second Severe Cyclonic Storm to make landfall in West Bengal after Cyclone Aila. The storm produced heavy rain over many parts of West Bengal with Digha receiving 98 mm, Kolkata receiving 101 mm, Halisahar recording 95 mm and Dumdum receiving 90 mm of rain. Strong winds were also reported in many parts of South Bengal. Strong winds of 75 km/h also battered the Kolkata by uprooting many trees. One youth was killed due to uprooting of trees before the storm made landfall.

Cyclonic storm (IMD)
Tropical storm (SSHWS)
Duration	December 2 – December 7
Peak intensity	75 km/h (45 mph) (3-min)  998 hPa (mbar)

On December 2, a depression formed over the southwestern Arabian Sea, east of Somalia. It strengthened into a cyclonic storm on December 4 owing to favorable conditions in the surrounding area, earning the name Pawan.[40] The system continued north, gaining a little more strength, and then turned west the following day,[41] Pawan struggled to maintain its structure due to a high amount of wind shear, but continued to move west towards Somalia. This wind shear caused Pawan's convection to briefly dissipate, but it soon regenerated. Pawan eventually made landfall in the Puntland region of Somalia, just south of Eyl, late on December 6, bringing heavy rain and mudslides to the surrounding areas. It then degenerated into a well-marked low-pressure area inland on December 7.[42]

Pawan killed six people in Somalia.[43] Rainfall accumulations brought by Pawan reached up to 3 inches in Somalia, an unusually large amount of rain for December, resulting in flash flooding in the region. Two vehicles were swept away by torrential rain generated by the storm in Bosaso, while two boats capsized off the coast of Eyl due to rough surf.[42][44] Pawan was the first tropical cyclone to make landfall in Somalia since Cyclone Sagar in 2018.

Deep depression (IMD)
Tropical storm (SSHWS)
Duration	December 3 – December 5
Peak intensity	55 km/h (35 mph) (3-min)  1000 hPa (mbar)

On December 3, a depression formed over the east-central Arabian Sea, with the IMD marking it as Depression ARB 06. It gradually strengthened into a deep depression soon after. Initial forecasts expected the system to intensify into a cyclonic storm, however, a high amount of wind shear caused it to weaken substantially, and it weakened into a low-pressure area on December 5, west of the Indian coast.

Heavy rains associated with the depression caused extensive flooding in Tamil Nadu.[45] Twenty-four-hour accumulations exceeded 150 mm (5.9 in) in many areas, including 190 mm (7.5 in) in Sathankulam.[46] Officials issued extreme rainfall warnings for six districts and more than 21,500 trained volunteers were placed on standby. The Paravanar River topped its banks, flooding an estimated 10,000 homes.[47] A total of 1,305 huts and 465 homes were destroyed across Tamil Nadu.[48] During then night of December 2, three homes collapsed in Mettupalayam killing 17 occupants. Eight other people died in rain-related incidents.[49]

Deep depression (IMD)
Duration	December 8 – December 10
Peak intensity	55 km/h (35 mph) (3-min)  1000 hPa (mbar)

On December 6, the JTWC began to monitor an area of low pressure near the newly-formed Cyclonic Storm Pawan. Two days later, on December 8, the low gained more convection and a defined circulation while moving westward, with the IMD classifying the system as Depression ARB 08. The system later intensified into a deep depression during the early hours of December 9. On December 10, the system degenerated into a well-marked low off the coast of Somalia.