z-logo
open-access-imgOpen Access
Reconstruction of the deformed collision zone Between India and Asia by backward motion of lithospheric blocks
Author(s) -
Replumaz A.,
Tapponnier P.
Publication year - 2003
Publication title -
journal of geophysical research: solid earth
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.67
H-Index - 298
eISSN - 2156-2202
pISSN - 0148-0227
DOI - 10.1029/2001jb000661
Subject(s) - geology , collision , lithosphere , collision zone , kinematics , geodesy , crust , tectonics , seismology , geodynamics , geodetic datum , geometry , geophysics , computer science , physics , mathematics , computer security , classical mechanics
On the basis of a synthesis of tectonic data available on the India‐Asia collision, we present a first attempt to reconstruct the evolution of the collision zone. Assuming that the deformation of the lithosphere is localized along narrow shear zones and that the interiors of mantle blocks in between remain relatively undeformed, we define block contours from the fault pattern and move back the blocks along their boundary faults. Along convergent or extensional boundaries, the crust is assumed to shorten or stretch coherently. Step‐by‐step, we go backward in time to finally reach the collision onset. For each time step, we find a solution compatible with the data set available and the position of the adjacent blocks for each block. The search for compatibility at the scale of the entire collision zone allows for solving the kinematics of regions with fewer data and suggests plausible scenarios for regions where data is lacking. For each step, we calculate large‐scale displacement maps, and determine Euler poles for each block. For the most recent time step, the map proposed is compared to GPS motions. The deformation budget implies that extrusion absorbed ∼30% of the convergence between India and Siberia during the entire collision span, but varied with time, accounting for as little as 3% or as much as 60% of this convergence at different epochs.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here