NCCC_old167: Corn Breeding Research

(Multistate Research Coordinating Committee and Information Exchange Group)

Status: Inactive/Terminating

SAES-422 Reports

Annual/Termination Reports:

[07/03/2013] [07/03/2013] [04/21/2015] [09/09/2015] [01/19/2017]

Date of Annual Report: 07/03/2013

Report Information

Annual Meeting Dates: 03/14/2012 - 03/15/2012
Period the Report Covers: 10/01/2010 - 09/01/2011

Participants

Brief Summary of Minutes

Please see attached "Copy of Minutes" file below for NCCC167's 2012 meeting minutes.

Accomplishments

Publications

Impact Statements

Back to top

Date of Annual Report: 07/03/2013

Report Information

Annual Meeting Dates: 03/13/2013 - 03/14/2013
Period the Report Covers: 10/01/2011 - 09/01/2012

Participants

Brief Summary of Minutes

Please see attached "Copy of Minutes" file for NCCC167's 2013 meeting minutes.

Accomplishments

Publications

Impact Statements

Back to top

Date of Annual Report: 04/21/2015

Report Information

Annual Meeting Dates: 12/08/2013 - 12/11/2013
Period the Report Covers: 12/01/2012 - 12/01/2013

Participants

Brief Summary of Minutes

See attached "Copy of Minutes" file for NCCC167's 2013 annual report.

Accomplishments

Publications

Impact Statements

Back to top

Date of Annual Report: 09/09/2015

Report Information

Annual Meeting Dates: 03/11/2015 - 03/12/2015
Period the Report Covers: 03/01/2014 - 02/01/2015

Participants

Brief Summary of Minutes

Please see attached "Copy of Minutes" file for NCCC197's 2014/2015 annual report.

Accomplishments

Publications

Impact Statements

Back to top

Date of Annual Report: 01/19/2017

Report Information

Annual Meeting Dates: 03/16/2016 - 03/17/2016
Period the Report Covers: 04/01/2015 - 03/01/2016

Participants

Brief Summary of Minutes

Please see attached meeting minutes file.

Accomplishments

Publications

Impact Statements

Back to top
Log Out ?

Are you sure you want to log out?

Press No if you want to continue work. Press Yes to logout current user.

Report a Bug
Report a Bug

Describe your bug clearly, including the steps you used to create it.