top of page


When Systems Collide: The HMAS Melbourne–Voyager Disaster
On the night of February 10th, 1964 , two Royal Australian Navy vessels — the aircraft carrier HMAS Melbourne and the destroyer HMAS Voyager — were conducting night flying exercises off the coast of Jervis Bay. At around 8:56 p.m. , the Voyager was instructed to take up a “plane guard” position — a routine maneuver to trail the carrier and retrieve aircrew in case of emergency. But what followed was anything but routine. The Voyager unexpectedly turned toward the Melbourne
Edward Brathwaite
Dec 30, 20252 min read


Nuclear Case Study: The Three Mile Island Wake-Up Call
Summary On March 28, 1979, the Unit 2 reactor at Three Mile Island in Pennsylvania suffered what would become the most serious accident in U.S. commercial nuclear history — a partial core meltdown. It began with something that looked routine: a secondary cooling pump tripped. But a small mechanical fault — a pressure relief valve that stuck open — allowed coolant to escape. In the control room, operators were faced with confusing, incomplete data. They believed the system had
Edward Brathwaite
Dec 2, 20252 min read


Turning Setbacks into Solutions: How We Use ICAM at Savant Studio
Stuff goes wrong—missed hand-offs, fuzzy briefs, tech hiccups. We don’t hide it; we learn from it. ICAM gives us a clean way to do that without blame. We collect the facts (timeline, artefacts, short interviews) and map them to four buckets: Absent/Failed Defences (A/FD): What barrier was missing or didn’t work? Individual/Team Actions (I/TA): What people did, saw, or assumed in the moment. Task/Environmental (T/EC): Conditions, tools, constraints that shaped the work. Org
Edward Brathwaite
Nov 11, 20251 min read
bottom of page