The scope of this article is limited to the Indian Ocean in the Northern Hemisphere, east of the Horn of Africa and west of the Malay Peninsula.

It slowly consolidated, and the Thai Meteorological Department (TMD) designated the active low pressure area as a tropical depression on May 1 in the Gulf of Thailand.

The TMD issued heavy rain and flash flood warnings for western provinces during the system's passage over the Isthmus of Kra.

[4] The next day, Prachuap Khiri Khan Province was declared a disaster zone after low-lying areas were flooded with waters up to one metre deep.

[6] This system was not considered to be a tropical depression by any other agencies while in the Gulf of Thailand, but was tracked by the Joint Typhoon Warning Center.

[8] Heavy rains caused by the rainbands of the cyclone led to the third One Day International cricket match between India and Bangladesh being abandoned.

With a favorable upper-level environment and warm sea surface temperatures, it rapidly intensified to attain peak winds of 240 km/h (150 mph) on June 3, as warned by the India Meteorological Department.

Intense cyclones like Gonu have been extremely rare over the Arabian Sea, as most storms in this area tend to be small and dissipate quickly.

Over the next few days, it developed deep flaring convection near an exposed low-level circulation centre (LLCC) as it drifted in the open sea.

[13] Despite moderate to high vertical wind shear, the disturbance produced surface pressure falls of up to 2.7 mbar (hPa) in Port Blair, in the Andaman Islands, on June 19.

[16] Several hours later, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert (TCFA), with winds near 30 knots (56 km/h; 35 mph).

[20] The JTWC issued its final advisory later, as the system began to weaken due to land interaction and wind shear.

[25] The JTWC noted in its Significant Tropical Weather Outlook for the North Indian Ocean on June 24 that strong monsoonal low-level flow contributed to increased cyclonic vorticity, with low vertical wind shear and warm sea surface temperatures.

[12] As it moved northwest just off the Pakistan coast, winds of about 26 knots (48 km/h; 30 mph) and a surface pressure of 990 mbar (hPa) were observed in Karachi near midday on June 25.

[30] After further organization, it made its second landfall at about 0300 UTC June 26 along the Makran coast, near Ormara and Pasni, Balochistan province, in southwestern Pakistan.

[34] The cyclone trapped 2 merchant ships: Al-Picaso and Lady Hamad, and 4 fishing boats: Al-Taif, Al-Noor, Sumbal Sultani and Al-Tariq, 100 nmi (190 km; 120 mi) off Karachi.

The Pakistan Navy rescued 56 sailors from the merchant ships and 36 fishermen from the fishing boats after they were detected by Breguet Atlantique aircraft.

[35] The heavy downpour also flooded the Kech Korandi riverine, inundating the city of Turbat and causing more than 10,000 people to evacuate their houses.

[36] At least 380 people died in Balochistan,[37] with another 250 dead in Sindh and 100 in the North-West Frontier Province,[38] and further rains associated with the remnants of the cyclone hampered rescue efforts.

[43] The Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert shortly after, noting that observations from the eastern coast of India had recorded falls in pressure corresponding with the system's development.

The PMD stated that the remnants "had the potential" to cause widespread heavy rain with strong winds in Sindh, Balochistan, Azad Kashmir and North-West Frontier provinces.

[50] In its fourth advisory on July 1, the PMD warned about the "high probability" of the system moving westward towards southern Sindh (instead of northwestward as previously projected), and regenerating over the Arabian Sea.

[52] Eventually, the circulation centre became fully exposed in unfavourable conditions, and the JTWC declared it "no longer suspect for development" later that day.

[53] While it was over western India adjoining the Arabian Sea, the deep convection associated with the remnants of the cyclone brought heavy rains to Maharashtra, causing disruptions in transport due to floods and high winds in Mumbai.

[55] On July 1, the Naval Research Laboratory (NRL) began to track a developing disturbance in the north Bay of Bengal.

[56] The system was noted in the Significant Tropical Weather Advisory issued by the Joint Typhoon Warning Center (JTWC) that same day.

[63] On August 5, a low pressure area that had lingered in the northwestern Bay of Bengal organised into a depression about 230 km southeast of Balasore.

[12] On October 27, a westward-moving disturbed area of weather formed about 885 nm east of Cape Guardafui, Somalia was designated Depression ARB 02/2007 by the IMD.

It gradually became better organised as it passed to the south of the islands, and the system was designated Depression BOB 09 by the India Meteorological Department early on November 11.

[79] As it intensified to a Category 4-equivalent cyclone on November 14, thousands of emergency officials were put on standby in eastern India and Bangladesh in advance of the storm's arrival.