ASCOD
armored fighting vehicle
The ASCOD (Austrian Spanish Cooperation Development) armoured fighting vehicle family is the product of a cooperation agreement between Austrian Steyr-Daimler-Puch AG and Spanish General Dynamics Santa Bárbara Sistemas. Both companies are now divisions of a unit of General Dynamics. The ASCOD family includes the LT 105 light tank equipped with a 105 mm gun, a surface-to-air missile launcher, an anti-tank guided missile launcher, mortar carrier, R&R vehicle, command-and-control vehicle, ambulance, artillery observer, and the AIFV model.
In Spanish service, the vehicle is called "Pizarro". The Austrian version is called "Ulan".
History
The ASCOD was designed to replace the older light armoured fighting vehicles of the Austrian and Spanish armies, such as the M113 armored personnel carrier and the Saurer APC. The Ulan, the Austrian version of the Pizarro, would provide a flexible complement to their heavy Leopard 2A4. The Ulan would allow the Austrian army to deploy rapidly and effectively over longer distances, especially for foreseeable future operations—such as trouble-spots for UN operations.
In 1982, Steyr-Daimler-Puch Spezialfahrzeug initiated the conception phase for the development of a new infantry fighting vehicle. This was followed by initial talks with the militaries of Greece, Norway and Switzerland to find the desired requirements for a new IFV. In 1985, the decision to develop a new IFV was made following the Bundesheer announcement of the military requirement for the Kampfschützenpanzer 90 (combat infantry fighting vehicle 90). Based on this, Steyr-Daimler-Puch Spezialfahrzeug started the conception of the vehicle.
The public source identifies “ASCOD” as armored fighting vehicle. This brief keeps that definition visible, then builds a research path around ASCOD, armored and fighting.
Why this record matters
A short description can identify a subject without explaining its stakes. For “ASCOD”, the useful work is to connect “armored fighting vehicle” 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 Sep 6, 2026. The linked authority identifier is Q697225. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1982 and 1985.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 “ASCOD”, its source revision and the description used here.
- Expand the search: follow ASCOD primary sources, ASCOD archive and ASCOD 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 “ASCOD”?
- 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 “ASCOD” 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.