EuclidSTAGE ONE: Perform testing to gather data of in-train forces. STAGE TWO: Build a model of those forces showing every detail of their potential. STAGE THREE: Write a program to evaluate train make-up and all of the in-train forces that it can produce.
STAGE TWO: Build a model of those forces showing every detail of their potential.
STAGE THREE: Write a program to evaluate train make-up and all of the in-train forces that it can produce.
As Balt points out, and to my knowledge - this has already been done. Hence the existing rules for train make-up.
The prime reason for block-swapping is to prevent handling a given car at every single terminal. This is why humps are disappearing. Not to mention that terminal dwell is a major productivity killer.
Keeping entire 200 car trains in the "proper order" would bring the railroad to a halt.
Keep in mind, too, that a 50' boxcar loaded with balsa may well weigh less than an empty LP gas car (partly conjecture on my part, but...).
And even if you do get the train in the "proper order," a dragging brake changes the whole dynamic...
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...
Euclid BaltACD oltmannd BaltACD oltmannd Euclid This issue is not just a matter of having computers and doing modeling. Everybody is doing that every day. The point is that the computer modeling needed for solving the problem of excess in-train forces has got to be directed at that problem. So the first step is to find examples of that problem by measuring in-train forces. Then use the most applicable computer analysis to see if it verifies that same problem. If it does not verify the problem, then try to figure out why a real problem is not detected by the computer program. In other words, you need to test real trains to learn how to build the program that can flag that problem before it causes a derailment. Validation work had long been done. Models work very well. You can't practically model every train for every operational scenario before you dispatch. Train forces are the results of train handling which depend largely on what's happening where on the railroad plus unintended stuff. You gonna model the train going into emergency every 50 feet? For a separated air hose at every one of 200 locations on the train? Or even every combination of DB and service brake application for every spot the train might have to slow down? Not happening. Can't happen. Euc wants all that modeling done for each train that departs its originating terminal - for each and every train, every trip. Probably ending in discipline for somebody if the train derails for any reason anywhere. Yup. And what are you going to use for train handling inputs? You put that exact train out on the road for 10,000 days in a row and you'll have 10,000 unique sets of train handling data (brake, throttle, DB, etc.) Which is a concept Euc can't or won't comprehend. My favorite interest is automobile racing - virtually all forms from F1 through IndyCar, NASCAR and on down to Club racing and the local bull ring dirt tracks. In many cases there are 'spec classes' where the intent of the specifications are to make the cars as identical as humanly possible to that the driver is the variable to the success or failure in any competition. The drivers is the 'master sensor' and is the one that inputs throttle, brake and steering inputs to make the car go - good drivers are faster than less than good driver. I won't hazard any guess to what a 'computer' driver's performance would be. I have not been on any trains that are being operated with the various locomotive operation computer application, as such I am not in any position to comment on how well those programs peform, what their sensory inputs are and how they react to those sensory inputs. Jeff Hergert would be a much better source on their operation and quirks. I do not understand why you and Don assume that the “modeling” I refer to will be done for every train before it is allowed to depart from its terminal. My reference to “modeling” refers only to the second stage of a 3-stage process as follows: STAGE ONE: Perform testing to gather data of in-train forces. STAGE TWO: Build a model of those forces showing every detail of their potential. STAGE THREE: Write a program to evaluate train make-up and all of the in-train forces that it can produce. After the data is gathered by testing to learn the entire scope of those forces, computer models of those forces are built. The final model will show every detail of the buildup and dissipation of those forces as they move through the train car by car. This would be a big task costing many millions of dollars. It has not been done yet. It would take considerable time. It will be revised occasionally to account for new types of rolling stock. The testing to gather data alone will also be a lot of work, yet I expect the data might show things that have not been known. It might show force multiplication that is sometimes greater than has been determined by practice. And I don't think that everything developed for the model will have to come from actual measuring of the in-train forces. There can be a mix of approaches with the model making. For one thing, they could model a 250-car train to learn about the in-train foreces. I think this is what the FRA has in mind. I understand that the only similar project that has been done is extensive modeling of tank cars following the Lac Megantic wreck. The purpose was to study how tank cars collide in high speed derailments in order to build them with more crashworthiness. In any case, the modeling for in-train forces would be an enormous task. The cost will certainly be objectionable, as will the prospect of the resulting knowledge that might lead to mandates limiting train length. HOWEVER-- Once the modeling has been done, the occurrences of all in-train forces will be understood. At present, they are not fully understood. But when they are understood, a program will be written. It is the program that will be used to evaluate every train to determine whether it is safe to run. So the “modeling” will be done for the purpose of writing the program. Then the program will evaluate each train to show all of the potential in-train forces and warn against operation of some the force potential is high enough to show a derailment hazard. So you put the train car-list into the program, and it gives you the answer. I don’t know how long that would take, but maybe only seconds. So the data gathering, modeling, and developing a program is a massive effort needed to build the system, but it certainly does NOT have to be done for each train. All three stages of development will have been completed before the working system will be used in actual service of evaluateing trains for excess force potential.
BaltACD oltmannd BaltACD oltmannd Euclid This issue is not just a matter of having computers and doing modeling. Everybody is doing that every day. The point is that the computer modeling needed for solving the problem of excess in-train forces has got to be directed at that problem. So the first step is to find examples of that problem by measuring in-train forces. Then use the most applicable computer analysis to see if it verifies that same problem. If it does not verify the problem, then try to figure out why a real problem is not detected by the computer program. In other words, you need to test real trains to learn how to build the program that can flag that problem before it causes a derailment. Validation work had long been done. Models work very well. You can't practically model every train for every operational scenario before you dispatch. Train forces are the results of train handling which depend largely on what's happening where on the railroad plus unintended stuff. You gonna model the train going into emergency every 50 feet? For a separated air hose at every one of 200 locations on the train? Or even every combination of DB and service brake application for every spot the train might have to slow down? Not happening. Can't happen. Euc wants all that modeling done for each train that departs its originating terminal - for each and every train, every trip. Probably ending in discipline for somebody if the train derails for any reason anywhere. Yup. And what are you going to use for train handling inputs? You put that exact train out on the road for 10,000 days in a row and you'll have 10,000 unique sets of train handling data (brake, throttle, DB, etc.) Which is a concept Euc can't or won't comprehend. My favorite interest is automobile racing - virtually all forms from F1 through IndyCar, NASCAR and on down to Club racing and the local bull ring dirt tracks. In many cases there are 'spec classes' where the intent of the specifications are to make the cars as identical as humanly possible to that the driver is the variable to the success or failure in any competition. The drivers is the 'master sensor' and is the one that inputs throttle, brake and steering inputs to make the car go - good drivers are faster than less than good driver. I won't hazard any guess to what a 'computer' driver's performance would be. I have not been on any trains that are being operated with the various locomotive operation computer application, as such I am not in any position to comment on how well those programs peform, what their sensory inputs are and how they react to those sensory inputs. Jeff Hergert would be a much better source on their operation and quirks.
oltmannd BaltACD oltmannd Euclid This issue is not just a matter of having computers and doing modeling. Everybody is doing that every day. The point is that the computer modeling needed for solving the problem of excess in-train forces has got to be directed at that problem. So the first step is to find examples of that problem by measuring in-train forces. Then use the most applicable computer analysis to see if it verifies that same problem. If it does not verify the problem, then try to figure out why a real problem is not detected by the computer program. In other words, you need to test real trains to learn how to build the program that can flag that problem before it causes a derailment. Validation work had long been done. Models work very well. You can't practically model every train for every operational scenario before you dispatch. Train forces are the results of train handling which depend largely on what's happening where on the railroad plus unintended stuff. You gonna model the train going into emergency every 50 feet? For a separated air hose at every one of 200 locations on the train? Or even every combination of DB and service brake application for every spot the train might have to slow down? Not happening. Can't happen. Euc wants all that modeling done for each train that departs its originating terminal - for each and every train, every trip. Probably ending in discipline for somebody if the train derails for any reason anywhere. Yup. And what are you going to use for train handling inputs? You put that exact train out on the road for 10,000 days in a row and you'll have 10,000 unique sets of train handling data (brake, throttle, DB, etc.)
BaltACD oltmannd Euclid This issue is not just a matter of having computers and doing modeling. Everybody is doing that every day. The point is that the computer modeling needed for solving the problem of excess in-train forces has got to be directed at that problem. So the first step is to find examples of that problem by measuring in-train forces. Then use the most applicable computer analysis to see if it verifies that same problem. If it does not verify the problem, then try to figure out why a real problem is not detected by the computer program. In other words, you need to test real trains to learn how to build the program that can flag that problem before it causes a derailment. Validation work had long been done. Models work very well. You can't practically model every train for every operational scenario before you dispatch. Train forces are the results of train handling which depend largely on what's happening where on the railroad plus unintended stuff. You gonna model the train going into emergency every 50 feet? For a separated air hose at every one of 200 locations on the train? Or even every combination of DB and service brake application for every spot the train might have to slow down? Not happening. Can't happen. Euc wants all that modeling done for each train that departs its originating terminal - for each and every train, every trip. Probably ending in discipline for somebody if the train derails for any reason anywhere.
oltmannd Euclid This issue is not just a matter of having computers and doing modeling. Everybody is doing that every day. The point is that the computer modeling needed for solving the problem of excess in-train forces has got to be directed at that problem. So the first step is to find examples of that problem by measuring in-train forces. Then use the most applicable computer analysis to see if it verifies that same problem. If it does not verify the problem, then try to figure out why a real problem is not detected by the computer program. In other words, you need to test real trains to learn how to build the program that can flag that problem before it causes a derailment. Validation work had long been done. Models work very well. You can't practically model every train for every operational scenario before you dispatch. Train forces are the results of train handling which depend largely on what's happening where on the railroad plus unintended stuff. You gonna model the train going into emergency every 50 feet? For a separated air hose at every one of 200 locations on the train? Or even every combination of DB and service brake application for every spot the train might have to slow down? Not happening. Can't happen.
Euclid This issue is not just a matter of having computers and doing modeling. Everybody is doing that every day. The point is that the computer modeling needed for solving the problem of excess in-train forces has got to be directed at that problem. So the first step is to find examples of that problem by measuring in-train forces. Then use the most applicable computer analysis to see if it verifies that same problem. If it does not verify the problem, then try to figure out why a real problem is not detected by the computer program. In other words, you need to test real trains to learn how to build the program that can flag that problem before it causes a derailment.
Validation work had long been done. Models work very well.
You can't practically model every train for every operational scenario before you dispatch. Train forces are the results of train handling which depend largely on what's happening where on the railroad plus unintended stuff.
You gonna model the train going into emergency every 50 feet? For a separated air hose at every one of 200 locations on the train? Or even every combination of DB and service brake application for every spot the train might have to slow down?
Not happening. Can't happen.
Euc wants all that modeling done for each train that departs its originating terminal - for each and every train, every trip. Probably ending in discipline for somebody if the train derails for any reason anywhere.
Yup. And what are you going to use for train handling inputs? You put that exact train out on the road for 10,000 days in a row and you'll have 10,000 unique sets of train handling data (brake, throttle, DB, etc.)
Which is a concept Euc can't or won't comprehend.
My favorite interest is automobile racing - virtually all forms from F1 through IndyCar, NASCAR and on down to Club racing and the local bull ring dirt tracks. In many cases there are 'spec classes' where the intent of the specifications are to make the cars as identical as humanly possible to that the driver is the variable to the success or failure in any competition. The drivers is the 'master sensor' and is the one that inputs throttle, brake and steering inputs to make the car go - good drivers are faster than less than good driver. I won't hazard any guess to what a 'computer' driver's performance would be.
I have not been on any trains that are being operated with the various locomotive operation computer application, as such I am not in any position to comment on how well those programs peform, what their sensory inputs are and how they react to those sensory inputs. Jeff Hergert would be a much better source on their operation and quirks.
You continually demonstrate you have no idea how trains come into being or why they end up in the form they do.
Railroads service customers - customers get and release cars - cars that customers get or release can be in one's and two's or twenty's and thirty's or even more. Some trains are fully built at origin, many more are not. Those that aren't fully built will be involved in pick ups and/or set offs as the train moves from its origin to its destination. Such a train might depart origin with light power and end up with 200 or more cars when it gets to its destination - or it may arrive destination with light power after being 200 or more cars for periods during its trek.
A function of PSR among most of the carriers is a reduction in the number of yards and expanding Yardmaster responsibilities to cover multiple yards. Another function of PSR is the act of 'block swapping' between trains that have diffeent origins and different destinations at some point where both trains share their routes. The block can be 1 car or 150 cars and it will change on a daily basis.
One thing modeling has done from my experience up until the time I retired was to create Train Handling Rules and Timetable Special Instructions concerning permissible train make up. Some of the simple rulings are 1. blocks of 30 more more empties can have no more that 10 loads in whatever cars follow the empty block. 2. long (longer than 60 foot) empty cars are restricted to how much tonnage can trail behind them. 3. placement restrictions between various types of HAZMAT. 4. Placement restrictions between shiftable loads and HAZMAT. There are probably a dozen or more other placement restrictions that will crop up from time to time - like clearance implicated cars being handled within five cars of the locomotives.
Never too old to have a happy childhood!
It's those darned shades of gray, again...
-Don (Random stuff, mostly about trains - what else? http://blerfblog.blogspot.com/)
EuclidThis issue is not just a matter of having computers and doing modeling. Everybody is doing that every day. The point is that the computer modeling needed for solving the problem of excess in-train forces has got to be directed at that problem. So the first step is to find examples of that problem by measuring in-train forces. Then use the most applicable computer analysis to see if it verifies that same problem. If it does not verify the problem, then try to figure out why a real problem is not detected by the computer program. In other words, you need to test real trains to learn how to build the program that can flag that problem before it causes a derailment.
oltmannd Euclid BaltACD Euclid ... I doubt the railroads would program simulators that show that derailments can be caused by excess buff forces in their ultra-long trains. But I suspect that if they had real world data, it would show that in-train forces associated with these trains will derail them under certain conditions. Indeed, that is the conclusion of the FRA and unions. And there is mounting empirical evidence of the correlation. ... Your lack of knowledge of railroad operations and supervision is SHOUTING. Well if you have the knowledge; show me the use of computers to model the in-train forces in a 250-car train with suitable distributed power and best train handling practice in moderately hilly terrain, at typical road speeds. Also, if the industry has this capability, why aren’t they using it to predict derailments caused by in-train forces? If they are doing that, why are these derailments occurring? They do have modeling tools. They do use them to set rules for train make-up and territory. They are often used retrospectively to analyze derailments. They are generally difficult to use and tough to deploy as tools for train consist management. Car geometry plays a big role as does ROW geometry and in-train forces.
Euclid BaltACD Euclid ... I doubt the railroads would program simulators that show that derailments can be caused by excess buff forces in their ultra-long trains. But I suspect that if they had real world data, it would show that in-train forces associated with these trains will derail them under certain conditions. Indeed, that is the conclusion of the FRA and unions. And there is mounting empirical evidence of the correlation. ... Your lack of knowledge of railroad operations and supervision is SHOUTING. Well if you have the knowledge; show me the use of computers to model the in-train forces in a 250-car train with suitable distributed power and best train handling practice in moderately hilly terrain, at typical road speeds. Also, if the industry has this capability, why aren’t they using it to predict derailments caused by in-train forces? If they are doing that, why are these derailments occurring?
BaltACD Euclid ... I doubt the railroads would program simulators that show that derailments can be caused by excess buff forces in their ultra-long trains. But I suspect that if they had real world data, it would show that in-train forces associated with these trains will derail them under certain conditions. Indeed, that is the conclusion of the FRA and unions. And there is mounting empirical evidence of the correlation. ... Your lack of knowledge of railroad operations and supervision is SHOUTING.
Euclid ... I doubt the railroads would program simulators that show that derailments can be caused by excess buff forces in their ultra-long trains. But I suspect that if they had real world data, it would show that in-train forces associated with these trains will derail them under certain conditions. Indeed, that is the conclusion of the FRA and unions. And there is mounting empirical evidence of the correlation. ...
Your lack of knowledge of railroad operations and supervision is SHOUTING.
They do have modeling tools. They do use them to set rules for train make-up and territory.
They are often used retrospectively to analyze derailments.
They are generally difficult to use and tough to deploy as tools for train consist management. Car geometry plays a big role as does ROW geometry and in-train forces.
I was involved in investigations to produce computer models of train handling on the then Hamersley Iron and Mt Newman Mining railways, now Rio Tinto and BHP respectively. This was between 1976 and 1978. I believe this work was used in the work leading up to Rio Tinto's present remote controlled trains.
Back then the electronics required were quite big and clumsy. We could only instrument a pair of cars, which we moved to different locations in the train.
Of course these trains of 144 to 200 cars were always either completely empty of fully loaded, and the cars were effectively identical in size and weight.
But the tests were carried out and the models developed. These days much more could be done at a much lower cost. We actually had a black and white video camera and a reel to reel video recorder which may have been powered by car batteries, just to give an idea of what was available.
On the Hamersley trains the cars at each end were always the newest cars available, so that the trailing cars were always fitted with the best air brake valves to reduce the chances of dragging brakes on the trailing cars.These cars were all pairs with only a single air brake valve for the two cars, which substantially reduced the propagation time of the air brake signals.
200 cars with individual brake valves would be subject to greater delays in application and release of the brakes.
Of course, all these trains now have ECP brakes, whether the trains are remotely controlled or conventionally driven. The significant reduction in in train forces allowed by ECP brakes is regarded as a neccesity for remotely operated trains.
Peter
oltmanndOr, why haven't these derailments stopped happening.
As I noted earlier, there's rules, and there's following them.
Too, consider the problem of combining proper placement with blocking.
Or, why haven't these derailments stopped happening.
RRs have, for a very long time, built trains the would derail if they went into emergency in just the right spot. Once in a blue moon, they would and did!
tree68There's rules, then there's compliance with the rules...
It's not like a RFE has to pull physical tapes anymore. All the stuff has instant triggers, instant downloads, instant reviews.
It's been fun. But it isn't much fun anymore. Signing off for now.
The opinions expressed here represent my own and not those of my employer, any other railroad, company, or person.t fun any
And there is Supervision to ensure compliance.
Without proper Supervision, you don't have much. Without a rules compliant culture you have even less.
There's rules, then there's compliance with the rules...
All I can say is that such modeling was taking place when I was still employed. That being said I have been retired since December 2016 and subsequently PSR attacked my former employer in the form of a dying EHH and virtually all Operating Management was replaced by EHH cronies - with all that being the case I have no idea what form of modeling is taking place.
I do know that when I was working the CSX Train Handling Rule and divisional employee timetable special instructions had a number of restrictions on how to build trains and how much trailing tonnage was allowed before a helper or DPU was required.
Personal observations from some local incidents AFTER EHH and PSR were thrust into operations, indicated to me, that some of the restrictions that were in effect when I was working did not appear to be in effect from the incidents (derailments) that happened.
Euclid... I doubt the railroads would program simulators that show that derailments can be caused by excess buff forces in their ultra-long trains. But I suspect that if they had real world data, it would show that in-train forces associated with these trains will derail them under certain conditions. Indeed, that is the conclusion of the FRA and unions. And there is mounting empirical evidence of the correlation. ...
Overmod Euclid I suggest a means to actually measure buff and draft force on each coupler joint in a test train that duplicates an actual revenue train. Probably be easier to equip them with magnetic or clamp-on battery-powered accelerometers, and store the results with GPS location and timestamp, then stream all the results wirelessly. Assign an IoT address to each one to keep them definitively apart. Where the effort ought to be placed is better control of the 'fence' activity in Locotrol so that any trailing power modulates its dynamic correctly for the part of its train between nodes. Without that, any long train on an irregular profile might indeed be another Springfield cocked and unlocked... You'd use exactly the same set of accelerometers, feeding into one of the train management programs, to figure out what that ought to be, and what permanent methods should be implemented (probably as an AAR standard) to deal with it.
Euclid I suggest a means to actually measure buff and draft force on each coupler joint in a test train that duplicates an actual revenue train.
Probably be easier to equip them with magnetic or clamp-on battery-powered accelerometers, and store the results with GPS location and timestamp, then stream all the results wirelessly. Assign an IoT address to each one to keep them definitively apart.
Where the effort ought to be placed is better control of the 'fence' activity in Locotrol so that any trailing power modulates its dynamic correctly for the part of its train between nodes. Without that, any long train on an irregular profile might indeed be another Springfield cocked and unlocked...
You'd use exactly the same set of accelerometers, feeding into one of the train management programs, to figure out what that ought to be, and what permanent methods should be implemented (probably as an AAR standard) to deal with it.
tree68It's probably already been done, virtually - ie, on a computer. Acceleration, deceleration, and buff forces can easily be simulated, and I'm pretty sure most profiles have been recorded as well. And probably for less money than it would take to equip some 200 cars.
Acceleration, deceleration, and buff forces can easily be simulated, and I'm pretty sure most profiles have been recorded as well.
And probably for less money than it would take to equip some 200 cars.
In the early 1990's CSX had a Simulator for Engineers that married the calculation of in train forces by using the data of actual trains that had been operated and the ability to operate that train of data over any of the territory CSX was operating.
Of course in the 1990's Distributed Power was not on CSX's horizon.
I am certain that in the 21st Century, the CSX Simulator does replicate that various operating modes with DPU in one or more locations within specified trains; with those location(s) able to be manipulated on instructor demand.
In my use of the simulator what was missing was the actual physical impacts from slack action - the buff and draft kicks in the pants.
It's probably already been done, virtually - ie, on a computer.
EuclidI suggest a means to actually measure buff and draft force on each coupler joint in a test train that duplicates an actual revenue train.
Euclid Here is some news about this question. Does anybody actually know the answer? Railroad labor advocacy seems to frequently cite this increase of danger with monster trains. However, that view is understandable because everyone agrees that monster trains reduce crew costs, and thus cause a loss of jobs. The media obviously jumped onto that bandwagon in response to the East Palestine wreck, which was then affirmed by the Springfield, OH wreck. This latest news suggests that engineers may need more training to know how to operate the longer trains. https://fortune.com/2023/04/28/railroad-derailment-long-trains-federal-regulators-problem-contributor/ The feds are warning railroads that their love of long trains is leading to horrible accidents and derailments—but they’re not doing anything about it yet
It's gonna be more territory specific than train consist specific. FEC could run just about anything, anywhere, anytime no sweat. Horseshoe curve? CSX Boston Line? We'd have to talk...
But of course this solution to the ultra-long train derailment problem will be fiercely opposed by the railroad companies because of their dread of ECP brakes. It is only the social impact of train disasters written in blood that will push this forward. But the industry would give up the long trains if it would avoid ECP.
jeffhergert... The FRA wants more crew training. Maybe that's not where the problem is. Crews run these things everyday. They get to know what works and what doesn't. Maybe railroad management needs more training in making up trains. Jeff
The FRA wants more crew training. Maybe that's not where the problem is. Crews run these things everyday. They get to know what works and what doesn't. Maybe railroad management needs more training in making up trains.
Jeff
On 'my' division of CSX, there were a number of TTSI's that related to train make-up that limited the positions of various cars/types when built into trains. Many of these restrictions were related to the trailing tonnage that could be in the train behind such cars. My division did include mountainous territory with a high degree of curvature in surmounting those grades. These restrictions had been developed from the examination of causes of derailments over the years - learned in 'blood'. While these restrictions were second nature to the yardmasters on the division who made every effort to comply with the restrictions - my divisions restrictions were not uniformly enacted across the company as a whole. Flatlanders did not have the restrictions, even though they were building trains that would operate through the territory that occasioned the restictions. A company failure in my mind.
Within the last year or so, UP announced a computer program that can run a train's route and show where problems might happen. I don't think it is used to reposition cars, just give them an advance heads up about where something might happen.
Just looking at a train list is sometimes enough because it's obvious that things should be changed. A few times I know where a crew raised objections and were told to go with it. Then the train derailed on that crew's portion of the run. (Funny how even though the crew told the FRA investigators that fact, it didn't make it into the FRA accident report.)
DP is not the panacea it's made out to be. Yes they do help. All our trains over 10000 feet need a mid train DP. Longer trains over a certain weight threshold need a mid and rear DP. Some still get torn up, sometimes into three or four pieces. Sometimes it's a problem with the DP that causes the initial action that results in a train breaking into two.
Not all trains are the same. One of our mixed manifests is often 60 or 70 % cushioned drawbars. We have a couple that have few of the cushioned drawbars. Both types can often be in the 12000 to 15000 foot range. Guess which type is likely to have problems out on the road.
We've had some intermodals up tp 18000 feet. Many are often in the 12000 to 15000 foot range. They normally don't have many problems. (Other than open container doors.) They are relatively light and don't have cushioned drawbars. They aren't bad to run.
Regarding air brake usage, Most trains I get I only have to use air when stopping. Eastbound, except for light trains, like empty unit trains, I will need to use air once for sure to control speed. That's coming down the short 1.25% grades coming down into the Missouri River valley. There's two other areas eastbound where I may need to use air to maintain speed, but even in those places if I have enough good dynamics I won't need to use air.
Our community is FREE to join. To participate you must either login or register for an account.