Boeing RC-135
reconnaissance aircraft family by Boeing

The Boeing RC-135 is a family of large reconnaissance aircraft built by Boeing and modified by a number of companies, including General Dynamics, Lockheed, LTV, E-Systems, and L3Harris Technologies, and used by the United States Air Force and Royal Air Force to produce theater and national level intelligence with near real-time on-scene collection, analysis and dissemination capabilities.
Based on the Boeing C-135 Stratolifter airframe, various types of RC-135s have been in service since 1961. Unlike the KC-135, which is recognized by Boeing as the Model 717, most of the current RC-135 fleet, with the exception of the RAF's RC-135Ws, is internally designated as the Model 739 by the company. Many variants have been modified numerous times, resulting in a large variety of designations, configurations, and program names.
Design and development
In 1962, the first RC-135 variant, the RC-135A, was ordered by the United States Air Force to replace the Boeing RB-50 Superfortress. Originally nine were ordered but this was later reduced to four. Boeing allocated the variant the designation Boeing 739-700 but they were a modified variant of the KC-135A then in production. They used the same Pratt & Whitney J57 turbojet engines as the tanker and carried cameras in a bay just aft of the nose wheel well where the forward fuel tank was normally located. They had no in-flight refueling system and they were used for photographic and surveying tasks. Although the RC-135A was the first designation in the RC-135 family, it was not the first RC-135 in service.
The public source identifies “Boeing RC-135” as reconnaissance aircraft family by Boeing. This brief keeps that definition visible, then builds a research path around Boeing, RC-135 and reconnaissance.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Boeing RC-135”, the useful work is to connect “reconnaissance aircraft family by Boeing” 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 Aug 10, 2026. The linked authority identifier is Q132516. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1961 and 1962.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. 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 “Boeing RC-135”, its source revision and the description used here.
- Expand the search: follow Boeing RC-135 primary sources, Boeing RC-135 archive and Boeing 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 “Boeing RC-135”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Boeing RC-135” 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.