Black-grass in a crop field

Grass weeds are a major challenge in UK agriculture and are often highly competitive in arable crops.

Some of the most common grass weeds in the UK include: Black-grass (Alopecurus myosuroides), Italian rye-grass (Lolium multiflorum), Brome (Bromus sp.), wild-oats (Avena sp.), Couch grass (Elytrigia repens), annual meadow grass (Poa annua) and Rat's-tail Fescue (Vulpia myuros).

You can find specific topic pages for black-grass and brome. See also related topics of: broad-leaved weeds, herbicides, herbicide resistance and integrated weed management

Key features of grass weeds

  • Grass weeds are monocots meaning that each seed initially contains one embryonic leaf (cotyledon)
  • Long and often narrow blades (leaves) with parallel veins
  • Stems usually hollow
  • Usually small inconspicuous spikelets (spikelets are the flowering unit of a grass)
  • Grass weeds are summer annuals, winter annuals or perennials

As many important cereal crops (oats, barley, wheat) are also grasses, it can make identification of grass weed problems challenging in the field. 'How to identify grass weeds in arable fields' on the AHDB website is a useful tool for in depth identification. 

 

Management options

There are a number of management options with the main ones being cultural and chemical (herbicide) control. 

Cultural control

  • A wide range of cultural control techniques can be employed specific to the targeted grass weed. This may include using optimal rotations, tillage and cultivations, suitable crop row spacing, using competitive crop varieties/cultivars and altering key timings (e.g drilling dates). 
  • The aim is to have optimal field conditions that make it more challenging for weed population establishment and growth.
  • For example delayed drilling of winter wheat is a commonly recommended to avoid the main black-grass flush.

Chemical control

  • A wide range of pre-emergence and post-emergence herbicides can be used on grass weeds - most commonly this includes ALS inhibitors (e.g sulfonylureas) (HRAC Group 2) and ACCase inhibitors (HRAC Group 1)
  • Some other pre-emergent options: HRAC Group 3 inhibition of microtubule assembly (Pendimethalin, trifluralin), HRAC Group 15 Inhibition of long-chain fatty acid synthesis (Flufenacet, tri-allate), 
  • Some other common post-emergent options: HRAC Group 9 inhibition of EPSP synthase (glyphosate)

 

Herbicide resistance

  • Widespread target site resistance and enhanced metabolism resistance to ALS and ACCase inhibiting herbicides has been reported across many grass weed species. Often seeing multiple resistance in populations and resistance is a growing problem.
  • This has increased the reliance on pre-emergent options and glyphosate - putting increasing pressure on weeds to become resistant to glyphosate. As such a widely relied upon herbicide, glyphosate resistance risk should be continually monitored. 
  • Genetic testing has elucidated some of the common mutations responsible for TSR in grasses. 
  • Regular monitoring and resistance testing is recommended along with integrating cultural control methods. 

 

Please attach any relevant projects or pages linked to grass weeds to to this topic page.

Related Organisations

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

Connected Content

Herbicide Resistance

Herbicide resistance is the inherited ability of a weed to survive a rate of herbicide which would be lethal to a member of the normal population. It can develop over time based on repeated selection pressure imposed on the weed. This selection pressure changes the population from susceptible to resistant. Herbicide resistance is becoming an increasing problem in UK agriculture, in both grass weeds and broad-leaf weeds. See also the general topic on herbicides.

Black-grass

Black-grass (Alopecurus myosuroides) is a major weed in winter sown cereals.

Bioherbicide

This Topic doesn't yet have a Stewarded summary, but connected groups, content and organisations show below. Click the 'Ask to Join' button if you would like to be a Steward for this Topic and provide a summary of current knowledge and recommend useful resources, organisations, networks and projects. "Like" this Topic if you would like to see it prioritised for providing a wikipedia style summary.

European Weed Research Society Workshop - Cambridge May 2023

'Integrated Weed Management (IWM) systems in the agroecology context; new challenges.' NIAB, Cambridge, UK 24th - 26th of May 2023

Wheat

Wheat is the most widly grown crop in the UK. Nationally yields average around 8 t/ha/

Cereals

Herbicides

Herbicides are substances (usually chemical) used to control weeds in a variety of situations including agriculture, horticulture and managed landscapes. Herbicides are classified according to their mode of action (MOA) - this is the precise biochemical mechanism in which the herbicide targets and kills the weed. The 'active ingredient' of the herbicide is the specific herbicidal compound that has the phytotoxic effect and this is formulated with a variety of other ingredients (including other active substances, surfactants, buffers, adjuvants e.t.c) to make a final product which is given a trade name by the herbicide manufacturer. With any herbicide product you will find an associated product label which explains how to use the product safely and legally. This page provides an overview of herbicides including how they are classified and used. Please link any pages or projects relating to herbicide use to this topic page.  Some widely used herbicides (e.g glyphosate) also have their own topic page. Other related topics on FarmPEP include herbicide resistance,  bioherbicides, broad leaved weeds and grass weeds.  

Broad-Leaved Weeds

Broad-leaved weeds are a varied group of weeds that can grow and cause significant problems in arable fields in the UK. Some of the most common broad-leaved weeds in the UK include: Common Chickweed (Stellaria media) , Scentless Mayweed (Tripleurospermum inodorum), Common poppy (Papaver rhoeas), Charlock (Sinapis arvensis L.), Fat-hen (Chenopodium album L.), Common groundsel (Senecio vulgaris), Docks (Rumex spp) and Creeping thistle (Cirsium arvense). See also related topics of: grass-weeds, herbicides, herbicide resistance and integrated weed management.

Glyphosate

The herbicide glyphosate was first registered in 1974 under the original trade name RoundUp (Monsanto) and has since become one of the most commonly used herbicides globally. It is a non-selective, post-emergent herbicide with a wide range of uses including arable, forestry, and horticulture.

Integrated Weed Management (IWM)

IWM involves using numerous weed control methods to try and manage a weed problem sustainably. Whilst herbicides can still be used as part of an IWM approach, a major aim is to reduce reliance on them by also incorporating methods including, cultural, mechanical, biological, thermal and genetic control. A combination of such approaches can allow for optimal control of a specific weed problem. Related topics on FarmPEP include herbicides and herbicide resistance. You can also view the topic pages on grass weeds and broad-leaved weeds which provide examples of suitable control methods.

Agricultural modelling for weed management

Crop modelling is a useful tool in agriculture to improve our understanding how a crop grows in interaction with all external factors, including environmental interactions and the crop management practices in place. The idea is that by modelling cropping system factors as a mathematical representation, and incorporating real past data to 'calibrate' the model,  you can then simulate various scenarios and predict the impacts of certain changes on crop growth. One example of this would be a simulation of predicted environmental conditions under various climate scenarios to predict the impacts of climate change on crop growth and yields. Whilst models are oversimplifications of reality and can never capture all the complexity of agricultural systems, modelling has been a vital tool underpinning key agricultural developments and models are constantly being developed to be more dynamic, complex and sensitive. One particular application of modelling is in weed control. This page highlights the application of modelling in weed management and introduces a case study of a weed model from a DEFRA report.       

Developing strategies for reducing the risk from herbicide-resistant wild oats

Wild-oats are a highly competitive grass-weed in the UK of which there are two important species: common wild-oats (Avena fatua) and winter wild-oats (Avena sterilis ssp. ludoviciana). Failure to control wild oats in arable fields can lead to high penalties to yield, seed crop contamination, income loss for farmers and reduced competitiveness of UK agriculture. Whilst herbicide resistance selection has been slower in wild-oats compared to other grass weeds such as Black-grass (Alopecurus myosuroides), it is still a growing problem and since this report was published in 2001, resistance has been reported across hundreds of farms across many UK counties.  Continuing development of herbicide resistance in wild-oats will limit pesticide choice and possibly lead to a higher dependence on environmentally 'risky' herbicides that are more likely to reach water. The objective of this project was to conduct and collate research on the characterisation of herbicide resistance in wild-oats with the aim of informing strategies for the prevention, containment and control of herbicide resistant populations. Links to the full project are provided at the bottom of the page.

Wild oats Identification

Dr Stephen Moss has kindly given permission for his useful Wild-oat identification posters to be shared on FarmPEP. 

Harvest Weed Seed Control

Harvest Weed Seed Control (HWSC) A project to explore harvest weed seed control (HWSC) under UK conditions as a method to control grassweeds and reduce the dependence on chemical control, particularly glyphosate.

The AHDB encyclopaedia of arable weeds

This guidance provides an easy reference to the major broad-leaved and grass weeds in the UK, including how to identify and manage them based on an understanding of their biology.

The rise of herbicide resistance in black-grass – a 35-year story

A new paper published by ADAS summarises evolving black-grass herbicide resistance over the last 35 years, including the effectiveness of the dwindling actives left, and the vital role of routine resistance testing.

Getting to The Roots of Black-Grass's Waterlogging Tolerance

Root structures and genetics give the weed an advantage over wheat and explain field patches.  

Stow Longa Technology Centre Blackgrass Trials Tour

Monday 10th June - AM session only Monday 1st July - AM and PM session

NCSPulse PEP
BCPC weeds knowledge bank

This site offers free access to Proceedings from over 50 years of BCPC Conferences and Symposia dating all the way back to 1954; over 100 Technical Reports from the Weed Research Organization; and the WRO Annual Reports which include reports from each research section of the WRO.

Across the Straits: A Unified Approach to Tackle Grassweed Herbicide Resistance

The Straits committee is a voluntary partnership between Kent County Council and neighbouring local authorities in France (Département du Pas-de-Calais, Département du Nord), Belgium (Provincie Oost-Vlaanderen, Provincie West-Vlaanderen) and the Netherlands (Provincie Zuid-Holland, Provincie Zeeland). This partnership helps to support organisations on either side of the channel to work together where it is useful to do so.  As part of the The Straits Committee Small Project Initiative, ADAS have teamed up with agricultural organisations in France (Chambre d'agriculture), Belgium (Inagro & UGent/HOGENT) and the Netherlands (AIKC Rusthoeve) following discussions that grassweeds and herbicide resistance were common problems in all of these regions. An escalating issue across arable farming in  Europe is herbicide resistance. This is defined as 'the inherited ability of a weed to survive a rate of herbicide that would normally kill it’. It impacts crop yield, increases costs for farmers, and limits crop rotation options. In particular, Black-grass (Alopecurus myosuroides) and other grassweeds are highly problematic in the South-East UK and cereal growing coastal regions of Belgium, France, and the Netherlands. The project aims to Assess resistance to determine the extent of the problem in the Straits regions Foster ongoing collaboration among agricultural organisations working in these areas to help support growers Provide joint and cohesive guidelines to help growers manage resistance effectively, reduce ineffective use of herbicides and promote best use of non-chemical control as part of an integrated weed management (IWM) approach. Updates will be made to this page as the project progresses, including survey links and results, guidelines, advice sheets, fact-files and more, so please do follow, like and comment on this page to keep updated!    This is the Grassweeds project, co-funded under the Straits Committee small project initiative by Kent County Council (UK), Provincie West-Vlaanderen (BE), Provincie-Oost-Vlaanderen (BE), Provincie Zeeland (NL), & Département du Pas-de-Calais (FR).

About text formats
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
File

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.
Basic tags

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

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.
Sets a cookie on the visitor's browser. Can be in either NAME=VALUE format, or a more verbose format including the path and expiration date; see the link for full details on the syntax.
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.
Open Graph

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.
Links an article to an author's Facebook profile, should be either URLs to the author's profile page or their Facebook profile IDs. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The date this content was published on, with an optional time value. Needs to be in ISO 8601 format.
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.
Twitter Cards

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.