LIEUTENANT AL-KASEASBEH BURNED IN STRANGE FIRE
His fate was sealed at the time of Cain and Able, but it was easier to find it when we knew the method of execution. 2/6/2015.
When looking for someone’s fate in the Torah Code, how the name is spelled is critical. If a name is Hebrew then how it is spelled in Hebrew is the way to go, but when the name isn’t Hebrew the following practice is essential to know. There are no letters for S in Hebrew – shin/sin and samech. Samech is most commonly used for transliterations, but it is the rarer S. Likewise, there are no letters for T in Hebrew – tav and tet. Tet is most commonly used for transliterations, but it is the rarer T. It is my practice to search for news worthy names in the newspaper HaAretz. When I find they use samech or tet, I substitute the more common form. The Code more often uses shin/sin and tav for transliterations. Using this rule we can find Lieutenant Kaseasbeh’s fate encoded with the minimum skip of his name.
STATISTICAL SIGNIFICANCE OF FIGURE 1. As per my standard protocol, no statistical significance is assigned to the axis term, here AL-KASEASBEH at its lowest skip in wrapped Torah. Three terms met my a priori criteria for analysis. Of these the most significant one was AND SLEW HIM. The phrase occurs once in Torah when Cain slays Able. Perhaps what got so much attention with AL-KASEASBEH was the fact that he was slain so horribly by his Muslim brothers that his blood calls out from the ground for revenge which King Abdullah of Jordan is now administering. This term interested the pilot's name. The odds against it being somewhere on the 304-letter matrix were about 1,003 to 1. Overlooking the topics of shared or conflicting letters, the odds against it being in a 56-letter box with AL-KASEASBEH were about to 5,443 to 1.The phrase STRANGE FIRE occurs four times in Torah. The odds against its appearance in the open text were about 251 to 1. Finally, SURELY DIE appeared in the open text against odds of about 37.6 to 1. Overall, this spectacular description of the lieutenant's fate appeared against odds of about 9,482,845 to 1. I did not include PILOT because it violated my 3-letter spacing rule for short, 3-letter words, and I did not include UNDER THE SKYS because it was only found a posteriori.
Why Hindsight is 20-20 Vision, and Predictions are Risky. When I posted Figure 2 (minus the term BURNT) I wrote of the statistical significance of the matrix, "As per my standard protocol, no statistical significance is assigned to the axis term, here M. KASEASBEH at its 102nd lowest skip in wrapped Torah. My general rule is to not use such a poor ELS rank unless there are at least two a priori key words at a special case skip. Here there are four such terms -TO BEHEAD, (5)775/2015, JORDAN and WAR. Before considering the ELS rank of the axis term, TO BEHEAD was found at a special case against odds of about 438 to 1.... the final odds against the matrix existing of about 18,605 to 1."
Where did I go wrong? For starters, an axis term ELS rank of 102 is exceedingly high. Perhaps we shouldn't use so high a rank even with four great terms. There may also be a problem with how I conducted the search for TO BEHEAD. If I find an a priori key word when the axis term is at or near its minimum skip then the special case rules are justified. But in this case I deliberately bypassed 101 incidents of M. KASEASBEH at lower skips just because I wanted to see if the expected means of execution would be there at the same absolute skip of the axis term. This is not my normal protocol, and it is a questionable practice. Using this technique, a match might be found with an axis term at its thousandth lowest skip or higher if the axis term is found in great abundance. So, although I divide combined odds by the ELS rank of the axis term, perhaps even that correction is not enough. The spectacular odds for Figure 1, which is based on the minimum skip of the axis term, are posted above. But it should be noted again on Figure 2 that although the key word I sought was wrong, the correct word, BURNT, shared a letter with it. It almost looks like the Code Author knew someone would look for TO BEHEAD and therefore He included the correction as part of the same word. While that might be so, in reality the word BURNT at a non-special case skip (a special case skip is +/- 1 or the absolute skip of the axis term) is not statistically significant. It had about a 61% chance to be somewhere on the full matrix while TO BEHEAD had only a 0.22% chance to be there at a special case skip. The full Figure 2 odds against the find are downgraded from 1 chance in 18,605 to 1 chance in 801. If we just look at the terms on Figure 2 with a white background (excluding BURNT) then what is found in the remaining 406 letters had one chance in 2,392 to be there. This means that it was not worth the extension to 696 letters to pick up BURNT.