CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

HMS Ariadne (1805)

1803 cutter

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 revisionDec 16, 2025
Entity authorityQ65083652
Source-derived summary

HMS Ariadne was launched at Cowes in 1803 as the civilian vessel Ariadne. The Royal Navy purchased her in July 1805 as an advice boat and commissioned her under Lieutenant John Wells. It renamed her HMS Dove later that year, and then in 1806 renamed her HMS Flight.

In September 1806 Flight disappeared in the English Channel, and was presumed to have foundered with the loss of all hands.

Citations

References

Hepper, David J. (1994). British Warship Losses in the Age of Sail, 1650–1859. Rotherfield: Jean Boudriot. ISBN 0-948864-30-3.

Winfield, Rif (2008). British Warships in the Age of Sail 1793–1817: Design, Construction, Careers and Fates.

Editorial summary

The public source identifies “HMS Ariadne (1805)” as 1803 cutter. This brief keeps that definition visible, then builds a research path around Ariadne and cutter.

Editorial reviewA practical starting point whose main value is the path it opens into stronger specialist and primary sources. The current lead gives the account dated anchors—1803, 1805, 1806, 1994—that can be checked directly. The selected authority fields contribute no independent date. Its value is orientation rather than verdict, with Ariadne and cutter providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “HMS Ariadne (1805)”, the useful work is to connect “1803 cutter” 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 Dec 16, 2025. The linked authority identifier is Q65083652. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1803, 1805, 1806 and 1994.

Critical limits

A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 “HMS Ariadne (1805)”, its source revision and the description used here.
  2. Expand the search: follow HMS Ariadne (1805) primary sources, HMS Ariadne (1805) archive and Ariadne 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 “HMS Ariadne (1805)”?
  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 HMS Ariadne (1805)” 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.