Finance DocketBefore the Surface Transportation Board

FD 34868

Docket Yard · docketyard.org/d/FD-34868 · entries shown: all, newest first

COLUMBUS AND GREENVILLE RAILWAY COMPANY-TRACKAGE RIGHTS EXEMPTION-KANSAS CITY SOUTHERN RAILWAY COMPANY

Caption from the Board’s record.

3 filings, 2 decisions and 0 environmental comments observed here; last checked 10 Oct 2026, 21:36 UTC; last new entry 26 Aug 2026, 15:29 UTC.

Cite View on stb.gov

Entries

30 Nov 2007 (printed as 11/30/2007)

Misc.

220852Miscellaneous

Columbus And Greenville Railway Company
served 13 Feb 2007 (printed as 2/13/2007)

Decision

37706Secretary

DECISION GRANTED COLUMBUS AND GREENVILLE RAILWAY COMPANY'S MOTION FOR A PROTECTIVE ORDER.
served 26 Jan 2007 (printed as 1/26/2007)

Decision

37705Director Of Proceedings

PROVIDED NOTICE THAT KANSAS CITY SOUTHERN RAILWAY COMPANY AGREED TO GRANT COLUMBUS AND GREENVILLE RAILWAY COMPANY NONEXCLUSIVE OVERHEAD TRACKAGE RIGHTS IN COLUMBUS, MS.
12 Jan 2007 (printed as 1/12/2007)

Motion

218458Motion For Protective Order

Columbus And Greenville Railway Company

in the protective-order register
12 Jan 2007 (printed as 1/12/2007)

Notice

218457Notice Of Exemption

Columbus And Greenville Railway Company

Parties on record

Who filed, from the Board’s “Filed For” cells, resolved by rule (how). Nothing here says what anyone argued. Click a name to filter; “page” opens the party’s record.

page

Follow this docket

Or: Atom feed · webhook

Send new entries to a webhook

Cite this docket

STB Finance Docket No. 34868

Accessed 10 Oct 2026; bulk archive docketyard-2026-10-01.sqlite.gz.

Permanent address
docketyard.org/d/FD-34868
As data: JSON · bulk

About this record

What an FD proceeding is — what is asked for, what the Board can do, what happens next. Every entry links to the Board’s own file. Dates are quoted from the record, never computed. Captions and summaries appear as the Board prints them. Source: STB record search.

Corrections

Does something on this sheet not match the Board's record? Every entry carries its source, so a correction propagates everywhere the entry appears. How to report one.