Not logged in
PANGAEA.
Data Publisher for Earth & Environmental Science

Turgeon, Steven C; Creaser, Robert A (2008): Osmium concentrations and isotope ratios of ODP Hole 207-1260B and the Furlo section [dataset]. PANGAEA, https://doi.org/10.1594/PANGAEA.769773, Supplement to: Turgeon, SC; Creaser, RA (2008): Cretaceous oceanic anoxic event 2 triggered by a massive magmatic episode. Nature, 454(7202), 323-327, https://doi.org/10.1038/nature07076

Always quote citation above when using data! You can download the citation in several formats below.

RIS CitationBibTeX CitationShow MapGoogle Earth

Abstract:
Oceanic anoxic events (OAEs) were episodes of widespread marine anoxia during which large amounts of organic carbon were buried on the ocean floor under oxygen-deficient bottom waters (Schlanger and Jenkyns, 1976; Schlanger et al., 1987). OAE2, occurring at the Cenomanian/Turonian boundary (about 93.5 Myr ago) (Gradstein et al., 2004), is the most widespread and best defined OAE of the mid-Cretaceous. Although the enhanced burial of organic matter can be explained either through increased primary productivity or enhanced preservation scenarios (Schlanger and Jenkyns, 1976; Schlanger et al., 1987). the actual trigger mechanism, corresponding closely to the onset of these episodes of increased carbon sequestration, has not been clearly identified. It has been postulated that large-scale magmatic activity initially triggered OAE2 (Sinton and Duncan, 1997; Kerr, 1998, doi:10.1144/gsjgs.155.4.0619), but a direct proxy of magmatism preserved in the sedimentary record coinciding closely with the onset of OAE2 has not yet been found. Here we report seawater osmium isotope ratios in organic-rich sediments from two distant sites. We find that at both study sites the marine osmium isotope record changes abruptly just at or before the onset of OAE2. Using a simple two-component mixing equation, we calculate that over 97 per cent of the total osmium content in contemporaneous seawater at both sites is magmatic in origin, a ~30–50-fold increase relative to pre-OAE conditions. Furthermore, the magmatic osmium isotope signal appears slightly before the OAE2 -as indicated by carbon isotope ratios- suggesting a time-lag of up to ~23 kyr between magmatism and the onset of significant organic carbon burial, which may reflect the reaction time of the global ocean system. Our marine osmium isotope data are indicative of a widespread magmatic pulse at the onset of OAE2, which may have triggered the subsequent deposition of large amounts of organic matter.
Project(s):
Coverage:
Median Latitude: 26.482755 * Median Longitude: -20.872100 * South-bound Latitude: 9.265510 * West-bound Longitude: -54.544200 * North-bound Latitude: 43.700000 * East-bound Longitude: 12.800000
Date/Time Start: 2003-02-09T07:35:00 * Date/Time End: 2003-02-12T23:45:00
Minimum DEPTH, sediment/rock: 3.05 m * Maximum DEPTH, sediment/rock: 427.69 m
Event(s):
207-1260B * Latitude: 9.265510 * Longitude: -54.544200 * Date/Time Start: 2003-02-09T07:35:00 * Date/Time End: 2003-02-12T23:45:00 * Elevation: -2548.8 m * Penetration: 509 m * Recovery: 326.49 m * Location: South Atlantic Ocean * Campaign: Leg207 * Basis: Joides Resolution * Method/Device: Drilling/drill rig (DRILL) * Comment: 46 cores; 370.3 m cored; 138.7 m drilled; 88.2 % recovery
Furlo * Latitude: 43.700000 * Longitude: 12.800000 * Location: Italy * Method/Device: Drilling/drill rig (DRILL)
Comment:
Sediment depth is given in mcd.
Parameter(s):
#NameShort NameUnitPrincipal InvestigatorMethod/DeviceComment
1Event labelEvent
2Sample code/labelSample labelTurgeon, Steven C
3DEPTH, sediment/rockDepth sedmGeocode
4OsmiumOsng/kgTurgeon, Steven C
5Rhenium-187/Osmium-188 ratio187Re/188OsTurgeon, Steven C
6Rhenium-187/Osmium-188, error187Re/188Os e±Turgeon, Steven C
7Osmium-187/Osmium-188 ratio187Os/188OsTurgeon, Steven C
8Osmium-187/Osmium-188, error187Os/188Os e±Turgeon, Steven C
9Osmium-187/Osmium-188 ratio187Os/188OsTurgeon, Steven Cinitial
10CommentCommentTurgeon, Steven C
Size:
316 data points

Download Data

Download dataset as tab-delimited text — use the following character encoding:

View dataset as HTML