About: Elastic Defense   Sponge Permalink

An Entity of Type : dbkwik:resource/BjYlvqMExdfza5TjENXkCg==, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

German Elastic Defense doctrine called for the creation of three defensive zones, the ‘Outpost’ zone, the ‘Battle’ zone, and the ‘Rearward’ zone. The Outpost zone would be occupied by only the minimum amount of troops required to maintain constant observation and combat enemy reconnaissance. The Battle zone, typically having anywhere from 1,500 to 3,000 meters in depth, was where the enemy was to be worn down over time. Meanwhile, the Rearward zone would hold the majority of heavy artillery or anti-tank weapons that would aid to defeat the enemy in the Battle zone. When the enemy was finally worn down enough, German troops would use the reserves that had been saved from a concentrated defensive line and launch prompt counterattacks so that the defensive line would "bounce" back to its orig

AttributesValues
rdf:type
rdfs:label
  • Elastic Defense
rdfs:comment
  • German Elastic Defense doctrine called for the creation of three defensive zones, the ‘Outpost’ zone, the ‘Battle’ zone, and the ‘Rearward’ zone. The Outpost zone would be occupied by only the minimum amount of troops required to maintain constant observation and combat enemy reconnaissance. The Battle zone, typically having anywhere from 1,500 to 3,000 meters in depth, was where the enemy was to be worn down over time. Meanwhile, the Rearward zone would hold the majority of heavy artillery or anti-tank weapons that would aid to defeat the enemy in the Battle zone. When the enemy was finally worn down enough, German troops would use the reserves that had been saved from a concentrated defensive line and launch prompt counterattacks so that the defensive line would "bounce" back to its orig
dcterms:subject
dbkwik:world-war-2...iPageUsesTemplate
Date
  • Circa 1917
Type
  • Army Tactic
Caption
  • An example of a British elastic defense from World War I
Objective
  • Minimize the amount of casualties taken defending while maximizing the casualties suffered by the enemy during an attack
abstract
  • German Elastic Defense doctrine called for the creation of three defensive zones, the ‘Outpost’ zone, the ‘Battle’ zone, and the ‘Rearward’ zone. The Outpost zone would be occupied by only the minimum amount of troops required to maintain constant observation and combat enemy reconnaissance. The Battle zone, typically having anywhere from 1,500 to 3,000 meters in depth, was where the enemy was to be worn down over time. Meanwhile, the Rearward zone would hold the majority of heavy artillery or anti-tank weapons that would aid to defeat the enemy in the Battle zone. When the enemy was finally worn down enough, German troops would use the reserves that had been saved from a concentrated defensive line and launch prompt counterattacks so that the defensive line would "bounce" back to its original point. Following the First World War, the German Elastic Defense remained largely unchanged, yet was felt by many German commanders to be unfit for the new war. Some concessions made to allow for a more mobile defense were the more sparing use of trenches, instead replaced for fox holes and strong points, though tougher defenses were always sought after. Furthermore, the anti-tank gun was given far more precedence in the design of the position. Another important feature of the German Elastic Defense was the use of a false first trenchline, typically used on the Eastern Front. What this did was absorb the majority of Soviet artillery fire while German troops quickly moved back to rear positions, as soon as the barrage ended, they moved into this first line so as to counter enemy advances. Examples of the German Elastic Defense can be seen in many instances during the war, notably, the fighting in Normandy in the Bocage country.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software