The Varsity was developed by Vickers and based on the Viking and Valetta to meet Air Ministry Specification T.13/48 for a twin-engined training aircraft to replace the Wellington T10 and the Valetta T3 and T4.[2] The main differences were the wider-span wings, longer fuselage and tricycle undercarriage. There was also a ventral pannier to allow a trainee bomb aimer to lie in a prone position and a bomb bay with a capacity for 24 x 25lb smoke & flash bombs.[2]
The first prototype Type 668 Varsity VX828 was first flown by J 'Mutt' Summers and G R 'Jock' Bryce from Wisley on 17 July 1949.[2]
A civil version the VC.3 was planned but with the success of the VC.2 Viscount the idea was abandoned.[2]
Operational history
Varsity T.1 of the Royal Air Force College Cranwell in 1968
The Varsity was introduced to replace the Wellington T10 trainer. Following deliveries to trials units the first production aircraft were delivered for operational use in 1951 to No. 201 Advanced Flying School at RAF Swinderby, where they were used to train pilots to fly multi-engined aircraft. It also equipped two Air Navigator Schools in 1952, and the Bomber Command Bombing school, with the job of training crews for RAF Bomber-Command's V-bomber crews.[3]
The Swedish Air Force operated a single Varsity from January 1953 to 1973 mainly for electronic intelligence missions. The Swedish military designation was Tp 82.
The last flying example (Serial WL679) was operated by the Royal Aircraft Establishment; it was retired into preservation at the Royal Air Force Museum Midlands, Cosford in 1992.
Operators
Varsity T1 on display at the Newark Air MuseumVarsity T1 on display at the Newark Air Museum
Andrews, C.F. and E.B. Morgan. Vickers Aircraft since 1908. London: Putnam, 1988. ISBN0-85177-815-1.
Bagshaw, R. Deacon, R. Pollock, A. and Thomas, M. RAF Little Rissington: The Central Flying School years 1946 - 1976. Pen & Sword, 2006 ISBN1-84415-381-9
This template's initial visibility currently defaults to autocollapse, meaning that if there is another collapsible item on the page (a navbox, sidebar, or table with the collapsible attribute), it is hidden apart from its title bar; if not, it is fully visible.
To change this template's initial visibility, the |state=parameter may be used:
{{Vickers Varsity|state=collapsed}} will show the template collapsed, i.e. hidden apart from its title bar.
{{Vickers Varsity|state=expanded}} will show the template expanded, i.e. fully visible.
Templates using the classes class=navbox ({{navbox}}) or class=nomobile ({{sidebar}}) are not displayed in article space on the mobile web site of English Wikipedia. Mobile page views accounted for 60% to 70% of all page views from 2020 through 2025. Briefly, these templates are not included in articles because 1) they are not well designed for mobile, and 2) they significantly increase page sizes—bad for mobile downloads—in a way that is not useful for the mobile use case. You can review/watch phab:T124168 for further discussion.
TemplateData
A navigational box that can be placed at the bottom of articles.
This template's initial visibility currently defaults to autocollapse, meaning that if there is another collapsible item on the page (a navbox, sidebar, or table with the collapsible attribute), it is hidden apart from its title bar; if not, it is fully visible.
To change this template's initial visibility, the |state=parameter may be used:
{{Vickers Varsity|state=collapsed}} will show the template collapsed, i.e. hidden apart from its title bar.
{{Vickers Varsity|state=expanded}} will show the template expanded, i.e. fully visible.
Templates using the classes class=navbox ({{navbox}}) or class=nomobile ({{sidebar}}) are not displayed in article space on the mobile web site of English Wikipedia. Mobile page views accounted for 60% to 70% of all page views from 2020 through 2025. Briefly, these templates are not included in articles because 1) they are not well designed for mobile, and 2) they significantly increase page sizes—bad for mobile downloads—in a way that is not useful for the mobile use case. You can review/watch phab:T124168 for further discussion.
TemplateData
A navigational box that can be placed at the bottom of articles.
This template's initial visibility currently defaults to autocollapse, meaning that if there is another collapsible item on the page (a navbox, sidebar, or table with the collapsible attribute), it is hidden apart from its title bar; if not, it is fully visible.
To change this template's initial visibility, the |state=parameter may be used:
{{Vickers Varsity|state=collapsed}} will show the template collapsed, i.e. hidden apart from its title bar.
{{Vickers Varsity|state=expanded}} will show the template expanded, i.e. fully visible.
Templates using the classes class=navbox ({{navbox}}) or class=nomobile ({{sidebar}}) are not displayed in article space on the mobile web site of English Wikipedia. Mobile page views accounted for 60% to 70% of all page views from 2020 through 2025. Briefly, these templates are not included in articles because 1) they are not well designed for mobile, and 2) they significantly increase page sizes—bad for mobile downloads—in a way that is not useful for the mobile use case. You can review/watch phab:T124168 for further discussion.
TemplateData
A navigational box that can be placed at the bottom of articles.
This template's initial visibility currently defaults to autocollapse, meaning that if there is another collapsible item on the page (a navbox, sidebar, or table with the collapsible attribute), it is hidden apart from its title bar; if not, it is fully visible.
To change this template's initial visibility, the |state=parameter may be used:
{{Vickers Varsity|state=collapsed}} will show the template collapsed, i.e. hidden apart from its title bar.
{{Vickers Varsity|state=expanded}} will show the template expanded, i.e. fully visible.
Templates using the classes class=navbox ({{navbox}}) or class=nomobile ({{sidebar}}) are not displayed in article space on the mobile web site of English Wikipedia. Mobile page views accounted for 60% to 70% of all page views from 2020 through 2025. Briefly, these templates are not included in articles because 1) they are not well designed for mobile, and 2) they significantly increase page sizes—bad for mobile downloads—in a way that is not useful for the mobile use case. You can review/watch phab:T124168 for further discussion.
TemplateData
A navigational box that can be placed at the bottom of articles.