Home Open Account Help 517 users online

Passenger Trains > Amtrak Cascades Airo Test Run as 967


Date: 08/27/26 13:27
Amtrak Cascades Airo Test Run as 967
Author: highballer1

The first Amtrak Cascades trainset with Siemens Charger 7001 ran south to Portland and currently it’s showing as the same number, 967 northbound. The train has run behind the projected schedule all day but also had a F40PH Oregon cab control car in tow southbound. Anyone have any details on this run today other than training?

Posted from iPhone



Edited 2 time(s). Last edit at 08/27/26 14:52 by highballer1.



Date: 08/27/26 13:44
Re: Amtrak Cascades Airo Test Run as 966
Author: hsr_fan

Looking at the tracker history, it was held to a max speed of 59 mph even on the 79 mph sections.



Date: 08/27/26 14:24
Re: Amtrak Cascades Airo Test Run as 967
Author: highballer1

The train just left Olympia-Lacey northbound as #968! No full set was requested, no testing of the lifts and a much briefer stop. Wonder what the hold on speed was and the Oregon control cab car 90252 was on the rear and the whole train was wyed again. Where’s the problem with the cab control coach being the leader??? Puzzling

Posted from iPhone



Edited 1 time(s). Last edit at 08/27/26 21:14 by highballer1.



Date: 08/27/26 20:44
Re: Amtrak Cascades Airo Test Run as 967
Author: NPRocky

One quick correction. The number I saw on the Oregon cab car in Olympia was 90252 (there is no 90242). I'm really getting worried that they're not testing the Airo cab car on BNSF between Portland and Seattle but haven't heard anything as to why. They tested it on the UP weeks ago with no reported issues. They had a near miss with a truck on that run, but it was apparently the truck driver's fault.



Date: 08/27/26 20:51
Re: Amtrak Cascades Airo Test Run as 967
Author: highballer1

I caught my mistake with the number of the cabbage control car after the fact Rocky. My old fingers on my phone are not as nimble as they once were.

Posted from iPhone



Date: 08/27/26 21:46
Re: Amtrak Cascades Airo Test Run as 967
Author: roustabout

NPRocky Wrote:
-------------------------------------------------------
> One quick correction. The number I saw on the
> Oregon cab car in Olympia was 90252 (there is no
> 90242). I'm really getting worried that they're
> not testing the Airo cab car on BNSF between
> Portland and Seattle but haven't heard anything as
> to why. They tested it on the UP weeks ago with no
> reported issues. They had a near miss with a truck
> on that run, but it was apparently the truck
> driver's fault.

I have heard that BNSF will not allow the Airo ocntrol cab to lead; they must wye the train so that the locomotive leads or use a cab car



Date: 08/27/26 23:34
Re: Amtrak Cascades Airo Test Run as 967
Author: andrewamtrak

roustabout Wrote:
-------------------------------------------------------
> NPRocky Wrote:
> --------------------------------------------------
> -----
> > One quick correction. The number I saw on the
> > Oregon cab car in Olympia was 90252 (there is
> no
> > 90242). I'm really getting worried that they're
> > not testing the Airo cab car on BNSF between
> > Portland and Seattle but haven't heard anything
> as
> > to why. They tested it on the UP weeks ago with
> no
> > reported issues. They had a near miss with a
> truck
> > on that run, but it was apparently the truck
> > driver's fault.
>
> I have heard that BNSF will not allow the Airo
> ocntrol cab to lead; they must wye the train so
> that the locomotive leads or use a cab car



Correct, there is a BNSF prohibition on the cabcars leading.

Posted from Android



Date: 08/28/26 04:29
Re: Amtrak Cascades Airo Test Run as 967
Author: jp1822

andrewamtrak Wrote:
-------------------------------------------------------
> roustabout Wrote:
> --------------------------------------------------
> -----
> > NPRocky Wrote:
> >
> --------------------------------------------------
>
> > -----
> > > One quick correction. The number I saw on the
> > > Oregon cab car in Olympia was 90252 (there is
> > no
> > > 90242). I'm really getting worried that
> they're
> > > not testing the Airo cab car on BNSF between
> > > Portland and Seattle but haven't heard
> anything
> > as
> > > to why. They tested it on the UP weeks ago
> with
> > no
> > > reported issues. They had a near miss with a
> > truck
> > > on that run, but it was apparently the truck
> > > driver's fault.
> >
> > I have heard that BNSF will not allow the Airo
> > ocntrol cab to lead; they must wye the train so
> > that the locomotive leads or use a cab car
>
>
>
> Correct, there is a BNSF prohibition on the
> cabcars leading.
>
> Posted from Android

Oh, boy...... Here we go!!! This makes it a bit counter-productive with the basic Airo train set philosophy/use. 



Date: 08/28/26 06:52
Re: Amtrak Cascades Airo Test Run as 967
Author: highballer1

This “problem” that BNSF seems to have, makes no sense! Tell me why they allow the Talgo series 8 trainsets to operate with their respective cab cars forward! And the Northeast Corridor Amtrak testing utilized the cab-coach car to be the leader.

Posted from iPhone



Date: 08/28/26 10:35
Re: Amtrak Cascades Airo Test Run as 967
Author: koloradokid

highballer1 Wrote:
-------------------------------------------------------
> This “problem” that BNSF seems to have, makes
> no sense! Tell me why they allow the Talgo series
> 8 trainsets to operate with their respective cab
> cars forward! And the Northeast Corridor Amtrak
> testing utilized the cab-coach car to be the
> leader.
>
> Posted from iPhone

It's BNSF and Amtrak, who knows. and we will likely never know!

RR



Date: 08/28/26 12:44
Re: Amtrak Cascades Airo Test Run as 967
Author: amtrak8

More than likely will result in a lawsuit between Amtrak/WSDOT and BNSF or a formal FRA complaint.  Stay tuned.



Date: 08/28/26 13:23
Re: Amtrak Cascades Airo Test Run as 967
Author: Lackawanna484

How is Amtrak's HHP8 cab car plan coming along?

Posted from Android



[ Share Thread on Facebook ] [ Search ] [ Start a New Thread ] [ Back to Thread List ] [ <Newer ] [ Older> ] 
Page created in 0.0465 seconds