Sopwith L.R.T.Tr.
British WW1 triplane escort fighter aircraft
The Sopwith Long Range Tractor Triplane (L.R.T.Tr) was a prototype British long-range three-seat triplane escort fighter of the First World War. Its unusual layout had a small gunner's nacelle mounted on the upper wing for an all-round field of fire. Only a single example was built, as other, smaller fighters proved more practicable.
Development and design
In early 1916, the British War Office drew up a specification for a multi-seat escort fighter to be powered by one of the new Rolls-Royce Eagle engines, intended to protect formations of bombers from German fighters, with an additional role of destroying enemy airships. While the specification did not require high speed, a good field of fire for its guns was essential, while the secondary anti-Zeppelin role demanded an endurance of at least seven hours.
Orders were placed for prototypes from Armstrong Whitworth (the F.K.6), Sopwith and Vickers (the F.B.11). All three designs were driven by the need to provide wide fields of fire in the absence of an effective synchronisation gear that would allow safe firing of guns through the propeller disc.
The Sopwith proposal was modified from an existing design for a two-seat triplane, with a nacelle for a gunner added to the upper wing. It had three-bay, narrow chord wings, with the streamlined nacelle housing the upper gunner who was armed with a Lewis gun built around the centre section of the upper wing. Ailerons were fitted to all wings, with air brakes fitted to the lower wing.
“Sopwith L.R.T.Tr.” enters the record as british WW1 triplane escort fighter aircraft. Crown Archives preserves that source wording while asking what Sopwith, British and triplane can confirm, complicate or overturn.
Why this record matters
“Sopwith L.R.T.Tr.” is worth following because a concise public description often conceals a longer documentary argument. Here, Sopwith, British and triplane 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 Nov 8, 2025. The linked authority identifier is Q4898611. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1916.
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.
- 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 “Sopwith L.R.T.Tr.”, its source revision and the description used here.
- Expand the search: follow Sopwith L.R.T.Tr. primary sources, Sopwith L.R.T.Tr. archive and Sopwith 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 “Sopwith L.R.T.Tr.”?
- 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 “Sopwith L.R.T.Tr.” 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.