Jump to content

2007 Pacific typhoon season

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Ryansit639 (talk | contribs) at 12:43, 17 September 2007 (→Severe Tropical Storm Pabuk (Chedeng)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Ongoing weather

2007 Pacific typhoon season
Seasonal boundaries
First system formedMarch 31, 2007
Last system dissipatedSeason currently active
Strongest storm
NameSepat
 • Maximum winds205 km/h (125 mph)
 • Lowest pressure910 hPa (mbar)
Seasonal statistics
Total storms12 official, 1 unofficial
Typhoons9
Super typhoons2 (unofficial)
Total fatalitiesAt least 120
Total damageUnknown
Pacific typhoon seasons
2005 2006 2007 2008 2009
Wikinews has news related to:

The 2007 Pacific typhoon season has no official bounds; it runs year-round in 2007, but most tropical cyclones tend to form in the northwestern Pacific Ocean between May and November.[1] These dates conventionally delimit the period of each year when most tropical cyclones form in the northwestern Pacific Ocean.

The scope of this article is limited to 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 2007 Pacific hurricane season. Tropical Storms formed in the entire West Pacific basin are assigned a name by the Japan Meteorological Agency (JMA). Tropical depressions in this basin have the "W" suffix added to their Joint Typhoon Warning Center identifier. 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). This can result in the same storm having two names.

Storms

In storm information below, wind-speed advisories differ from the Joint Typhoon Warning Center (JTWC) to the JMA as the JTWC uses the United States criteria of 1-minute mean to designate maximum sustained winds, while the JMA uses the 10-minute mean wind criteria to designate tropical cyclone maximum sustained winds. This difference generally results in JTWC maximum winds appearing higher than the maximum winds described by the JMA for the same cyclone.

Typhoon Kong-rey

Main article: Typhoon Kong-rey (2007)
 
DurationUnknown – Unknown
Peak intensityWinds not specified;

On March 26, the Naval Research Laboratory (NRL) identified a broad area of low pressure in the Western North Pacific. It moved west-northwestward over the next few days, slowly gaining organization. According to the Japan Meteorological Agency, it became a tropical depression on March 30. The next day, the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert due to an increased consolidation of the low-level circulation of the system. The JTWC issued its first warning on Tropical Depression 01W late that evening local time. As it continued to strengthen, the JTWC upgraded it to a tropical storm, the first of the season. The JMA followed suit, and named the system Kong-rey. The name was submitted by Cambodia, and refers to a character in a Khmer legend, which is also the name of a mountain.[2]

Kong-rey continued to organize and intensified into a severe tropical storm early the next morning local time. The JTWC then upgraded it to a typhoon on April 2. As the system took a more poleward track towards the Northern Mariana Islands, the National Weather Service office in Guam noted that damaging winds were now not expected on the island. Elsewhere in the Marianas, preparations were made and flights were cancelled in anticipation of the typhoon. Kong-rey passed through the islands in the early hours of the morning on April 3 local time. The JMA upgraded Kong-rey to a typhoon later that afternoon, as it developed an eye. It strengthened slightly further before encountering wind shear and colder sea surface temperatures and was downgraded back to a severe tropical storm on April 4. As Kong-rey accelerated towards the northeast, it began undergoing extratropical transition early on April 5 and the JTWC issued its final warning. The JMA issued its final warning on the morning of April 6 after it had completed extratropical transition. No casualties or major damage was reported.

Typhoon Yutu (Amang)

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

On May 15, a significant consolidation of organisation in a tropical disturbance located south-southeast of Guam led to Dvorak technique numbers equating to a windspeed of 45 kt from the Air Force Weather Agency. Later that day, the Japan Meteorological Agency designated the system a tropical depression, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert.[3] The next day, the JMA began issuing full advisories on the tropical depression. It developed slowly, resulting in a reissuance of the TCFA later that day. In this second TCFA, the JTWC noted "an increasingly well-defined" low-level circulation centre.[4] The JTWC upgraded the system to Tropical Depression 02W at 1200 UTC, based on satellite intensity estimates and QuikSCAT.[5]

The JMA designated 02W as Tropical Storm Yutu early on May 17, as the system strengthened further. The name 'Yutu' was contributed by China, and refers to a rabbit in a Chinese fable.[2] The JTWC followed suit 3 hours later, upgrading the system to Tropical Storm 02W as it moved quickly westwards, heading for Yap. Tropical storm warnings and watches were put in place for most of the Federated States of Micronesia, but were later cancelled after Yutu passed through quickly.

It then took a northwesterly turn, entered the PAGASA area of responsibility on May 18 as it reached severe tropical storm strength,[6] and was named "Amang". Later that day, the JTWC upgraded it to a typhoon, and identified a "distinct eye feature",[7] and the JMA upgraded the severe tropical storm to a typhoon at 1800 UTC as it continued to intensify. It began to recurve towards Iwo Jima, undergoing rapid intensification,[8] with "enhanced poleward outflow and low vertical wind shear".[9] It reached its peak on the evening of May 20, as a strong Category 4-equivalent typhoon, just short of becoming a super typhoon.

Despite moving into cooler waters, its strong poleward outflow helped it to maintain a high intensity, while carrying a 20 nautical mile-wide eye, on the early morning of May 21.[10] It then began to gradually weaken, passing over Okinotorishima and near Iwo Jima that day as it sped off to the northeast. Maximum winds on Iwo Jima occurred around 1500 UTC that day, with 66 kt (122 km/h, 76 mph) sustained gusting to 104 kt (193 km/h, 120 mph), when a minimum central pressure of 976 hPa was recorded.[11] It then started extratropical transition, and the JTWC issued its final warning on the morning of May 22. The JMA issued its last advisory after extratropical transition completed a day later.

Tropical Storm Toraji

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

An area of disturbed weather formed in the South China Sea on July 2 and gradually consolidated over the next two days as it moved west-northwestward. A Tropical Cyclone Formation Alert was issued by the Joint Typhoon Warning Centre on the morning of July 4, and later that day the disturbance was upgraded straight to a tropical storm just south-east of Hainan Island. It made landfall on the island shortly after. China claimed that a tropical depression formed in the morning on July 2, made landfall in Hainan later that afternoon with maximum sustained winds of 15 m/s (55 km/h, 35 mph)[12] and deepened to 988hPa[13] before making its second landfall. In response to the storm, Guangxi evacuated nearly 147 thousand people.[14]

The Japan Meteorological Agency upgraded the tropical depression to Tropical Storm Toraji on the morning of July 5 while it was in the Gulf of Tonkin, after the centre of the storm had emerged back over water. The name Toraji was contributed by North Korea and refers to the broad bellflower (platycodi radix).

Toraji made landfall in Vietnam around 1200 UTC later that evening, having not strengthened much while over the Gulf of Tonkin. The JMA never analysed the storm beyond 994 hPa and minimal tropical storm strength. The JTWC issued its last advisory after landfall, and the JMA followed suit shortly after.

Typhoon Man-yi (Bebeng)

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

The Naval Research Laboratory began to track an area of disturbed weather just north of the equator on July 4. The circulation centre and surrounding convection started to take shape, although the system was in a "marginal upper-level environment" with moderate vertical wind shear.[15][16] Surface pressure drops of less than 0.5 mb (hPa) were observed on July 6, as the system moved westward.[16] Early on July 7, the Japan Meteorological Agency (JMA) listed the system as a weak tropical depression. Hours later, the Joint Typhoon Warning Centre (JTWC) issued a Tropical Cyclone Formation Alert, as the system consolidated further with "deep convective banding" and improving upper-level conditions.[17]

The JTWC issued its first warning on Tropical Depression 04W later that day,[18] and forecast a gradual intensification, as weak to moderate wind shear and weak poleward outflow balanced the effect of high ocean heat content.[19] The JMA began issuing full tropical cyclone advisories on the tropical depression at the same time.[20] As the depression gained more organisation, it was upgraded to a tropical storm that night by the JTWC.[21] The JMA finally upgraded it to a tropical storm later that evening as the large system consolidated, naming it Man-yi.[22] The name "Man-yi" was contributed by Hong Kong, and is the Chinese name of a strait turned reservoir (the High Island Reservoir). Man-yi continued to organize and became a severe tropical storm on July 9, when downed electricity lines caused widespread power outages on Guam.[23] Tropical storm warnings and typhoon watches were put in place for most of Yap State at some point during the storm. Strong waves from the typhoon capsized a ship 375 miles to the northwest of Guam, killing three and leaving six missing.[24]

The JTWC upgraded the storm to a typhoon on the afternoon of July 10, based on Dvorak technique satellite intensity estimates of 65 kt by both the JMA and the JTWC. Early the next day, the system entered the Philippine Area of Responsibility and was named "Bebeng" by PAGASA. At the same time, the JMA upgraded Man-yi to a typhoon.

Moving over warmer waters, Man-yi underwent rapid deepening late on July 11 and early on July 12 as it churned towards Okinawa in Japan. The United States Military upgraded the Tropical Cyclone Condition of Readiness (TCCOR) levels for Kanto, Yokosuka, Sasebo and Okinawa on the afternoon of July 12 as Man-yi neared the islands.[25] Man-yi was upgraded twice to super-typhoon strength over the next day as it passed through the prefecture. The passage of Man-yi resulted in 37 injuries and widespread power outages in Okinawa.[26] The TCCOR level for Okinawa was downgraded to 1R (recovery) on July 13 while Kanto, Yokosuka and Sasebo's levels were all upgraded in anticipation of the typhoon.[27] Man-yi made brief landfall in Kagoshima Prefecture on Kyūshū early the next day before turning to the east and making brief landfalls in Kōchi Prefecture on Shikoku and in Wakayama Prefecture on Honshū.

As it interacted with land and started to undergo extratropical transition, the typhoon weakened and was downgraded to a tropical storm by the JTWC and a severe tropical storm by the JMA. It became extratropical on July 15 according to the JTWC and hence it issued its final advisory. The JMA issued its final advisory two days later.

Typhoon Usagi

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

On July 26, the Naval Research Laboratory identified an area of disturbed weather east of the Mariana Islands. This area moved westward and increased in organization, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert on the system on July 27.[28] The Japan Meteorological Agency designated the system a tropical depression later that day.[29] The next day, the JMA began issuing advisories on the depression, and the JTWC followed suit, designating it Tropical Depression 05W.[30]

The system quickly strengthened as it approached the Mariana Islands, and the JTWC upgraded it to a tropical storm six hours later.[31] The JMA did so early on July 29, designating the system as Tropical Storm Usagi.[32] The name Usagi was contributed by Japan, and means "rabbit" in Japanese.[2] The National Weather Service office in Guam issued tropical storm warnings for Pagan Island and Agrihan in the Northern Marianas shortly after the system was upgraded.[33]

Usagi passed between Pagan and Agrihan later on July 29,[34] and began to quickly strengthen. The JTWC upgraded it to a typhoon later that day, citing Dvorak technique numbers indicating an estimate of 65 knots (120 km/h, 75 mph) and a developing eye.[35] The system gradually turned toward the northwest, and the JMA upgraded it to a severe tropical storm early on July 30,[36] and then to a typhoon on July 31 as it passed to the south of Iwo Jima.[37] Usagi moved northwest over warm waters, reaching peak intensity on August 1 before weakening due to cooling sea surface temperatures and increasing wind shear as it approached Kyūshū. Usagi made landfall on August 2 near Nobeoka, Miyazaki as a rapidly weakening typhoon, and it was downgraded to a severe tropical storm shortly after. The system continued weakening rapidly as it moved across Kyūshū and Honshū, and the JMA downgraded it to a tropical storm later that day.[38]

The JTWC downgraded the system to a tropical storm late on August 2 and issued its last advisory early on August 3 as it began to undergo extratropical transition. Usagi then made further landfalls on northern Honshū in Aomori Prefecture before becoming fully extratropical on August 4, leading the JMA to stop advisories. Usagi was responsible for 18 injuries in Kyūshū.[39]

Severe Tropical Storm Pabuk (Chedeng)

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

A tropical disturbance developed southeast of Chuuk early on July 31. The system moved west-northwestward over the next several days with little change in organization. On August 4, however, organized convection quickly began to redevelop, and the Japan Meteorological Agency began monitoring it as a tropical depression. The system continued to strengthen, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert on the system early the next day, noting that its environment was "strongly favorable for development".[40] The Japan Meteorological Agency designated the system Tropical Storm Pabuk shortly after.[41] The name "Pabuk" was submitted by Laos, and refers to a large freshwater fish in the Mekong River.[2] The JTWC designated the system Tropical Storm 07W at about the same time, and on August 5 PAGASA named the system Chedeng. As Pabuk continued to move to the northwest, it gained some organisation as it slowly developed outflow.[42] It was upgraded by the JMA to a severe tropical storm on August 6. Moving westwards towards Taiwan, an area of convection south of Pabuk separated and formed its own low-level circulation. Pabuk's upper-level outflow inhibited this new area of convection.

After passing over Taiwan, Pabuk took aim at Hong Kong.[43] The Hong Kong Observatory and Macau's Meteorological and Geophysical Bureau both hoisted strong wind signal 3 on August 9 as the system passed to the south of Hong Kong. The JMA downgraded the storm to a tropical depression later that day and issued its final public advisory, with the JTWC following suit shortly after. The tropical depression then turned back to the east-northeast on August 10[44], forcing the HKO to re-issue signal 3. The HKO also warned that winds were expected to strengthen further locally, and that the Hong Kong Education Bureau had suspended all classes for the day.[45] The HKO issued the gale or storm warning signal 8 at 2:30 p.m. HKT (0630 UTC) later that day as Pabuk moved closer to the territory.[46] This was downgraded to signal 3 later that night as Pabuk took another turn in direction and headed west inland into Guangdong. Early next morning, Pabuk resumed a northeasterly track, edging once again closer to the Pearl River Delta[47] before it weakened further and HKO cancelled all signals.[48]

At least 11 people were killed in the Philippines by Pabuk.[49]

Tropical Storm Wutip (Dodong)

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

A tropical disturbance developed to the south of the developing Tropical Storm Pabuk on August 5, and was first mentioned by the Joint Typhoon Warning Center in its Significant Tropical Weather Outlook on August 6.[50] The Japan Meteorological Agency designated it a tropical depression later that night.[51] By the next day, although still attached to Pabuk and being inhibited by shearing from an upper-level outflow anticyclone over Pabuk,[52] the JTWC issued a Tropical Cyclone Formation Alert.[53] As Pabuk moved away, the depression gradually strengthened, and the JMA designated it Tropical Storm Wutip early on August 8.[54] The name Wutip was submitted by Macau, and means butterfly.[2] It struggled against land interaction, however, and did not strengthen considerably, remaining poorly organised. The storm quickly weakened, and the JMA issued its last advisory on Wutip early on August 9, downgrading it to a tropical depression. The JTWC issued its last advisory shortly after.

Three people were killed and 17 others injured in the Philippines by Tropical Storm Wutip.[55]

Typhoon Sepat (Egay)

 
DurationUnknown – Unknown
Peak intensityWinds not specified;
Main article: Typhoon Sepat (2007)

An area of disturbed weather developed west of the Northern Mariana Islands on August 11. Early the next day, the JMA began issuing advisories on the depression,[56] and the JTWC followed suit, designating it Tropical Depression 09W.[57] Twelve hours later, the JTWC upgraded the tropical depression to a tropical storm[58] based on Dvorak technique satellite intensity estimates and[59] the storm exhibiting tightly-curved convective bands. An upper-level low helped to reduce wind shear that had been affecting the storm.[59] The JTWC also warned of the possibility of rapid intensification.[59] The JMA upgraded the depression to a tropical storm later that day[60] and named it Sepat, a name contributed by Malaysia referring to a freshwater fish species.[2]

By early on August 13, Sepat had moved into PAGASA's area of responsibility and attained the local name "Egay". The JMA upgraded Sepat to a severe tropical storm shortly after.[61] Late that night, Sepat underwent rapid intensification as expected, and was upgraded by the JTWC to a super typhoon the next morning.[62] Sepat slowed in forward speed and took a turn from a west-southwest motion to a more poleward one.[63] Continuing to intensify,[64] Sepat reached a peak minimum central pressure of 910 hPa on the morning of August 16.[65] High ocean heat content and good equatorward outflow allowed Sepat to maintain its intensity, but an eyewall replacement cycle began later that night, resulting in weakening.[66] It made landfall in eastern Taiwan between Taitung and Hualien on the morning of August 18 local time at around 5 a.m. (2100 UTC August 17)[67] and weakened to a minimal typhoon.[68] After crossing the island, Sepat held on to minimal typhoon intensity before weakening to a severe tropical storm that night.[69] It made a second landfall, in mainland China, about 24 hours after landfall on Taiwan and was downgraded to a tropical storm the next morning. It further weakened inland and the JMA issued its final advisory on the morning of August 20.

On August 15, monsoon rains brought by Typhoon Sepat flooded and paralyzed traffic in Metro Manila.[70] Classes and services in government offices were suspended until August 17.[71]

Typhoon Fitow

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

On August 28, an area of disturbed weather that had lingered east-northeast of Saipan became better organised. The Joint Typhoon Warning Center initiated warnings on Tropical Depression 10W the next morning,[72] and the JMA initiated advisories on a tropical depression the same day.[73] Under favourable conditions, the system intensified quickly, becoming Tropical Storm Fitow by afternoon [74] and a severe tropical storm by the evening of August 29. [75] Intensification continued, and Fitow became a typhoon early on August 30.[76] Fitow made landfall near Tokyo, Japan late on September 6[77][78] The JMA downgraded Fitow to a severe tropical storm early on September 7[79], and a tropical storm later that day.[80] The cyclone degenerated into a remnant low on September 8.[81]

Wikinews has related news:

Severe Tropical Storm Danas

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

A disturbed area of weather northwest of Wake Island formed early on September 3 and tracked north then northwest, becoming more organised, and on September 6 was recognised as a full tropical depression by the JMA. [82] A TCFA was issued on the same day.[83] The storm continued northwest-ward toward Japan, becoming Tropical Storm Danas early on September 7.[84] The storm slowed its westward movement and headed north, and then northeast, becoming a severe tropical storm on September 9.[85] By the 11th, cooler waters had weakened the storm down to a tropical storm[86] and the storm degenerated into a remnant low later that day.[87]

Typhoon Nari (Falcon)

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

An area of disturbed weather developed northwest of Guam on September 10 and moved northwestward, slowly increasing in organisation. The Japan Meteorological Agency began monitoring the system as a tropical depression the next day. The depression continued to organise and strengthen, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert on it during the afternoon of September 12, and began issuing advisories on Tropical Depression 12W an hour later. The JMA followed suit early on September 13 and initiated advisories on the system; PAGASA named the system Falcon shortly after. The depression continued to intensify, and the JMA upgraded it to Tropical Storm Nari later that morning. The storm then underwent rapid intensification that afternoon and evening, strengthening from a tropical depression to a typhoon in just 18 hours. The JMA upgraded Nari to a severe tropical storm late that afternoon, and by late that evening, Nari was upgraded to a typhoon. Nari reached its peak on September 14th, and began weakening soon afterwards. It turned extratropical right after landfall in South Korea at tropical storm strength. The name Nari was submitted by South Korea, and means lily.[2]

Typhoon Wipha (Goring)

Template:HurricaneActive

An area of disturbed weather formed southeast of Naha, Okinawa early on September 13. This area gradually became better organised, and a TCFA was issued late on September 14.[88] The JMA upgraded the storm to a tropical depression on September 15,[89] and the JTWC soon followed suit with Tropical Depression 13W.[90] PAGASA named the storm "Goring" later that day. On September 16, the storm had gained enough organisation to be designated as a tropical storm.[91]

Current storm information

As of 0700 UTC September 16, the JMA reports Typhoon Wipha to be located near 23.0°N 126.6°E. The system has maximum 10-minute average winds of 75 kt (140 km/h, 85 mph), gusting to 105 kt (195 km/h, 120 mph). It has a minimum pressure of 960 hPa, and is moving west-northwest at 10 kt (19 km/h, 12 mph).

As of 0600 UTC, the JTWC reports Typhoon 13W (Wipha) to be located about 210 nm (390 km, 240 mi) south-southwest of Naha, Okinawa, with maximum 1-minute sustained winds of 90 kt (165 km/h, 105 mph). The system has a maximum associated wave height of 27 ft (8.2 m).

Other storms

These systems were not officially named as tropical storms by the JMA, although the JMA might have monitored them as tropical depressions. They were, however, designated as tropical cyclones by the Philippines (PAGASA), China (CMA), Thailand (TMD), and/or the JTWC.

TMD Tropical Depression

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

On April 26, an area of disturbed weather formed east of the Malay Peninsula. On May 1, the Thai Meteorological Department (TMD) upgraded the same low pressure cell to a tropical depression in the Gulf of Thailand.[92] It made landfall 10 hours later in Amphoe Pathiu, Chumphon Province.[93] It then passed over the Isthmus of Kra into the Andaman Sea.

The TMD warned residents about heavy rainfall and possible flooding in western provinces during the system's passage. In Ratchaburi Province, disaster response teams prepared for the evacuation of settlements in mountaineous terrain on May 3.[94] The next day, Prachuap Khiri Khan Province was declared a disaster zone after low-lying areas were flooded with waters up to one metre deep. In the capital municipality, a prison was inundated, necessitating the evacuation of prisoners to Ratchaburi. In addition, a portion of rail was flooded, but train services were not disrupted. In Surat Thani Province, mudslides halted traffic in the municipal area. Multiple landslide warnings were also issued in other provinces.[95]

This system was not considered to be a tropical depression by any other agencies while in the Gulf of Thailand, but was tracked by the Naval Research Laboratory.

JTWC Tropical Storm 06W

 
DurationUnknown – Unknown
Peak intensityWinds not specified;

An area of disturbed weather developed in the South China Sea on July 31. Despite strong wind shear in the area, the system gradually increased in organization as it remained nearly stationary, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert on the system on August 2.[96] The JTWC classified the system as Tropical Depression 06W shortly after,[97] with the JMA designating it a tropical depression at the same time.[98] Despite strong wind shear in the area, the system slowly intensified as it meandered along the coast of Vietnam, and the JTWC upgraded it to a tropical storm early on August 4.[99] However, later that day, the JTWC downgraded the storm back to a depression due to the loss of most of the convection.[100]

At least 60 people died in Vietnam due to extensive floods .[101] Total rainfall from 06W in Vietnam throughout the course of the storm was over 24 inches (610 mm).[102] Total rainfall in Hainan during the passage of the tropical storm was 231.6mm.[103]

Timeline of recent events

Main article: Timeline of the 2007 Pacific typhoon season

September

September 12
  • 6 p.m. UTC - Tropical Depression 12W forms southwest of Naha, Okinawa.
September 13
  • 3:45 a.m. UTC - PAGASA designates Tropical Depression 12W as Tropical Depression Falcon.
  • 6 a.m. UTC - The JMA designates Tropical Depression 12W as Tropical Storm Nari.
  • 9 a.m. UTC - The JTWC upgrades Tropical Depression 12W to Tropical Storm 12W (Nari).
  • 3 p.m. UTC - PAGASA upgrades Tropical Depression Falcon to Tropical Storm Falcon (Nari).
  • 6 p.m. UTC - The JMA upgrades Tropical Storm Nari to Severe Tropical Storm Nari.
  • 9 p.m. UTC - The JTWC upgrades Tropical Storm 12W (Nari) to Typhoon 12W (Nari).
September 14
  • 12 a.m. UTC - The JMA upgrades Severe Tropical Storm Nari to Typhoon Nari.
  • 2:45 a.m. UTC - PAGASA upgrades Tropical Storm Falcon (Nari) to Typhoon Falcon (Nari).
  • c. 12 p.m. UTC - Typhoon Nari grazes Kumejima, due west of Okinawa Island.
September 15
  • 9 a.m. UTC - Tropical Depression 13W forms southeast of Naha, Okinawa.
  • 9 a.m. UTC - PAGASA designates Tropical Depression 13W as Tropical Depression Goring.
September 16
  • 12 a.m. UTC - The JMA designates Tropical Depression 13W as Tropical Storm Wipha.
  • 3 a.m. UTC - The JTWC upgrades Tropical Depression 13W to Tropical Storm 13W (Wipha).
  • 3 a.m. UTC - PAGASA upgrades Tropical Depression Goring to Tropical Storm Goring (Wipha).
  • c. 4:30 a.m. UTC - Typhoon Nari grazes Jeju-do, just southwest of mainland South Korea.
  • c. 8:30 a.m. UTC - Typhoon Nari makes landfall in southeastern Jeollanam province, on the Korean Peninsula.
  • 12 p.m. UTC - The JMA downgrades Typhoon Nari to a severe tropical storm.
  • 12 p.m. UTC - The JMA upgrades Tropical Storm Wipha to Severe Tropical Storm Wipha.
  • 3 p.m. UTC - The JMA downgrades Severe Tropical Storm Nari to a tropical storm.
  • 3 p.m. UTC - The JTWC downgrades Typhoon 12W (Nari), in the process of extratropical transition, to a tropical storm, and issues its final warning.
  • 3 p.m. UTC - The JTWC upgrades Tropical Storm 13W to Typhoon 13W (Wipha).
  • 3 p.m. UTC - PAGASA upgrades Tropical Storm Goring to Severe Tropical Storm Goring (Wipha).
  • c. 10 p.m. UTC - Tropical Storm Nari passes over Ulleungdo.
September 17
  • 12 a.m. UTC - The JMA issues its final warning on the extratropical remnants of Tropical Storm Nari.
  • 3 a.m. UTC - The JMA upgrades Severe Tropical Storm Wipha to Typhoon Wipha.
  • 3 a.m. UTC - PAGASA upgrades Severe Tropical Storm Goring to Typhoon Goring (Wipha).

Storm names

See also: Lists of tropical cyclone names and Tropical cyclone naming

Western North Pacific tropical cyclones are named by the RSMC Tokyo-Typhoon Center of the Japan Meteorological Agency. Unlike other basins, where storms are named based on annual lists, tropical cyclones in this basin are named based on the following revolving list. Names were contributed by 13 members of the ESCAP/WMO Typhoon Committee, except for Singapore. The 13 nations or territories, along with Micronesia, each submitted 10 names, which are used in alphabetical order by the English name of the country. Names marked with an asterisk are set for retirement due to its effects in the 2006 season. Otherwise, the list is the same one used for the 2006 Pacific typhoon season except for Pakhar, Noksuri and Haikui, which replaced Matsa, Nabi, and Longwang.[104] The first storm of the season was named Kong-rey. This is the first time that the name Wipha was used; It spelling was corrected from Vipa in 2002.[105]

Contributing Nation Names
Cambodia Damrey Kong-rey 0701 Nakri Krovanh Sarika
China Haikui Yutu 0702 Fengshen Dujuan Haima
DPR Korea Kirogi Toraji 0703 Kalmaegi Mujigae Meari
Hong Kong Kai-Tak Man-yi 0704 Fung-wong Choi-wan Ma-on
Japan Tembin Usagi 0705 Kammuri Koppu Tokage
Laos Bolaven Pabuk 0706 Phanfone Ketsana Nock-ten
Macau Chanchu* Wutip 0707 Vongfong Parma Muifa
Malaysia Jelawat Sepat 0708 Nuri Melor Merbok
Micronesia Ewiniar Fitow 0709 Sinlaku Nepartak Nanmadol
Philippines Bilis* Danas 0710 Hagupit Lupit Talas
RO Korea Kaemi Nari 0711 Changmi Sudal Noru
Thailand Prapiroon Wipha 0712 (active) Mekkhala Nida Kulap
U.S.A. Maria Francisco Higos Omais Roke
Vietnam Saomai* Lekima Bavi Conson Sonca
Cambodia Bopha Krosa Maysak Chanthu Nesat
China Wukong Haiyan Haishen Dianmu Haitang
DPR Korea Sonamu Podul Noul Mindulle Nalgae
Hong Kong Shanshan Lingling Dolphin Lionrock Banyan
Japan Yagi Kajiki Kujira Kompasu Washi
Laos Xangsane* Faxai Chan-hom Namtheun Pakhar
Macau Bebinca Peipah Linfa Malou Sanvu
Malaysia Rumbia Tapah Nangka Meranti Mawar
Micronesia Soulik Mitag Soudelor Fanapi Guchol
Philippines Cimaron Hagibis Molave Malakas Talim
RO Korea Chebi Noguri Koni Megi Noksuri
Thailand Durian* Rammasun Morakot Chaba Khanun
U.S.A. Utor Matmo Etau Aere Vicente
Vietnam Trami Halong Vamco Songda Saola

This is the only time that the name "Vipa" was used. Its spelling was corrected to "Wipha" in 2002.[105]

Philippines

In the Philippines the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) uses its own naming scheme for tropical cyclones within its area of responsibility. Lists are recycled every four years.

  • Amang 0702
  • Bebeng 0704
  • Chedeng 0706
  • Dodong 0707
  • Egay 0708
  • Falcon 0711
  • Goring 0712 (active)
  • Hanna (unused)
  • Ineng (unused)
  • Juaning (unused)
  • Kabayan (unused)
  • Lando (unused)
  • Mina (unused)
  • Nonoy (unused)
  • Onyok (unused)
  • Pedring (unused)
  • Quiel (unused)
  • Ramon (unused)
  • Sendong (unused)
  • Tisoy (unused)
  • Ursula (unused)
  • Viring (unused)
  • Weng (unused)
  • Yoyoy (unused)
  • Zigzag (unused)
  • Abe (unused)
  • Berto (unused)
  • Charo (unused)
  • Dado (unused)
  • Estoy (unused)
  • Felion (unused)
  • Gening (unused)
  • Herman (unused)
  • Irma (unused)
  • Jaime (unused)

See also

Template:Tcportal

References

  1. ^ http://www.typhoon2000.ph/garyp_mgtcs/may03sum.txt
  2. ^ a b c d e f g http://www.jma.go.jp/jma/jma-eng/jma-center/rsmc-hp-pub-eg/tyname.html
  3. ^ http://www.webcitation.org/5OsVeLOvw
  4. ^ http://www.webcitation.org/5OsVVNnd6
  5. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007051615-WDPN.PGTW
  6. ^ http://www.webcitation.org/5OvItpCgk
  7. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007051815-WDPN.PGTW
  8. ^ http://www.webcitation.org/5OxtdN1za
  9. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007052015-WDPN.PGTW
  10. ^ http://www.webcitation.org/5OzUSAWvv
  11. ^ http://www.webcitation.org/5P0yVygEO
  12. ^ http://news.tq121.com.cn/index.php?id=31962
  13. ^ http://weather.unisys.com/hurricane/archive/07070506
  14. ^ http://www.cma.gov.cn/qxxw/t20070706_201895.phtml
  15. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007070516-ABPW.PGTW
  16. ^ a b ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007070606-ABPW.PGTW
  17. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007070702-WTPN.PGTW
  18. ^ http://www.webcitation.org/5Q9mpNBC9
  19. ^ http://www.webcitation.org/5Q9oJj1Rv
  20. ^ http://www.webcitation.org/5Q9q46k4h
  21. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007070721-WTPN.PGTW
  22. ^ http://www.webcitation.org/5QBbpbGO7
  23. ^ Storm exposes GPA vulnerabilities" by Gaynor Dumat-ol Daleno, Pacific Daily News, 10 July 2007
  24. ^ Associated Press (2007). "At Least 3 Die in Shipwreck After Log Carrier Runs Into Typhoon Man-Yi". Retrieved 2007-07-14.
  25. ^ http://www.webcitation.org/5QHA9Lvr2
  26. ^ http://www.ndtv.com/convergence/ndtv/story.aspx?id=NEWEN20070018886
  27. ^ http://www.webcitation.org/5QIp5bcPS
  28. ^ http://listserv.uiuc.edu/wa.cgi?A2=ind0707d&L=wx-tropl&T=0&P=49131
  29. ^ http://listserv.uiuc.edu/wa.cgi?A2=ind0707d&L=wx-tropl&T=0&P=52496
  30. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007072815-WTPN.PGTW
  31. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007072821-WTPN.PGTW
  32. ^ http://listserv.uiuc.edu/wa.cgi?A2=ind0707e&L=wx-tropl&T=0&P=920
  33. ^ http://listserv.uiuc.edu/wa.cgi?A2=ind0707d&L=wx-tropl&T=0&P=60506
  34. ^ http://listserv.uiuc.edu/wa.cgi?A2=ind0707e&L=wx-tropl&T=0&P=1031
  35. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007072921-WTPN.PGTW
  36. ^ http://listserv.uiuc.edu/wa.cgi?A2=ind0707e&L=wx-tropl&T=0&P=10178
  37. ^ http://listserv.uiuc.edu/wa.cgi?A2=ind0707e&L=wx-tropl&T=0&P=23783
  38. ^ http://www.webcitation.org/5QnoxwrSd
  39. ^ http://news.bbc.co.uk/2/hi/asia-pacific/6928931.stm
  40. ^ http://www.webcitation.org/5QrV9UEcZ
  41. ^ http://www.webcitation.org/5QrUisG7f
  42. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007080603-WDPN.PGTW
  43. ^ http://www.webcitation.org/5Qw3hcrHE
  44. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/Tokyo/2007081000.RJTD
  45. ^ http://www.webcitation.org/5Qyz1SfjJ
  46. ^ http://www.info.gov.hk/gia/wr/200708/10/P200708100252.htm
  47. ^ http://www.info.gov.hk/gia/wr/200708/11/P200708110058.htm
  48. ^ http://www.info.gov.hk/gia/wr/200708/11/P200708110107.htm
  49. ^ http://www.nytimes.com/2007/08/09/world/asia/09asiastorms.html
  50. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007080622-ABPW.PGTW
  51. ^ "TROPICAL DEPRESSION 1002 HPA AT 14N 128E WEST SLOWLY."
  52. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007080706-ABPW.PGTW
  53. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007080710-WTPN.PGTW
  54. ^ http://www.webcitation.org/5QveYQwBH
  55. ^ http://www.reliefweb.int/rw/rwb.nsf/db900sid/LRON-75WDVR?OpenDocument&rc=3&emid=FL-2007-000125-PHL
  56. ^ http://www.webcitation.org/5R27gMhi1
  57. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007081209-WTPN.PGTW
  58. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007081215-WTPN.PGTW
  59. ^ a b c ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007081215-WDPN.PGTW
  60. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/Tokyo/2007081218.RJTD
  61. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/Tokyo/2007081306.RJTD
  62. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007081503-WDPN.PGTW
  63. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007081515-WDPN.PGTW
  64. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007081603-WDPN.PGTW
  65. ^ http://www.webcitation.org/5R7nAjOR1
  66. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007081615-WDPN.PGTW
  67. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007081803-WDPN.PGTW
  68. ^ "www.webcitation.org/5RAux0QOD".
  69. ^ "www.webcitation.org/5RBaYJ7 DL".
  70. ^ http://newsinfo.inquirer.net/breakingnews/metro/view_article.php?article_id=82753
  71. ^ http://newsinfo.inquirer.net/breakingnews/metro/view_article.php?article_id=82675
  72. ^ http://www.webcitation.org/5RRO8fMD7
  73. ^ http://www.webcitation.org/5RRdq2DRO
  74. ^ http://www.webcitation.org/5RRvY3wO7
  75. ^ http://www.webcitation.org/5RSTzZ1BY
  76. ^ http://www.webcitation.org/5RTxllIjg
  77. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007090621-WTPN.PGTW
  78. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007090703-WTPN.PGTW
  79. ^ http://www.webcitation.org/5RfLticGc
  80. ^ http://www.webcitation.org/5RgCLvEx1
  81. ^ http://www.webcitation.org/5RhC3MCKm
  82. ^ http://www.webcitation.org/5RemhDQnW
  83. ^ http://www.webcitation.org/5Rg8d8IOC
  84. ^ http://www.webcitation.org/5Rg8MV1L7
  85. ^ http://www.webcitation.org/5RjRT64U4
  86. ^ http://www.webcitation.org/5RmNHITAt
  87. ^ http://www.webcitation.org/5RmeUUSrW
  88. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007091422-WTPN.PGTW
  89. ^ http://www.webcitation.org/5Rs2go3sQ
  90. ^ ftp://ftp.met.fsu.edu/pub/weather/tropical/GuamStuff/2007091509-WTPN.PGTW
  91. ^ http://www.webcitation.org/5RsyICRTz
  92. ^ http://www.webcitation.org/5OYVtqA60
  93. ^ http://www.webcitation.org/5OflZMymj
  94. ^ http://etna.mcot.net/query.php?nid=29216
  95. ^ http://etna.mcot.net/query.php?nid=29232
  96. ^ http://www.webcitation.org/5QnnpEgiU
  97. ^ http://www.webcitation.org/5QnmeN9vY
  98. ^ http://www.webcitation.org/5QnmkpKYv
  99. ^ http://www.webcitation.org/5Qpk7PTqg
  100. ^ http://www.webcitation.org/5Qr36gUbH
  101. ^ http://vnexpress.net/Vietnam/Xa-hoi/2007/08/3B9F906A/
  102. ^ http://www.latimes.com/news/nationworld/world/wire/sns-ap-vietnam-storm,1,6489764.story
  103. ^ http://mb.hainan.gov.cn/gov/text/qxxx081208071.txt
  104. ^ http://www.smg.gov.mo/ccaa/typhoon/e_tcname_y2k.htm
  105. ^ a b "Typhoon Committee Operational Manual Meteorological Component" (PDF). Wprld Meteorological Organization. p. 36. Retrieved 2007-09-16.
Wikimedia Commons has media related to 2007 Pacific typhoon season.

Template:2000-2009 Pacific typhoon seasons

Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=2007_Pacific_typhoon_season&oldid=158483600"