FORCETALLY
Loading the evidence…
Preparing your view.
Preparing your view.
Support aircraftActive ServiceProfile in progress
Strategic transport/VIP transport/tanker
Airbus CC-330 Husky is a strategic transport/VIP transport/tanker. It was built by Airbus. Reported operators include Royal Canadian Air Force.
Technical data
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
Strategic transport/VIP transport/tanker
Airbus
Active Service
Royal Canadian Air Force
2023
Airbus A330 MRTT
CC-150 Polaris
CC-330 Husky
Reference text from Wikipedia contributors, used under CC BY-SA 4.0.
Airbus CC-330 Husky equipment records. Variants, orders and quantities are shown as reported in each inventory source; coverage is incomplete.
CanadaReported count for CC-330 Husky · A330-200. Country-wide list; no individual service specified. 1 distinct count cell(s) from the same source list; shared rowspan cells counted once. Retired, wholly reserve and on-order rows are excluded; the reported count retains any explicitly mixed stock scope in the quoted row. Count column(s): in service: 3. Origin: Multinational. The listed variants/roles are the scope, not an immediately deployable count. The components do not establish one inventory census date; the stored date is the retrieved source snapshot.