YorkRailFan
Established Member
Reports first emerged from TOC's Twitters that a train was on fire at Darlington (LNER posted here:https://twitter.com/LNER/status/1723019790472667320), this was later confirmed to be a XC Voyager (interestingly, XC has stayed quiet about this) by David Frankal (post here:https://twitter.com/DavidFrankal/status/1723014643268915567), this was later confirmed to be 220 003 (post here: https://twitter.com/NBHCommRail/status/1723061685122916861) and this was apparently caused by a bird getting stuck in the exhaust fan.
From LNER: Due to a fire on a train at #Darlington, train services through this station may be subject to disruption on all routes. Disruption is expected until 17:45 We are sorry for the inconvenience this may cause to your journey today.
LNER later said: Disruption caused by a fire on a train at #Darlington has now ended. Services are no longer affected by this problem. We are sorry for the inconvenience this may cause to your journey today.
Tweet/post from David Frankal (image included):Passengers evacuated from 1V66 at Darlington, all safe.
The front unit in question is 220 005 (on RTT here as 1V66: https://www.realtimetrains.co.uk/service/gb-nr:G59599/2023-11-10/detailed#allox_id=1) currently running over 50 minutes late.David later said: It's now been reinstated, front unit only
Confirmation of it being 220 003 from NBH Community Rail Group on Twitter/X: Looks like 220 003 had the little "issue". I'd hate to be one having to sort that mess out...
Choo Choo on Twitter/X about it likely being a bird getting stuck in the exhaust fan: Bird got stuck in the exhaust fan which caused flames to appear apparently