CACrown ArchivesThe cinema collection
EN/FR
Search
Menu
Research dossier · General Reference

Mace-Trefethen M-101 Macerschmitt

type of aircraft

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 revisionNov 9, 2025
Entity authorityQ6723020 ↗
Source-derived summary

The Mace-Trefethen M-101 Macerschmitt, also called the Could-Bee, is a single place homebuilt aircraft design built in the late 1950s.

Design

The M-101 is a single-place, strut-braced, tapered mid-wing, conventional landing gear equipped aircraft. Entrance is through a sliding canopy. Brake components were adapted from a Cessna 310 and a Piper Cub.

Operational history

The M-101 was test flown on 15, July 1959 at Sacramento Municipal Airport.

Editorial summary

Begin with the source’s own compact description: “Mace-Trefethen M-101 Macerschmitt” is type of aircraft. The dossier treats that line as a proposition to test through Mace-Trefethen, M-101 and Macerschmitt, not as a finished interpretation.

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—1959—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, Mace-Trefethen, M-101 and Macerschmitt is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “type of aircraft” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

Evidence profile

Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Nov 9, 2025. The linked authority identifier is Q6723020. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1959.

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 “Mace-Trefethen M-101 Macerschmitt”, its source revision and the description used here.
  2. Expand the search: follow Mace-Trefethen M-101 Macerschmitt primary sources, Mace-Trefethen M-101 Macerschmitt archive and Mace-Trefethen 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 “Mace-Trefethen M-101 Macerschmitt”?
  2. What terminology or title could unlock a more precise catalogue search?
  3. Which cited source is closest to the event, object or claim?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Mace-Trefethen M-101 Macerschmitt” 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.