¹ The shape‑shifting story of Hind Rajab: how a fog‑of‑war tragedy was recast as a deliberate execution 🧵
The death of six‑year‑old Hind Rajab has become one of the most emblematic stories of this war, told and retold as an archetypal tale of ultimate atrocity — Israeli tanks supposedly executing, at point‑blank range, the children trapped in a car.
This thread examines how that narrative was manufactured — through shifting testimonies, selective omissions, and partisan “forensic” analysis — and shows why this framing, when examined closely, completely falls apart.
Fair warning: it’s a rather long read — but the devil, as always, is in the details.⏬
² First, a few key facts about this incident:
• On the morning of 29 January 2024, residents of Tel al‑Hawa neighborhood were urged to evacuate south. Nevertheless, several testimonies indicate that the car carrying Hind Rajab was driving north.
• Starting from early morning, heavy clashes broke out between Hamas and IDF forces in the area.
• Photos and videos taken after the car was discovered show that its windows were sealed with plastic sheeting.
• According to Hind’s mother, it was raining that day, so visibility was poor.
• Early Al Jazeera reporting explicitly stated that the car was first shot at while it was on the move.
In other words, a car with plastic-covered windows was moving through a combat zone toward Israeli positions, in poor visibility conditions, heading north — the opposite direction of the evacuation order.
Taken together, these details show why the car could have been understandably perceived by the IDF forces as an obvious hostile threat. ⏬
³ Unsurprisingly, the first major change Al Jazeera made in its next retelling — the reconstruction published on 22 February 2024 — was to claim that the car wasn't moving, but already stopped near a gas station, when tanks opened fire.
That single adjustment — from a moving car in the middle of a combat zone to a parked civilian vehicle — removed a key part of the context that explained why the car could plausibly be perceived as a hostile threat and instead made it appear as deliberate execution of an unmistakably civilian car.⏬
⁴ This was far from the only “adjustment” Al Jazeera made.
Their own screenshots of WhatsApp messages between Hind’s uncle and the Red Crescent show that at 2:28 p.m. the uncle wrote (in Arabic):
“They were at the Faris station. They were in a black Picanto. They got out and they are in a house right next to it.”
And yet, that crucial line was never mentioned in the English narration.
However, if some or all members of the family had left the car, the entire “children trapped inside” premise collapses — and with it, the foundation of the alleged execution story. ⏬
⁵ Another critical part of the same WhatsApp exchange omitted in English narration is the last two messages in which Hind’s uncle notifies the Red Crescent that Hind's cousin Layan was killed. These messages were sent immediately after the Red Crescent asked the uncle to keep the line open so they could reach the family — something they had not managed to do until that point.
Nevertheless, Al Jazeera truncated its English narration at the message just before that, claiming that at that moment the Red Crescent - not Hind's uncle - reached Layan and heard her being shot on the call, contrary to what the Arabic messages show.
The recording of this alleged call played a central role in dramatizing the story, shaping much of its emotional impact and being replayed across media platforms. If that call never happened as described, the audio recording circulated worldwide becomes unverified at best — and potentially fabricated. And since much of the “forensic analysis” used to construct the canonical narrative relied on that recording, its credibility — and the conclusions drawn from it — are fatally undermined.
Perhaps that was the reason why these key messages was never mentioned by Al Jazeera English — and why the entire exchange was omitted from all subsequent reconstructions, both by Al Jazeera and others.⏬
⁶ The alleged call with Layan became the linchpin of Forensic Architecture’s investigation — the foundation of the “deliberate execution” claim. Yet even assuming the recording is genuine, the full audio tells a very different story.
First, FA claimed that only one weapon type was audible, with the firing rate supposedly matching Israeli rifles or a tank-mounted gun. However, their analysis was limited only to the second half of the recording, ignoring two shorter bursts a few seconds earlier.
One of these bursts was long enough to allow an estimate of its firing rate — roughly 10 shots per second (≈ 600 rpm) — matching that of the AK‑47, Hamas’s standard rifle.
This indicates that at least two different weapons were fired in sequence, reflecting an ongoing firefight between Israeli forces and Hamas — not a one‑sided, deliberate volley at a civilian car.
Furthermore, FA identified 64 gunshots in the audio track but only about 30 bullet holes along the line they used for trajectory modelling — which they assumed corresponded to the shots heard in the recording.
In other words, at least half of the rounds must have struck elsewhere, at a target near or behind the car, further reinforcing the crossfire scenario.
This conclusion is further supported by reports from the same day describing intense clashes in Tel al‑Hawa, and by another recording in which a dispatcher asks Hind, “Is there gunfire around you?”
Together, these details suggest that the car was caught between opposing lines of fire, not deliberately targeted — directly contradicting the accusatory narrative Forensic Architecture helped promote.⏬
⁷ FA also claimed — based on their 3D reconstruction — that Israeli tank crews had a “clear line of sight” to the children inside the car, implying a deliberate execution at close range.
Yet multiple reports note that the girls were seated in the back, and in the recorded call, Layan can be heard saying, “We are hiding in the car", suggesting they were crouched low behind the front seats.
In addition, FA’s reconstruction indicates that the fire came from the rear-right direction — given that geometry and the plastic-covered windows, the gunner could not have seen the children, especially under the rainy, cloudy conditions described by witnesses.
In short, FA’s “clear line of sight” claim collapses under the combined weight of physical and visual constraints — the firing angle, plastic-covered windows, poor weather, and interior seating position all make it impossible that the gunner could have seen the children inside the car.⏬
⁸ As a sidenote, it’s worth mentioning that FA’s “investigation” was commissioned by Al Jazeera, and that FA were among the last “experts” still blaming the Al-Ahli hospital explosion on Israel — long after U.S. and French intelligence, as well as AP — and even HRW — concluded it was most likely a misfired Islamic Jihad rocket.
This pattern of bias perhaps explains their consistent disregard for evidence contradicting the narratives they set out to promote.⏬
⁹ Another aspect of the story that kept shifting was the car’s supposed destination — variously described as al-Ahli Hospital, the family’s home in northern Gaza City, or, in a later Al Jazeera interview with Hind’s mother, as “a town that’s further out”.
The one thing common to all those different destinations was the same initial direction: north, not south, opposite to IDF evacuation orders.
Forensic Architecture were the only ones to acknowledge this contradiction, but excused it by claiming the southern route was blocked. Yet their own map shows a clear alternative path via Beirut Street (green arrow) leading straight to al-Rashid Road — the designated evacuation corridor.
Even if one junction was obstructed, the route south was still open. The family went the other way — north, contrary to the evacuation order — not because of any blockage, but by choice.⏬
¹⁰ Equally, the timeline kept shifting.
Early reports placed the start of the incident — the family’s departure and the firing on the car by Israeli forces — in the early afternoon, placing the first contact with the Red Crescent soon after the incident began.
Forensic Architecture’s June report shifted the beginning of the event to the “early hours” of 29 January, while Sky News Oct 2024 article for a first time quoted Hind’s mother giving a precise time for the attack — 8:10 a.m., said to be ten minutes after departure.
This revision of the timeline creates a six-hour gap between the alleged shooting (8:10 a.m.) and the first documented PRCS contact (~2:30 p.m.).
What happened in those missing hours, and why did neither FA nor Sky News address it?
And why did the mother share this key piece of information only several months later — after months of reports placing the event in the early afternoon — with a “morning” version first surfacing in June, and the precise hour only emerging in October?
Viewed alongside her evolving statements about the family’s destination — first supposedly walking east to al-Ahli Hospital, then waiting for Bashar to return from another town — the constant revision of such core facts undermines the credibility of her account in general.⏬
¹¹ In summary, the inconsistencies outlined throughout this thread demonstrate how a battlefield encounter clouded by uncertainty in the midst of crossfire was gradually reframed into a narrative of deliberate atrocity.
The evidence instead suggests a chaotic encounter in which poor visibility, miscommunication, and the pressures of combat likely resulted in tragic misidentification and the deaths of civilians caught in the crossfire.
Recognizing these complexities does not diminish the human loss; rather, it restores factual integrity to a dramatic event that has been repeatedly weaponized for political ends.
¹ The IPC “famine” designation for Gaza City relied heavily on the claimed July surge in “malnutrition-related” deaths.
However a careful analysis of the MoH’s own numbers shows that this "surge" was a complete fabrication. 🧵
² About a week ago, I showed that the Gaza MoH’s own data contains no trace of a “rapid increase” or “acceleration” — let alone “exponential growth” — in malnutrition-related deaths.⏬
³ Even if we accept at face value the absurd claim that actual deaths were at least 30× higher than reported, the claimed “rapid increase” should still have produced, at the very least, a clear upward trend in the data.
Instead, the figures remain flat in the three weeks before the FRC report’s cut-off date — completely undermining its claim of “acceleration.”⏬
¹ Unpacking IPC’s Response to Criticism — Part 1 🧵
As I wrote yesterday, the IPC admitted that the malnutrition rates charts they used as key "evidence" for allegedly rapidly deteriorating situation and breach of the famine threshold weren’t based on the data shared in the annex of their report.
Now they claim it was all based on a completely different dataset, supposedly received on Aug 12 — but whose very existence they never bothered to disclose until now.⏬
² I must say: if this were a submission to a serious scientific journal, an admission like this -"oops, we forgot to include the actual dataset our analysis is based on" - especially if made only after people started pointing the mismatch, would trigger an immediate retraction.
But this is IPC we’re talking about, so the regular scientific standards clearly do not apply.⏬
³ In any case, yesterday I highlighted just one gem: a sub-sample of only 12 children with over 90% malnutrition, which FRC presented with a straight face as part of the evidence base for a July “uptrend” in malnutrition.
Importantly, the full July dataset from this particular provider - "Action Against Hunger" - already appeared in earlier Nutrition Cluster outputs and in the IPC annex itself, but had been excluded from final Gaza Governorate analysis due to data quality issues (one of the QA metrics called "DPS" above 30).
FRC's decisions to bring it back and count it as valid evidence - particularly the statistically meaningless 12-children sub-sample with absurdly high 91.7% "malnutrition rate" - says a lot about the seriousness of this analysis.⏬
¹ The deeper I dig into IPC’s August famine report, the worse it gets.
Turns out that the July data fudge wasn’t the only fabrication, but they also tried to retroactively rewrite what supposedly happened in May and early June.🧵
² Just look at IPC’s malnutrition chart for Gaza Governorate.
See the part for May and early June?
A neat downward slope, as if rates were falling and things improving.
Wonderful, right?
WAIT, WHAT?!⏬
³ Weren't the UN agencies warning us at the time of steady deterioration, worsening access to food, and malnutrition climbing higher and higher — not improving?!
Here's jut one example - from "Gaza Humanitarian Response Update | 25 May - 7 June 2025" ⏬
¹ Yesterday I exposed two scandalous facts - also noted in Israel’s official response to the IPC "famine" designation:
1⃣ FRC ignored half of July’s malnutrition data
2⃣ Full data showed rates under 15%
In response, IPC apologists tried to rationalize this omission. 🧵
¹ The biggest problem with the Gaza City bogus "famine" designation isn’t that IPC used MUAC or the 15% threshold.
The real scandal is that Gaza City’s malnutrition rate in July never actually crossed 15%.
This is huge - yet it’s barely being talked about.🧵
² IPC claimed Gaza Governorate crossed the famine threshold with ~16% malnutrition, but this figure was based on only half of July’s data (7,519 kids).
However, the full July dataset (15,749 kids), published on Aug 6, showed 12.2% rate - well below the 15% cutoff.⏬
³ So IPC knew the full July data put Gaza City’s malnutrition rate under 15%.
Yet they declared famine based on an earlier partial sample - ignoring the complete results that disproved their claim.
¹ Did IPC really change the rules for determining famine in Gaza, as @FreeBeacon recently claimed?
Yes and no.
No: They didn’t introduce a new malnutrition indicator or cut the famine threshold in half.
Yes: They significantly lowered the evidentiary bar in practice. 🧵
² Let’s start with the “no” - contrary to the article’s claim, neither the use of mid-upper arm circumference (MUAC) to measure Global Acute Malnutrition (GAM) nor the 15% GAM-by-MUAC threshold is unique to Gaza.
Both appear in the 2019 IPC manual and have been used in other IPC analyses, including the latest for South Sudan.
However, the way they’ve been applied in Gaza diverges significantly from what IPC methodology requires.⏬
³ First of all, the IPC manual explicitly states that 15% is an ad hoc heuristic - not a rigorously defined global threshold - and that when classifying on MUAC, analysts must use historical local data on the WHZ/MUAC baselines and the relationship between the two indicators.
In Gaza IPC reports, that fundamental requirement has been consistently ignored.⏬