AirAsia Flight QZ8501

Analyses of distinct mundane events, using the methods of Sidereal mundane astrology
Post Reply
User avatar
Jim Eshelman
Are You Sirius?
Posts: 19063
Joined: Sun May 07, 2017 12:40 pm

AirAsia Flight QZ8501

Post by Jim Eshelman »

AirAsia Flight 8501 was destroyed December 28, 2014, apparently at 6:12 WIB (23:12 UT December 27) at 3S22'15", 109E41'28", while flying from Surabaya, Indonesia to Singapore. All 162 people aboard the flight (passengers and crew) died, including one infant. (The flight departed Surabaya at 5:35 WIB, in case anyone wants to work with the take-off chart.)

The plane encountered bad weather. The pilot requested permission to veer left from their flight path and climb to a higher altitude to avoid it. The first permission was granted, but not the second. Six minutes later, they were lost from radar. I have used the time the transponder signal was lost (perhaps from a lightning strike? I'm guessing), although the flight apparently was still in the air for several minutes after that. But something happened at 6:18 to kill the transponder, just as Mercury rose at the location. (Once more we see Mercury-Uranus for an aircraft disaster - and this one involving a storm.)

Year: Capsolar
Sun sq. Asc (1°35')
Venus on MC (2°25')
wider angularities of Moon, Mars, Jupiter, Pluto
The Moon-Jupiter-Pluto & Venus-Mars aspects we've seen all year
Moon-Mars sq. (2°36' in mundo)
Mars-Jupiter sq. (1°44' in mundo)

Half year: Cansolar (Dormant.) Moon-Mercury sq. (1°09').

Quarter: Libsolar
Uranus sq. MC (1°28')
Mercury on Dsc (3°12'), Venus on Dsc (5°27'), Sun on Dsc (6°47'), Pluto on MC (4°52')
Moon-Saturn sq. (1°12')
Me/Ur on horizon (0°04'), Me/Pl on angles (0°50'), Ve/Pl on angles (0°18'), Su/Pl on angles (0°58')
Uranus-Pluto sq. (1°31' in mundo)
Sun-Venus conj. (1°20' in mundo)
Mercury-Venus conj. (1°37')

Month: Caplunar (Dormant.)

Week: Liblunar
By flow-through, the Liblunar is probably the operative chart, although Mercury's orb is slightly large for clearing dormancy:
Mercury on MC (3°19')
Uranus on Asc (8°34'), Sun on MC (8°34'), Venus on MC (5°20'), Pluto on MC (9°50')
Uranus-Pluto sq. (1°16' in mundo)
Su/Pl on MC (0°38'), Su/Ur on angles (0°00')

Day: Capsolar Quotidian & Transits
CapQ Moon op. s. Sun (0°16'), SQ Sun (0°42')
CapQ Asc sq. t. Sun (0°54')
----------------------------------------
t. Pluto op. s. Moon (0°55')
t. Venus conj. s. MC (1°10')

Day: Canpsolar Quotidian & Transits
t. Uranus conj. CanQ Moon (0°14')
t. Pluto sq. CanQ Moon (0°40')
CanQ MC sq. s. Neptune (0°06')
CanQ WP on t. Neptune (1°51')
-------------------------------------------
t. Sun sq. s. Moon (0°02')
t. Moon sq. s. MC (1°10')

SUMMARY
Year: Sun, Venus (Moon, Mars, Jupiter, Pluto). Moon-Mars-Jupiter, Moon-Jupiter-Pluto, Venus-Mars.
Half year: (Dormant.)
Quarter: Uranus (Sun, Mercury, Venus, Pluto). Moon-Saturn, Sun-Venus, Su/Pl, Mercury-Venus, Me/Ur, Me/Pl, Ve/Pl, Uranus-Pluto.
Month: (Dormant.)
Week (Liblunar by flow-through): Mercury (Sun, Venus, Uranus, Pluto). Su/Ur, Su/Pl, Uranus-Pluto.
Day (Capsolar): Sun, Moon-Sun (CapQ). Venus, Moon-Pluto (transits to Capsolar).
Day (Cansolar): Neptune Moon-Uranus-Pluto (CanQ). Moon, Moon-Sun (transits to Cansolar).
Jim Eshelman
www.jeshelman.com
User avatar
Jim Eshelman
Are You Sirius?
Posts: 19063
Joined: Sun May 07, 2017 12:40 pm

Re: AirAsia Flight QZ8501

Post by Jim Eshelman »

It's not an outstanding showing. It's probably adequate.

In part, for an event like this, I measure whether it's outstanding on whether or not the astrological information could have been put to good use in preventing something like this in a perfect world where astrology is routinely used in the same way that, say, weather forecasts are used in flight planning. In this case, astrology could have reduced risk significantly and meaningfully, but perhaps only at too great an economic cost to make it realistic to consider.

Let's break this down...

If I were a flight planner (or airlines risk officer, or whatever), I would have started paying attention in October with the Libsolar. Through the region where they were flying, Uranus was angular (in close aspect to Pluto), and we had the Mercury/Uranus midpoint line sliding through the region. At the actual location of the destructive event, Me/Ur was a mere 0°04' from the horizon. By now, any Mercury-Uranus aspect tightly foreground or with its midpoint narrowly on the angles should worry people who are responsible for airplane flight safety! -- But to use this information (which would require better computer software than I have, in order to plot it carefully), airlines would have needed to designate a corridor several miles either side of this Mercury/Uranus line as a high risk zone for three months, try not to fly along it, and flag any unusual situation near it very rapidly. This is what I mean by economic feasibility: Could we get the airlines to agree to this kind of restriction and heightened security - perhaps collaboratively - given the economic realities? I'd like to think we could.

But then, where do we go from there?

Under normal conditions, the lunar ingresses wouldn't have gotten my attention for that particular region. I can see the Liblunar flowing through, but I'd have ignored it for the exact location. (I haven't checked to see if the Mercury, and perhaps Mercury-Uranus, was more centered on one of the airports involved. But it wouldn't have caught my attention too much for the exact flight location.)

The Day indicators are less than stunning. The main indication applies to the whole world: the Pluto transits to both Capsolar Moon and CanQ Moon, with Uranus joining on the CanQ. If I were responsible for the safety or passengers, I'd block out this whole time period as much accelerated risk - several weeks. Again, how does an airline handle this during holiday accelerations of air traffic and large increases of passengers? What are the practicalities? I could justify warnings better if the CapQ had critical angular contacts to localize this; it does not. But we do have the CanQ angularities of Neptunes. (In real life risk management, would they drop down the extra layer? They should, but it makes it harder to "sell" with extra layers.)

It doesn't narrow to the day so well. The most I could have told them is that a certain band is very high-risk for airplane disasters for three months, the current few weeks are generally much accelerated risk from the Pluto and Uranus transits to the two Moons, and maybe - just maybe, if I'd looked deep enough - that there was a band of confusion, disorientation, and bad judgment that should set off red flags on a particular day. Maybe that would have been enough, maybe not.

We'd need better software but, in the fictitious world where we had such buy-in to use astrology for this purpose, that software could be developed - there would be engineers and other resources to produce it.
Jim Eshelman
www.jeshelman.com
User avatar
Jim Eshelman
Are You Sirius?
Posts: 19063
Joined: Sun May 07, 2017 12:40 pm

Re: AirAsia Flight QZ8501

Post by Jim Eshelman »

Oh, and as long as we're fantasizing... If I were connected to Malaysia Air or any of its subsidiaries, I'd start becoming downright hair-trigger phobic about Neptune lines! Neptune was angular in the Day charts for the disappearance of Malaysia Flight 370 and the loss of AirAsia Flight 8501 (operated by Malaysia Air), and in the Caplunar for the shooting down of Malaysia Fligght 17.

These also all occurred under charts showing very serious economic blows - do you think that's enough to get their attention?
Jim Eshelman
www.jeshelman.com
User avatar
Jim Eshelman
Are You Sirius?
Posts: 19063
Joined: Sun May 07, 2017 12:40 pm

Re: AirAsia Flight QZ8501

Post by Jim Eshelman »

Investigators have now reported that, "The way the pilots responded to a technical malfunction resulted in the crash" of this plane, per CNN.

The plane disappeared as Pluto (squared by Uranus) exactly rose (0°03') and with Mercury square Mars (0°18'). The following parans were in force at 3S22 when this occurred:

Saturn-Neptune sq. (0°34')
Uranus-Pluto sq. (0°11', 0°46', 0°53')
Jim Eshelman
www.jeshelman.com
Post Reply