ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Double Trouble: Hurricanes and Earthquakes Combined

Updated on November 30, 2016
retrojoe profile image

Has studied astrology/historical seismology since the late '70s in San Francisco. Published in the ISAR International Astrologer in 2012.

Location of hurricane Otto (southeast corner of Nicaragua) at one minute after a 6.9 magnitude earthquake occurred (bulls eye representing the epicenter) under the ocean off the west coast of Central America.
Location of hurricane Otto (southeast corner of Nicaragua) at one minute after a 6.9 magnitude earthquake occurred (bulls eye representing the epicenter) under the ocean off the west coast of Central America. | Source

Coincidence or Cause and Effect?

Earth date 2016.11.24: At around midday local time, Otto, a Category 2 hurricane, made landfall in southeast Nicaragua with 110 mph (175 kph) winds. Fortunately it was in a sparsely populated area, near the border of Costa Rica. Not long after that (12:44pm, local time), a magnitude 6.9 earthquake occurred off the west coast of Nicaragua, 150 km (93 miles) SSW of the nearby country of El Salvador. Fortunately, that shock was not close enough or large enough to a populated center to cause any real damage. For the record, the distance between the two destructive forces of nature was no more than 400 km (250 miles); at the time of the earthquake.

Since I routinely investigate worldwide seismic events of at least 6.8 magnitude, I determined that this earthquake was, as far as astrology was concerned, a random event. However, there may be a connecting link or cause and effect relationship between the storm and the temblor.

In the June 2009 issue of the scientific journal Nature, scientists in Taiwan published a report that showed “a definitive connection between fault slip and changes in atmospheric pressure.” What they looked at specifically was how Typhoons appeared to set off small earthquakes along the fault between the Philippine Sea Plate and the Eurasian Plate.

This adds weight to the notion that a sudden plunge in barometric pressure can be the tipping point event that triggers an earthquake along a nearby fault that was about due to release its pent up stresses.

British depiction of the earthquake that destroyed Port Royal, Jamaica on Saturday, 7 June 1692 (the population moved to what would become Kingston after that).
British depiction of the earthquake that destroyed Port Royal, Jamaica on Saturday, 7 June 1692 (the population moved to what would become Kingston after that).

Not Just an Isolated Incident..

Another good example related to this idea is what occurred in Jamaica on 7 June 1692. On that date at 11:40am, local time, an earthquake of at least 7 magnitude struck the island at Port Royal. Approximately 2,000 people lost their lives as buildings tumbled and much of the land that was beneath them fell into the harbor. Unlike what happened recently in Nicaragua though, this one had a link to astrology, but there is also strong circumstantial evidence that it was triggered by a rare hurricane that hit the western side of the island at that time as well. Not only did this storm occur at about the same time and place, but this hurricane was a rare one in that it was the only one to have ever occurred in Jamaica in the month of June. Interestingly, hurricane Otto was the most powerful storm to reach landfall in the Caribbean area so late in the season. It was also one of two or three since 1950 that began in the Atlantic and ended up in the Pacific and still rated as a hurricane.

Ninety-two years after the 1692 Port Royal disaster, their was a category 2 hurricane which was at its worst between 8:30pm and 11pm, local time in the southern portion of Jamaica on 30 July 1784. A large, damaging earthquake of unknown magnitude reportedly occurred during the worst hour of the storm (at between 9pm and 10pm, local time). Many lives were lost and about a dozen ships were wrecked. It would appear that the hurricane did perhaps most of the damage but the earthquake added greatly to the misery. Interestingly, Astrological Aspect Values (or angular relationships between solar system bodies that related to past earthquakes) were peaking in a very big way approximately four hours after this earthquake.

A perfect storm of disaster occurred at just before noon on 1 September 1923 when an 8.0 magnitude earthquake occurred near Tokyo at the same time as residence lit their stoves for lunch and then began feeling the effects of a Typhoon to the north.
A perfect storm of disaster occurred at just before noon on 1 September 1923 when an 8.0 magnitude earthquake occurred near Tokyo at the same time as residence lit their stoves for lunch and then began feeling the effects of a Typhoon to the north.

A Disaster the Japanese can Never Forget..

An even more disastrous example of earthquakes occurring during storms was the Great Kanto earthquake of 1 September 1923, which destroyed Tokyo in Japan, and took the lives of over 100,000 people there. A very large portion of the lives that were lost were due to fires that erupted all over the city caused by people lighting their stoves for the mid-day meal as the earthquake struck (at just before noon, local time). At the same time, the barometric pressure was falling rapidly due to an incoming typhoon and the wind speed soon grew to an intensity of 60mph. The fires burned for days because of the many uncontrolled fires that were whipped into fierce winds mixed with fire that incinerated tens of thousands of people. The only good thing that can be said about this earthquake is that the anniversary of it is used each year to prepare for future earthquakes.

That last disaster may be the worst case of such a connection between immense storms with near simultaneous releases of local seismic energy. The next catastrophe is controversial but often quoted so I have chosen to include it to make matters clearer than have been made in the past. Old lists of the most deadly of historical earthquakes often site a great earthquake occurring on October 11, 1737, which destroyed Calcutta, India and resulted in the death of 300,000 people.

After discovering an article dated January 1994 and written by Rober Bilham, I came to realize that most of the deaths were likely caused by waters along the Bay of Bengal rising to at least 40 feet above their normal levels. All reports indicated that there was a severe storm, but not all witnesses mentioned an earthquake. That does not necessarily mean that there was not really an earthquake but more likely that it was not the principle cause of the death and destruction.

At first I thought that this event occurred one to several days after a mega quake in the Kamchatka region of Russia. It turns out that the October 11 date was in the Gregorian or present calendar rather than the old Julian calendar. As a result, the destruction of Calcutta in October 1737 occurred 5 days prior to the Kamchatka earthquake and tsunami. It thus did not happen within the large window surrounding a significant spike in Astro-Aspect Values that occurred at the time of the Kamchatka earthquake. In other words, a huge earthquake would not be expected at this earlier time.

What makes this seismic event tarnished is the fact that the emphasis on what caused the destruction and death (the later quite possibly over exaggerated) was most likely due to a cyclone which caused the surge of water to inundate the populated areas along the Bay of Bengal shore. Some accounts, especially from sailors, insisted that there was an earthquake at the time of the storm, which there very well could have been, but unlikely to have caused a tsunami.

In summary: During the evening of the 11th of October, 1737 (perhaps almost the 12th of October), there was a cyclone that caused much death and destruction in Calcutta and surrounding areas (all but one of the 29 ships in the harbor were ruined for example). At the same time there was a significant seismic event in the area that was noticeable to many witnesses, but not all witnesses. This would seem to indicate that an earthquake occurred, similar to the event in Jamaica during the hurricane of July 30-31, 1784, but was not the primary cause of any damage or deaths.

In other words, it is still a possibility that this storm, causing a sudden and precipitous drop in barometric pressure, triggered a fairly large earthquake. However, the possible magnitude of the event would likely have been approaching a magnitude of 7 rather than a magnitude of 8 or more. Therefore, the listing of this event as an earthquake which caused hundreds of thousands of deaths is unjustified. However, many modern chroniclers have gone as far as to list this event as “Fake”, which this author feels is going a bit too far.

© 2016 Joseph Ritrovato

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)