2002 Pacific typhoon season

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
2002 Pacific typhoon season
First system formed January 9, 2002
Last system dissipated December 11, 2002
Strongest storm1 Fengshen – 920 hPa (mbar), 185 km/h (115 mph) (10-minute sustained)
Total depressions 37
Total storms 26
Typhoons 15
Super typhoons 8 (unofficial)[nb 1]
Total fatalities 725
Total damage $9.537 billion (2002 USD)
1Strongest storm is determined by lowest pressure
Pacific typhoon seasons
2000, 2001, 2002, 2003, 2004

The 2002 Pacific typhoon season was an active season, with many tropical cyclones affecting Japan and China. Every month had tropical activity, with most storms forming from July through October. Overall, there were 37 tropical depressions declared officially or unofficially, of which 26 became named storms; of those, there were 15 typhoons, which is the equivalent of a minimal hurricane, while 8 of the 15 typhoon intensified into super typhoons unofficially by the JTWC.

The season began early with the first storm, Tapah, developing on January 10, east of the Philippines. Two months later, Typhoon Mitag became the first super typhoon [nb 1] ever to be recorded in March. In June, Typhoon Chataan dropped heavy rainfall in the Federated States of Micronesia, killing 48 people and becoming the deadliest natural disaster in the state of Chuuk. Chataan later left heavy damage in Guam before striking Japan. In August, Typhoon Rusa became the deadliest typhoon in South Korea in 43 years, causing 238 deaths and $4.2 billion in damage.[nb 2] Typhoon Higos in October was the third strongest typhoon to strike Tokyo since World War II. The final typhoon of the season was Typhoon Pongsona, which was one of the costliest storms on record in Guam; it did damage worth $700 million on the island before dissipating on December 11.

The western Pacific basin covers the Pacific Ocean, north of the equator and west of the International Date Line. Storms that form east of the date line and north of the equator are called hurricanes; see 2002 Pacific hurricane season. Tropical Storms formed in the entire Northwest Pacific basin are assigned a name by the Japan Meteorological Agency (JMA). Tropical depressions in this basin have the "W" suffix added to their number when classified by the Joint Typhoon Warning Center (JTWC). Tropical depressions that enter or form in the Philippine area of responsibility are assigned a name by the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA), which can result in the same storm having two names; in these cases both storm names are given below, with the PAGASA name in parentheses.

Seasonal summary and predictions

File:FEMA - 7423 - Photograph by Andrea Booher taken on 12-13-2002 in Guam.jpg
Damage from Typhoon Pongsona in Guam

On March 6, meteorologists from University College London at TropicalStormRisk.com issued a forecast for the season for above average activity, since sea surface temperatures were expected to be slightly warmer than usual; the group used data by the Joint Typhoon Warning Center (JTWC), and compared the potential 28.6 storms to the 30-year average of 26.3.[2] The group raised the number of predicted storms in April to 29.6, and again in early May to 30.5.[3][4] They ultimately overestimated the number of storms that would form.[5] The Laboratory for Atmospheric Research at the City University of Hong Kong also issued a season forecast in April 2002, predicting 27 storms with a margin of error of 3, of which 11 would become typhoons, with a margin of error of 2. The agency noted a stronger than normal subtropical ridge over the open Pacific Ocean, as well as ongoing El Niño conditions that favored development, but expected below-normal development in the South China Sea.[6] These predictions proved to be largely accurate.[7]

During the year, the Japan Meteorological Agency (JMA) issued advisories on tropical cyclones west of the International Date Line to the Malay Peninsula, and north of the equator, in its role as the official Regional Specialized Meteorological Center, as designated by the World Meteorological Organization in 1989. The JMA issued forecasts and analyses every six hours starting at midnight UTC using numerical weather prediction (NWP) and a climatological tropical cyclone forecast model. They used the Dvorak technique and NWP to estimate 10-minute sustained winds and barometric pressure.[8] The JTWC also issued warnings on storms within the basin, operating from Pearl Harbor in Hawaii and supplying forecasts to the United States Armed Forces in the Indian and Pacific Oceans. The agency moved their backup facility from Yokosuka, Kanagawa in Japan to Monterey, California in 2002. Several meteorologists left the agency near the beginning of the year, although the new forecasters compensated for their inexperience by relying on the consensus of various forecast models. In 2002, the JTWC began experimenting with five-day forecasts.[9]

During most of the year, sea surface temperatures were above normal near the equator, and were highest around 160° E from January to July, and in November. Areas of convection developed farther east than usual, causing many storms to develop east of 150° E. The average point of formation was 145.9° E, the easternmost point since 1951. Partially as a result, no tropical storms made landfall in the Philippines for the first time since 1951, according to the JMA. Two storms – Ele and Huko – entered the basin from the Central Pacific, east of the International Date Line. Overall, there were 26 named storms in the basin in 2002, which was slightly below the norm of 26.7. A total of 15 of the 26 storms became typhoons, a slightly higher than normal proportion.[8]

The season began early, but did not become active until June, when six storms passed near or over Japan after a ridge weakened.[8] Nine storms developed in July, many of which influenced the monsoon trough over the Philippines to produce heavy rainfall and deadly flooding.[10] The flooding was worst in Luzon, where 85 people were killed. The series of storms caused the widespread closure of schools and offices. Many roads were damaged, and the floods left about $1.8 million (₱94.2 million PHP)[nb 3] in crop damage, largely to rice and corn.[11] Overall damage from the series of storms was estimated at $10.3 million (₱522 million PHP).[12][nb 3] From June to September, heavy rainfall affected large portions of China, resulting in devastating flooding that killed over 1,500 people and left $8.2 billion (¥68 billion CNY) in damage.[13][nb 4] During this time, Tropical Storm Kammuri struck southern China with a large area of rainfall that damaged or destroyed 245,000 houses. There were 153 deaths related to the storm, mostly inland in Hunan,[15] and damage totaled $322 million (¥2.665 billion CNY).[16][nb 4] Activity shifted farther to the east after September, with Typhoon Higos striking Japan in October and Typhoon Pongsona hitting Guam in December.[8]

Storms

All storms named by the JMA, as well as other notable tropical cyclones, have complete sections below. The track maps plot the track and intensity of the storms; light and dark blue indicate tropical depression and tropical storm status, respectively, and intensifying colors of yellow through red correspond to the Saffir–Simpson hurricane wind scale from 1 to 5.

Tropical Storm Tapah (Agaton)

Tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration January 9 – January 14
Peak intensity 75 km/h (45 mph) (10-min)  996 hPa (mbar)

The first storm of the season was Tropical Storm Tapah, which formed on January 9 near Palau.[8] It developed from the monsoon trough and was first observed by the JTWC two days before its formation.[9] The system initially consisted of an area of convection with a weak circulation, located in an area of weak wind shear.[17] On January 10, the JMA classified the system as a tropical depression,[8] the same day that the JTWC initiated advisories on Tropical Depression 01W and PAGASA classified it as "Agaton". The storm moved west-northwestward due to a ridge to the north, and the system gradually became better organized.[17] On January 12, the JMA upgraded the depression to Tropical Storm Tapah, and later that day estimated peak winds of 75 km/h (45 mph).[8] Around that time, Tapah developed an eye feature beneath its convection, prompting both the JTWC and PAGASA to estimate peak winds of 95 km/h (60 mph).[17] An approaching trough weakened the ridge, which turned the storm to the northwest. Due to increasing wind shear,[9] convection gradually weakened, and the JMA downgraded Tapah to a tropical depression on January 13; however, other agencies maintained the system as a tropical storm. The next day, Tapah dissipated along the eastern coast of Luzon in the Philippines.[8][17]

Typhoon Mitag (Basyang)

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
150px 150px
Duration February 26 – March 9
Peak intensity 175 km/h (110 mph) (10-min)  930 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Mitag (2002)

Typhoon Mitag developed from a trough near the equator on February 25 near the Federated States of Micronesia (FSM). It moved westward through the archipelago and intensified into a typhoon, before passing near Yap on March 2.[18] High winds and heavy rainfall affected the state, causing an islandwide power outage and destroying hundreds of houses. Mitag severely damaged crops, resulting in food shortages. The rainfall and storm surge flooded much of the coastline as well as Yap's capital, Colonia. Damage totaled $150 million, mostly to crops. There was one death related to the storm's aftermath.[19]

After affecting Yap, Mitag turned to the northwest and later to the north due to an approaching trough.[9] It passed to the north of Palau, contributing to one death there. Despite predictions of weakening,[18] the typhoon continued to intensify, reaching peak 10-minute winds of 175 km/h (110 mph) on March 5.[8] The JTWC estimated peak 1-minute winds of 260 km/h (160 mph) when the storm was about 610 km (380 mi) east of Catanduanes in the Philippines; this made Mitag a super typhoon, the first one on record in the month of March. The combination of cooler air and interaction with the westerlies caused Mitag to weaken significantly. Only four days after reaching peak winds, the storm had dissipated well to the east of the Philippines.[18]

Tropical Depression 03W (Caloy)

Tropical depression (JMA)
Tropical depression (SSHWS)
150px 150px
Duration March 19 – March 25
Peak intensity 55 km/h (35 mph) (10-min)  1000 hPa (mbar)

On March 15, the JTWC began monitoring a tropical disturbance, and four days later upgraded it to a tropical depression near Palau.[9][18] The next day, both the JMA and PAGASA classified the system as a depression, and PAGASA named it "Caloy".[20] Moving west-northwestward due to a ridge to the north,[9] the depression moved across the Philippine island of Mindanao on March 21 and continued through the archipelago.[18] Owing to strong wind shear, the system never intensified,[9] and the JMA discontinued advisories on March 23 after the system reached the South China Sea.[20] The JTWC maintained the system as a tropical depression until March 25, when a mid-latitude trough absorbed the system off the east coast of Vietnam.[9]

Heavy rains from the depression affected the southern Philippines, causing flash flooding and landslides.[18] The storm damaged 2,703 homes, including 215 that were destroyed. Damage totaled about $2.4 million (₱124 million PHP).[nb 3] There were 35 deaths in the Philippines, mostly in Surigao del Sur in Mindanao from drownings.[18][21]

Typhoon Hagibis

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
150px 150px
Duration May 14 – May 21
Peak intensity 175 km/h (110 mph) (10-min)  935 hPa (mbar)

The monsoon trough spawned a tropical disturbance near the Caroline Islands in the middle of May.[9] By that time, the system was an area of convection with a weak circulation, although the system organized as outflow improved. It tracked northwestward within the monsoon trough,[22] steered by a mid-level ridge.[9] The system developed into a tropical depression on May 14 about 500 km (310 mi) southwest of Chuuk Lagoon,[8] and early the next day the JTWC initiated advisories.[9] For several days the depression remained weak, until it intensified into Tropical Storm Hagibis on May 16 about 200 km (120 mi) southwest of Guam.[8] The developing storm dropped rainfall on Guam that ended the island's wildfire season.[23] The storm quickly intensified, developing an eye feature later that day.[22] Early on May 18, the JMA upgraded Hagibis to a typhoon,[8] and around that time, an approaching trough turned the storm to the northeast.[22]

While accelerating northeastward, Hagibis developed a well-defined eye and underwent a period of rapid deepening.[22] On May 19, the JMA estimated peak 10-minute winds of 175 km/h (110 mph),[8] and the JTWC estimated 1-minute winds of 260 km/h (160 mph);[9] this made Hagibis a super typhoon, the second of the year. At the time of its peak, the typhoon was located about 305 km (190 mi) west-southwest of the northernmost Northern Marianas Islands.[22] Hagibis only maintained its peak for about 12 hours,[8] after which the eye began weakening.[22] The trough that caused the typhoon's acceleration also caused the storm to lose tropical characteristics, and dry air gradually became entrained in the circulation.[22] On May 21, Hagibis became extratropical to the east of Japan after having weakened below typhoon intensity. The remnants continued to the northeast and dissipated south of the Aleutian Islands on May 22.[8]

Severe Tropical Storm Noguri (Espada)

Severe tropical storm (JMA)
Category 2 typhoon (SSHWS)
150px 150px
Duration June 4 – June 11
Peak intensity 110 km/h (70 mph) (10-min)  975 hPa (mbar)

In early June, a disturbance within the monsoon trough persisted in the South China Sea to the east of Vietnam.[24] On June 4, a tropical depression developed just off the east coast of Hainan,[8] with a broad circulation and scattered convection. The system tracked slowly eastward due to a ridge to the north, and conditions favored intensification, including favorable outflow and minimal wind shear.[24] The JTWC initiated advisories on June 6,[9] and despite the favorable conditions, the depression remained weak. On June 7, the system briefly entered the area of responsibility of PAGASA, and the agency named it Espada. Later that day, the JTWC upgraded the depression to a tropical storm,[24] and on June 8 the JMA upgraded the depression to Tropical Storm Noguri halfway between Taiwan and Luzon.[8] Increased outflow from an approaching trough allowed the storm to quickly intensify. The JTWC upgraded Noguri to a typhoon late on June 8,[9] after an eye developed. By that time, the storm was moving to the northeast due to a building ridge to the southeast.[24] The JMA only estimated peak 10-minute winds of 110 km/h (70 mph), making it a severe tropical storm.[8] However, the JTWC estimated peak winds of 160 km/h (100 mph),[9] after the eye became well-organized. Increasing wind shear weakened Noguri, and the storm passed just west of the Miyako-jima on June 9. The convection diminished, and the JTWC declared Noguri extratropical while the storm was approaching Japan.[24] The JMA continued tracking the storm until it dissipated over the Kii Peninsula on June 11.[8]

While the storm passed south of Taiwan, it dropped heavy rainfall peaking at 320 mm (13 in) in Pingtung County.[24] Rainfall in Japan peaked at 123 mm (4.8 in) at a station in Kagoshima Prefecture.[25] The threat of the storm prompted school closures and 20 airline flight cancellations.[26] Noguri injured one person, damaged one house, and caused about $4 million (¥504 million JPY) in agricultural damage.[nb 5][27]

Typhoon Rammasun (Florita)

Typhoon (JMA)
Category 3 typhoon (SSHWS)
150px 150px
Duration June 28 – July 6
Peak intensity 155 km/h (100 mph) (10-min)  945 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Rammasun (2002)

Typhoon Rammasun was the first of four typhoons to contribute to heavy rainfall and deadly flooding in the Philippines in July 2002; there were 85 deaths related to the four storms,[12] with 2,463 homes damaged or destroyed.[21] Rammasun developed around the same time as Typhoon Chataan, but farther to the west. The storm tracked northwestward toward Taiwan, and on July 2 it attained its peak intensity with winds of 160 km/h (100 mph). Rammasun turned northward, passing east of Taiwan and China.[10] In Taiwan, the outer rainbands dropped rainfall that alleviated drought conditions.[28] In contrast, rainfall in China followed previously wet conditions, resulting in additional flooding,[29] although less damage than expected; there was about $85 million in crop and fishery damage in Zhejiang.[30][nb 4]

After affecting Taiwan and China, Rammasun began weakening due to an approaching trough, which turned the typhoon northeastward. It passed over the Japanese island of Miyako-jima and also produced strong winds in Okinawa.[10] About 10,000 houses lost power on the island,[31] and high surf killed two sailors.[9] On the Japanese mainland, there was light crop damage and one serious injury.[32][33] After weakening to a tropical storm, Rammasun passed just west of the South Korean island of Jejudo,[9] where high waves killed one person.[34] The storm crossed the country, killing three others and leaving $9.5 million in damage.[9] High rains also affected North Korea and Primorsky Krai in the Russian Far East.[35][36]

Typhoon Chataan (Gloria)

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
150px
Duration June 28 – July 11
Peak intensity 175 km/h (110 mph) (10-min)  930 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Chataan

Typhoon Chataan formed on June 28, 2002, near the FSM,[8] and for several days it meandered while producing heavy rainfall across the region. In Chuuk, a state in the FSM, the highest 24-hour precipitation total was 506 mm (19.9 in),[37] which was greater than the average monthly total.[38] The rain produced floods up to 1.5 m (4.9 ft) deep,[39] causing deadly landslides across the island that killed 47 people; this made Chataan the deadliest natural disaster in the island's history. There was also one death on nearby Pohnpei, and damage in the FSM totaled over $100 million.[40]

After affecting the FSM, Chataan began a northwest track as an intensifying typhoon. Its eye passed just north of Guam on July 4, though the eyewall moved across the island and dropped heavy rainfall. Totals were highest in southern Guam, peaking at 536 mm (21.1 in). Flooding and landslides from the storm severely damaged or destroyed 1,994 houses.[37][41] Damage on the island totaled $60.5 million, and there were 23 injuries. The typhoon also affected Rota in the Northern Mariana Islands with gusty winds and light rainfall.[40] Typhoon Chataan attained its peak intensity of 175 km/h (110 mph) on July 8. It weakened while turning to the north, and after diminishing to a tropical storm, Chataan struck eastern Japan on July 10.[8] High rainfall, peaking at 509 mm (20.0 in), flooded 10,270 houses. Damage in Japan totaled about $500 million (¥59 billion JPY).[42][nb 5]

Typhoon Halong (Inday)

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
150px 150px
Duration July 6 – July 16
Peak intensity 155 km/h (100 mph) (10-min)  945 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Halong (2002)

The monsoon trough spawned a tropical depression on July 5 near the Marshall Islands, near where Chataan originated.[8][10] For much of its duration, Halong moved toward the northwest, gradually intensifying into a tropical storm. Early on July 10, Halong passed just south of Guam as a tropical storm, according to the JMA, although the JTWC assessed it as a typhoon near the island. It had threatened to strike the island less than a week after Chataan's damaging landfall, and although Halong remained south of Guam, it produced high waves and gusty winds on the island.[10] The storm disrupted relief efforts following Chataan, causing additional power outages but little damage.[43]

After affecting Guam, Halong quickly strengthened into a typhoon and reached its peak winds on July 12.[8] The JTWC estimated peak 1-minute winds of 250 km/h (155 mph),[9] while the JMA estimated 10-minute winds of 155 km/h (100 mph).[8] The typhoon weakened greatly while curving to the northeast,[10] although its winds caused widespread power outages on Okinawa.[44] Halong struck southeastern Japan, dropping heavy rainfall and producing strong winds that left $89.8 million (¥10.3 billion JPY) in damage.[45][46][47][48][49][50][51][nb 5] There was one death in the country and nine injuries.[46][52] Halong became extratropical on July 16 and dissipated the next day.[8]

Severe Tropical Storm Nakri (Hambalos)

Severe tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration July 7 – July 13
Peak intensity 95 km/h (60 mph) (10-min)  983 hPa (mbar)

A circulation formed on July 7 in the South China Sea, with associated convection located to the south. Outflow increased as the system became better organized,[10] and late on July 7 a tropical depression formed to the southwest of Taiwan.[8] A ridge located over the Philippines caused the system to track northeastward.[10] Early on July 9, the JMA upgraded the depression to Tropical Storm Nakri near western Taiwan.[8] It was a small storm, and while moving along the northern portion of the island, Nakri weakened as its convection diminished.[10] However, it intensified while moving away from Taiwan, reaching peak winds of 95 km/h (60 mph) on July 10.[8] The monsoon trough turned Nakri to the east for two days, until a weakening ridge turned it to the north on July 12.[9] That day, the storm passed just west of Okinawa, and shortly thereafter Nakri weakened to a tropical depression,[8] after experiencing cooler waters and increasing shear.[9] On July 13, Nakri dissipated west of Kyushu.[8]

While passing over Taiwan, Nakri dropped heavy rainfall that reached 647 mm (25.5 in) at Pengjia Islet.[10] A total of 170 mm (6.7 in) fell in one day at the Feitsui Dam, representing the highest daily total at that point in the year. Taiwan had experienced drought conditions prior to earlier Typhoon Rammasun, and additional rainfall from Nakri eliminated all remaining water restrictions.[53] Airline flights were canceled throughout the region due to the storm, and some schools and offices were closed.[54] Nakri killed one fisherman and a shipworker during its passage.[55] High rains also affected southeastern China,[10] and later Okinawa.[56] The storm induced heavy rainfall in the Philippines,[10] as well as in Japan, where landslides and flooding were reported along a cold front.[57]

Typhoon Fengshen

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
150px 150px
Duration July 13 – July 28
Peak intensity 185 km/h (115 mph) (10-min)  920 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Fengshen (2002)

The monsoon trough spawned a tropical depression on July 13, which quickly intensified due to its small size. By July 15, Fengshen attained typhoon status, and after initially moving to the north, it began a movement toward the northwest. On July 18, the typhoon reached peak 10-minute winds of 185 km/h (115 mph), according to the JMA, making it the strongest storm of the season. The JTWC estimated peak 1-minute winds of 270 km/h (165 mph), and the agency estimated that Fengshen was a super typhoon for five days.[8][9] This broke the record for longest duration at that intensity, previously set by Typhoon Joan in 1997,[10] and later tied by Typhoon Ioke in 2006.[58]

While near peak intensity, Typhoon Fengshen underwent the Fujiwhara effect with Typhoon Fung-wong, causing the latter storm to loop to its south.[10] Fengshen gradually weakened while approaching Japan, and it crossed over the country's Ōsumi Islands on July 25 as a severe tropical storm.[8] When the typhoon washed a freighter ashore, four people drowned and the remaining fifteen were rescued.[59][60] In the country, Fengshen dropped heavy rainfall and produced heavy rains,[61] causing mudslides, $4 million (¥475 million JPY) in crop damage,[62][nb 5] and one death.[61] After affecting Japan, Fengshen weakened in the Yellow Sea to a tropical depression, before moving across China's Shandong Peninsula and dissipating on July 28.[8]

Tropical Depression 13W (Juan)

Tropical depression (PAGASA)
Tropical storm (SSHWS)
150px 150px
Duration July 18 – July 23
Peak intensity 55 km/h (35 mph) (10-min)  997 hPa (mbar)

On July 16, an area of convection increased northwest of Palau with a weak circulation. Moderate shear dispersed the thunderstorms, although the system gradually organized.[10] It tracked northwestward due to a ridge to the north,[9] becoming a tropical depression on July 18. PAGASA gave the system the local name "Juan", and the JTWC classified it as Tropical Depression 13W, although the JMA did not classify it as a tropical storm. Early on July 19, the depression struck Samar Island in the Philippines, and continued northwestward through the archipelago. An increase in convection the next day prompted the JTWC to upgrade the system to a tropical storm before it moved over Luzon and the Metro Manila area.[10] Increasing shear and disrupted outflow due to land interaction weakened the system, and the JTWC discontinued advisories on July 22.[9] PAGASA continued tracking the system until the following day.[21]

The depression dropped heavy rainfall in the Philippines during its passage,[9] only weeks after several consecutive tropical systems caused deadly flooding in the country. The rains forced 2,400 people to evacuate. Storm-related tornadoes and landslides killed at least three people.[10] Three people were electrocuted, and flash flooding killed at least two people.[63] In all, Tropical Depression Juan killed 14 people and injured two others. There were 583 houses that were damaged or destroyed, and damage totaled about $240,000 (₱12.1 million PHP),[21][nb 3] mostly on Luzon.[10]

Typhoon Fung-wong (Kaka)

Typhoon (JMA)
Category 1 typhoon (SSHWS)
150px 150px
Duration July 18 – July 27
Peak intensity 130 km/h (80 mph) (10-min)  960 hPa (mbar)

A small circulation formed northeast of the Northern Marianas Islands on July 18.[10] Later that day, the JMA classified the system as a tropical depression.[8] Convection and outflow increased the next day, and the system moved slowly westward due to a ridge over Japan. After further organization, the JTWC initiated advisories on July 20 while the depression was just southwest of Iwo Jima.[10] Shortly thereafter, the JMA upgraded it to Tropical Storm Fung-Wong.[8] On July 22, the storm began undergoing the Fujiwhara effect with the larger Typhoon Fengshen to the east, causing Fung-wong to turn southwestward. Around that time, the storm entered PAGASA's region, earning it the local name "Kaka". Fung-wong quickly intensified after developing a small eye, becoming a typhoon on July 23,[10] with peak winds of 130 km/h (80 mph).[8] It turned to the south and later southeast while interacting with the larger Fengshen, which passed north of it.[10] On July 25, the typhoon weakened to a severe tropical storm while at the southernmost point of its track.[8] The storm turned to the north and completed a large loop between the Ryukyu and Northern Marianas Islands that day.[10] The combination of cooler waters, wind shear, and dry air caused weakening,[9] and the storm deteriorated into a tropical depression on July 27. Passing a short distance south of Kyushu, Fung-wong dissipated later that day.[10]

The storm dropped heavy rainfall in Japan, reaching 717 mm (28.2 in) at a station in Miyazaki Prefecture.[64] The rains caused two landslides and resulted in delays to bus and train systems, as well as cancellations to ferry and airline routes. There was also minor crop damage.[65]

Tropical Storm Kalmaegi

Tropical storm (JMA)
Tropical depression (SSHWS)
150px 150px
Duration July 20 (entered basin) – July 21
Peak intensity 65 km/h (40 mph) (10-min)  1002 hPa (mbar)

A tropical disturbance developed on July 17 in the Central Pacific Ocean, near the International Date Line.[9] Deep convection with outflow persisted around a circulation,[10] and at 06:00 UTC on July 20 the JMA classified the system as a tropical depression, just east of the date line and about 980 km (610 mi) west-southwest of Johnston Atoll. The system crossed the line shortly thereafter and quickly intensified into Tropical Storm Kalmaegi.[8] The JMA classified the system as a tropical storm, although the JTWC maintained it as a tropical depression.[10] Kalmaegi moved northwestward due to a ridge to the north, and initially a tropical upper tropospheric trough provided favorable conditions. However, the trough soon increased wind shear and restricted outflow, which caused quick weakening.[9] The thunderstorms diminished from the circulation,[10] and around 12:00 UTC on July 22, Kalmaegi dissipated about 30 hours after forming.[8]

Severe Tropical Storm Kammuri (Lagalag)

Severe tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration August 2 – August 7
Peak intensity 100 km/h (65 mph) (10-min)  980 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Tropical Storm Kammuri (2002)

A large monsoonal system persisted toward the end of July 2002 near the Philippines. On August 2, a tropical depression formed off the northwest coast of Luzon and moved west-northwestward. Late on August 3, it intensified into Tropical Storm Kammuri off the coast of Hong Kong. A weakening ridge turned the storm northward toward the coast of China. Tropical Storm Kammuri made landfall late on August 4, after reaching peak winds of 100 km/h (65 mph). The system dissipated over the mountainous coastline of eastern China and merged with a cold front on August 7.[16]

High rainfall from Kammuri affected large portions of China, particularly in Guangdong province where it moved ashore.[16] In Hong Kong, the rains caused a landslide and damaged a road.[66] Two dams were destroyed in Guangdong by the flooding,[67] and 10 people were killed by a landslide.[16] Throughout the province, over 100,000 people had to evacuate due to flooding, and after 6,810 houses were destroyed.[16][68] The floods damaged roads, railroads, and tunnels, and left power and water outages across the region.[16] Rainfall was beneficial in alleviating drought conditions in Guangdong,[69] although further inland the rains occurred after months of deadly flooding.[70] In Hunan Province, the storm's remnants merged with a cold front and destroyed 12,400 houses.[16] Across its path, the floods damaged or destroyed 245,000 houses, and destroyed about 60 hectares (150 acres) of crop fields. Kammuri and its remnants killed 153 people,[15] and damage was estimated at $509 million (¥4.219 billion CNY).[16][nb 4]

Tropical Storm Vongfong (Milenyo)

Tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration August 10 – August 20
Peak intensity 75 km/h (45 mph) (10-min)  985 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Tropical Storm Vongfong (2002)

A tropical depression developed on August 10 east of the Philippines. Initially it was disorganized due to hostile conditions, and it failed to intensify significantly before crossing the Philippine island of Luzon.[16] There, flooding forced 3,500 people to evacuate their homes.[71] In the Philippines, the storm killed 35 people and caused $3.3 million in damage, with 13,178 houses damaged or destroyed. It was the final storm named by PAGASA during the season.[21]

After affecting the Philippines, the tropical depression dissipated in the South China Sea on August 14. The next day, the system reformed, although the JTWC labeled the new depression as a separate cyclone.[16] It moved northwestward, strengthening into Tropical Storm Vongfong on August 18. It brushed eastern Hainan before making landfall on August 19 in southern China near Wuchuan, Guangdong.[8] Soon after the circulation dissipated, it dropped heavy rainfall across the region.[16] One person died in a traffic accident in Hong Kong, and landslides killed twelve people.[16][72] The storm destroyed 6,000 houses, mostly in Guangdong, and damage in the country totaled at least $86 million.[16][nb 4]

Typhoon Phanfone

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
150px 150px
Duration August 11 – August 20
Peak intensity 155 km/h (100 mph) (10-min)  940 hPa (mbar)

The monsoon trough spawned a tropical depression on August 11, just west of Ujelang Atoll.[8][9] It moved generally northwestward due to a ridge to the north,[16] quickly intensifying into Tropical Storm Phanfone by August 12.[8] With good outflow and developing rainbands, the storm continued to strengthen,[16] becoming a typhoon on August 14.[8] Phanfone developed a well-defined eye, surrounded by deep convection.[16] On August 15, the JMA estimated 10-minute winds of 155 km/h (100 mph),[8] and the JTWC estimated 1-minute winds of 250 km/h (155 mph), making it a super typhoon.[9] Diminished outflow and an eyewall replacement cycle caused weakening,[16] and it passed near Iwo Jima on August 16.[8] Phanfone turned to the northeast two days later due to a weakening ridge, and dry air caused rapid deterioration. Passing southeast of Japan, it fell to tropical storm status on August 19 before becoming extratropical the next day;[16] the remnants continued to the northeast and crossed the International Date Line on August 25.[8]

Wind gusts on Iwo Jima reached 168 km/h (105 mph).[16] Rainfall in mainland Japan peaked at 416 mm (16.4 in) near Tokyo, and the typhoon flooded 43 houses.[73] High rains caused road damage and landslides, as well as some aquaculture damage.[74] The storm caused 22 ferry routes and 10 flights to be canceled,[75] and temporarily shut down refineries near Tokyo.[76] On the offshore island of Hachijō-jima, high winds caused a temporary power outage.[77]

Typhoon Rusa

Typhoon (JMA)
Category 4 typhoon (SSHWS)
150px 150px
Duration August 22 – September 1
Peak intensity 150 km/h (90 mph) (10-min)  950 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Rusa

Typhoon Rusa developed on August 22 from the monsoon trough in the open Pacific Ocean, well to the southeast of Japan. For several days, Rusa moved to the northwest, eventually intensifying into a powerful typhoon.[9] The JMA estimated peak 10-minute winds of 150 km/h (90 mph),[8] and the JTWC estimated peak 1-minute winds of 215 km/h (135 mph).[9] On August 26, the storm moved across the Amami Islands of Japan,[8] where Rusa left 20,000 people without power and caused two fatalities.[78][79] Across Japan, the typhoon dropped torrential rainfall peaking at 902 mm (35.5 in) in Tokushima Prefecture.[80]

After weakening slightly, Rusa made landfall on Goheung, South Korea with 10-minute winds of 140 km/h (85 mph). It was able to maintain much of its intensity due to warm air and instability from a nearby cold front.[8][81] Rusa weakened while moving through the country, dropping heavy rainfall that peaked at 897.5 mm (35.33 in) in Gangneung. A 24-hour total of 880 mm (35 in) in the city broke the record for the highest daily precipitation in the country; however, the heaviest rainfall was localized.[81] Over 17,000 houses were damaged, and large areas of crop fields were flooded.[82] In South Korea, Rusa killed at least 233 people,[83] making it the deadliest typhoon in over 43 years,[84] and caused $4.2 billion in damage.[83] The typhoon also dropped heavy rainfall in neighboring North Korea, leaving 26,000 people homeless and killing three.[85] Rusa also destroyed large areas of crops in the country, which was already affected by ongoing famine conditions.[86] The typhoon became extratropical over eastern Russia on September 1, dissipating three days later.[8]

Typhoon Sinlaku

Typhoon (JMA)
Category 3 typhoon (SSHWS)
150px 150px
Duration August 27 – September 9
Peak intensity 150 km/h (90 mph) (10-min)  950 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Sinlaku (2002)

Sinlaku formed on August 27 northeast of the Northern Marianas Islands. After initially moving to the north, it began a generally westward motion that it maintained for the rest of its duration. Sinlaku strengthened into a typhoon and attained its peak winds on August 31. Over the next few days, it fluctuated slightly in intensity while moving over or near several Japanese islands.[8] On September 4, the typhoon's eye crossed over Okinawa.[9] It dropped heavy rainfall and produced strong winds that left over 100,000 people without power.[87] Damage on the island was estimated at $14.3 million,[88][nb 5] including $3.6 million in damage to Kadena Air Base.[9]

After affecting Okinawa, Sinlaku threatened northern Taiwan, which had been affected by two deadly typhoons in the previous year.[89] Damage ended up being minimal on the island,[90] although two people were killed.[83] Sinlaku weakened slightly before making its final landfall in eastern China near Wenzhou on September 7.[8] The storm produced a record wind gust there of 204 km/h (127 mph),[16] and just south of the city, high waves destroyed several piers and a large boat.[91] High rainfall and winds from Sinlaku wrecked 58,000 houses, and large areas of crops were destroyed. Damage in China was estimated at $709 million,[16][nb 4] and there were 28 deaths there.[83]

Typhoon Ele

Typhoon (JMA)
Category 4 typhoon (SSHWS)
150px 150px
Duration August 30 (entered basin) – September 10
Peak intensity 165 km/h (105 mph) (10-min)  940 hPa (mbar)

An eastern extension of the monsoon trough southwest of Hawaii organized into Tropical Depression Two-C on August 27 and strengthened into Tropical Storm Ele six hours later. Despite the nearby presence of Alika, Ele developed rapidly and strengthened into a hurricane on August 28. After contributing to the demise of Alika, Ele intensified to winds of 205 km/h (125 mph) before crossing the International Date Line on August 30.[92]

Reclassified as a typhoon,[8] Ele moved north-northwestward due to a weakness in the ridge to the north. Early on August 31, the JTWC estimated the storm's peak 1-minute winds at 165 km/h (105 mph).[16] On September 2, the JMA estimated peak 10-minute winds of 165 km/h (105 mph) while Ele was northeast of Wake Atoll.[8] The typhoon turned to the northeast due to an approaching trough,[9] although Ele resumed its previous north-northwest motion after a ridge built behind the trough.[16] It gradually weakened due to cooler waters and increasing wind shear,[9] and on September 6 Ele deteriorated below typhoon status.[8] The thunderstorms became detached from the circulation,[9] causing Ele to weaken to a tropical depression late on September 9. By that time, it began moving to the northeast, and on September 10 it transitioned into an extratropical storm. The remnants of Ele continued to the northeast until moving back into the central Pacific as an extratropical storm on September 11 and dissipating on September 13.[8]

Tropical Storm Hagupit

Tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration September 9 – September 16
Peak intensity 85 km/h (50 mph) (10-min)  990 hPa (mbar)

An area of convection developed on September 8 to the northeast of Luzon.[93] Moving to the west due to a ridge to the north,[9] it slowly organized,[93] forming into a tropical depression on September 9 in the South China Sea. As it approached southeastern China, the depression intensified into Tropical Storm Hagupit and reached peak winds of 85 km/h (50 mph). At around 19:00 UTC on September 11, the storm made landfall west of Macau and quickly weakened into a tropical depression.[8] The JTWC promptly discontinued advisories,[9] although the JMA continued tracking Hagupit over land. The remnants executed a loop over Guangdong before moving offshore and dissipating on September 16 near Hong Kong.[8]

Hagupit dropped heavy rainfall along the coast of China for several days, peaking at 344 mm (13.5 in) in Zhanjiang City. The rains flooded widespread areas of crop fields and resulted in landslides. In Guangdong, 330 houses were destroyed, and damage was estimated at $32.5 million.[93][nb 4] In Hong Kong, 32 people were injured due to the storm,[94] and 41 flights were canceled.[9] In Fuzhou in Fujian Province, thunderstorms related to Hagupit flooded hundreds of houses. Further west in Jiangxi, floods from the storm destroyed 3,800 houses, ruined 180 bridges, and killed 25.[93] Offshore, a helicopter rescued the crew of 25 from a sunken boat during the storm.[9][94]

Tropical Storm Changmi

Tropical storm (JMA)
150px 150px
Duration September 20 – September 22
Peak intensity 85 km/h (50 mph) (10-min)  985 hPa (mbar)

An area of thunderstorms increased near the FSM on September 15 within the monsoon trough. Located within an area of moderate wind shear, its convection was intermittent around a weak circulation. On September 18, the JTWC issued a Tropical Cyclone Formation Alert (TCFA), and the JMA classified the system as a tropical depression; however, the two warning agencies were tracking different circulations within the same system, and by September 19 the circulation JMA was tracking became the dominant system. Shortly thereafter, the agency downgraded the system to a low pressure area after it weakened.[93] The next day, JMA again upgraded the system to a tropical depression,[8] and the JTWC issued a second TCFA when the system had a partially exposed circulation near an area of increasing convection.[93] Late on September 21, the JMA upgraded the depression to Tropical Storm Changmi to the south of Japan. The next day, Changmi attained peak winds of 85 km/h (50 mph).[8] However, the JTWC noted that the system was absorbing dry air and becoming extratropical, and thus did not issue warnings on the storm.[93] Moving northeastward, Changmi became an extratropical cyclone on September 22, and gradually became more intense until crossing the International Date Line early on September 25.[8]

Tropical Storm Mekkhala

Tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration September 22 – September 28
Peak intensity 85 km/h (50 mph) (10-min)  990 hPa (mbar)

An elongated trough with associated convection developed in the South China Sea by September 21. Light shear and increasing outflow allowed the system to become better organized,[93] and it formed into a tropical depression on September 22 between Vietnam and Luzon.[8] A ridge to the northeast allowed the system to track northwestward.[9] For several days the depression failed to organize further, despite favorable conditions; however, late on September 24 the circulation developed rainbands and a weak eye feature.[93] Early the next day, the JMA upgraded it to Tropical Storm Mekkhala, which quickly intensified to a peak intensity of 85 km/h (50 mph).[8] At around 12:00 UTC on September 25, Mekkhala made landfall on western Hainan near peak intensity. Soon after, it moved into the Gulf of Tonkin and weakened due to land interaction and increasing shear.[9] Mekkhala remained a weak tropical storm until September 28, when it weakened to a tropical depression and dissipated soon after in the extreme northern portion of the Gulf of Tonkin.[8]

Mekkhala dropped heavy rainfall along its path, peaking at 479 mm (18.9 in) in Sanya, Hainan.[93] Along the island, high winds washed ashore or sank 20 boats,[95] and 84 fishermen were rescued. Throughout Hainan, the high rains wrecked 2,500 houses and left $80.5 million in damage.[nb 4] High rains spread into southwestern China, particularly in Guangxi. In Beihai, the storm destroyed 335 houses, resulting in $22 million in damage.[93][nb 4]

Typhoon Higos

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
150px 150px
Duration September 26 – October 2
Peak intensity 175 km/h (110 mph) (10-min)  930 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Higos (2002)

Typhoon Higos developed on September 25 east of the Northern Marianas Islands. It tracked west-northwestward for its first few days, steadily intensifying into a powerful typhoon by September 29. Higos weakened and turned to the north-northeast toward Japan, making landfall in that country's Kanagawa Prefecture on October 1.[8] Shortly thereafter, it crossed over Tokyo, becoming the third strongest typhoon to do so since World War II.[9] It weakened while crossing Honshu, and shortly after striking Hokkaidō on October 2, Higos became extratropical. The remnants passed over Sakhalin and dissipated on October 4.[8]

Before striking Japan, Higos produced strong winds in the Northern Marianas Islands while passing to their north. These winds damaged the food supply on two islands.[96] Later, Higos moved across Japan with wind gusts as strong as 161 km/h (100 mph),[97] including record gusts at several locations.[98] A total of 608,130 buildings in the country were left without power,[97] and two people were electrocuted in the storm's aftermath.[93] The typhoon also dropped heavy rainfall that peaked at 346 mm (13.6 in).[97] The rains flooded houses across the country and caused mudslides.[99] High waves washed 25 boats ashore and killed one person along the coast.[97][99] Damage in the country totaled $2.14 billion (¥261 billion JPY),[nb 5] and there were five deaths.[97] Later, the remnants of Higos affected the Russian Far East, killing seven people in two shipwrecks near Primorsky Krai.[100]

Severe Tropical Storm Bavi

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
150px 150px
Duration October 8 – October 13
Peak intensity 100 km/h (65 mph) (10-min)  985 hPa (mbar)

A tropical disturbance organized within the monsoon trough in early October near the FSM. The convection gradually consolidated around a single circulation,[101] developing into a tropical depression on October 8.[8] Wind shear was weak and outflow was good, which allowed for slow strengthening; however, the system was elongated, with a separate circulation to the west. Around this time, the system produced gale force winds on Kosrae in the FSM.[101] Late on October 9, the JMA upgraded the depression to Tropical Storm Bavi to the east of Guam,[8] although it was still a broad system at the time. After becoming a tropical storm, Bavi moved generally northward due to a ridge retreating to the northeast. By October 11, winds were fairly weak near the center and were stronger in outer rainbands.[101] That day, the JMA estimated peak winds of 100 km/h (65 mph).[8] Despite the broad structure,[101] with an exposed circulation at the peak, the JTWC estimated winds as high as 130 km/h (80 mph), making Bavi a typhoon. Shortly after reaching peak winds, the storm turned to the northeast and entered the westerlies.[9] Increasing shear weakened the convection,[101] and Bavi became extratropical on October 13. It continued to the northeast and crossed into the Central Pacific on October 16.[8]

Severe Tropical Storm Maysak

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
150px 150px
Duration October 26 – October 30
Peak intensity 100 km/h (65 mph) (10-min)  980 hPa (mbar)

On October 25, an organized area of convection persisted southeast of Wake Island. With minimal wind shear, it quickly developed a circulation,[101] becoming a tropical depression on October 26.[8] Due to a ridge to the east, it moved generally northwestward and slowly intensified.[101] Late on October 27, it strengthened into Tropical Storm Maysak.[8] Initially, the system absorbed nearby dry air, although the storm was able to continue developing deep convection.[101] An approaching trough turned Maysak to the northeast,[9] and on October 29 it reached peak winds of 100 km/h (65 mph), according to the JMA.[8] On two occasions, the JTWC assessed Maysak as briefly intensifying into a typhoon,[102] based on an eye feature, although increased shear later caused weakening.[101] Continuing to the northeast, Maysak moved into the central Pacific Ocean on October 30,[8] by which time it had become extratropical.[101]

Typhoon Huko

Typhoon (JMA)
Category 1 typhoon (SSHWS)
150px 150px
Duration November 3 (Entered basin) – November 7
Peak intensity 140 km/h (85 mph) (10-min)  985 hPa (mbar)

In the central Pacific Ocean, a tropical depression developed in the monsoon trough on October 24 to the south of Hawaii. It moved generally west-northwestward, intensifying into Tropical Storm Huko on October 26. It became a hurricane two days later, and briefly weakened back to tropical storm status before becoming a hurricane again on October 31. On November 3, Huko crossed the International Date Line into the western Pacific.[92] Despite favorable inflow patterns and warm sea surface temperatures,[101] Huko only strengthened to reach peak winds of 140 km/h (85 mph).[8] It moved quickly to the west-northwest due to a strong ridge to its north. Dry air caused Huko to weaken slightly, and on November 4 the typhoon passed about 95 km (60 mi) northeast of Wake Island.[101] The typhoon brought heavy rains and winds gusts of 40–45 mph (64–72 km/h) to the island.[103] Huko moved through a weakness in the ridge, resulting in a turn to the north and northeast.[101] Late on November 5, Huko weakened below typhoon status,[8] and increasing shear caused further weakening.[101] On November 7, Huko became extratropical, and later that day its remnants crossed back into the central Pacific.[8] Several days later, the remnants affected northern California.[101]

Typhoon Haishen

Typhoon (JMA)
Category 2 typhoon (SSHWS)
150px 150px
Duration November 20 – November 25
Peak intensity 155 km/h (100 mph) (10-min)  955 hPa (mbar)

In the middle of November, an area of thunderstorms developed southwest of Chuuk in the FSM within the monsoon trough. With weak shear and good outflow, it slowly organized,[104] becoming a tropical depression on November 20.[8] It moved quickly to the west-northwest,[104] intensifying into Tropical Storm Haishen late on November 20 to the southeast of Guam.[8] While passing south of the island, Haishen produced gale-force winds. The convection organized into a central dense overcast and developed an eye feature.[104] Early on November 23, Haishen intensified into a typhoon;[8] around that time, it began moving to the north due to an approaching trough.[104] The typhoon quickly intensified to peak winds of 155 km/h (100 mph).[8] Soon after, Haishen began weakening due to increasing shear, and the eye quickly dissipated.[104] Late on November 24, it weakened below typhoon status, and early on November 25 Haishen became extratropical. The remnants continued to the northeast, dissipating on November 26.[8]

Typhoon Pongsona

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
150px 150px
Duration December 2 – December 11
Peak intensity 165 km/h (105 mph) (10-min)  940 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Typhoon Pongsona

Typhoon Pongsona was the last typhoon of the season, and was the second costliest disaster in 2002 in the United States and its territories.[105] It formed on December 2,[8] having originated as an area of convection to the east-southeast of Pohnpei in late November. With a ridge to the north, the depression tracked generally westward for several days,[106] intensifying into Tropical Storm Pongsona on December 3.[8] After an eye developed on December 5,[106] the storm attained typhoon status to the north of Chuuk.[8] Steady intensification continued, until it became more rapid on December 8 while approaching Guam.[106] That day, the JMA estimated peak winds of 165 km/h (105 mph),[8] and the JTWC estimated peak winds of 240 km/h (150 mph), making Pongsona a super typhoon.[9] Around its peak intensity, the eye of the typhoon moved over Guam and Rota.[9] After striking Guam, Pongsona began moving to the north and later to the northeast, quickly weakening due to the presence of dry air and interaction with an approaching mid-latitude storm. After the convection diminished over the center,[106] Pongsona became extratropical early on December 11. Early the next day, it dissipated east of Japan.[8]

On Guam, Pongsona was the third most intense typhoon on record to strike the island, with wind gusts reaching 278 km/h (173 mph). Damage totaled $700 million, making it one of the five costliest storms on Guam. The typhoon injured 193 people and killed one person. In addition to its strong winds, Pongsona dropped torrential rainfall that peaked at 650.5 mm (25.61 in).[107] A total of 1,751 houses were destroyed on Guam, and another 6,740 were damaged to some degree. Widespread areas lost water, and the road system was heavily damaged. On neighboring Rota, Pongsona damaged 460 houses and destroyed 114, causing an additional $30 million in damage.[108] Both Guam and the Northern Marianas Islands were declared federal disaster areas, which made federal funding available for repairing storm damage. In Guam, the federal government provided about $125 million in funding for individuals and other programs.[109][110]

Other storms

On February 15, a weak tropical depression developed east of Mindanao, according to the JMA; by the next day, the system dissipated.[111] In the beginning of April, a tropical disturbance developed along the southern end of a stationary cold front west of Enewetak Atoll.[9] While gradually organizing, the system produced gale-force wind gusts in the FSM.[112] On April 5, the JTWC initiated advisories on Tropical Depression 04W. The system moved northwestward due to a nearby extratropical storm, which later caused the depression to also become extratropical about 650 km (405 mi) west-southwest of Wake Atoll.[9] The JMA issued its last advisory on April 8.[9]

A tropical depression formed in the South China Sea on May 28,[9] given the name "Dagul" by PAGASA.[22] The JTWC never anticipated significant strengthening,[113] and the system largely consisted of convection displaced to the southeast of a broad circulation.[22] A ridge to the southeast steered the depression to the northeast, and on May 30 the depression made landfall in southwestern Taiwan. The combination of land interaction and wind shear caused dissipation that day.[9]

The JMA monitored a tropical depression east of Iwo Jima on July 25, although by the next day the agency was no longer tracking the system.[10] On August 3, a small circulation was located just off the southeast coast of Japan, which later developed an area of convection over it. The JTWC initiated advisories on Tropical Depression 17W at 06:00 UTC on August 5,[16] describing the system as a "midget cyclone". A mid-level ridge to the southeast steered the depression eastward away from Japan. Unfavorable conditions caused weakening, and the JTWC discontinued advisories six hours after its first warning.[9] Another tropical depression formed on September 21 to the northeast of the Marshall Islands, but dissipated by the next day.[93]

Three non-developing depressions formed in October. The first was classified as a depression by the JMA on October 12 in the South China Sea. It quickly dissipated, although the system dropped heavy rainfall reaching 108 mm (4.3 in) at a station in the Paracel Islands.[101] The second, classified as Tropical Depression 27W by the JTWC, formed on October 17 about 1,220 km (760 mi) east-northeast of Saipan. It moved westward due to a ridge to the north, and failed to intensify due to weak outflow and dry air. It dissipated on October 19.[9] The day before, another depression formed near the International Date Line.[101] Classified as Tropical Depression 28W by the JTWC, it moved generally northward due to a break in the ridge. Wind shear dissipated the depression on October 20.[101]

Storm names

Within the western Pacific Ocean, both the JMA and PAGASA assign names to tropical cyclones that develop in the basin, which can result in a tropical cyclone having two names.[114] As part of its duty as a Regional Specialized Meteorological Center (RSMC), the JMA's Typhoon Center in Tokyo assigns international names to tropical cyclones on behalf of the World Meteorological Organization's Typhoon Committee, should they be judged to have 10-minute sustained winds of 65 km/h (40 mph).[115] The PAGASA assigns names to all tropical cyclones that move into or form as a tropical depression in their area of responsibility, located between 135°E and 115°E and between 5°N-25°N, even if the cyclone has had an international name assigned to it.[114] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.[115] PAGASA also has an auxiliary naming list, of which the first ten are published, should their list of names be exhausted.

International names

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Tropical cyclone naming

During the season 24 named tropical cyclones developed in the Western Pacific and were named by the Japan Meteorological Agency, when it was determined that they had become tropical storms. These names were contributed to a list of a 140 names submitted by the fourteen members nations and territories of the ESCAP/WMO Typhoon Committee.

Tapah Mitag Hagibis Noguri Rammasun Chataan Halong Nakri Fengshen Kalmaegi Fung-wong Kammuri
Phanfone Vongfong Rusa Sinlaku Hagupit Changmi Mekkhala Higos Bavi Maysak Haishen Pongsona

Two central pacific storms, Hurricane Ele 02C and Hurricane Huko 03C, crossed into this basin. They became Typhoon Ele and Typhoon Huko, keeping their original name and "C" suffix in their warnings by JTWC.[9]

Philippines

Agaton Basyang Caloy Dagul Espada
Florita Gloria Hambalos Inday Juan
Kaka Lagalag Milenyo Neneng (unused) Ompong (unused)
Paeng (unused) Quadro (unused) Rapido (unused) Sibasib (unused) Tagbanwa (unused)
Usman (unused) Venus (unused) Wisik (unused) Yayang (unused) Zeny (unused)
Auxiliary list
Agila (unused) Bagwis (unused) Ciriaco (unused) Diego (unused) Elena (unused)
Forte (unused) Gunding (unused) Hunyango (unused) Itoy (unused) Jessa (unused)

The Philippine Atmospheric, Geophysical and Astronomical Services Administration uses its own naming scheme for tropical cyclones in their area of responsibility. PAGASA assigns names to tropical depressions that form within their area of responsibility and any tropical cyclone that might move into their area of responsibility,[17] and the lists are reused every four years.[116] Names that were not assigned are marked in gray.

Retirement

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: List of retired Pacific typhoon names and List of retired Philippine typhoon names

The names Chataan, Rusa, and Pongsona were retired by the WMO's Typhoon Committee. The names Matmo, Nuri, and Noul were chosen to replace Chataan, Rusa and Pongsona respectively.[117]

Season effects

The following table does not include unnamed storms, and PAGASA names are in parenthesis. Storms entering from the Central Pacific only include their information while in the western Pacific, and are noted with an asterisk *.

Name Dates active Peak classification Sustained
wind speeds		 Pressure Land areas affected Damage
(USD)		 Deaths Refs
Tapah January 10 – 14 Tropical storm 75 km/h (45 mph) 996 hPa (29.42 inHg) Philippines None None [118]
Mitag (Basyang) February 26 – March 9 Typhoon 175 km/h (110 mph) 930 hPa (27.46 inHg) Federated States of Micronesia, Palau $150 million 2 [19]
03W (Caloy) March 20 – 23 Tropical Depression 55 km/h (35 mph) 1000 hPa (29.53 inHg) Philippines $2.4 million 35 [21]
Hagibis May 14 – May 21 Typhoon 175 km/h (110 mph) 935 hPa (27.61 inHg) Guam None None [23]
Noguri (Espada) June 4 – June 11 Severe tropical storm 110 km/h (75 mph) 975 hPa (28.79 inHg) Japan, Taiwan $4 million None [27]
Rammasun (Florita) June 28 – July 6 Typhoon 155 km/h (100 mph) 945 hPa (27.91 inHg) China, Korean Peninsula, Ryukyu Islands, Taiwan $100 million 97 [9][12][30][34]
Chaatan (Gloria) June 28 – July 11 Typhoon 175 km/h (110 mph) 930 hPa (27.46 inHg) Chuuk, Guam, Japan $660 million 54 [40][42]
Halong (Inday) July 6 – July 16 Typhoon 155 km/h (100 mph) 945 hPa (27.91 inHg) Guam, Philippines, Japan $89.8 million 10 [45][46][47][48][49][50][51]
Nakri (Hambalos) July 7 – July 13 Severe tropical storm 95 km/h (60 mph) 983 hPa (29.03 inHg) Philippines, China, Taiwan, Japan None 2 [55]
Fengshen July 13 – July 28 Typhoon 185 km/h (115 mph) 920 hPa (27.17 inHg) Japan, China $4 million 5 [59][61][62]
13W (Juan) July 18 – July 23 Tropical depression 55 km/h (35 mph) 997 hPa (29.44 inHg) Philippines $240 thousand 14 [10][21]
Kalmaegi July 20 – July 21 Tropical storm 65 km/h (40 mph) 1003 hPa (29.62 inHg) None None None [8]
Fung-wong (Kaka) July 18 – July 27 Typhoon 130 km/h (80 mph) 960 hPa (28.35 inHg) Japan None None [64]
Kammuri (Lagalag) August 2 - August 7 Severe tropical storm 100 km/h (65 mph) 980 hPa (28.94 inHg) China $509 million 153 [15][16]
Vongfong (Milenyo) August 10 - August 20 Tropical storm 75 km/h (45 mph) 985 hPa (29.09 inHg) Philippines, China $89.3 million 47 [16][21][72]
Phanfone August 11 - August 20 Typhoon 155 km/h (100 mph) 940 hPa (27.76 inHg) Japan None None [16]
Rusa August 22 - September 1 Typhoon 150 km/h (90 mph) 950 hPa (28.05 inHg) Japan, South Korea, North Korea $4.2 billion 238 [78][79][83][85]
Sinlaku August 27 - September 9 Typhoon 150 km/h (90 mph) 950 hPa (28.05 inHg) Japan, China $723 million 30 [16][83][88]
Ele* August 30 - September 10 Typhoon 165 km/h (105 mph) 940 hPa (27.76 inHg) None None None [8]
Hagupit September 9 - September 16 Tropical storm 85 km/h (50 mph) 990 hPa (29.23 inHg) China $32.5 million 25 [93]
Changmi September 18 - September 22 Tropical storm 85 km/h (50 mph) 985 hPa (29.09 inHg) None None None [8]
Mekkhala September 22 - September 28 Tropical storm 85 km/h (50 mph) 990 hPa (29.23 inHg) China $103 million None [93]
Higos September 26 – October 2 Typhoon 175 km/h (110 mph) 930 hPa (27.47 inHg) Japan, Primorsky Krai $2.14 billion 12 [97][100]
Bavi October 8 - October 13 Severe tropical storm 100 km/h (65 mph) 985 hPa (29.09 inHg) None None None [8]
Maysak October 26 - October 30 Severe tropical storm 100 km/h (65 mph) 980 hPa (28.94 inHg) None None None [8]
Huko* November 3 – November 7 Typhoon 140 km/h (85 mph) 985 hPa (29.09 inHg) None None None [8]
Haishen November 20 – November 25 Typhoon 155 km/h (100 mph) 955 hPa (28.20 inHg) None None None [8]
Pongsona December 2 – December 11 Typhoon 140 km/h (85 mph) 940 hPa (27.76 inHg) Guam, Northern Marianas Islands $730 million 1 [107][108]
Season Aggregates
28 systems January 9 – December 11 185 km/h (115 mph) 920 hPa (27.17 inHg) >9.54 billion 725


See also

Notes

  1. ↑ 1.0 1.1 A super typhoon is an unofficial category used by the Joint Typhoon Warning Center (JTWC) for a typhoon with winds of at least 240 km/h (150 mph).[1]
  2. ↑ All damage totals are valued as of 2002 and in United States dollars, unless otherwise noted.
  3. ↑ 3.0 3.1 3.2 3.3 The total was originally reported in Philippine pesos. Total converted via the Oanda Corporation website.[14]
  4. ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 The total was originally reported in Chinese renminbi. Total converted via the Oanda Corporation website.[14]
  5. ↑ 5.0 5.1 5.2 5.3 5.4 5.5 The total was originally reported in Japanese yen. Total converted via the Oanda Corporation website.[14]

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.00 8.01 8.02 8.03 8.04 8.05 8.06 8.07 8.08 8.09 8.10 8.11 8.12 8.13 8.14 8.15 8.16 8.17 8.18 8.19 8.20 8.21 8.22 8.23 8.24 8.25 8.26 8.27 8.28 8.29 8.30 8.31 8.32 8.33 8.34 8.35 8.36 8.37 8.38 8.39 8.40 8.41 8.42 8.43 8.44 8.45 8.46 8.47 8.48 8.49 8.50 8.51 8.52 8.53 8.54 8.55 8.56 8.57 8.58 8.59 8.60 8.61 8.62 8.63 8.64 8.65 8.66 8.67 8.68 8.69 8.70 8.71 8.72 8.73 8.74 8.75 8.76 8.77 8.78 8.79 8.80 8.81 8.82 8.83 8.84 8.85 8.86 8.87 8.88 8.89 8.90 8.91 8.92 8.93 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ 9.00 9.01 9.02 9.03 9.04 9.05 9.06 9.07 9.08 9.09 9.10 9.11 9.12 9.13 9.14 9.15 9.16 9.17 9.18 9.19 9.20 9.21 9.22 9.23 9.24 9.25 9.26 9.27 9.28 9.29 9.30 9.31 9.32 9.33 9.34 9.35 9.36 9.37 9.38 9.39 9.40 9.41 9.42 9.43 9.44 9.45 9.46 9.47 9.48 9.49 9.50 9.51 9.52 9.53 9.54 9.55 9.56 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.00 10.01 10.02 10.03 10.04 10.05 10.06 10.07 10.08 10.09 10.10 10.11 10.12 10.13 10.14 10.15 10.16 10.17 10.18 10.19 10.20 10.21 10.22 10.23 10.24 10.25 10.26 10.27 10.28 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 12.2 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ 15.0 15.1 15.2 Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ 16.00 16.01 16.02 16.03 16.04 16.05 16.06 16.07 16.08 16.09 16.10 16.11 16.12 16.13 16.14 16.15 16.16 16.17 16.18 16.19 16.20 16.21 16.22 16.23 16.24 16.25 16.26 16.27 Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ 17.0 17.1 17.2 17.3 17.4 Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ 18.0 18.1 18.2 18.3 18.4 18.5 18.6 Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ 21.0 21.1 21.2 21.3 21.4 21.5 21.6 21.7 Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ 22.0 22.1 22.2 22.3 22.4 22.5 22.6 22.7 22.8 Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ 24.0 24.1 24.2 24.3 24.4 24.5 Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ 27.0 27.1 Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ 34.0 34.1 Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ 40.0 40.1 40.2 Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ 46.0 46.1 46.2 Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ 47.0 47.1 Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ 48.0 48.1 Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ 50.0 50.1 Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ 51.0 51.1 Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ 55.0 55.1 Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ 59.0 59.1 Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ 61.0 61.1 61.2 Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ 62.0 62.1 Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ 64.0 64.1 Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ 72.0 72.1 Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ 78.0 78.1 Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ 79.0 79.1 Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ 81.0 81.1 Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ 83.0 83.1 83.2 83.3 83.4 83.5 Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ 85.0 85.1 Lua error in package.lua at line 80: module 'strict' not found.
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ 88.0 88.1 Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  90. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  91. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  92. ↑ 92.0 92.1 Lua error in package.lua at line 80: module 'strict' not found.
  93. ↑ 93.00 93.01 93.02 93.03 93.04 93.05 93.06 93.07 93.08 93.09 93.10 93.11 93.12 93.13 93.14 Lua error in package.lua at line 80: module 'strict' not found.
  94. ↑ 94.0 94.1 Lua error in package.lua at line 80: module 'strict' not found.
  95. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  96. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  97. ↑ 97.0 97.1 97.2 97.3 97.4 97.5 Lua error in package.lua at line 80: module 'strict' not found.
  98. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  99. ↑ 99.0 99.1 Lua error in package.lua at line 80: module 'strict' not found.
  100. ↑ 100.0 100.1 Lua error in package.lua at line 80: module 'strict' not found.
  101. ↑ 101.00 101.01 101.02 101.03 101.04 101.05 101.06 101.07 101.08 101.09 101.10 101.11 101.12 101.13 101.14 101.15 101.16 101.17 Lua error in package.lua at line 80: module 'strict' not found.
  102. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  103. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  104. ↑ 104.0 104.1 104.2 104.3 104.4 Lua error in package.lua at line 80: module 'strict' not found.
  105. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  106. ↑ 106.0 106.1 106.2 106.3 Lua error in package.lua at line 80: module 'strict' not found.
  107. ↑ 107.0 107.1 Lua error in package.lua at line 80: module 'strict' not found.
  108. ↑ 108.0 108.1 Lua error in package.lua at line 80: module 'strict' not found.
  109. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  110. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  111. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  112. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  113. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  114. ↑ 114.0 114.1 Lua error in package.lua at line 80: module 'strict' not found.
  115. ↑ 115.0 115.1 Lua error in package.lua at line 80: module 'strict' not found.
  116. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  117. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  118. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=2002_Pacific_typhoon_season&oldid=1103827"