cfr_sections
Data license: Public Domain (U.S. Government data) · Data source: Federal Register API & Regulations.gov API
4 rows where agency = "STB" and part_number = 1250 sorted by section_id
This data as json, CSV (advanced)
Suggested facets: amendment_citations
| section_id ▼ | title_number | title_name | chapter | subchapter | part_number | part_name | subpart | subpart_name | section_number | section_heading | agency | authority | source_citation | amendment_citations | full_text |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 49:49:9.1.1.1.16.0.9.1 | 49 | Transportation | X | C | 1250 | PART 1250—RAILROAD PERFORMANCE DATA REPORTING | § 1250.1 General. | STB | (a) The reporting period covers: (1) For § 1250.2(a)(1)-(9), 12:01 a.m. Saturday-11:59 p.m. Friday; (2) For § 1250.2(a)(10), the previous calendar month; (3) For § 1250.2(a)(11), 12:01 a.m. Sunday-11:59 p.m. Saturday; (4) For § 1250.3(a)(1)-(2), 12:01 a.m. Saturday-11:59 p.m. Friday. (b) The data required under § 1250.2 and § 1250.3(a) must be reported to the Board via the method and in the form prescribed by the Board's Office of Public Assistance, Governmental Affairs, and Compliance (OPAGAC) by 5 p.m. Eastern Time on Wednesday of each week. In the event that a particular Wednesday is a Federal holiday or falls on a day when STB offices are closed for any other reason, then the data should be reported on the next business day when the offices are open. (c) Each reporting railroad shall provide an explanation of its methodology for deriving the data with its initial filing and an update if and when that methodology changes. This explanation should include the unit train definition that the railroad will use in its data reporting, which shall reflect its assignment of train codes in accordance with its normal business practices. If and when a railroad changes its definition of unit train it shall notify the Board of the change at the time it goes into effect in the form prescribed by OPAGAC. (d) Unless otherwise provided, the performance data, Chicago data and alert levels, narrative infrastructure reporting, and any methodologies or explanations of data collection reported to the Board under this part will be publicly available and posted on the Board's Web site. | ||||||
| 49:49:9.1.1.1.16.0.9.2 | 49 | Transportation | X | C | 1250 | PART 1250—RAILROAD PERFORMANCE DATA REPORTING | § 1250.2 Railroad performance data elements. | STB | [81 FR 87484, Dec. 5, 2016, as amended at 82 FR 13402, Mar. 13, 2017; 85 FR 30851, May 21, 2020] | (a) Each Class I railroad must report the performance data elements in paragraphs (a)(1)-(9) and (11) of this section on a weekly basis, and the data elements in paragraph (a)(10) on a monthly basis, for the reporting period, as defined in § 1250.1(a). However, with regard to data elements in paragraph (a)(7) and (8), Kansas City Southern Railway Company is not required to report information by state, but instead shall report system-wide data. (1) System-average train speed for the overall system and for the following train types for the reporting week. (Train speed should be measured for line-haul movements between terminals. The average speed for each train type should be calculated by dividing total train-miles by total hours operated.) (i) Intermodal. (ii) Grain unit. (iii) Coal unit. (iv) Automotive unit. (v) Crude oil unit. (vi) Ethanol unit. (vii) Manifest. (viii) System. (2) Weekly average terminal dwell time, measured in hours, excluding cars on run-through trains ( i.e., cars that arrive at, and depart from, a terminal on the same through train), for the carrier's system and its 10 largest terminals in terms of railcars processed. (Terminal dwell is the average time a car resides at a specified terminal location expressed in hours.) (3) Weekly average cars on line by the following car types for the reporting week. (Each railroad shall average its daily on-line inventory of freight cars. Articulated cars should be counted as a single unit. Cars on private tracks ( e.g., at a customer's facility) should be counted on the last railroad on which they were located. Maintenance-of-way cars and other cars in railroad service are to be excluded.) (i) Box. (ii) Covered hopper. (iii) Gondola. (iv) Intermodal. (v) Multilevel (Automotive). (vi) Open hopper. (vii) Tank. (viii) Other. (ix) Total. (4) Weekly average dwell time at origin for the following train types: Grain unit, coal unit, automotive unit, crude oil unit, ethanol unit, and all other unit trains. (For the purposes of this data el… | |||||
| 49:49:9.1.1.1.16.0.9.3 | 49 | Transportation | X | C | 1250 | PART 1250—RAILROAD PERFORMANCE DATA REPORTING | § 1250.3 Chicago terminal reporting. | STB | (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 th… | ||||||
| 49:49:9.1.1.1.16.0.9.4 | 49 | Transportation | X | C | 1250 | PART 1250—RAILROAD PERFORMANCE DATA REPORTING | § 1250.4 Rail infrastructure projects reporting. | STB | (a) Class I railroads shall submit annually a narrative report of significant rail infrastructure projects that will be commenced during the current calendar year, and a six-month update on those projects. The reports should briefly describe each project, its purpose, location (state/counties), and projected date of completion. (b) A “significant rail infrastructure project” is defined as a project with anticipated expenditures of $75 million or more over the life of the project. (c) The narrative report should be submitted no later than March 1 of each calendar year and the update no later than September 1 of each calendar year via email to the Board's Office of Public Assistance, Governmental Affairs and Compliance (OPAGAC) via the method and in the form prescribed by OPAGAC. In the event that March 1 or September 1 is a Federal holiday, weekend, or falls on a day when STB offices are closed for any other reason, then the data should be reported on the next business day when the offices are open. |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE cfr_sections (
section_id TEXT PRIMARY KEY,
title_number INTEGER,
title_name TEXT,
chapter TEXT,
subchapter TEXT,
part_number TEXT,
part_name TEXT,
subpart TEXT,
subpart_name TEXT,
section_number TEXT,
section_heading TEXT,
agency TEXT,
authority TEXT,
source_citation TEXT,
amendment_citations TEXT,
full_text TEXT
);
CREATE INDEX idx_cfr_title ON cfr_sections(title_number);
CREATE INDEX idx_cfr_part ON cfr_sections(part_number);
CREATE INDEX idx_cfr_agency ON cfr_sections(agency);