Light leaf spot lesions on oilseed rape

Light leaf spot (LLS) is a disease of oilseed rape and some vegetable brassicas, caused by the fungus, Pyrenopeziza brassicae.

This major foliar pathogen is notoriously difficult to identify with an airborne polycyclic lifecycle – capable of several infection cycles a season, making it hard to control as reinfection is constantly occurring. Severity can be suppressed through monitoring, cultural controls, and targeted fungicide applications.

Damage and Economic Importance

The disease typically reduces yield by a third of the incidence (90% plants affected at early stem extension causes 30% yield loss) and on average, UK yield losses equate to £110-160M per year. The disease has increased in southern Britain (AHDB east and west regions) in recent years due to favourable weather, changes in fungicide use and cultivars grown. For disease-prone regions it is recommended to use relatively resistant varieties (and see fungicide information below).

Appearance and Lifecycle

Typical symptoms:

Visible symptoms appear after a long period of symptomless growth, as speckles of white spore pustules on leaves, stems and pods. The spores are only visible after a period of dry weather. As infections mature, the fungus can also cause bleaching and stunting of leaves in affected positions causing leaf distortion and by spreading to the growing point, can cause stunting of the whole plant.

LLS lesion and spores on OSR leaf.
LLS spores on the underside of OSR leaf.

    

     

 

 

 

 

 

 

 

LLS lesion on OSR stem.

 

Lifecycle:

  1. The fungus survives over summer on crop debris, volunteers and some weeds, from which it can spread short distances (less than a few metres) by rain-splashed spores called conidia. It can also develop structures called apothecia, which release wind-dispersed sexual spores (ascospores) that can blow long distances but mostly affect crops within 300m of the debris.
  2. After initial infections during the autumn, rain-splashed spores from infected plants cause disease intensification. Because of this dispersal method, new infections develop around initial primary infection "foci" and the disease appears to be patchy within the field.
  3. A second phase of wind-dispersed ascospores often occurs in the spring to spread the disease again to new crops and higher positions in the pod canopy, which can lead to early pod senescence and pod-shatter.

The amount of stem and pod infection determines the amount of inoculum for winter oilseed rape crops in the next season and along with weather records, is the basis for a forecast of LLS severity the following season – see Light leaf spot forecast | AHDB. This forecast indicates the predicted disease severity in different parts of the country and a crop specific interactive forecast allows growers to input various options to assess the effect of cultivar choice, sowing date and fungicide regime.

 

Management Recommendations:

Key drivers of risk:

  • High levels of infection in the previous summer
  • Presence of infected residues
  • Close proximity to oilseed rape fields
  • Early sowing date
  • Low resistance varieties
  • Using home saved seed from heavily infected crops

Fungicide Choice

Information on fungicide efficacy is available from the AHDB. It is important to apply fungicides before the disease becomes severe. Due to a long symptomless phase of infection, it is a good idea to check reports of disease monitoring and disease forecasts (above). For fungicide efficacy against LLS – see Fungicide performance update and FRAG UK Fungicide resistance management in OSR.

Most currently recommended products contain azoles, mixed or alternated with other modes of action such as SDHIs or strobilurins. These are best applied ahead of significant disease development. A mid-autumn application is suggested in regions prone to high levels of disease and this is often before visible symptoms occur, although backward crops may suffer a yield reduction if autumn-applied fungicides have a growth regulatory affect. Fungicides give little control on crops that are already severely infected. In addition, a spray at the start of stem extension is recommended if the disease incidence is over 15%.

The disease is hard to see following wet weather, except for symptoms of leaf bleaching and distortion. Disease assessment can be improved by taking about 20 low-mid-canopy leaves, shake most water off and incubate them in a closed plastic bag in a cool room (ideally 5-10°C) for 3-4 days before looking at them. Any sporulation should be clear on the leaves if the disease is present.

Varietal Resistance

Having a variety with a higher LLS rating can help reduce levels of infection within the crop. For 2022-23, the current resistance scores vary from 5 - 8 in the east-west region or 6 - 8 in the north region, so none are completely resistant. For information on current cultivar resistance, please see the AHDB Recommended List, scroll past the wheat, barley and oats section to the winter oilseed rape section.

Cultural Control

As OSR volunteers from the previous season’s crop debris, or brassica cover crops can act as a reservoir of the disease, having a good crop rotation that maximises the separation of new OSR fields from old (at least 300 metres) can help to reduce epidemics. OSR stubbles on farm should be cultivated/ploughed to bury any infected crop debris.

Drill later if possible, particularly in higher-risk situations as this reduces the chance of crop emergence coinciding with the first release of spores from infected crop debris.

Monitoring

A major challenge with LLS is that it is notoriously difficult to identify, particularly in the early stages of infection when symptoms are minimal or not visible at (see photo examples below). Regular monitoring and crop walking is key to knowing when and in what capacity to respond to infection. There are several tools that can now be used to aid identification:

Bayer SpotCheck is a fantastic service in collaboration with ADAS, providing growers and agronomists with free conclusive diagnosis of disease in oilseed rape crops, with particular focus on light leaf spot. A sample of 30-35 leaves is incubated for 48 hours and results returned within 7 working days. More information can be found on their website here.

SwiftDetect is a rapid testing service that can determine LLS presence before symptoms are visible, claiming a turnaround time of 1 business day. They also test for other diseases in wheat and barley. Visit the SwiftDetect page on FarmPEP for further information (see related organisations below).

Multispectral imaging is another precision technology that is being developed that uses image analysis of leaves to detect the disease in early stages. This could allow photos to be taken of a crop canopy 

Using these services and development of precision technologies to aid crop monitoring can help the farmer/grower to effectively plan targeted sprays. This will not only reduce overall costs but increase the efficacy of chemical applications and reduce crop protection use, helping to safeguard against fungicide resistance. In a future where integrated pest management (IPM) is essential, this technology will help farmers to justify fungicide applications. The technology can also benefit plant breeders seeking to develop new resistant varieties.

 

Related Links:

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.

Oilseed Rape is the most widely grown break crop in the UK. The seed is crushed to produce vegetable oil and the remaining rapeseed meal is a high protein animal feed. 

Oilseed rape diseases can be caused by a variety of factors, including fungal, bacterial or viral infections, pests and insects, and environmental stress.

Fungicides are a type of agrochemical used specifically to kill fungal pathogens or inhibit the growth of fungi and the spores that they produce. They full under the umbrella of plant protection products (PPPs), also referred to as pesticides, along with other agrochemicals such as herbicides and insecticides that target weeds and insect pests respectively.  Prior to the development of fungicides, there are many historic cases of pathogenic fungi devastating crop yields - one of the most famous being the Irish Potato famine of 1845-52. This was caused by the potato late blight fungal pathogen Phytophthora infestans which today still causes massive losses to agriculture globally, although management by fungicides is now an important component of control.  A wide variety of fungicides exist with various modes of action (MOAs) to effectively control many fungal diseases including mildews, rusts, blights and leaf spots. A threat to modern agriculture is the development and spread of resistance to such fungicides amongst fungal populations.

Phoma leaf spot and stem canker is one of the most damaging diseases in oilseed rape, caused by two closely related fungal pathogens: Leptosphaeria maculans (Plenodomus lingam) and L. biglobosa (P. biglobosus).

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.