Callender-Hamilton bridge
fourth Walton Bridge built across the River Thames (1953-2013)
The Callender-Hamilton bridge is a modular portable pre-fabricated truss bridge, with British patent numbers 423926 and 423996, and US Patent No. 2,024,001. It is primarily designed for use as permanent civil bridging as well as for emergency bridge replacement and for construction by military engineering units. Assembling a Callender-Hamilton bridge takes much longer than the more familiar Bailey bridge as it is made up of individual lengths of galvanised steel bolted together with galvanised high-strength steel bolts, all of which require torque settings. It is stronger and simpler in design concept than the Bailey bridge.
History
The Callender-Hamilton bridge system was designed by New Zealand civil engineer A. M. Hamilton, and patented by him in 1935. The system is currently fabricated by Painter Brothers, Hereford, operating within the Balfour Beatty Power Networks Division formerly British Insulated Callender's Cables.
Hamilton's bridge concept was inspired by his work between 1928 and 1932 as principal engineer on the 'Hamilton Road' through Iraqi Kurdistan. He described the building of this road in his book Road Through Kurdistan: Travels in Northern Iraq, 1937. Hamilton became aware of the need for strong, adaptable bridges made from simple components that could easily be transported and erected in remote locations or on difficult terrain.
“Callender-Hamilton bridge” enters the record as fourth Walton Bridge built across the River Thames (1953-2013). Crown Archives preserves that source wording while asking what Callender-Hamilton, bridge and fourth can confirm, complicate or overturn.
Why this record matters
“Callender-Hamilton bridge” is worth following because a concise public description often conceals a longer documentary argument. Here, Callender-Hamilton, bridge and fourth provides the most credible route into that argument.
Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Sep 5, 2026. The linked authority identifier is Q5021896. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1935, 1928, 1932 and 1937.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Callender-Hamilton bridge”, its source revision and the description used here.
- Expand the search: follow Callender-Hamilton bridge primary sources, Callender-Hamilton bridge archive and Callender-Hamilton research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Callender-Hamilton bridge”?
- Which earlier names or jurisdictions may reveal additional records?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “Callender-Hamilton bridge” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.