z-logo
open-access-imgOpen Access
A comparison of grass silages harvested at first, second and third cut on feed intake and milk production of dairy cows
Author(s) -
Auvo Sairanen,
Sari Kajava,
Annu Palmio,
Marketta Rinne
Publication year - 2021
Publication title -
agricultural and food science
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.347
H-Index - 35
eISSN - 1795-1895
pISSN - 1459-6067
DOI - 10.23986/afsci.101833
Subject(s) - silage , dry matter , milk production , zoology , agronomy , lactation , biology , mathematics , pregnancy , genetics
The objective of this study was to compare the milk production potential of first, second and third harvest of grass silage from the same sward in Northern latitudes. Three change-over design dairy cow feeding experiments were conducted during different years which differed markedly in weather conditions. The silages were supplemented with a cereal based The objective of this study was to compare the milk production potential of subsequent first, second and third cuts of grass silage from the same sward in Northern latitudes. Three change-over design dairy cow feeding experiments were conducted during different years which differed markedly in weather conditions. The silages were supplemented with a cereal based concentrate (average concentrate proportion 431 g kg-1 diet dry matter). Feed intake and milk production was highest with first-cut and lowest with third-cut silage. The energy corrected milk yields averaged over three experiments were 35.0, 33.2 and 31.9 kg d-1 for first, second and third harvest silages, respectively. Respective dry matter intakes were 23.1, 21.9 and 20.7 kg d-1. Compared to analysed feed values, the average intake of third-cut silages was lower than expected. Due to the high risk of low intake potential of third-cut silages, they are not recommended for cows in early lactation if there are other silages available.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here