Ryan YQM-98 R-Tern
type of aircraft
The Ryan YQM-98 R-Tern (also called Compass Cope R) was a developmental aerial reconnaissance drone developed by Ryan Aeronautical. It could take off and land from a runway like a manned aircraft, and operate at high altitudes for up to 24 hours to perform surveillance, communications relay, or atmospheric sampling.
Design and development
"Compass Cope" was a program initiated by the United States Air Force (USAF) in 1971 to develop an upgraded reconnaissance drone that could take off and land from a runway like a manned aircraft, and operate at high altitudes for up to 24 hours to perform surveillance, communications relay, or atmospheric sampling. Two aircraft, the Boeing YQM-94 Compass Cope B, and the Ryan Aeronautical YQM-98A Compass Cope R participated in the program.
Boeing was originally selected as a sole source for the Compass Cope program, with the USAF awarding the company a contract for two YQM-94A (later YGQM-94A) demonstrator vehicles in 1971. However, Ryan then pitched an alternative, and the next year the USAF awarded Ryan a contract for two YQM-98A (later YGQM-98A) demonstrators as well.
Ryan's entry into the competition was the Model 235, an updated variant of the Model 154 / AQM-91 Firefly. The YQM-98A's general configuration was similar to that of the Boeing Compass Cope B, resembling a jet sailplane with a twin-fin tail, retractable tricycle landing gear, and an engine in a pod on its back. The engine was a Garrett YF104-GA-100 turbofan, with 4,050 pound-force (18.0 kN) thrust. The Compass Cope R had a clear resemblance to the Model 154, though its wings were straight instead of swept.
The public source identifies “Ryan YQM-98 R-Tern” as type of aircraft. This brief keeps that definition visible, then builds a research path around Ryan, YQM-98 and R-Tern.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Ryan YQM-98 R-Tern”, the useful work is to connect “type of aircraft” to the records capable of establishing context and consequence.
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 Mar 10, 2026. The linked authority identifier is Q4053424. The first chronological checks are 1971.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 “Ryan YQM-98 R-Tern”, its source revision and the description used here.
- Expand the search: follow Ryan YQM-98 R-Tern primary sources, Ryan YQM-98 R-Tern archive and Ryan 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 “Ryan YQM-98 R-Tern”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Ryan YQM-98 R-Tern” 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.