Jack Buckingham
cricketer (1903-1987)

John Buckingham (21 January 1903 – 25 January 1987) was an English cricketer who played first-class cricket for Warwickshire between 1933 and 1939. He was born at Grimethorpe, Yorkshire and died at Moseley, Birmingham.
An itinerant semi-professional footballer, Buckingham played for Wellington Town in the early 1930s and turned out in second eleven matches for Warwickshire, as a lower-order right-handed batsman and wicketkeeper, from 1931. He made his first-class debut in 1933 in a match against the West Indians, scoring two runs and making two stumpings. In 1934, Warwickshire's regular wicketkeeper, Jack Smart, was injured in mid-June; Buckingham kept wicket for the rest of the season "and revealed himself as more than a useful bat", according to the 1935 edition of Wisden Cricketers' Almanack. In addition to 24 catches and 17 stumpings, Buckingham made 454 runs at an average of 23.89 in 1934.
Despite this success, Buckingham did not retain his place when Smart, at the age of 44, was fit to resume in 1935, and in that season and the next he played in only a few matches. Smart retired, however, at the end of the 1936 season and Buckingham was then from the start of the 1937 season Warwickshire's regular wicketkeeper up to the Second World War. His wicketkeeping style, according to an obituary in Wisden, was "brilliant rather than consistent" and he was "apt to snatch" at the ball. But his pugnacious batting was an asset as well: "Never a sound or orthodox player, he had plenty of strokes and hit the ball astonishingly hard for so small a man," Wisden's obituary noted.
“Jack Buckingham” enters the record as cricketer (1903-1987). Crown Archives preserves that source wording while asking what Jack, Buckingham and cricketer can confirm, complicate or overturn.
Why this record matters
“Jack Buckingham” is worth following because a concise public description often conceals a longer documentary argument. Here, Jack, Buckingham and cricketer provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Aug 22, 2026. The linked authority identifier is Q20810561. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1903, 1987, 1933 and 1939.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. 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
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Jack Buckingham”, its source revision and the description used here.
- Expand the search: follow Jack Buckingham primary sources, Jack Buckingham archive and Jack 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 “Jack Buckingham”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Jack Buckingham” 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.