There is a detail in this story that almost nobody knows and that changes how the whole disclosure history reads. The engagement of 12 July 2007 was described in a published book, in detail, with the radio traffic, more than six months before anyone outside the military saw the footage.
How the book came to exist
David Finkel, a reporter for a major American newspaper, spent much of 2007 embedded with the battalion whose infantry company was working the district that morning. He lived with the unit through most of its deployment.
The result, published in 2009, was an account of one battalion's year in eastern Baghdad. It is a book about soldiers rather than about policy, and it covers the deployment as those soldiers experienced it.
What it contains about this engagement
A detailed account of the airstrike, written from the perspective of the unit on the ground, drawing on the cockpit radio exchanges that appear on the recording.
That is the significant part. A journalist was able to work from the radio traffic of a classified gun camera recording, and publish it, in 2009.
| Date | What existed | Who could see it |
|---|---|---|
| July 2007 | The recording and its radio traffic | Inside the military |
| 2008–2009 | The same material | Still not Reuters, despite formal requests |
| 2009 | A published book describing it | Anyone who bought it |
| April 2010 | The footage itself | Everyone |
Why that detail matters so much
Two facts that do not sit comfortably together
- Throughout 2008 and 2009, Reuters was being refused access to this recording, having asked for it since the day after its two employees were killed.
- During the same period, an embedded reporter had enough access to the same material to describe the engagement and quote the radio in a commercially published book.
Nothing here suggests the reporter did anything improper. Embedded journalists are given access as a matter of routine, and describing an engagement your unit was involved in is ordinary reporting.
What it shows is that the material was not locked away for reasons of pure operational secrecy. It was available to someone the institution had chosen to give access to, and not available to the employer of two dead men who kept asking formally.
The book as a check on the transcript
There is a second reason this matters, and it is technical. When a leaked recording appears, one standard attack is to question whether the transcript is accurate or the audio manipulated.
Here that attack was closed off in advance. An account drawing on the same radio exchanges had been published by an established journalist at a major newspaper, before the leak, with no connection to WikiLeaks. The two align. Almost no leaked recording in history has had an independent prior check of that kind. By the standards of verification, this is close to ideal.
A check almost no leaked recording ever gets
An account drawing on the same radio exchanges was published before the leak, by an established journalist with no connection to WikiLeaks. The two align. That closed off the usual attack on a leaked recording's authenticity before it could be made.
What it adds beyond the footage
Context the camera cannot supply. The state of the battalion by July, the casualties they had taken, the exhaustion, the way a district turns into a set of threats in the minds of people being shot at in it every week.
None of that is exculpatory and the book does not present it as such. It is the ground-level texture that explains why the voices on the radio sound the way they do, without asking the reader to approve of it.
What embedding gives and what it costs
This book is also a good place to think about embedded reporting generally, because it shows both sides at once.
What embedding gives is access nobody else has: months with the same soldiers, the small details, the deterioration, the way a unit talks when it has stopped performing for visitors. Very little serious writing about how a war feels to the people fighting it comes from anywhere else.
What it costs is perspective. A reporter living with one company sees that company's war. The people on the other side of the wall are, structurally, the people shooting at your hosts. It takes real discipline to write about a district from inside an armoured vehicle and remember that several hundred thousand people live there.
The honest reading is that both things are present in this case. The book is a strong account of a battalion and a thin account of the neighbourhood, and the thinness is not a personal failing so much as the shape of the arrangement.
Why nobody connected the book to the airstrike at the time
Because in 2009 there was nothing to connect it to. It read as one engagement among many in a book full of them, and there was no footage in the public domain to match it against.
Only after April 2010 did readers who had the book realise they had already read this scene. By then the story had a title and a political shape, and a quiet fact about disclosure went largely unremarked. It deserves better: the plainest available evidence that the refusal to release this recording was a choice about who, not a necessity about what. The main account picks the story up from there.
For the engagement the book describes, see the day itself; for the recording it drew on, see the main account of the video.
Questions people ask about this
Did the book reveal the airstrike before WikiLeaks?
Does that mean the leak was unnecessary?
Why does it matter for verification?
Where this comes from
- The Good Soldiers — David Finkel, Sarah Crichton Books (2009)
- July 12, 2007, Baghdad airstrike — Wikipedia
- Reuters news archive — Thomson Reuters
Spotted something wrong? Tell us and we will fix it.