40Ar/^39Ar Thermochronology Constraints on Jurassic Tectonothermal Event of Nyainrong Microcontinent
To reveal the Jurassic tectonothermal event occurring to the Nyainrong microcontinent which is gripped among the Bangong-Nujiang suture zone,^40Ar/^39Ar dating was carried out on the basement orthogneiss and Jurassic granitc gneiss in the microcontinent. In the heating stage, four sam- pies exhibite...
Gespeichert in:
Veröffentlicht in: | Journal of earth science (Wuhan, China) China), 2014-02, Vol.25 (1), p.98-108 |
---|---|
Hauptverfasser: | , , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | To reveal the Jurassic tectonothermal event occurring to the Nyainrong microcontinent which is gripped among the Bangong-Nujiang suture zone,^40Ar/^39Ar dating was carried out on the basement orthogneiss and Jurassic granitc gneiss in the microcontinent. In the heating stage, four sam- pies exhibited a flat plateau age, with the value Tp concentrated in the range of 166-176 Ma; isochron age Ti was concentrated in the range of 165-175 Ma, and their corresponding ages were the consistent within allowable range. The ages should be representative of the era of the final deformation of the Amdo gneiss and cooling emplacement of the magmatic rock in the Jurassic. The geochronological studies have shown that the final deformation of microcontinent crystalline basement and the cooling of the Mesozoic large-scale tectonothermal events occurred in late Middle Jurassic. In Middle Jurassic, Nyainrong microcontinent experienced strong tectonic movement. Combining with the geochronologi- cal with isotope geochemistry for the microcontinent, the cause of the tectonothermal event should be attributed to the collision between the Nyainrong microcontinent and South Qiangtang Block following the northward subduction of Bangong-Nujiang oceanic crust. |
---|---|
ISSN: | 1674-487X 1867-111X |
DOI: | 10.1007/s12583-014-0403-0 |