Typhoon Flo (1993)

Typhoon Flo, known in the Philippines as Typhoon Kadiang, was a catastrophic and deadly minimal typhoon that hit the northern Philippines during October 1993. It also caused the largest 72-hour forecast error for the year due to its interaction with the nearby Super Typhoon Ed. The twenty-seventh depression, twenty-second named storm and the eleventh typhoon of the 1993 Pacific typhoon season, Flo originated from an area of convection that was embedded from a monsoon trough during September 28. Two days later, a tropical depression formed within this trough, to the west of Guam. Slowly organizing, it remained a tropical depression until on October 2, when it strengthened to a tropical storm and was given the name Flo by the Japan Meteorological Agency. Slight wind shear from nearby Ed inhibited development; however, it intensified to a minimal typhoon as it neared the coastline of Luzon. On October 3, it made landfall near the Isabela-Aurora in its peak. It then crossed the country while weakening, and moved ashore near the South China Sea the next morning. It then unexpectedly moved back to the country due to its interaction with Ed, and it moved back to the Philippine Sea on October 17 before accelerating to the south of Japan. It then became extratropical on the next day.

"Typhoon Kadiang" redirects here. Not to be confused with Typhoon Kading.
Typhoon Flo (Kadiang)
Typhoon (JMA scale)
Category 1 typhoon (SSHWS)
Typhoon Flo near peak intensity while approaching the Philippines on October 4, along with strengthening Ed to its east
FormedOctober 1, 1993
DissipatedOctober 11, 1993
(Extratropical after October 8)
Highest winds10-minute sustained: 120 km/h (75 mph)
1-minute sustained: 130 km/h (80 mph)
Lowest pressure970 hPa (mbar); 28.64 inHg
Fatalities576 confirmed[1]
Damage$188 million (1993 USD)
Areas affectedPhilippines
Part of the 1993 Pacific typhoon season

Flo caused over 500 deaths, mainly due to flash floods. Some houses were also buried in mud due to the lahar released by Mount Pinatubo. The total damages from the typhoon were finalized at $188 million (1993 USD).[2]

Meteorological history
Map plotting the storm's track and intensity, according to the Saffir–Simpson scale
Map key
Saffir–Simpson scale
  Tropical depression (≤38 mph, ≤62 km/h)
  Tropical storm (39–73 mph, 63–118 km/h)
  Category 1 (74–95 mph, 119–153 km/h)
  Category 2 (96–110 mph, 154–177 km/h)
  Category 3 (111–129 mph, 178–208 km/h)
  Category 4 (130–156 mph, 209–251 km/h)
  Category 5 (≥157 mph, ≥252 km/h)
  Unknown
Storm type
triangle Extratropical cyclone, remnant low, tropical disturbance, or monsoon depression

A persistent and broad area of convection was first mentioned by the Joint Typhoon Warning Center (JTWC) on September 28 for possible tropical cyclogenesis, to the northwest of Palau.[3] It slowly moved to the northwest while becoming well defined, and a Tropical Cyclone Formation Alert (TCFA) was issued on the afternoon of September 30. The disturbance had a blossoming convection surrounding its low-level circulation center at that time.[3][4] The next day, the Japan Meteorological Agency (JMA) reported that the area of convection coalesced to a tropical depression, located approximately 970 km to the east-northeast of Manila, Philippines.[4][5] On the same day, the JTWC followed suit and gave the system its identifier 22W.[3][6] The PAGASA also declared the system a tropical depression at that time in the Philippine Area of Responsibility and was provided the name Kadiang.[7] The storm intensified overnight in the Philippine Sea and early the next day, the JMA, JTWC and the PAGASA declared it a tropical storm, with the former giving it the name Flo.[3][6][5] At this time, Flo was located in a marginally favorable environment for further strengthening, with warm sea surface temperatures and good outflow, being offset by moderate wind shear from the nearby Ed, which was impacting Guam at that time.[6] Its central dense overcast also became defined on satellite imagery, sign that the system was strengthening.[6] Also at that day, the JMA upgraded the system to a severe tropical storm, with its ragged eye emerging.[5] The PAGASA also followed at that time.[2] Forecasts shows that Flo will move away from the Philippines; however, the system accelerated to the west, nearing the coastline of Isabela.[8] On the next day, the JTWC upgraded Flo to a typhoon, with the JMA and the PAGASA following suit.[3][6][5] At that time, the system is approaching the Aurora-Quezon border.[9] It soon reached its peak intensity, having maximum sustained winds of 120 km/h (75 mph) and a minimum pressure of 970 hPa, while nearing landfall.[6] It made landfall on the afternoon of the same day near the Isabela-Aurora border, moving slightly to the north-northwest.[8] It traversed the Northern Luzon that night, while weakening to a severe tropical storm.[8][6] On October 5, it moved ashore on Lingayen Gulf, before moving on the South China Sea by the afternoon.[8][6] Interaction with Ed, which was located to the south of Japan and a high pressure over South China forced Flo to undergo a cyclonic loop near Pangasinan before making landfall again near Bolinao before dawn, as a high-end tropical storm.[8][6] At first, Flo is forecasted to move through the west, making landfall in South China; however, due to these circumstances, the system accelerated even closer to the country.[6] Moving to the northeast, it made another and last landfall near San Fernando, La Union at night.[8][6] On the next morning, Flo has exited the Philippines landmass, before passing near the Nansei Islands, just before starting its extratropical transition.[6] At 18:00 UTC of October 18, it then fully became extratropical near Japan.[4] The remnants of the system accelerated to the north-northeast, before dissipating on 06:00 UTC of October 11 over the Sea of Okhotsk.[4]

Preparations

As Flo approaches the Philippines, all the domestic and international flights at Ninoy Aquino International Airport were cancelled and over 3,000 families were evacuated.[2] Some residents near the mountains and lahar-threatened communities were also forced to leave.[2] Military trucks were also dispatched to help the evacuees and rescue equipment were readied in case of flash floods.[2][10] Sea vessels and large cargo boats were advised to dock in a safe place due to possible storm surge and the Department of Education suspended primary and secondary classes.[11] Isabela, Cagayan, Ifugao, and several other nearby provinces, including the populous Metro Manila have been placed on storm alerts.[11][12] Government offices were also suspended.[12] The Philippine President at that time, Fidel V. Ramos, approved ₱10.2 million ($360,000) from the calamity fund for food packs that would be given to the evacuees.[2]

Impact
Flo inland on October 5

Between 02:00 and 04:00 UTC, Flo (known as Kadiang in the Philippines) made landfall between Isabela and Aurora coastline, causing large storm surges.[8][13][14] At least 576 died, and both an unknown number of missing and injured were reported from the typhoon.[15][8][16] In the capital Manila, strong winds broke the moorings of a barge and another small freighter, pushing them to the shorelines of the Roxas Boulevard.[15][17][18] The capital also experienced 93 mph winds from the storm.[19] Two more fishing ships, MV Camiguan and MV Uniselva, were also washed out in the shores off Manila Bay due to storm surges.[20][21] Mudflows from Mount Pinatubo were also triggered by the typhoon, inundating houses in Pampanga.[2] Over 40,000 hectares of farmland were also destroyed and/or flooded in Central and Northern Luzon.[2] Widespread flooding were also reported at these areas, including some parts of Calabarzon and Metro Manila.[2][10] Adding on, over 384,802 families were affected.[2]

As reported by the National Disaster Coordinating Council, the total damages from the typhoon were estimated at ₱5.3 billion ($188 million, 2005 USD).[2][22][23] The total deaths were finalized from 86 to 576 individuals, making it one of the deadliest tropical cyclones to hit the country.[7][24]

Aftermath

International aid

President Fidel Ramos declared vast majority of Northern Luzon in state of calamity due to the catastrophic effects of Flo in the Philippines.[25] The president also approved $1.35 million for agricultural rehabilitation.[25]

However, these efforts were halted as Typhoon Ira of early-November of the same season caused heavy destruction towards the country.[26]

See also

References
  1. Sajise, Percy E.; Ticsay, Mariliza V.; Saguiguit, Gil C. Jr. (2010-02-10). Moving Forward: Southeast Asian Perspectives on Climate Change and Biodiversity. Institute of Southeast Asian Studies. ISBN 978-981-230-978-5.
  2. "Philippines Typhoon Flo Oct 1993 UN DHA Information Reports 1-5". ReliefWeb. October 6, 1993. Retrieved March 25, 2021.
  3. Joint Typhoon Warning Center; Naval Pacific Meteorology and Oceanography Center (1994). Annual Tropical Cyclone Report: 1993 (PDF) (Report). United States Navy, United States Air Force. p. 56. Retrieved May 11, 2020.
  4. Kenneth R. Knapp; Michael C. Kruk; David H. Levinson; Howard J. Diamond; Charles J. Neumann (2010). 1993 Typhoon FLO (1993271N14134). The International Best Track Archive for Climate Stewardship (IBTrACS): Unifying tropical cyclone best track data (Report). Bulletin of the American Meteorological Society. Retrieved May 11, 2020.
  5. "RSMC Best Track Data - 1990-1999" (.TXT). Japan Meteorological Agency. January 4, 1992. Retrieved May 11, 2020.
  6. "ROYAL OBSERVATORY HONG KONG TROPICAL CYCLONES IN 1993" (PDF). Hong Kong Observatory. Retrieved March 25, 2021.
  7. "Deadliest, most destructive cyclones of the Philippines". The Philippine Star. November 11, 2013. Retrieved March 25, 2021.
  8. "THE ELEVEN WORST TYPHOONS OF THE PHILIPPINES (1947-2006)". typhoon2000.ph. Retrieved March 25, 2021.
  9. "GUSTY TYPHOON FLO BASHES MANILA, RURAL PHILIPPINES". Orlando Sentinel. October 5, 1993. Retrieved March 25, 2021.
  10. "Tropical storm Flo batters northern Philippines". upi.com. October 5, 1993. Retrieved March 25, 2021.
  11. "Storm nears Philippines, another typhoon approaches". upi.com. October 4, 1993. Retrieved March 25, 2021.
  12. "Philippine storm toll climbs to 15". upi.com. October 5, 1993. Retrieved March 25, 2021.
  13. "Typhoon tears into Philippine coast". The Pantagraph. 1993-10-04. p. 5. Retrieved 2021-04-03.
  14. "Typhoon Flo hits Philippines". The Central New Jersey Home News. 1993-10-05. p. 6. Retrieved 2021-04-01 – via Newspapers.com.open access
  15. "Typhoon Flo hits Philippines". Battle Creek Enquirer. 1993-10-04. p. 7. Retrieved 2021-04-01 – via Newspapers.com.open access
  16. "Typhoon Flo lashes Philippines". The Berkshire Eagle. 1993-10-05. p. 8. Retrieved 2021-04-01 – via Newspapers.com.open access
  17. "Typhoon Flo batters Philippines". Santa Maria Times. 1993-10-04. p. 19. Retrieved 2021-04-01 – via Newspapers.com.open access
  18. "Typhoon slams Philippines". Iowa City Press-Citizen. 1993-10-04. p. 3. Retrieved 2021-04-03.
  19. "Manila battered by 93 mph winds from Typhoon Flo; no deaths reported". The Californian. 1993-10-05. p. 4. Retrieved 2021-04-03 – via Newspapers.com.open access
  20. "Shorebound ships". Times Colonist. 1993-10-07. p. 1. Retrieved 2021-04-01 – via Newspapers.com.open access
  21. "Philippine Supreme Court Jurisprudence". chanrobles.com. August 24, 2011. Retrieved March 27, 2021.
  22. "Climate disasters in PH becoming costlier". news.abs-cbn.com. June 28, 2012. Retrieved March 27, 2021.
  23. "Most destructive tropical cyclones". gmanetwork.com. June 25, 2009. Retrieved March 27, 2021.
  24. environmental science a shared responsibility towards the earth. Rex Book Store. ISBN 9789712320262. Retrieved March 27, 2021.
  25. "Ramos declares state of calamity in northern flood area". UPI. Retrieved 2021-04-03.
  26. "Evacuations urged as typhoon Ira nears northern Philippines". UPI. Retrieved 2021-04-03.
Wikimedia Commons has media related to Typhoon Flo (1993).
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.