49 CFR § 1250.3

49 CFR · Transportation

§ 1250.3 — Chicago terminal reporting.

49 CFR § 1250.3

TitleTitle 49: Transportation PartPart 1250: Railroad Performance Data Reporting

SourceeCFR (current through Apr 10, 2026)

This text of 49 C.F.R. § 1250.3 (Chicago terminal reporting.) is published on Counsel Stack Legal Research, covering United States primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook

49 C.F.R. § 1250.3 (2026).

Text

§ 1250.3 Chicago terminal reporting.

(a)Each Class I railroad operating at the Chicago gateway must jointly report the following performance data on a weekly basis for the reporting period, as defined in § 1250.1(a). The reports required under this section may be submitted by the Association of American Railroads (AAR).

(1)Average daily car volume in the following Chicago area yards: Barr, Bensenville, Blue Island, Calumet, Cicero, Clearing, Corwith, Gibson, Kirk, Markham, and Proviso for the reporting week; and

(2)Average daily number of trains held for delivery to Chicago sorted by receiving carrier for the reporting week. The average daily number should be derived by taking a same time snapshot each day of the reporting week, capturing the trains held for each railroad at that time

Free access — add to your briefcase to read the full text and ask questions with AI

§ 1250.3 Chicago terminal reporting.

(a) Each Class I railroad operating at the Chicago gateway must jointly report the following performance data on a weekly basis for the reporting period, as defined in § 1250.1(a). The reports required under this section may be submitted by the Association of American Railroads (AAR).

(1) Average daily car volume in the following Chicago area yards: Barr, Bensenville, Blue Island, Calumet, Cicero, Clearing, Corwith, Gibson, Kirk, Markham, and Proviso for the reporting week; and

(2) Average daily number of trains held for delivery to Chicago sorted by receiving carrier for the reporting week. The average daily number should be derived by taking a same time snapshot each day of the reporting week, capturing the trains held for each railroad at that time, and then adding those snapshots together and dividing by the days in the reporting week.

(i) For purposes of this request, “held for delivery” refers to a train staged by the delivering railroad short of its scheduled arrival at the Chicago gateway at the request of the receiving railroad, and that has missed its scheduled window for arrival.

(ii) If Chicago terminal yards not identified in § 1250.2(b)(1) are included in the Chicago Transportation Coordination Office's (CTCO) assessment of the fluidity of the gateway for purposes of implementing service contingency measures, then the data requested in § 1250.2(b)(1) shall also be reported for those yards.

(b) The Class I railroad members of the CTCO (or one Class I railroad member of the CTCO designated to file on behalf of all Class I railroad members, or AAR) must:

(1) File a written notice with the Board when the CTCO changes its operating Alert Level status, within one business day of that change in status.

(2) If the CTCO revises its protocol of service contingency measures, file with the Board a detailed explanation of the new protocol, including both triggers and countermeasures, within seven days of its adoption.

(c) Reports under paragraph (b) of this section shall be reported to the Director of the Office of Public Assistance, Governmental Affairs and Compliance (OPAGAC) via the method and in the form prescribed by OPAGAC.