If the Last Photograph Shows a Rooster, What Must Richmond Reconsider About Bill Cosgrove?
The Australian War Memorial identifies the Beaufighter in its photograph as A19-74, with a boxing rooster on its nose. The same catalogue connects that aircraft to the crash that killed Flight Sergeant Bill Cosgrove and Flight Sergeant Bernard Le Griffon. For Richmond supporters, that image raises a troubling question: if the last aircraft pictured carries a rooster, what does that mean for the tiger and “Eat ’Em Alive” remembered as Cosgrove’s? The easy responses—dismiss the image or dismiss the tradition—both risk asking a photograph to decide more than it can. The stakes are not just a caption; they are whether the club’s wartime memory can withstand close inspection. In the full feature, we examine how the Memorial’s catalogue identifies the photographed nose art—and what that image can, and cannot, establish.
The puzzle turns on a distinction supporters may rarely need to make: the aircraft a pilot was regularly associated with, the aircraft he flew on a particular sortie, and the aircraft recorded in a photograph are not necessarily the same thing. Yet a familiar phrase such as “his plane” can quietly merge those identities. Once that happens, a catalogue entry and a remembered emblem seem to contradict each other before their records have been compared. The serial number offers a way to ask a more disciplined question, but it does not by itself settle what happened. Which records connect the man, the marking and the final flight—and how independently can each link be checked? In our Members investigation, we test how aircraft serials, regular assignments and a specific sortie complicate the phrase “his plane.”
What can an aircraft number settle—and what can’t it?
Richmond’s attachment to Cosgrove gives this investigation its emotional force, but it cannot be the only measure of its historical care. Le Griffon was also aboard the aircraft and also died; his name and service deserve more than a passing place in a story organised around football. The service and memorial records can help recover both men as people, while also setting limits on what a club connection can explain. A supporter’s loyalty may illuminate why an emblem mattered without telling us what the pilot thought in his last moments. The distinction is important: remembrance can be personal and powerful without becoming permission to invent an ending. In the full feature, we look at service and memorial records that restore both crewmen beyond Richmond’s familiar football connection.
A catalogue can establish what appears in its frame and identify the aircraft it records. That is valuable evidence, not a complete account of every machine associated with a pilot. A nose-art photograph cannot, on its own, establish which other aircraft a person flew, when a marking was painted, or what an image outside the frame looked like. Those questions call for different evidence, and the available accounts do not all have the same proximity to the events. The challenge is to keep those differences visible instead of forcing the picture to carry the whole story. What would a caption need to say so readers can see both its authority and its limits? In the full feature, we dissect the gap between a photograph’s visible detail and claims about aircraft elsewhere or on other dates.
How much should one photograph be asked to prove?
Maintenance and assignment records may bring the aircraft question closer to an answer, but they raise a second test: what can evidence about availability establish about the crash itself? A note that one machine was under repair might help explain why a crew used another; it would not automatically explain why that aircraft was lost. Conflating those questions could turn an ordinary operational detail into an unsupported account of cause. Nor does the word “borrowed” necessarily describe a private choice: aircraft availability belonged to a military unit’s practical decisions. The distinction matters because each claim needs its own documentary support, not a persuasive-sounding chain of assumptions. In our Members investigation, we trace the maintenance account, aircraft availability and the separate question of what caused the fatal loss.
The calendar can also make a compelling story seem more settled than its evidence. Wartime correspondence may show that Cosgrove remained connected to Richmond; a later premiership may explain why supporters hold the story close. But dates matter: a letter cannot prove he knew a later result, and sporting success cannot establish what he experienced. The same restraint applies to recollections passed down after the event. They can preserve real personal meaning, while leaving open when details were recorded and how they relate to contemporary documents. Richmond need not choose between affection and accuracy. It must decide how to connect them without turning coincidence into proof. In the full feature, we examine how wartime letters, dates and later football memory can be connected without claiming more than they show.
What does responsible remembrance still need to establish?
Even the circumstances of the loss call for careful wording. Accounts describe the crash near Goodenough Island in differing ways, including descriptions of the wreckage’s position. Those variations may be reconcilable, but a secondary summary cannot stand in for the original accident inquiry. The surviving material identifies a date, an aircraft and two men; it does not license an invented cockpit scene or a confident cause. That leaves a consequential editorial choice for Richmond: repeat the most vivid version, or distinguish established details from questions still requiring primary records. What standard should a tribute meet before its wording becomes part of the club’s remembered history? In our Members investigation, we test conflicting crash descriptions against the unanswered work of original operational and accident records.
Not a member yet? Join RTSSG for the complete investigation and more Richmond research.
Richmond news by Richmond people, for Richmond people.
Comments