Warning

Warning: This site contains images and graphic descriptions of extreme violence and/or its effects. It's not as bad as it could be, but is meant to be shocking. Readers should be 18+ or a mature 17 or so. There is also some foul language occasionally, and potential for general upsetting of comforting conventional wisdom. Please view with discretion.
Showing posts with label Brown Moses. Show all posts
Showing posts with label Brown Moses. Show all posts

Tuesday, January 3, 2017

Aleppo Convoy Attack: Did the Russians Slant Gravity?

Aleppo Convoy Attack: Did the Russians Slant Gravity?
September  29, 2016, last edits October 8
moved January 3, 2017 from How we Can Know Russia Did Not Bomb the Aleppo Aid Convoy

Note, Jan. 3: Besides moving this from its original spot, I've decided (back in October) this isn't the best leading argument I thought it was. (see postscript below) But it is what it is, a possible supporting clue. It might be as valid as it seemed - which was pivotal, a smoking gun. And it has some side-issues of importance either way.
---
Recently I addressed the September 19 SARC convoy attack that killed a reported 31 people (and that might be everyone) with a post How we "Know" Russia or Syria Bombed the Aleppo Aid Convoy (21st Century Wire re-post of version 1) With the West blaming Russia and Russia and Syria blaming terrorists, there are many aspects to the case slowly coming into focus at the ACLOS (A Closer Look On Syria) page Attack on Red Crescent convoy in Urm al-Kubra and its talk page, besides in some spots linked below.

I'll leave most aspects alone here and lead with this clue. It's a forensic argument, but a fairly simple one that clearly illustrates the fraudulent nature of the Russian airstrike narrative. While this point is obvious once you see it, it seems everyone has failed to notice it until now.

First, this regards the same scientific proof the anti-Russia media hordes have already run with. The remains of a Russian-made gravity-driven bomb, of the model OFAB-250, were seen inside a blast crater at the attack site. This 250-pound bomb has a distinct tail section that, if twisted and crumpled, would look just like the thing found inside the warehouse where trucks were unloading. It's under a hole in the roof such a bomb could tear. We've established that the hole wasn't there yet on the afternoon before the attack (Russian drone footage proves this), so it most likely happened during the infamous attack.

A Russian bomb found at the site looked like clear proof, likely to play into any slanted UN investigation, and picked up quickly by some like The UK Independent,  several Ukrainian outfits like UAToday and UNIAN, and the Daily Beast: This Is How Russia Bombed the U.N. Convoy (filed under "GUILTY AS CHARGED" - see right), besides mentions elsewhere.

These all cite Bellingcat, Elliot Higgins' open source investigations group, widely used to lend a science-like sheen to the blatant propaganda claims of the Atlantic community and its local terrorist proxies, in Syria, Ukraine, and elsewhere. Others had noticed a distinct shape half-buried under some boxes, at the crater's center, but it's Bellingcat that apparently got the White Helmets to send a clearer image of the tail section, still in situ but with debris removed. With this, they published Confirmed : Russian Bomb Remains Recovered from Syrian Red Crescent Aid Convoy Attack 

How the fragment looks doesn't matter here - everyone agrees on what it probably is. There was such debris and, Bellingcat implies, it was found in a way that "confirmed" the existing claims of Russian guilt. So this is perhaps the best answer to how we "know" Russia did this with aerial bombardment. One of their bombs is in the crater inside the warehouse.

Below is the graphic Bellingcat produced and that's been widely reused to prove Russian blame, as well as to question it. To start with, I don't question anything in this image - this is an accurate and useful tool. We'll refer to it below. It does not confirm Russian guilt: rather, it strongly contradicts it.
Yellow shows match from OFAB to the debris seen - Magenta arrows point from entry hole to the OFAB tail fin in the crater - green box just helps clarify its there, even if not visible from this angle.





There is a decent argument that this tail section is from a bomb that detonated somewhere else, and was simply planted here. If it was un-exploded but buried, as some have presumed, why would the White Helmets half-excavate it like that just for a photo? It's dangerous. And if it detonated and was thus inert, then why are there intact cardboard boxes just inches away, still mostly stacked together properly? (that's part of why some have presumed this was a "dud.") (see ACLOS discussion of the scene)

These are good questions, but to me they seem secondary to the main problem, now that I finally see it.

It's Slanted, Dummy!
The OFAB-250 bomb has no propulsion system. It doesn't fly. When first dropped, it'll have some of the jet's momentum, but once it starts plummeting, that's all it does, for 20,000 feet or so. If one were to punch through this roof as seen, it would do nothing but plunge into the ground directly beneath the hole.

But looking at Bellingcat's proof graphic above, a curious thing - the magenta line of arrows does not go straight down, does it? For some reason the crater is not directly beneath the hole. It's off by a good distance, around a meter.


This might be no bizarre mystery. Consider that any projectile launched from the ground will arc up to a highest point and then back down on a gently curving diagonal track like this, as it traverses its horizontal distance (basic illustration at right - purple is a gravity drop, magenta again shows the slanted descent, traced back into its full arc.)

A mortar shell or rocket will also cause directional damage reflecting both its direction of flight and angle of descent. The pattern of damage on the walls and truck, boxes and people would tell us where it came from. We can already see the basic descent angle  The detonation blast moves radially from the magenta line, perpendicular, so basically its bottom edge runs along the yellow line in Bellingcat's graphic above. Note burn marks on the pillar starting at that line. In fact, the way the magenta and yellow lines meet at 90 degrees in that image is rather helpful to see why this is no Russian-dropped bomb. 

Here's my version (all lines and locations approximate: photo rotation/perspective distortion and 3-D effect are minimal and not considered). As above, purple is an OFAB-250 drop angle (zero), and magenta is the evident angle (app. 25-30 degrees from vertical). (see ACLOS posting with discussion). As we can see, the angle Bellingcat traces to the the crater's center is correct enough.
30 degrees or less off from vertical is fairly steep, suggesting the projectile was fired from nearby. This would be to give it a relatively vertical angle, but it's still not enough to mimic a dropped bomb very well.

What I think happened: some locally-fired rocket or mortar shell * was able to pierce the roof, hit the center of that crater, and only then detonate. This suggests unusual weight and penetration capability (the noted steep descent angle would help with this) as well as some kind of delay fuze.  These features both seem unusual and might be something new (though I'm not the most read-up on weapon trends).

 * The general blast pattern is similar to rocket impacts I've studied, so I feel that's more likely. But some mortar or artillery shells operate on similar principles, and I don't know enough to exclude these.

Whatever its main action, the blast apparently caused a sort of fireball, occupying a space that's hard to explain.  The shape marked in orange is a cross section of the 'forward' half of this. If we take that orange area and extrude it radially around the magenta line, it makes sort of funnel-shaped area that's the best place to look for damage. We can see where a rolling fireball scorched the surfaces at random spots within that zone, including on the back wall just one small patch at its furthest reach. 

Shrapnel
Shrapnel marks should occur in the same basic area as the fireball, but with a wider scatter pattern. On the walls and truck (so anywhere in this photo) we see few if any clear marks. The densest band of shrapnel would mark the columns on the right-hand and inner faces, form an arc high along the back wall and/or  across the ceiling, angling down across the truck's side (higher at the back end, lower near the middle-front) and into the boxes. The right-hand wall would be marked near the bottom if at all, and into the boxes there and the ground. 

The resolution on these areas is not the best, as they're mostly a ways across the room, and most of them are smoke-stained too. Only the nearer pillar is sure to show it, and might, partly (a few marks at the top). 

Of course none of this material is made of cardboard or flesh, so lighter shrapnel might leave mark you could see only with a magnifying glass. The people are not here to look at, thankfully. So let's look at the cardboard. Here's the most detailed view I could find of how it gets torn. (new window for fuller view)

Considering the above, low damage along front wall is expected. The picture below is from a similar view to the others but closer to the crater and looking more towards the front wall. The truck is off-frame to the left. I dropped blue dots where I saw a mark or tear like the ones above.

From left to right these start higher, shift lower, get denser, and then get jumbled or no longer there in the immediate impact area. This possible shrapnel is looking light, sharp, and not too energetic (smaller blast than usual perhaps). This seems unusual, and perhaps new, like the delayed detonation after an unusually good roof-piercing. Also, I marked a few small soot/scorch marks of a lesser 'fireball' on this side of the detonation (blue circles). The fire had less space to form here. The wall doesn't seem scorched at all.

Flight Path:
Anyway, this pattern seems to fit perfectly with the other angle of impact clues.

Looking at the crater and the roof hole, it's hard to say which is closer to that nearest pillar line. They both seem fairly close, maybe 1/3 of the way between the rows. If they lines up exactly, the line between them would run perpendicular to the front wall, or straight into the building from across its front lot. But this isn't very exact.

The orange shape cross section in my graphic above marks out a plane, which should be about on the fireball's longest axis. This suggests it's also on the projectile's flight path - it expands more in this direction because it's detonating while moving with kinetic energy, which it got from traveling inside the rocket/shell along that line.

So, tracing that line along the ceiling from the furthest smoke stains to the nearest and then to center of the hole should be the basic trajectory. It's close to straight into the building, with a slight angle from the west. The building's rotation from north roughly cancels this out, putting the source of fire almost due south. This is traced in orange below, and the flight path extension runs back in gold:

The range could be wider, but not by much. The distance out on this line is unsure, but my eye is drawn to that road area (an old airstrip?). That seems kind of nice and open, accessible area to work, just about exactly 800 meters from the roof hole. But I might be biased - in my experience, 800m south is a good place to fire false-flag rockets from. It could easily be closer, or a bit further, but in this direction.

Summary / Whodunnit
There may or may not have been aircraft involved in this attack. But whose that would be remains open to question, despite Western assurances only Russian or Syrian jets could possibly operate there.

Consider: there's no room in the Russian blame story for local artillery (rocket/mortar) strikes as part of it. Most activists say there was jet bombing, jet machine gunning, and helicopter barrel bombing involved. Some also specify surface missiles/rockets were used, all fired by government forces. These could produce such an arc if they were close enough, but they weren't - rather, they were kilometers away to the east in Aleppo. This angle could also come from a jet-fired missile, But this can't be either of those, according to the allegations; there's a gravity bomb sitting in that crater. 

Local rebels covered up this local strike, planting that tail assembly and calling it a Russian bombing, so clearly it's themselves or allies they're covering for. The area all around is reportedly under control of Harakat Noureddin al-Zenki, "moderate Islamists" who formerly received US military aid. They've since been cut-off, but might still cooperate with Washington if asked. Al-Zenki was recently accused of launching a chemical weapons attack in Aleppo (August 2, ACLOS), and earlier had two top commanders openly partake in the abuse and beheading by knife of a captured boy (al-Zenki promised the killers were arrested, but they were seen out with guns two weeks later - again, see ACLOS). Is this another crime to add to their rap sheet? 

So, if there were jets or drones or helicopters coordinating with this, they would be someone on the rebel-terrorisits-NATO-coalition side, not the Russia-Syria side. They would be doing it secretly, to frame Russia and Syria. The official denials fit with that perfectly, as does the information warfare to follow - insistence on Russian guilt and demands for a no-fly zone in response. So if this was, as alleged, an "airstrike" - even in part - it's all clearly part of the same team effort with the terrorists who fired into the SARC warehouse that night. The aim of this effort is, at least, to undermine all efforts to engage the Islamist forces that prevent a return to peace in Syria. At most, it's the start of an all-out effort to put these terrorists in charge of all Syria's land and people.
---
Postscript, Oct. 3: I left a comment at Bellincat's article, but they refused to approve it. Other newer comments are approved, but not mine. Past precedent already showed Higgins and co. refuse to review or even acknowledge work that trumps their own. Truth-based investigators should have no trouble considering an alternate view, but these guys avoid the truth every time it runs counter the kind of findings they're expected to come up with. This or them is another "open-source" disinformation hit-and-run against Syria.

Postscript Oct. 8: I've decided this isn't the best leading argument I thought it was. It didn't seem to phase Bellingcat's sleuths or much of anyone else so far, and in fact I can't prove that is significant. To clarify, the bomb wouldn't fall absolutely straight down. It would start with the jet's forward momentum, and that would fade  away, but not completely. How much would remain at the end? That depends on the laws of physics (known but difficult for me to measure and calculate), the speed of the jet, and the altitude dropped from.

For reference,  I did a rough measure finally and decided the descent angle we see is around 20 degrees, not 25-30. A good range is 18-22 degrees from vertical. All directional clues (shrapnel marks, fireball spread) remain consistent with this. If that could be an OFAB-250 detonation (it can't) then this could be it coming in at such an angle.


In follow-up discussion, ACLOS member Resup provided this handy chart (can't verify but looks logical) of a model object (cannonball) of the same weight as an OFAB-250 dropped from a jet traveling the speed of sound (measures are in meters - y axis is altitde from 0, drop point, x axis is horizontal travel during the drop). At a standard altitude of 3,000 meters or more, the angle at ground level (-3000) would be effectively vertical, like I said.

But if it were lower, say 1000-1500 meters, the angle could easily be in the range seen. This would raise some logic problems (aren't they worried about Anti-Aircraft fire?). But it could be done, and so even with tons of math to get an exact speed/altitude required, people could just say "fine, they did that then."

So this can only be a supporting point to the multi-point case that this is a fake, staged scene. "And furthermore, there's such an incoming angle that the notion of a gravity bomb is questionable."

Wednesday, November 26, 2014

How "The Russians"* Covered up the Truth ... Partly, Gradually ... About MH17

How "The Russians"* Covered up the Truth ... Partly, Gradually ... About MH17
November 26-28, 2014
last edits Dec. 7

* "The Russians" here meaning whoever it was that ran and operated the Buk launcher (if it's all one and the same) that we're calling 3x2, blamed for the shoot-down of MH17. Note: it's quite likely they weren't Russian at all... 

Shortly after the July 17 crash of the Boeing 777 in Donetsk Oblast, Ukraine, Eliot Higgins (aka Brown Moses) and the Bellingcat team accurately tracked a certain mystery Buk (SA-11) launching unit across Eastern Ukraine, up to a last point very near a likely launch site for the missile that brought the jet down (while the full implications aren't clear, I concur with their basic findings, as explained here on an ACLOS page where a lot of my other points below are explained out).

More recently, Bellingcat landed another coup in the saga, in early November issuing a new report claiming to link that very launcher, or at least the truck hauling it, to a truck-bound launcher also seen inside Russia a few weeks before the incident, and again just after. If true, it would seem to be a smoking gun. I think it's at least partly true, and the problem is only with the "seem to be" part. And I have no solid alternative at the moment, just verifying part of, and pointing out some puzzling implications of, their findings.

The report and whole site was not coming up when I tried (might be a problem on my end), so I don't even know what's behind their pay-wall. In the interim I checked around. Here's a critical blog article I like that mentions another article praising the report. But what was useful was the Daily Mail's Australian promo article with the cover and a few images from the report as well as a summary. 'There is strong evidence indicating that the Russian military provided separatists in eastern Ukraine with the Buk missile launcher filmed and photographed in eastern Ukraine on July 17,' the on-line report states..."

In this, they identify Buk Telar launcher "3x2," as the report puts it, where the x is a middle digit seemingly painted out for some reason. 3x2 therefore seems a fair name for the thing, and I'll follow suit. From the Mail's graphics, I can see how they link the trucks hauling the launchers by license plate numbers. That looks sound, and minor details support that this is the same truck, apparently in Russia and then in Ukraine. (Or is this not the same famous truck here? It's a side-point.)

The actual launcher link sounds less clear in the Daily Mail report, but in Russia, that truck was hauling a launcher marked on the side with a small, unreadable number and the large number 3x2 (top frame in the below comparison). Seeming to have a number painted over, many will note, smells of a mini-coverup - and it's with a machine that then went (back?) to Ukraine for some secret work Russia denies, before going (back to?) about the Russian border, via everywhere, on a truck advertising a phone number of a guy who swears it was pro-Russian terrorists who stole his truck... (see below for the fuller picture)

However absurd the whole story, there's this compelling, supposed, cross-border match-up. Tying things together more yet, the top frame below shows the relevant part of the Paris Match photo (windscreen dots and all, after being skewed to match as much as possible, and darkened a bit) at the bottom. Again the top image is from Bellingcat via the Mail, with enhanced contrast to make the compositing clearer. The middle is the composite - bottom laid over top with transparency to let us compare). Another layer of just the number box, carefully lined up, had its white spots outlined in black, lining up with white in the other image. All areas of interest highlighted in red.

In fact, comparing the two like this, we can also see other points of continuity. Earlier, I guessed maybe "4 240" for the smaller number (or maybe "return to Putin"). The new image doesn't seem to help much there. I'm guessing it matches though, whatever it says. The light patch right before the small numbers, and on the lip just below that (the red marks on the right) seem to correspond. Also on that lip, just to the right, is a bend visible in the June image. I cropped the Paris Match sample too close to be clear here, but that too comes through on the machine seen in Ukraine. Best explanation for that: it's all the same weapon.

I noticed earlier the sliver of white paint (or so it seemed) in the blank ID number area in the Paris Match photo, wondering if it was a telltale partly-painted-out number meant to be noticed later and used to blame Russia. It may be exactly that; now we can see it's consistent with the edge of the "2" here, or a couple of other numbers painted at that level. Note also in the bottom image the tiny white dot left of the white sliver, on the cable shadow, that seemed like an artifact. In Russia (if so) we can see it there before - apparently the last part of the first number they also managed to never paint out fully.

That middle digit could well be a one. I thank ACLOS member Resup for bringing this to my attention. As Resup notes, there's the issue with Buk 312 of Russia allegedly seen going back to Russia, put out by the SBU but then pulled, as it was Ukraine's Buk 312 in the photo (the unit's number: bottom image at right). That was also seen in the field not long before this (top image at right), and may or may not be accounted for on the days in question.

Now ... if "the Russians" were smart, what they'd do is paint out the original 312 and then paint over it with Ukraine's style of marking 312, or really any number of a known unit seen in the field (and hope it can't be proven to be elsewhere...) It seems they did not do this. Here, 312 as seen in March (skewed as it was to fit the composite below. That's underlaid by the Bellingcat find, and we can see the lack of the little marking, and the much bigger, bolder, easier-to-spot numbers "the Russians"* had such a hard time hiding (below alone for comparison, not enhanced). Below all, the same area from the SBU pulled photo.

What all this implies, read as the Bellingcat agency reads it, and as the global masses and decision-makers they're informing have read it, is simply that this was all the same unit and clearly a Russian-controlled one. Since it was the same one as seen all around the MH17 crime scene, Putin or top officials almost must have approved something that special. This in turn justifies more sanctions and so forth.

All I can vouch for is the number match and vehicle match, or a complex paint job and bend-mimicking operation. The paint part seems most interesting, with consistent bits remaining of a number ... that might have been falsely painted on, by whoever, to begin with. The June image location I'll credit as likely sound. It seems a troubling challenge for anyone suspecting a Ukrainian and not Russian hand. Proceeding from there...

What Bellingcat probably mentioned but I'm emphasizing is that "the Russians" also, in doing this, made a display of shadiness in the gradual, partial, and traceable erasure of the ID number. Read straight, the alleged coverup is plain silly: they wanted to hide this thing's identity, maybe because they were about to do something secret with it. So first they painted out the number in the middle. Except they left one little corner of white visible. Maybe they just got tired. It's identifiable (in both images). Then before it appeared in Ukraine, it was rendered totally unidentifiable: they boldly blacked out the 3, and perhaps at the same time even, the 2 - except for a larger identifiable sliver. Just got tired, maybe. It's next to the other dot. Haha, no way to connect these now!

- "Now has no number on it AT ALL. No one can say what it is."
- "Brilliant, boss. they will think must have been a Kiev fighter jet! And we will make fake satellite photos to prove. The world will stand behind our invasion!"

That's not just sloppy and stupid like people can be. It's more like something someone else would have them do, in a script they wrote for other parties playing "the Rusians." Its purpose seems to expose, illustrate, or imply a crime, not to cover one up. In fact, it's a bit too obvious to even be a good false flag operation. But maybe that we can chalk up to run-of-the-mill Human stupidity (or worse yet, Neo-Nazi psycho stupidity)

Addendum on Consistency with the Operation, as Known Otherwise: 
Whatever one thinks of this graphic comparison and interpretation, the strange and suspect thinking it implies is consistent with what else we know about how this "secret" operation was carried out. If true, it would fit this broader pattern (real or reported clues left by whoever, all open to interpretation, and here couched in the terms of allegations by Kiev and supporters):
  • Recalling that this whole weapon itself would have no normal business in the area and would be denied later, it should have been kept secret. Instead, it was driven around in broad daylight on the same day as the crime, just partly covered with a tarp but revealing all clues needed to identify it, its hidden ID number, and its full rack of missiles.
  • The truck it was so displayed on was stolen in Donetsk, and kept with the huge sign on its side with the apparent owner's phone number on it. When the media called that number, little surprise, the owner told them pro-Russian "fighters from Slaviansk" who took over his whole trucking company on July 8 (see here) Put lightly, this is a stupid way to secure a rig one intends to use for a secret operation like this was supposed to be.
  • They loaded the truck in Donetsk, likely at the commandeered site in the north of Donetsk, near the Ukrainian base with Buk launchers, in a coincidence. This truck then got seen leaving Donetsk on the 17th, parked pointing east at the east outskirts, then seen driving in convoy (a couple civilian cars with the operational crew moved with the truck) past Zuhres and then through Torez to the east. They were seen arriving in Snizhne around noon, then the Buk unit seen off the truck and driving in stand-alone, and it was then seen again driving south out of Snizneh, towards the apparent launch location.
  • The people running the convoy made sure AP journalists saw them in Snizhne just before the shoot-down from a bit south of there. The convoy stopped, and a man in unusual uniform "approached the journalists. The man wanted to make sure they had not recorded any images of the missile launcher. Satisfied that they hadn’t" filmed that secret missile launcher there, but had noticed it, and their intention to remain sooper seekrit "the convoy moved on." All this was made quite clear to the media and apparently published even before the news that MH17 was shot down. (AP Via Washington Post
  • After the disastrous attempt to secretly provoke a Russian invasion, with utmost discretion the operators put the smoking gun, its rack of one-less missiles left uncovered, back on the same truck and drove it and the phone number back to Russia - by a strange detour on a long route towards the other easily-recognizable smoking gun rebel capitol, Lugansk ... when government ATO forces had just battled their way to the edge of Lugansk ... and got seen there passing at dawn on the main highway south, apparently having come from the center of town, and then presumably drove to Krasnodon (rebel-held) and to Russia....

The fail delivery here is almost flawless, with no mistake left unmade and hardly any reasonable gaps to call for deduction. Letting multiple camera views on both sides of the porous border capture and track the gradual move to this stealth mode seems pretty consistent to me.

Note, Dec. 7: Obviously, the big wrinkle with this apparent match is that it puts this shady device on Russian territory, worked into a whole convoy there, and thus presumably Russian in origin as alleged. That remains the simple (usually most logical) reading, but it has maybes and second thoughts worth raising at each branch of the possibilities tree of "if (or whether) Buk 3x2 was in Russia), which I explored here at the ACLOS Buk tracking talk page. Some of the possibilities: faked imagery (perhaps removing the evidence for Buk 3x2 being in Ukraine) - a rogue officer in Russia helping with the false-flag Trojan horse operation - similar to or exactly as reported, with some serious questions about the logic and method, and the hostile world reaction to the "crime" also called an accident still worth questioning. I really don't know how to call this case. As I said at the wiki, I feel sort of "weightless" compared to usual. This may be the extra-nuanced false-flag I wondered if I'd ever see - one that's got tricks we're not used to involved, and comes out harder - or impossible - to solve clearly - the perfect crime.