z-logo
Premium
SEDIMENT‐ASSOCIATED PESTICIDES IN AN URBAN STREAM IN GUANGZHOU, CHINA: IMPLICATION OF A SHIFT IN PESTICIDE USE PATTERNS
Author(s) -
Li Huizhen,
Sun Baoquan,
Lydy Michael J.,
You Jing
Publication year - 2013
Publication title -
environmental toxicology and chemistry
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.1
H-Index - 171
eISSN - 1552-8618
pISSN - 0730-7268
DOI - 10.1002/etc.2147
Subject(s) - fipronil , abamectin , pesticide , sediment , environmental science , environmental chemistry , aquatic ecosystem , ecotoxicology , ecology , biology , chemistry , paleontology
Pesticide use patterns in China have changed in recent years; however, the study of the environmental fate of current‐use pesticides (CUPs) and their ecotoxicological significance in aquatic ecosystems is limited. In the present study, sediments were collected from an urban stream in the Chinese city of Guangzhou. Sediment‐associated legacy organochlorine pesticides and CUPs—including organophosphates, pyrethroids, fipronil, and abamectin—were analyzed. Additionally, the relative toxicity of the sediments was evaluated with 10‐d bioassays using Chironomus dilutus . Fifteen of 16 sediments collected from the stream were acutely toxic to C. dilutus , with 81% of the samples causing 100% mortality. Abamectin, fipronil, and pyrethroids (mainly cypermethrin) were identified as the principal contributors to the noted toxicity in the midges, with median predicted toxic units of 1.63, 1.63, and 1.03, respectively. Sediments taken from downstream sites, where residential and industrial regions were located, had elevated CUP concentrations and sediment toxicity compared with upstream sites. The present study is the first of its kind to link sediment CUPs, fipronil, and abamectin concentrations with toxicity in urban streams in China with a focus on shifting pesticide usage patterns. Environ. Toxicol. Chem. 2013;32:1040–1047. © 2013 SETAC

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here