CACrown ArchivesHistory · sources · collections
Menu
Research dossier · General Reference

Beam engine

Early configuration of the steam engine

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionApr 29, 2026
Entity authoritySource title only
Source-derived summary

A beam engine is a type of steam engine where a pivoted overhead beam is used to apply the force from a vertical piston to a vertical connecting rod. This configuration, with the engine directly driving a pump, was first used by Thomas Newcomen around 1705 to remove water from mines in Cornwall. The efficiency of the engines was improved by engineers including James Watt, who added a separate condenser; Jonathan Hornblower and Arthur Woolf, who compounded the cylinders; and William McNaught, who devised a method of compounding an existing engine. Beam engines were first used to pump water out of mines or into canals but could be used to pump water to supplement the flow for a waterwheel powering a mill.

Editorial summary

The public source identifies “Beam engine” as early configuration of the steam engine. This brief keeps that definition visible, then builds a research path around Beam, engine and Early.

Editorial reviewA concise reference frame for defining the subject, testing terminology and identifying the institution closest to the evidence. The current lead gives the account dated anchors—1705—that can be checked directly. The selected authority fields contribute no independent date. Its value is orientation rather than verdict, with Beam, engine and Early providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “Beam engine”, the useful work is to connect “early configuration of the steam engine” to the records capable of establishing context and consequence.

Evidence profile

Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Apr 29, 2026. The first chronological checks are 1705.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. 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.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “Beam engine”, its source revision and the description used here.
  2. Expand the search: follow Beam engine primary sources, Beam engine archive and Beam research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Beam engine”?
  2. Which institution is responsible for the underlying evidence?
  3. What terminology or title could unlock a more precise catalogue search?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Beam engine” 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.