Peach potato aphid

The Peach-Potato Aphid (PPA) known as Mysus persicae is known to feed on a wide range of plants including several grown as crops. 

They are known to transmit viruses to crop plants including Turnips Yellow Virus (TuYV) which can lead to yield reductions in oilseed rape.

Damage

The Peach-Potato aphid originates from Asia where its host plant, the peach tree, is native.  However, it is now a pest with a world-wide distribution. The peach potato aphid (Myzus persicae) is a particularly polyphagous aphid with summer host plants from more than 40 different families and has the ability to transmit over 100 viruses.

Transmission of viruses can cause serious economic damage but only heavy infestations cause direct feeding damage. Peach potato aphid, Myzus persicae, is the most important vector of turnip yellows virus (TuYV), potato leaf roll virus (PLRV), potato virus A (PVA) and potato virus Y (PVY). It also transmits cauliflower mosaic virus (CaMV), beet yellows virus (BYV), beet chlorosis virus (BChV) and beet mild yellowing virus (BMYV). If aphids transmit viruses early in the season, the effects are greatest.

Appearance 

The aphid itself is 1-2mm long, oval in shape, and varies from green to pale yellow and pink and these can all occur in the same colony. The wingless peach–potato aphid is medium-sized and pale green to pink or almost black. The winged form is a similar size but has a black central abdominal patch on the upper surface with a pale underside.

Control Recommendations

The vast majority of M. persicae are resistant to pirimicarb and quite a high proportion are resistant to pyrethroid insecticides. There is no resistance to neonicotinoid insecticides. 

Natural enemies include parasitic wasps, ladybirds, predatory flies, spiders, ground beetles, rove beetles, lacewings and insect-pathogenic fungi. Providing habitats that encourage the presence of these can help control aphid numbers. They may not be effective in preventing virus transmission, as this can occur even at low aphid densities.

Early sowing of sugar beet can mean it is less likely to be affected, as older leaves are less palatable to the aphids.

Related Links

Aphid Monitoring Network 

Rothamsted Insect Survey 

 

Information and  from Rothamsted's Croprotect webpage supported by BBSRC NERC Sustainable Agriculture Research & Innovation Club

Related Organisations

Content below is from across the PEP community and is not necessarily endorsed by Stewards or by PEP

Connected Content

Integrated Pest Management highlights the growth of a healthy crop with the least possible disruption to agro-ecosystems and encourages natural pest control mechanisms. IPM is one of the tools for low-pesticide-input pest management, and IPM must now be implemented by all professional agchem users.

Pollen beetles (Meligethes aeneus) are prevalent during Spring and Summer months and are a significant pest of European oilseed rape.  

Sitobion avenae and Rhopalosiphum padi, otherwise known as the grain aphid and bird cherry-oat aphid, are the two main species of cereal aphids.

The Potato Cyst Nematode damages the roots causing poor growth, wilting during periods of water stress and early senescence.

Invertebrate pests cause problems in agriculture when the level of injury they cause reaches a point where the crop yield is significantly reduced.   

Potatoes are an important UK crop grown over 140,000 ha producing 5.5 Million tonnes

Write whatever you want here - this is the main section. You can add links, add pictures and embed videos. To paste text from elsewhere use CTRL+Shift+V to paste without formatting. Add videos by selecting 'Full HTML' below, copying the 'embed html' from the source page (eg Youtube), clicking 'Source' above and pasting where you want the video to appear.
You can upload an image here. It can be jpg, jpeg, gif or png format.
Upload requirements

You can upload a file here, such as a pdf report, or MS Office documents, Excel spreadsheet or Powerpoint Slides.

Upload requirements
Authors Order
Add Authors here - you can only add them if they already exist on PEP. Just start writing their name then select to add it. To add multiple authors click the 'Add another item' button below.

Please ensure that you have proof-read your content. Pages are not edited further once submitted and will go live immediately.

Configure the meta tags below.

Use tokens to avoid redundant meta data and search engine penalization. For example, a 'keyword' value of "example" will be shown on all content using this configuration, whereas using the [node:field_keywords] automatically inserts the "keywords" values from the current entity (node, term, etc).

Browse available tokens.

Simple meta tags.

The text to display in the title bar of a visitor's web browser when they view this page. This meta tag may also be used as the title of the page when a visitor bookmarks or favorites this page, or as the page title in a search engine result. It is common to append '[site:name]' to the end of this, so the site's name is automatically added. It is recommended that the title is no greater than 55 - 65 characters long, including spaces.
A brief and concise summary of the page's content, preferably 150 characters or less. Where as the description meta tag may be used by search engines to display a snippet about the page in search results, the abstract tag may be used to archive a summary about the page. This meta tag is no longer supported by major search engines.

Meta tags that might not be needed by many sites.

Geo-spatial information in 'latitude; longitude' format, e.g. '50.167958; -97.133185'; see Wikipedia for details.
Geo-spatial information in 'latitude, longitude' format, e.g. '50.167958, -97.133185'; see Wikipedia for details.
Robots
A comma-separated list of keywords about the page. This meta tag is used as an indicator in Google News.
Highlight standout journalism on the web, especially for breaking news; used as an indicator in Google News. Warning: Don't abuse it, to be used a maximum of 7 times per calendar week!
This meta tag communicates with Google. There are currently two directives supported: 'nositelinkssearchbox' to not to show the sitelinks search box, and 'notranslate' to ask Google not to offer a translation of the page. Both options may be added, just separate them with a comma. See meta tags that Google understands for further details.
Used to rate content for audience appropriateness. This tag has little known influence on search engine rankings, but can be used by browsers, browser extensions, and apps. The most common options are general, mature, restricted, 14 years, safe for kids. If you follow the RTA Documentation you should enter RTA-5042-1996-1400-1577-RTA
Indicate to search engines and other page scrapers whether or not links should be followed. See the W3C specifications for further details.
Tell search engines when to index the page again. Very few search engines support this tag, it is more useful to use an XML Sitemap file.
Control when the browser's internal cache of the current page should expire. The date must to be an RFC-1123-compliant date string that is represented in Greenwich Mean Time (GMT), e.g. 'Thu, 01 Sep 2016 00:12:56 GMT'. Set to '0' to stop the page being cached entirely.

The Open Graph meta tags are used to control how Facebook, Pinterest, LinkedIn and other social networking sites interpret the site's content.

The Facebook Sharing Debugger lets you preview how your content will look when it's shared to Facebook and debug any issues with your Open Graph tags.

The URL of an image which should represent the content. The image must be at least 200 x 200 pixels in size; 600 x 316 pixels is a recommended minimum size, and for best results use an image least 1200 x 630 pixels in size. Supports PNG, JPEG and GIF formats. Should not be used if og:image:url is used. Note: if multiple images are added many services (e.g. Facebook) will default to the largest image, not specifically the first one. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly.
The URL of an video which should represent the content. For best results use a source that is at least 1200 x 630 pixels in size, but at least 600 x 316 pixels is a recommended minimum. Object types supported include video.episode, video.movie, video.other, and video.tv_show. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
A alternative version of og:image and has exactly the same requirements; only one needs to be used. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly.
The secure URL (HTTPS) of an image which should represent the content. The image must be at least 200 x 200 pixels in size; 600 x 316 pixels is a recommended minimum size, and for best results use an image least 1200 x 630 pixels in size. Supports PNG, JPEG and GIF formats. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly. Any URLs which start with "http://" will be converted to "https://".
The type of image referenced above. Should be either 'image/gif' for a GIF image, 'image/jpeg' for a JPG/JPEG image, or 'image/png' for a PNG image. Note: there should be one value for each image, and having more than there are images may cause problems.
The date this content was last modified, with an optional time value. Needs to be in ISO 8601 format. Can be the same as the 'Article modification date' tag.
The date this content was last modified, with an optional time value. Needs to be in ISO 8601 format.
The date this content will expire, with an optional time value. Needs to be in ISO 8601 format.

A set of meta tags specially for controlling the summaries displayed when content is shared on Twitter.

Notes:
  • no other fields are required for a Summary card
  • Photo card requires the 'image' field
  • Media player card requires the 'title', 'description', 'media player URL', 'media player width', 'media player height' and 'image' fields,
  • Summary Card with Large Image card requires the 'Summary' field and the 'image' field,
  • Gallery Card requires all the 'Gallery Image' fields,
  • App Card requires the 'iPhone app ID' field, the 'iPad app ID' field and the 'Google Play app ID' field,
  • Product Card requires the 'description' field, the 'image' field, the 'Label 1' field, the 'Data 1' field, the 'Label 2' field and the 'Data 2' field.
A description that concisely summarizes the content of the page, as appropriate for presentation within a Tweet. Do not re-use the title text as the description, or use this field to describe the general services provided by the website. The string will be truncated, by Twitter, at the word to 200 characters.
By default Twitter tracks visitors when a tweet is embedded on a page using the official APIs. Setting this to 'on' will stop Twitter from tracking visitors.
The URL to a unique image representing the content of the page. Do not use a generic image such as your website logo, author photo, or other image that spans multiple pages. Images larger than 120x120px will be resized and cropped square based on longest dimension. Images smaller than 60x60px will not be shown. If the 'type' is set to Photo then the image must be at least 280x150px. This will be able to extract the URL from an image field if the field is configured properly.
The MIME type for the media contained in the stream URL, as defined by RFC 4337.