07.03.2017 Views

POLLINATORS POLLINATION AND FOOD PRODUCTION

individual_chapters_pollination_20170305

individual_chapters_pollination_20170305

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

THE ASSESSMENT REPORT ON <strong>POLLINATORS</strong>, <strong>POLLINATION</strong> <strong>AND</strong> <strong>FOOD</strong> <strong>PRODUCTION</strong><br />

60<br />

2. DRIVERS OF CHANGE OF <strong>POLLINATORS</strong>,<br />

<strong>POLLINATION</strong> NETWORKS <strong>AND</strong> <strong>POLLINATION</strong><br />

Of the separate incidents of honey bee mortality in Europe<br />

where insecticides were detected (an incident may include<br />

more than one coloniy or more than one apiary site), 27%<br />

contained organophosphorus insecticides or carbamate<br />

compounds, 14% contained organochlorine insecticide<br />

(gamma-HCH (lindane), and dieldrin) and pyrethroid<br />

insecticides were present in 7.8% of incidents; none were<br />

associated with neonicotinoids (Thompson and Thorbahn,<br />

2009). Between 1981 and 1991 around 65-70% of the 545<br />

incidents in the UK were identified as due to farmers not<br />

complying with label instructions and applying insecticides in<br />

flowering beans, peas and oilseed rape, or crops containing<br />

flowering weeds (Greig-Smith et al., 1994); of the remainder<br />

3% were associated with aerial applications (no longer<br />

permitted in the UK), 2% with use in feral bee control and<br />

in the remainder of reported incidents the use often could<br />

not be clearly identified from the information available.<br />

These incidents have resulted in improved regulation and<br />

enforcement in Europe (e.g. Directive 91/414 EEC) with<br />

subsequent reduction in incidents as well as providing<br />

information where uses according to the label require further<br />

education of farmers (Thompson and Thorbahn, 2009). For<br />

example, the reduction in the number of reported aphid<br />

honeydew-related insecticide incidents in the Netherlands<br />

from 119 in 2003 to 17 in 2006 was attributed to the<br />

reduction in the aphid control threshold for insecticide use<br />

in potatoes, which limited the availability of aphid honeydew<br />

(a source of sugar) and thus attraction of honey bees to the<br />

crop (Thompson and Thorbahn, 2009).<br />

These experiences from countries with incident schemes<br />

suggest that where there is no effective regulation or<br />

enforcement of key mitigation (Heong et al., 2013), it is likely<br />

that incidents of insecticide-associated honey bee mortality<br />

FIGURE 2.3.4<br />

Comparison of the risk index (HQ = application<br />

rate/LD50) with the number of honey bee incidents<br />

in which the pesticide was detected. Data are<br />

from the UK, Germany and the Netherlands 1985-<br />

2007. An HQ of 50 is used in risk assessments<br />

for pesticides to identify those uses that require<br />

further evaluation. Incidents may also contain<br />

pesticides not related to bee mortality, e.g. 1)<br />

fluvalinate used as a varroacide (to control the<br />

Varroa mite) and 2) captan, a fungicide applied at<br />

high rates (Thompson and Thorbahn 2009). The<br />

circles highlight the groupings of incidents involving<br />

different classes of insecticides. For reference<br />

the HQ of the neonicotinoids imidacloprid,<br />

thiamethoxam and clothiandin are >1000 but no<br />

incidents were reported.<br />

Number of honey bee incidents<br />

700<br />

600<br />

500<br />

400<br />

300<br />

200<br />

100<br />

are occurring; in the absence of honey bee impacts effects<br />

on wild bees are unclear. Mitigation measures to protect<br />

honey bees include only applying insecticides outside the<br />

flowering period, and closing or removing beehives or<br />

use of low-drift technology to reduce drift of spray onto<br />

nearby flowering crops or hedgerows containing flowering<br />

plants. To be effective, mitigation needs to take account of<br />

local practices and also apply to other insect pollinators.<br />

For example, beekeepers keeping native bees in Korea<br />

have reported that impacts of pesticide spray cannot be<br />

avoided because their hives cannot be moved (Park and<br />

Youn, 2012).<br />

These incident data have also been used to derive the<br />

hazard quotient (application rate (g active ingredient/ha)/<br />

LD 50<br />

(µg active ingredient/bee)) threshold of 50 to identify<br />

those uses of foliar applied pesticides with a risk of resulting<br />

in acute honey bee mortality and requiring further evaluation<br />

in the risk assessment, e.g., semi-field and field studies<br />

(EPPO, 2010). A comparison of the hazard quotient (HQ)<br />

with the number of incidents reported is shown in Figure<br />

2.3.4. Although the HQ for pyrethroid insecticides is far<br />

greater than 50 there is good evidence that, when applied<br />

according to the label, particularly at lower application<br />

rates, and not mixed with ergosterol biosynthesis-inhibiting<br />

(EBI) fungicides (see pesticide mixtures section) honey<br />

bee incidents are rarely observed due to the repellent<br />

properties of some of this class of insecticide (Thompson<br />

and Thorbahn, 2009). These national monitoring schemes<br />

have shown a decrease in the overall number of incidents<br />

reported over the last 20 years following reactive changes<br />

to product registrations and stewardship, e.g. limiting<br />

applications to non bee-attractive crops. However, high<br />

profile incidents are still reported such as the off-label use of<br />

HQ=50<br />

Organophosphorus,<br />

carbamate<br />

insecticides<br />

and gamma HCH<br />

Pyrethroid<br />

insecticides<br />

0<br />

1 10 100 1000 10000 100000<br />

Risk index (HQ = application rate/LD50)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!