Skip to content
Surf Wiki
Save to docs
science/earth-science

From Surf Wiki (app.surf) — the open knowledge base

Indian plate

Minor plate that separated from Gondwana


Minor plate that separated from Gondwana

FieldValue
imageFile:IndianPlate.png
typeMinor
area11900000 km2
move_directionNorth-east
move_speed26-36 mm/year
geo_featuresIndian subcontinent, Indian Ocean, Arabian Sea, Himalayas
Note

the geological term

The Indian plate is a minor tectonic plate straddling the equator in the Indian Ocean. Originally a part of the ancient continent of Gondwana, the Indian plate broke away from the other fragments of Gondwana and began moving north, carrying Insular India (Now called South Asia) with it. It was once fused with the adjacent Australian plate to form a single Indo-Australian plate, but recent studies suggest that India and Australia may have been separate plates for at least 3 million years. The Indian plate includes most of modern South Asia (the Indian subcontinent) and a portion of the basin under the Indian Ocean, including parts of Tibet, Sumatra, and extending up to but not including Ladakh, Kohistan, and Balochistan in Pakistan.

Plate movements

Until roughly , the Indian plate formed part of the supercontinent, Gondwana, together with modern Africa, Australia, Antarctica, and South America. Gondwana fragmented as these continents drifted apart at different velocities; a process which led to the opening of the Indian Ocean.

In the late Cretaceous approximately , and subsequent to the splitting from Gondwana of conjoined Madagascar and India, the Indian plate split from Madagascar and formed Insular India. It began moving north, at about 20 cm per year, and is believed to have begun colliding with Asia as early as , in the Eocene epoch of the Cenozoic. However, some authors suggest the collision between India and Eurasia occurred much later, around . If the collision occurred between 55 and 50 Mya, the Indian plate would have covered a distance of 3000 to(-), moving more quickly than any other known plate. In 2012, paleomagnetic data from the Greater Himalaya was used to propose two collisions to reconcile the discrepancy between the amount of crustal shortening in the Himalaya (~1300 km) and the amount of convergence between India and Asia (~3600 km). These authors propose a continental fragment of northern Gondwana rifted from India, traveled northward, and initiated the "soft collision" between the Greater Himalaya and Asia at ~50 Mya. This was followed by the "hard collision" between India and Asia occurred at ~25 Mya. Subduction of the resulting ocean basin that formed between the Greater Himalayan fragment and India explains the apparent discrepancy between the crustal shortening estimates in the Himalaya and paleomagnetic data from India and Asia. However, the proposed ocean basin was not constrained by paleomagnetic data from the key time interval of ~120 Mya to ~60 Mya. New paleomagnetic results of this critical time interval from southern Tibet do not support this Greater Indian Ocean basin hypothesis and the associated dual collision model.

In 2007, German geologists suggested the reason the Indian plate moved so quickly is that it is only half as thick (100 km) as the other plates which formerly constituted Gondwana. The mantle plume that once broke up Gondwana might also have melted the lower part of the Indian subcontinent, which allowed it to move both more quickly and farther than the other parts. The remains of this plume today form the Marion hotspot (Prince Edward Islands), the Kerguelen hotspot, and the Réunion hotspots. As India moved north, it is possible the thickness of the Indian plate degenerated further as it passed over the hotspots and magmatic extrusions associated with the Deccan and Rajmahal Traps. The massive amounts of volcanic gases released during the passage of the Indian plate over the hotspots have been theorised to have played a role in the Cretaceous–Paleogene extinction event, generally held to be due to a large asteroid impact.

In 2020, however, geologists at the University of Oxford and the Alfred Wegener Institute found that new plate-motion models displayed increased movement speeds in all mid-ocean ridges during the late Cretaceous, a result irreconcilable to current theories of plate tectonics and a refutation of the plume-push hypothesis. Pérez-Díaz concludes that the accelerated movement of the Indian plate is an illusion wrought by large errors in geomagnetic reversal timing around the Cretaceous–Paleogene boundary, and that a recalibration of the time scale shows no such acceleration exists.

The collision with the Eurasian plate along the boundary between India and Nepal formed the orogenic belt that created the Tibetan Plateau and the Himalaya Mountains, as sediment bunched up like earth before a plow.

The Indian plate is currently moving north-east at 5 cm per year, while the Eurasian plate is moving north at only 2 cm per year. This is causing the Eurasian plate to deform, and the Indian plate to compress at a rate of 4 mm per year.

Geography

The westerly side of the Indian plate is a transform boundary with the Arabian plate called the Owen fracture zone, and a divergent boundary with the African plate called the Central Indian Ridge (CIR). The northerly side of the plate is a convergent boundary with the Eurasian plate forming the Himalaya and Hindu Kush mountains, called the Main Himalayan Thrust.

Notes

References

References

  1. (2014-03-05). "Sizes of Tectonic or Lithospheric Plates". Geology.about.com.
  2. Oskin, Becky. (2013-07-05). "New Look at Gondwana's Breakup". Livescience.com.
  3. (2002). "Plate Boundary Zones". American Geophysical Union.
  4. Sinvhal, ''Understanding Earthquake Disasters'', p. 52, Tata McGraw-Hill Education, 2010, {{ISBN. 978-0-07-014456-9
  5. (1999). "A new seismic hazard map for the Indian plate region under the global seismic hazard assessment programme". Current Science.
  6. M. Asif Khan, ''Tectonics of the Nanga Parbat syntaxis and the Western Himalaya'', p. 375, Geological Society of London, 2000, {{ISBN. 978-1-86239-061-4
  7. Srikrishna Prapnnachari, ''Concepts in Frame Design'', page 152, Srikrishna Prapnnachari, {{ISBN. 978-99929-52-21-4
  8. [[Şengör. A.M. Celâl Şengör]] (1989). ''Tectonic evolution of the Tethyan Region'', Springer {{ISBN. 978-0-7923-0067-0
  9. {{Harvnb. Kind. 2007
  10. {{Harvnb. Kumar. Yuan. Kumar. Kind. 2007
  11. {{Harvnb. Scotese. 2001
  12. {{Harvnb. Aitchison. Ali. Davis. 2007
  13. van Hinsbergen, D.. (2012). "Greater India Basin hypothesis and a two-stage Cenozoic collision between India and Asia". Proceedings of the National Academy of Sciences.
  14. (2019-01-17). "Paleomagnetic results of Cretaceous cherts from Zhongba, southern Tibet: New constraints on the India-Asia collision". Journal of Asian Earth Sciences.
  15. The lithospheric roots in South Africa, Australia, and Antarctica are {{cvt. 300. to. 180. km thick. ({{Harvnb. Kumar. Yuan. Kumar. Kind. 2007) See also {{Harvnb. Kumar. Yuan. Kumar. Kind. 2007
  16. (2006). "Paleomagnetic evidence for a stationary Marion hotspot: Additional paleomagnetic data from Madagascar". Gondwana Research.
  17. Schulte, Peter. (5 March 2010). "The Chicxulub Asteroid Impact and Mass Extinction at the Cretaceous-Paleogene Boundary". AAAS.
  18. (2020). "Indo-Atlantic plate accelerations around the Cretaceous-Paleogene boundary: A time-scale error, not a plume-push signal". [[Geology (journal).
  19. Andrews, Robin George. (14 April 2021). "The New Historian of the Smash That Made the Himalayas". [[Quanta Magazine]].
Info: Wikipedia Source

This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page.

Want to explore this topic further?

Ask Mako anything about Indian plate — get instant answers, deeper analysis, and related topics.

Research with Mako

Free with your Surf account

Content sourced from Wikipedia, available under CC BY-SA 4.0.

This content may have been generated or modified by AI. CloudSurf Software LLC is not responsible for the accuracy, completeness, or reliability of AI-generated content. Always verify important information from primary sources.

Report