cbqer MidlandMike Murphy Siding I have to believe there are some details missing from the story. Didn't D&I have rights to run from Sioux City to Elk Point on the former state owned trackage and from there to Sioux Falls on BNSF owned trackage? ... I would guess that the trackage rights don't include passengers. Yes, they have trackage rights. How else would they bring 4-6 loads of rock weekly. Dick
MidlandMike Murphy Siding I have to believe there are some details missing from the story. Didn't D&I have rights to run from Sioux City to Elk Point on the former state owned trackage and from there to Sioux Falls on BNSF owned trackage? ... I would guess that the trackage rights don't include passengers.
Murphy Siding I have to believe there are some details missing from the story. Didn't D&I have rights to run from Sioux City to Elk Point on the former state owned trackage and from there to Sioux Falls on BNSF owned trackage? ...
I have to believe there are some details missing from the story. Didn't D&I have rights to run from Sioux City to Elk Point on the former state owned trackage and from there to Sioux Falls on BNSF owned trackage?
I would guess that the trackage rights don't include passengers.
Yes, they have trackage rights. How else would they bring 4-6 loads of rock weekly.
Dick
The question is if their rights include passengers. You are going to have to show me the wording in their documents that allow passengers.
When I wrote the post above, I confused Beresford with Canton. It is Canton to Elk Point that is still state owned. There is a branch of that track that starts at Hawarden and runs over to Beresford -- also state owned.
Dakguy201 Murphy Siding I have to believe there are some details missing from the story. Didn't D&I have rights to run from Sioux City to Elk Point on the former state owned trackage and from there to Sioux Falls on BNSF owned trackage? I'm guessing there were some communication problems involved and BNSF is just getting the blame for someone's poor planning. I doubt that BNSF made a last minute decision to ask for proof of liability inusrance. This line runs a half mile from my office and a half mile from my home. Given a multiple choice test, I think I could pick out the D&I trains horns. There are actually various owners of that line. From Sioux Falls to Beresford it is BNSF. From there to Elk Point (including the portion in Iowa) it is SD state owned but operated by the D&I. At Elk Point it joins the BNSF to Sioux City. All of it plus a great deal more was acquired by the state in the Milwaukee bankruptcy. As South Dakota sold pieces of the Milwaukee to BNSF, it attempted to insure at least one other operator had access to both the line and customers along it. In most cases that is the D&I although I don't think they actively utilize everything for which they have rights. A couple of years ago, there was a proposal to add a connecting track to the northwest quadrant of the place in Sioux City where this line crosses the UP. That would have the effect of allowing the D&I to deliver its trains, in particular the rock trains, to the UP yard for servicing UP customers. I believe that idea is on hold or perhaps died by BNSF's hands.
Murphy Siding I have to believe there are some details missing from the story. Didn't D&I have rights to run from Sioux City to Elk Point on the former state owned trackage and from there to Sioux Falls on BNSF owned trackage? I'm guessing there were some communication problems involved and BNSF is just getting the blame for someone's poor planning. I doubt that BNSF made a last minute decision to ask for proof of liability inusrance. This line runs a half mile from my office and a half mile from my home. Given a multiple choice test, I think I could pick out the D&I trains horns.
I have to believe there are some details missing from the story. Didn't D&I have rights to run from Sioux City to Elk Point on the former state owned trackage and from there to Sioux Falls on BNSF owned trackage? I'm guessing there were some communication problems involved and BNSF is just getting the blame for someone's poor planning. I doubt that BNSF made a last minute decision to ask for proof of liability inusrance. This line runs a half mile from my office and a half mile from my home. Given a multiple choice test, I think I could pick out the D&I trains horns.
There are actually various owners of that line. From Sioux Falls to Beresford it is BNSF. From there to Elk Point (including the portion in Iowa) it is SD state owned but operated by the D&I. At Elk Point it joins the BNSF to Sioux City. All of it plus a great deal more was acquired by the state in the Milwaukee bankruptcy.
As South Dakota sold pieces of the Milwaukee to BNSF, it attempted to insure at least one other operator had access to both the line and customers along it. In most cases that is the D&I although I don't think they actively utilize everything for which they have rights.
A couple of years ago, there was a proposal to add a connecting track to the northwest quadrant of the place in Sioux City where this line crosses the UP. That would have the effect of allowing the D&I to deliver its trains, in particular the rock trains, to the UP yard for servicing UP customers. I believe that idea is on hold or perhaps died by BNSF's hands.
Thanks to Chris / CopCarSS for my avatar.
The BNSF told us that week.
PNWRMNM Is there a point to this post? Either the BNSF thought they were dealing with honorable people, obviously they were not, or they forgot to tell the Dispatchers. This is the kind of behavior that rightly gives railfans a bad name and the carriers every encouragement to not deal with them ever, at all at all, because the carriers do not trust them. If something had happened who do you think the plaintiff's lawyers would go after? A judgement proof group of foamers or deep pockets BNSF. Yes there is a point to the post. I was simply telling a story. I am sorry you didn't see it that way. Dick Donaway
Is there a point to this post?
Either the BNSF thought they were dealing with honorable people, obviously they were not, or they forgot to tell the Dispatchers. This is the kind of behavior that rightly gives railfans a bad name and the carriers every encouragement to not deal with them ever, at all at all, because the carriers do not trust them.
If something had happened who do you think the plaintiff's lawyers would go after? A judgement proof group of foamers or deep pockets BNSF.
Yes there is a point to the post. I was simply telling a story. I am sorry you didn't see it that way.
Dick Donaway
The major 'bone of contention' of the railroads dealing with non-railroad entities as well as other railroadds is the assumption of liability. Nobody wants to assume liability. eg. Insurance and at high values. Catastrophic incidents run up $$$$$$$$ quickly.
Never too old to have a happy childhood!
CMStPnPI've heard other railfan groups complain about insurance coverage and really there is no law stopping them from forming their own insurance company for fan trips and the like.
One might wonder if such a program might just benefit all of the tourist operations, large to small.
Larry Resident Microferroequinologist (at least at my house) Everyone goes home; Safety begins with you My Opinion. Standard Disclaimers Apply. No Expiration Date Come ride the rails with me! There's one thing about humility - the moment you think you've got it, you've lost it...
PNWRMNM Is there a point to this post? Either the BNSF thought they were dealing with honorable people, obviously they were not, or they forgot to tell the Dispatchers. This is the kind of behavior that rightly gives railfans a bad name and the carriers every encouragement to not deal with them ever, at all at all, because the carriers do not trust them. If something had happened who do you think the plaintiff's lawyers would go after? A judgement proof group of foamers or deep pockets BNSF.
I was going to say much the same. Back in college when I was night auditor of a prominent brand hotel they insured the Airport Shuttle Vans up to 5,000,000 in liability that was for 1 year 24 by 7 operation. $80,000,000 in liability is very reasonable request and the premium for a 1-2 day trip, though steep should not have been astronomical for a railfan group to make...... a number of firms offer short term coverage for large amounts like that.
I've heard other railfan groups complain about insurance coverage and really there is no law stopping them from forming their own insurance company for fan trips and the like. C'mon folks your hauling the general public here, lets not stoop as low as Uber and Lyft with inadequate insurance coverage.
You nailed it. BNSF would, by virtue of having deep pockets, be 'on-the-hook'.
Norm
Several years ago, a group representing the SiouxLand Historic Railroad Association held the Milwaukee National Convention in Sioux City, IA. A great deal of the focus was around the Historic Assn.'s acquisition of the Milwaukee yards in Sioux City. All the planning went well even scheduling a D&I diesel (x Milwaukee GP) and cars from the 261 set to make a run from Sioux City, IA to Sioux Falls, SD, about 90 miles during the convention. (See article on the D&I in the Sept. 2017 Trains.)
Comes Monday of convention week and the BNSF, some of the trackage was BNSF, called and notified us if we were planning on using BNSF track, we had to provide liability to the tune of $80,000,000. Eighty million dollars. Right. For a two hour train ride. Back to the drawing board. BNSF was going to deliver the cars to Sioux City.
Someone came up with the idea of using busses to get from Sioux City to Hawarden, IA about 40 miles north of Sioux City and in D&I area. Fine. We bused to Hawarden, got on the train and head north. By the way, the sack lunches were still in Sioux City. We get to Canton, SD where there is joint trackage rights, yep. BNSF and D&I. So we continue to Sioux Falls on track owned by the BNSF with rights to the D&I. Well, we got to Sioux Falls where our lunches met us about 3 in the afternoon. All was forgotten and forgiven, the ride was great but so much for the legal team of the BNSF.
Our community is FREE to join. To participate you must either login or register for an account.