Severe Tropical Storm Sonamu (Auring) Severe tropical storm (JMA) Tropical storm (SSHS) DEL GALLEGO CAMARINES

SUR S/Y: 2013-2014 DEL GALLEGO NATIONAL HIGH SCHOOL

PROJECT IN
Duration January 1 January 10 Peak intensity 95 km/h (60 mph) (10min) 990 mbar (hPa) Early on January 1, the JMA reported that a tropical depression had developed, about 1,090 km (680 mi) to the southwest of Hagta, Guam.[11]Over the next couple of days, the depression moved towards the northwest and gradually developed further in an area of moderate vertical windshear.[11][12] Late on January 2, the depressions low level circulation center passed over the Philippine island of Mindanao but maintained its deep convective banding, which prompted the JTWC to issue a tropical cyclone formation alert.[13] During the next day PAGASA named the depression Auring as the system moved westwards and entered the Sulu Sea, before the JTWC initiated advisories and designated it as 01W.[14][15][16] The JMA subsequently reported later that day that the depression had developed into a tropical storm and named it Sonamu before the JTWC followed suit early on January 4, as the system continued to consolidate.[11][17] During that day, Sonamu intensified further before the JMA reported that the system had peaked early the next day, as a severe tropical storm with 10-minute sustained windspeeds of 95 km/h (60 mph).[11] Early on January 8, the JMA and JTWC reported that Sonamu had weakened into a tropical depression, before it dissipated during January 10, about 100 km (60 mi) to the west of Bintulu, in Eastern Malaysia.[11]

SCIENCE
( LIST OF TYPHOON JAN.- AUG 2013) SUBMITTED BY: Jessa B. Gruezo

SUBMITTED TO: MS. MARICRIS NATAO Severe Tropical Storm Sonamu (Auring)

Severe tropical storm (JMA) Tropical storm (SSHS)

Tropical Depression (Bising) Tropical depression (JMA)

Duration Duration January 1 January 10

January 6 January 13

Peak intensity 55 km/h (35 mph) (10min) 1002 mbar (hPa) Early on January 6, the JMA started to monitor a tropical depression that had developed, about 480 km (300 mi) to the southeast of Melekeok, Palau.[19]Over the next few days the JMA continued to monitor the system as a tropical depression before PAGASA named it Bising during January 11. On January 13, the PAGASA downgraded the system to a low-pressure area, before it merged into a bomb cyclone developing in the southern sea of Japanlate on the same day.[20][21] The weather system caused moderate to heavy rains across Bicol Region,Eastern Visayas, Central Visayas and Mindanao.[citation needed] Tropical Storm Shanshan (Crising)[edit source | editbeta]
Tropical storm (JMA) Tropical depression (SSHS)

Peak intensity 95 km/h (60 mph) (10min) 990 mbar (hPa) Early on January 1, the JMA reported that a tropical depression had developed, about 1,090 km (680 mi) to the southwest of Hagta, Guam.[11]Over the next couple of days, the depression moved towards the northwest and gradually developed further in an area of moderate vertical windshear.[11][12] Late on January 2, the depressions low level circulation center passed over the Philippine island of Mindanao but maintained its deep convective banding, which prompted the JTWC to issue a tropical cyclone formation alert.[13] During the next day PAGASA named the depression Auring as the system moved westwards and entered the Sulu Sea, before the JTWC initiated advisories and designated it as 01W.[14][15][16] The JMA subsequently reported later that day that the depression had developed into a tropical storm and named it Sonamu before the JTWC followed suit early on January 4, as the system continued to consolidate.[11][17] During that day, Sonamu intensified further before the JMA reported that the system had peaked early the next day, as a severe tropical storm with 10-minute sustained windspeeds of 95 km/h (60 mph).[11] Early on January 8, the JMA and JTWC reported that Sonamu had weakened into a tropical depression, before it dissipated during January 10, about 100 km (60 mi) to the west of Bintulu, in Eastern Malaysia.[11] Within the Philippines, 1 person died, while a passenger ship was stranded near the coast of Dumaguete City on January 3 before being rescued.[18]

Duration

February 18 February 23

Duration

June 6 June 12

Peak intensity 65 km/h (40 mph) (10min) 1002 mbar (hPa)

Peak intensity 85 km/h (50 mph) (10min) 990 mbar (hPa) Tropical Depression 03W formed east of the Philippines on June 6.[31] Moving in a general northward direction, the storm slowly began to intensify. The JMA issued their first tropical cyclone advisory on the developing system at 0000 UTC on June 8.[32] The tropical depression intensified further and was reclassified as Tropical Storm Yagi at 1200 UTC later that day by the JMA while still east of the Philippines.[33] The JTWC still considered the system as a tropical depression at the time, though the agency upgraded the storm's intensity six hours later. Slow, albeit gradual strengthening followed as the storm slowed in forward motion.[34][35] Yagi eventually peaked as a moderate tropical storm with a minimum barometric pressure with winds of 85 km/h (50 mph), gusting to 120 km/h (75 mph).[36] However, the storm was soon impacted by northwesterly wind shear, causing the system to become disorganized and weaken in intensity.[37] Yagi was downgraded back to tropical depression strength by the JMA at 1800 UTC on June 12, constituting the last advisory on the cyclone issued by the agency.[38] The JTWC continued to track the storm until 0000 UTC on June 13, by which time Yagi had fully dissipated.[34] Despite forecasts that Yagi would not significantly affect land, the PAGASA advised local disaster coordination councils and relief agencies to prepare for any imminent threat posed by the tropical storm. The National Disaster Risk Reduction and Management Council ordered local chapters to prepare for potential emergencyevacuations from disaster areas.[39] As a developing tropical cyclone, Yagi enhanced monsoonal flow into areas of the Philippines, causing extensive rainfall to some areas, particularly the Greater Manila Area. Thus, the rains caused the

On February 18, the JMA and PAGASA started to monitor a tropical depression, that had developed about 750 km (470 mi) to the southeast of General Santos City in southern Mindanao.[22][23] The JTWC upgraded the system to a tropical depression and designated it 02W early on February 19, but it issued a final warning on February 21 because of strong wind shear.[24][25] On February 20, classes in three cities in Cebu were suspended due to heavy and continuous rains.[26] Early on February 22, JMA upgraded the system to a tropical storm and named it Shanshan whereas the JTWC downgraded the system to a tropical disturbance instead.[27][28] Shanshan was downgraded to a tropical depression by JMA on February 23.[29] Heavy rains from the storm triggered significant flooding in the southern Philippines that killed four people and left two others missing. A total of 262,880 people were affected throughout the country, nearly half of whom were in the Davao Region. In terms of structural impact, 53 homes were destroyed while 119 more were damaged. Agricultural losses amounted to11.2 million (US$255,000).[30] Tropical Storm Yagi (Dante)[edit source | editbeta] Tropical storm (JMA) Tropical storm (SSHS)

PAGASA to officially announce the beginning of the rainy season for the island chain early on June 10.[40] As a weakening tropical cyclone, Yagi brought locally heavy rainfalls on the island of Honshu, though due to its rapid weakening it did not pose as a significant threat to Japan.[41] Tropical Storm Leepi (Emong)[edit source | editbeta] Tropical storm (JMA) Tropical storm (SSHS)

Due to heavy rainfall from the precursor tropical wave, the PAGASA issued a flash flood warning for parts of Mindanao on June 15.[47]Overnight, heavy precipitation was reported in Davao City, and as such city-emergency response teams were placed on alert for a potential flooding and evacuation scenario.[48] As a result of rainfall in Greater Manila, the Metropolitan Manila Development Authority began to offer free rides to stricken commuters.[49] This system caused rains over parts of the Philippines including Southern Luzon, Visayas and Northern Mindanao. Moving northward, Leepi passed east of Taiwan, but its outer rainbands caused downpours over eastern areas of the island.[50] While moving through the Ryukyu Islands, sustained winds in Okinawa reached 55 km/h (35 mph) and gusts peaked at 87 km/h (54 mph).[51] Despite dissipating and losing much of its convection prior to reaching Japan, the remnants of Leepi continued to drop heavy rainfall. In Umaji, Kchi, a station recorded 354.5 mm (13.96 in) of rain in a 24-hour period, more than half of the average June rainfall for the station.[52] Tropical Storm Bebinca (Fabian)[edit source | editbeta] Tropical storm (JMA) Tropical storm (SSHS)

Duration

June 16 June 21

Peak intensity 75 km/h (45 mph) (10min) 994 mbar (hPa) Early on June 16, both the JMA and PAGASA reported that a tropical depression had developed about 830 km (520 mi) to the southeast of Manilla in the Phillippines, with the latter naming it as Emong.[42][43] Over the next two days the depression gradually developed further, with the JTWC starting to issue warnings on the system and designated it as Tropical Depression 04W late on June 17. The JMA and JTWC subsequently reported during the next day that the depression had developed into a tropical storm with the latter naming it Leepi.[42][44] On June 20, Leepi began to interact with atropical upper tropospheric trough (TUTT) cell to the east, resulting in strong northwesterly vertical wind shear; as such, the low-level circulation center of the cyclone was displaced to the northeast of the convection, exposing the center in addition to several smaller toroidal circulations embedded within the primary circulation. Based on this occurrence, the JTWC downgraded the system to tropical depression intensity at 0300 UTC that day.[45] Wind shear continued to take its toll on the system, and as such the JMA issued its last advisory on the system at 0000 UTC on June 21.[46]

Duration

June 19 June 24

Peak intensity 75 km/h (45 mph) (10min) 990 mbar (hPa) In mid-June, an area of strong albeit disorganized convection persisted in theSouth China Sea, with its center approximately 1,110 km (690 mi) south ofHong Kong.[53] The disturbance gradually organized, and became sufficiently organized to be classified as a tropical depression by the JMA at 1800 UTC on June 19;[54] the PAGASA followed suit six hours later, naming the systemFabian.[55] Despite being hampered by wind shear generated by a nearby subtropical ridge, the depression

maintained a well defined center of circulation, allowing the system to intensify and organize throughout the day on June 20;[56] at 0000 UTC the following day, the JMA upgraded the cyclone to tropical storm strength, earning the designation of Bebinca.[57] Following this upgrade in strength, however, Bebinca failed to intensify further, and leveled out in intensity prior to making landfall on Hainan on June 22. Bebinca's passage over the island weakened the system to tropical depression strength, and, despite moving over the Gulf of Tonkin, failed to restrengthen before making a final landfall on June 23 east of Hanoi. Due to the potential effects of Bebinca, Sanya Phoenix International Airport cancelled or delayed 147 inbound and outbound flights, leaving 8,000 passengers stranded. Other forms of transportation in the Hainan area were also disrupted by the impending approach of the tropical storm.[58] In Beibu Bay on June 21, a fishing boat with four fishermen on board lost communication contact with the mainland;[59] they were later found the following day.[60] Rainfall in Hainan peaked at 227 mm (8.9 in) in Sanya. A total of 11.55 million people were affected.[61] Damage across Hainan Island amounted to 32.46 million (US$5.3 million).[62] Heavy rains affected several provinces in northern Vietnam, with a storm maxima of 356 mm (14.0 in) Hon Ngu, Nghe An Province.[63] Severe Tropical Storm Rumbia (Gorio)[edit source | editbeta] Main article: Tropical Storm Rumbia (2013) Severe tropical storm (JMA) Category 1 typhoon (SSHS)

system was designed as Invest 99W by the JTWC. Initially tracking southward, the invest-disturbance moved east and then recurved to the west.[64] Steadily organizing, the disturbance was classified as a tropical depression on June 27.[65] The initial tropical depression moved towards the northwest as the result of a nearby subtropical ridge.[66] On June 28, the disturbance strengthened to tropical storm strength,[67] and subsequently made its first landfall on Eastern Samar in the Philippines early the following day.[68][69] Rumbia spent roughly a day moving across the archipelago before emerging into the South China Sea.[70][71] Over open waters, Rumbia resumed strengthening, and reached its peak intensity with winds of 95 km/h (50 mph) on July 1, ranking it as a severe tropical storm.[72] The tropical cyclone weakened slightly before moving ashore the Leizhou Peninsula late that day. Due to land interaction, Rumbia quickly weakened into a low pressure area on July 2 and eventually dissipated soon afterwards.[citation needed] Prior to moving over the Philippines, extensive preparatory measures were undertaken by local and government relief agencies.[73] In the provinces of Eastern Visayas and Caragas, an estimated 6.9 million was allocated to relief materials.[74] Upon landfall, Rumbia caused extensive flooding across multiple islands, causing the cessation of transportation services and displacing thousands of people.[75] Power outages also resulted from the heavy rain and strong winds.[76] At its landfall on Leizhou Peninsula in China, Rumbia damaged large swaths of agricultural cropland and destroyed at least 112 buildings, causing 7.68 million in damage.[77] Overall, Rumbia killed at least 55 people in the Philippines and China, mostly as a result of floods.[78][79] Typhoon Soulik (Huaning)[edit source | editbeta] Main article: Typhoon Soulik (2013) Typhoon (JMA) Category 4 typhoon (SSHS)

Duration

June 27 July 2

Peak intensity 95 km/h (60 mph) (10min) 985 mbar (hPa) In late-June, an area of disturbed weather within the ITCZ persisted to the east of the Philippines, accompanied by a low-pressure area. At 1200 UTC on June 26, the Duration July 7 July 14

Peak intensity 185 km/h (115 mph) (10min) 925 mbar (hPa) In early July, an upper-level cold-core low persisted well to the northeast ofGuam.[80] Gaining tropical characteristics, the system soon developed a surface low and became a tropical depression early on July 7.[81] Tracking generally westward, a motion it would retain for its entire existence, the depression underwent a period of rapid intensification starting on July 8 that culminated in Soulik attaining its peak strength early on July 10.[82] At that time, the system had sustained winds estimated at 185 km/h (115 mph) andbarometric pressure of 925 mbar (hPa; 27.32 inHg).[83] Thereafter, an eyewall replacement cycle and cooler waters weakened the system.[84] Though it passed over the warm waters of the Kuroshio Current the following day,[85]dry air soon impinged upon the typhoon.[86] Soulik later made landfall late on July 12 in northern Taiwan before degrading to a tropical storm.[87][88] Briefly emerging over the Taiwan Strait,[89] the storm moved onshore for a second time in Fujian on July 13.[90][91] The system was last noted as a tropical depression early on July 14.[92] Striking Taiwan as a strong typhoon, Soulik brought gusts up to 220 km/h (140 mph) and torrential rains.[93] Numerous trees and power lines fell,[94] leaving roughly 800,000 without electricity.[95] Severe flooding prompted thousands to evacuate as well.[93] Four people lost their lives on the island while 123 more were injured.[96] Agricultural losses in Taiwan amounted to at least NT$1.27 billion (US$42.55 million).[97] In East China, more than 162 million people were affected by the storm. Heavy rains and typhoon-force winds caused extensive damage and killed three people in Guangdong and two in Jiangxi. More than 2,000 homes collapsed and losses reached 2.51 billion (US$408 million).[98] Tropical Storm Cimaron (Isang)[edit source | editbeta] Tropical storm (JMA) Tropical storm (SSHS)

Duration

July 15 July 18

Peak intensity 75 km/h (45 mph) (10min) 1000 mbar (hPa) Torrential rains over southern Fujian Province triggered significant flooding, with areas already saturated from Typhoon Soulik less than a week prior. A 24 hour peak of 505.3 mm (19.89 in) was measured in Mei Village, with an hourly maximum of 132.3 mm (5.21 in).[99] Many homes were inundated and several roads were washed out.[100] Some areas experienced 1-in-500-year flooding. Approximately 20.28 million people were affected by the storm, 8.92 million of whom were temporarily relocated. At least one person was killed and another was reported missing.[101] Direct economic losses from the storm amounted to 1.552 billion (US$252.8 million).[102] An unusually intense thunderstorm associated with Cimaron produced a prolific lightningevent over Xiamen, with 406 strikes recorded in two hours.[103] Severe Tropical Storm Jebi (Jolina)[edit source | editbeta] Severe tropical storm (JMA) Tropical storm (SSHS)

Duration

July 26 August 3

Duration

August 2 August 8

Peak intensity 100 km/h (65 mph) (10min) 985 mbar (hPa) On July 26, a low pressure area was observed 600 km (370 mi) east ofGeneral Santos City and was embedded along the intertropical convergence zone that brought heavy rains to Mindanao.[104] During the next three days, the low pressure area crossed the Philippines and arrived on the West Philippine Sea on July 30, located west of Batangas.[105] After favorable conditions, both PAGASA and JMA upgraded the system into a tropical depression and was named Jolina. On July 31, the JMA upgraded the system into a tropical storm and was given the international name Jebi.[106] In Cotabato City, incessant rains caused by the low-pressure area in Mindanao submerged 25 of its 37 villages. The floods forced the city government to suspend classes for elementary both public and private schools. Heavy rains also flooded areas around the Liguasan marshland, including 14 low-lying towns in Maguindanao and seven towns in North Cotabato.[107] At least six people were killed in Vietnam. The most extensive losses took place in Quang Ninh Province where 320 homes and 200 hectares of crops were damaged. Losses in the area amounted to VND10 billion (US$476,000).[108] Tropical Storm Mangkhut (Kiko)[edit source | editbeta] Tropical storm (JMA) Tropical storm (SSHS)

Peak intensity 75 km/h (45 mph) (10min) 992 mbar (hPa) On August 2, a low pressure area embedded along the intertropical convergence zone has formed to the east of Mindanao. During the next 2 days, the system crossed Mindanao and emerged over the Sulu Sea as it was located to the west of Dumaguete City. On August 5, PAGASA and JMA upgraded the system into a tropical depression and was given the local nameKiko. Over the last 24 hours, the tropical depression strengthened into a tropical storm and was given the international name Mangkhut by JMA. On August 7, Tropical Storm Mangkhut made landfall on Thai Binh Province in Vietnam, the same area where Tropical Storm Jebi made landfall just a week ago, claiming lives.[109][110][111][112][113] Downpours throughout Wednesday night till Thursday were recorded at 80mm deep on streets of the capital, causing difficulties for many people to go to work. Meanwhile, rainfall went up to about 300mm in central Thanh Hoa and northern Hai Phong city amid wind with a speed hitting 6288 km per hour.[114][115] Typhoon Utor (Labuyo)[edit source | editbeta] Main article: Typhoon Utor (2013) Typhoon (JMA) Category 4 super typhoon (SSHS)

Duration

August 8 August 18

Peak intensity 195 km/h (120 mph) (10min) 925 mbar (hPa) During August 8, the JMA, JTWC and PAGASA reported that a tropical depression had developed about 560 km (350 mi) to the north of Palau, with the latter naming it as Labuyo as it approached the Philippine Area of Responsibility.[116][117][118] During that day the depression moved westwards and consolidated within a favourable environment of weak vertical wind shearand strong outflow, which was enhanced by a TUTT Cell located to the northwest of the disturbance.[119][120] During the next day, the JTWC and the JMA reported that the depression had developed into a tropical storm, with the latter naming it as Utor.[121][122] Shortly thereafter, Utor began undergoing explosive intensification, achieving typhoon status early on August 10, as an eye developed.[123] On August 11, under the influence of low vertical wind shear, very favourable poleward and westward outflow, and warm sea surface temperature, Utor began to intensify more and formed a clear eye.[124] At 12:00 UTC, Typhoon Utor attained peak intensity by the ten-minute maximum sustained winds reaching 1195 km/h (105 mph) and the atmospheric pressure decreasing to 925 hPa (27.3 inHg). The system became exceptionally symmetrical, as the convective bands had further deepened and wrapped tighter around a 13 nautical miles (24 km; 15 mi) pin-hole eye, prompting JTWC upgrading Utor to a super typhoon.[125] Due to land interaction with Luzon, the pin-hole eye filled in quickly; as a result, JTWC downgraded Utor to a typhoon at 18:00 UTC.[126] Tracking along the southern periphery of asubtropical ridge to the north, Utor made landfall over northern Luzon around 19:00 UTC (03:00 PHT on August 12).[127]

On August 12, Utor moved out of the Philippines and emerged out to the South China Sea as a category 2 system, after weakening from the mountainous region in the Philippines. However, favourable conditions persisted, and Utor strengthened back to a category 3 status only several hours after returning to sea. After moving away from the Philippines, wind shear increased and sea temperatures dropped, somewhat slowing Utor's intensification. The system proceeded to track in a NW direction slowly.[128][129] On August 14, Utor weakened to a strong category 2 system with winds of over 170 km/h due to interaction with land and unfavourable conditions. The system moved slowly towards southern China.[130][131] On 15:00 August 14 local time, Utor made landfall in China in the Guangdongprovince as a category 1 system with maximum winds of 145 km/h (90 mph), where it quickly weakened. On August 15, after Utor made landfall in China. The remnants of Utor continued to travel slowly in a northerly direction.[citation needed] The Aurora province suffered the most damage from the typhoon, especially the coastal town of Casiguran. The capital of Manilareceived heavy rain but no significant damage was reported. 80% of the infrastructure was believed to be destroyed at Casiguran, that is, about 2000 homes. A total of over 12,000 homes were damaged. The town was isolated from the rest of the area when Utor's wind toppled transmission lines and cut off power.[citation needed] 158,000 residents were evacuated in southern China. Hong Kong was hit by winds of up to 85 km/h while neighbouring Macao was battered with gusts of 70 km/h. 1 death was reported in China. Hundreds of flights have been cancelled and more have been delayed. A 190 metre long cargo ship was sunk off the coast of Hong Kong due to waves reaching up to 15 metres high. The crew abandoned the vessel and were saved by rescue workers.[132][133][134][135] In total, Utor has caused 25 deaths. Residents affected are amounted to about 2.5 million. The typhoon has topped 392 million USD of damage.[136][137][138][139] Severe Tropical Storm Trami (Maring)[edit source | editbeta] Main article: Severe Tropical Storm Trami (2013) Severe tropical storm (JMA) Category 1 typhoon (SSHS)

Duration

August 15 August 22

Peak intensity 110 km/h (70 mph) (10min) 965 mbar (hPa) On August 15, a low pressure system formed about 200 kilometers east ofHengchun, Taiwan, in the Pacific Ocean. As the system tracked towards the east steadily, it slowly strengthened in favourable conditions to a tropical depression on August 17, at which point PAGASA began to monitor the depression. The system was named 12W and was designated as Maring by PAGASA. Maring began to interact with another depression north of it, exhibiting Fujiwhara Effect.[citation needed] On August 18, 12W strengthened into a tropical storm, receiving the name ofTrami, while steadily tracking generally eastwards.[140] In the afternoon of August 18, as heavy rains poured down across Luzon, government officials were forced to suspend classes and government work in some cities. PAGASA subsequently issued several rainfall advisories. Majors areas in Metro Manila and nearby provinces reported severe flooding. TheMarikina River as high as 19 meters, forcing authorities evacuate nearby residents. 8 people in the Philippines have been immediately killed due to severe flooding. The provinces of Pampanga, Bataan, Cavite, Laguna together with the cities of Metro Manila declared a state of calamity.[141][142][143][144][145] On August 20, a sea warning was given off by the Central Weather Bureau of Taiwan at 11:30am local time due to Trami. A land warning followed at 8:30pm. At this point, Trami had also been upgraded to a category 1 system according to the Saffir Simpson hurricane wind scale. The Yaeyama Islands and Miyako Islands of Japan have been battered with gusts from Trami as the system headed for Taiwan and China.[146][147] On August 21, gale force winds struck heavily populated areas in northern Taiwan as Trami tracked in a westerly direction. The system brought torrential rainfall to the

area, with Taipei receiving 12 inches of rain. A landslide occurred in Hsinchu county and trapped 70 residents. 10 people have been injured in Taiwan and more than 6000 had to evacuate homes. Despite gusty conditions and heavy rainfall, Trami only caused minor damage in Taiwan.[148][149] Trami continued to move west, and made landfall in the Fujian province of China on August 22, 2:40am local time. Winds peaked at 126km/h, and immense downpours were recorded over the cities of Fujian, Ningde, Putian and Sanming. 191 counties throughout the province had over 100mm of rain. Many public services were seriously affected. Hundreds of thousands of residents were evacuated.[150][151] Trami weakened below typhoon intensity on August 23. The remnants of the system continued to move inland in a westerly direction.[citation needed] Trami killed 18 people in the Philippines and caused intensive flooding all over the nation. The system also intensified floods brought by earlier monsoonal rains in China, wreaking havoc. In total, Trami has caused 1.83 million USD of damage.[152][153][154] Tropical Depression 13W[edit source | editbeta] Tropical depression (JMA) Tropical depression (SSHS)

Duration

August 16 August 18

Peak intensity 55 km/h (35 mph) (10min) 996 mbar (hPa) On August 16, there was a tropical disturbance developing on the Ryukyu Islands. It developed into a Tropical Depression and interacted with Tropical Storm Trami. It hit the Eastern Chinese coast and dissipated on August 18.[citation needed] Severe Tropical Storm Pewa[edit source | editbeta] Severe tropical storm (JMA)

Category 1 typhoon (SSHS)

Duration

August 19 (Entered basin) August 19

Peak intensity 65 km/h (40 mph) (10min) 1004 mbar (hPa) On August 19, the JMA and JTWC reported that Tropical Storm Unala had moved into the Western Pacific basin from the Central Pacific, as it rapidly weakened and moved westwards into the periphery of Severe Tropical Storm Pewa.[157][158] The system was last noted by the JMA later that day as it weakened into a tropical depression.[159][160]

Duration

August 18 (Entered basin) August 26

Peak intensity 100 km/h (65 mph) (10min) 990 mbar (hPa) On August 16, a low pressure area located about 845 km (525 mi) to the south south-west of Johnston Atoll was upgraded to Tropical Storm Pewa, the 1st named Central Pacific storm since 2010.[155] Pewa continued to strengthen until the system crossed the International Date Line on August 18.[156] On August 19, the JTWC reported that Pewa had become equivalent to a category 1 hurricane on the SSHS, before reporting that the system had weakened into a tropical storm. Pewa absorbed two other storms that also crossed the dateline Tropical Storm Unala on August 19 and Tropical Depression 03C on August 20.[citation needed] Tropical Storm Unala[edit source | editbeta] Tropical storm (JMA) Tropical depression (SSHS)

Tropical Storm Kong-rey (Nando)[edit source | editbeta] On August 23, an area of convection persisted southeast of Manila. As indicated in global models, the system is forecast to consolidate as it moves poleward to more favorable environment conditions.[citation needed]On August 25 JMA announced the formation of a Tropical Depression to the east of the Philippines[161] and PAGASA allocated the designationNando.[162]

Kong-rey (Nando)

TS

Satellite image Current storm status Tropical storm (JMA) Current storm status Tropical storm (1-min mean) As of: Location: Winds:

Storm track

03:45 UTC August 27 19.1N 124.0W About 287 nmi (532 km; 330 mi) NE of Manila, Philippines 40 knots (75 km/h; 45 mph) sustained (10-min mean) 45 knots (85 km/h; 50 mph) sustained (1-min mean) gusting to 60 knots (110 km/h; 70 mph) 996 hPa (29.41 inHg)

Pressure:

Movement: N at 9 kn (17 km/h; 10 mph)