Typical lesions of L. maculans on oilseed rape.

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).

Damage and Economic Importance

Phoma leaf spot and canker is one of the most damaging diseases in oilseed rape. Whilst leaf spots have minimal impact on growth and yield, severe cankers in the stem can cause lodging and senescence, subsequently having a greater negative impact.

The disease is more of a threat in the South due to the pathogen favouring warmer climates. The risk is generally lower north of Lincolnshire, as cold weather slows down disease development, resulting in reduced canker severity by harvest and a delay of ascopores release the following autumn. However, with climate change pushing global temperatures higher, there is a growing risk of disease and spread to northern parts of the country. Tackling this disease effectively is key to protecting the country’s oilseed supply.

 

Appearance and lifecycle

For both pathogens, the disease cycle is similar. The disease survives over summer on crop debris, particularly the taproot and stem bases of old oilseed rape stubble. Ascospores from this are released and spread by the wind onto young, susceptible plants.

August/early September is when spotting on leaves can start. The moist conditions cause ascospores to germinate, with lesions appearing 7-15 days after infection (depending on temperature), starting on lower leaves then spreading upwards due to rain splash.

From the leaf spot lesions, the fungus spreads to the stem and down to the base where it incubates until early spring, when rapid fungal growth produces a visible stem rot or canker.

 

Image source: AHDB

 

Symptoms:

L. maculans (Phoma A)

  • Tawny coloured lesions with dark specs (pycnidia)*
  • Stem-base cankers

L. biglobosa (Phoma B)

  • Smaller and darker with fewer pycnidia*
  • Stem lesions develop on the upper stem
*Both types vary though according to interactions with cultivar and recent weather and some spots have a yellow halo and browning of leaf veins

 

Phoma A (L. maculans) lesion.

 

Management Recommendations

Key drivers of phoma risk:

  • Crop residues - the main source of spores
  • Region
  • Climate – warm and wet summer/autumn weather is more favourable for spore release, infection and development. Higher autumn/winter temperatures encourage fungal development on the plant
  • Small plants – more susceptible and disease moves faster
  • Varieties – different levels of susceptibility

Varietal Resistance:

Currently, no varieties are completely resistant, but some varieties escape infection due to resistant genes. These either prevent spores from infecting or reduce severity of disease when infection does occur.  

In 2022, commercially available varieties have resistance ratings of 4 to 9 (pages 29 & 30 of the AHDB recommended list). Although two varieties are rated as 9 (fully resistant to the disease), one of those, ‘Crossfit’ is a hybrid type that is only recommended for use on clubroot-affected land. The other is a hybrid type called ‘Tennyson’, which is recommended only for the East-West region of the UK. Six other varieties have a score of 8 and ten have a score of 7, so most current varieties are resistant or moderately resistant. This is due to recent success in resistance breeding against L. maculans, although not necessarily improving resistance to L. biglobosa.

Fungicides:

The best timing of fungicides is just prior to the first significant release of ascospores in the autumn (ideally before more than 10-20% of plants have phoma leaf spots). Close monitoring is key to getting this right. Catching infection in time is also important as fungicides have little effect once the stem has been infected. Timing of spore release varies due to the weather, but AHDB have a handy Phoma leaf spot forecast to help guide monitoring and timing of sprays in the autumn.

To adhere with an IPM strategy and reduce levels of resistance, more susceptible varieties should be prioritised and thresholds must be stuck to. For example, the AHDB recommends only spraying resistant varieties if >20% have phoma leaf spot. In colder weather, when leaf spotting occurs later in the autumn, spraying resistant varieties may even be omitted altogether. For susceptible varieties, a two-spray programme autumn fungicide regime is best if phoma leaf spotting occurs early in the autumn (before mid-October), while a single autumn spray is effective if phoma leaf spotting is late (appearing after mid-October). In all cases, monitoring is key as each situation and climate is different. Consider a second spray, if not already planned, if reinfection is seen.

Information on fungicide efficacy is available from the AHDB – see: page 35 onwards in this link.

 

Some of the text on this page comes from Rothamsted's Croprotect web platform at https://croprotect.com/diseases/septoria-leaf-blotch. This page is also supported by funding from The British Society for Plant Pathology (BSPP).

Related Organisations

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

Connected Content

Diseases infect susceptible plant hosts, where environmental conditions favor disease development. Infected crops achieve lower yields and the quality of the produce can also be affected.

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. 

Crop protection refers to practices and measures employed in agriculture to safeguard crops from both biotic (pests, diseases and weeds) and abiotic (environmental factors) stresses. They key goal of crop production is to maintain crop productivity, health and quality whilst minimising yield losses.

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.

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.

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.