| Re: Evesham station - services, footbridge, facilities, incidents and events (merged posts) Posted by Chris from Nailsea at 22:00, 14th November 2024 |      |
I've merged a couple of topics here - simply because they all relate to Evesham.
That will hopefully assist in future reference for any of our readers on the Coffee Shop forum looking for 'Evesham'.
CfN.
| Re: Evesham Station Footbridge Posted by IndustryInsider at 17:33, 14th November 2024 | |
It's been shut for a couple of weeks now for a heavy refurbishment, including replacement of all the steps.
| Evesham Station Footbridge Posted by Witham Bobby at 14:35, 14th November 2024 | |
When I drove past the Evesham station approach just after 0700 this morning, I noticed boards out the front indicating that the footbridge was out of use, and directing intending passengers to use the road bridge to enter the station via the Worcester Road entrance and gain access to the up platform via the step-free route that has been created over the old Up Goods Loop.
Any ideas what's happened to the footbridge? Maintenance, or is there an abundance of caution about using the bridge in frosty times (there was no frost this morning, but there has been on the past couple of mornings)
| Re: Incident at Evesham 21/11/2012 Posted by Chris from Nailsea at 20:08, 23rd November 2012 | |
From the Malvern Gazette:
First rain, then fire delays rail services
Rail services to Malvern came to a halt for several hours on Wednesday night when the engine of a train caught fire in Evesham.
Firefighters attended the town^s station at 8.50pm following reports of a blaze in the undercarriage of the 19.44 service from Great Malvern to Paddington. On arrival, they found the fire had already been extinguished, but two crew members used foam to ensure it was fully out. They left the scene at 10.30pm.
First Great Western spokesman James Davis said it was too early to know the cause of the fire, which happened as the train pulled into the station. He said the flames extingushed themselves and all 14 passengers and crew were safely evacuated. Passengers were then taken to their destinations in taxis.
The train was stationary for about an hour and a half before it was taken to First Great Western^s Oxford depot to be assessed.
There were delays to trains travelling in both directions, with some terminating at stations several stops before their final destinations.
Mr Davis said it was not clear how much of the holdup was due to the fire, given earlier problems on lines caused by bad weather.
Dr Richard Long, of Bromsberrow Heath, near Ledbury, was a passenger on the 18.22 from Paddington which was forced to stop in Honeybourne, near Evesham, while the fire was dealt with.
He said: ^The train had already left half an hour late because of the weather. When we got to Honeybourne, we stopped and the train manager instructed us that the engine of the train in front was on fire. We sat there for about an hour and a half while the fire brigade came and put the flames out and then the engineers had to come make sure the train was safe to proceed.
^We had to get out at Worcester Shrub Hill and change trains to the 19.22 from Paddington. I finally got into Ledbury at about 12.45am ^ almost two-and-a-half hours late.
^When we had to get out at Shrub Hill there were 57 of us waiting to get to Ledbury or Hereford or Colwall, and so on. There was one complaint ^ but there was nothing more that the excellent First Great Western could have done.
^They were absolutely splendid and they kept us all informed and invited us to the buffet car and gave us carte blanche to have what we wanted.
^They brought round a sheet for us to write our email adresses on to compensate us, but I shan^t accept it because they were brilliant.^
Rail services to Malvern came to a halt for several hours on Wednesday night when the engine of a train caught fire in Evesham.
Firefighters attended the town^s station at 8.50pm following reports of a blaze in the undercarriage of the 19.44 service from Great Malvern to Paddington. On arrival, they found the fire had already been extinguished, but two crew members used foam to ensure it was fully out. They left the scene at 10.30pm.
First Great Western spokesman James Davis said it was too early to know the cause of the fire, which happened as the train pulled into the station. He said the flames extingushed themselves and all 14 passengers and crew were safely evacuated. Passengers were then taken to their destinations in taxis.
The train was stationary for about an hour and a half before it was taken to First Great Western^s Oxford depot to be assessed.
There were delays to trains travelling in both directions, with some terminating at stations several stops before their final destinations.
Mr Davis said it was not clear how much of the holdup was due to the fire, given earlier problems on lines caused by bad weather.
Dr Richard Long, of Bromsberrow Heath, near Ledbury, was a passenger on the 18.22 from Paddington which was forced to stop in Honeybourne, near Evesham, while the fire was dealt with.
He said: ^The train had already left half an hour late because of the weather. When we got to Honeybourne, we stopped and the train manager instructed us that the engine of the train in front was on fire. We sat there for about an hour and a half while the fire brigade came and put the flames out and then the engineers had to come make sure the train was safe to proceed.
^We had to get out at Worcester Shrub Hill and change trains to the 19.22 from Paddington. I finally got into Ledbury at about 12.45am ^ almost two-and-a-half hours late.
^When we had to get out at Shrub Hill there were 57 of us waiting to get to Ledbury or Hereford or Colwall, and so on. There was one complaint ^ but there was nothing more that the excellent First Great Western could have done.
^They were absolutely splendid and they kept us all informed and invited us to the buffet car and gave us carte blanche to have what we wanted.
^They brought round a sheet for us to write our email adresses on to compensate us, but I shan^t accept it because they were brilliant.^
| Re: Incident at Evesham 21/11/2012 Posted by Worcester_Passenger at 16:49, 22nd November 2012 | |
I would much rather we had the 165/166's back though 
Your wish has (alas) been granted:
15:51 London Paddington to Worcester Shrub Hill due 18:08
Will be formed of 3 coaches instead of 8.
This is due to an earlier train fault.
Message Received :22/11/2012 15:31
Will be formed of 3 coaches instead of 8.
This is due to an earlier train fault.
Message Received :22/11/2012 15:31
That'll be cosy...
| Re: Incident at Evesham 21/11/2012 Posted by lordgoata at 13:55, 22nd November 2012 | |
These 180s are jinxed aren't they? 
Yes, and they are royally peeing me off! Its been a nightmare this week, and when they are running they are totally useless on the local stopping services - they are full to bursting most of the time (especially if any prior cancellations or if they are delayed), and getting on or off takes ages with everyone standing in the isles.
Ticket inspections that were ramped right up on the morning turbos just prior to the 180's coming in, have all but stopped now (no inspections unless you are in First Class).
The overhead luggage shelf is so narrow most people can't get more than a jacket and a laptop bag on there, so bags all end up on the chairs/floor/tables, taking up yet more room.
The ridiculous chair back tables don't have a latch, so are starting to open by themselves due to the mechanism wearing out.
The only advantages appears to be the aircon (during summer), and a PA which you can actually understand. I would much rather we had the 165/166's back though
| Re: Incident at Evesham 21/11/2012 Posted by JayMac at 12:24, 22nd November 2012 | |
These 180s are jinxed aren't they?
| Re: Incident at Evesham 21/11/2012 Posted by IndustryInsider at 11:09, 22nd November 2012 | |
It remains to be seen which train was involved. If it was the 1944 from Great Malvern, then it should have been a class 180 (Adelante), but, Adelantes appear to be in difficulty again.
It was the 1944ex Malvern and it was a Class 180 (180104). Nothing too major, but there was an engine fire which was put out by the automatic extinguisher. Train crew usually arrange for the fire brigade to be called as a precaution, so they attended but were not required to fight any fire - merely to observe and confirm that with the engine isolated that there was not chance of anything re-igniting.
As I commented in another thread, the 180s have been struggling this week. Maximum of two diagrams covered this week with only one covered on Tuesday. One is/has been stranded on a broken jack in Old Oak Common though I believe - so it wasn't the trains fault! 180103 hasn't been seen in action for a couple of weeks now!
| Re: Incident at Evesham 21/11/2012 Posted by CLPGMS at 10:11, 22nd November 2012 | |
TWICE IN A DAY!
I wonder how many times a passenger has had to leave a train unexpectedly at the same station twice on the same day.
Yesterday, 21st November, I was on my way to the West Midlands, intending to catch the 1124 London Midland train from Worcester Foregate Street to Birmingham New Street. On arrival of the 0822 ex PAD at Worcester Shrub Hill, the Train Manager announced that he had been advised that, due to flooding in the Ledbury area, the train would be terminating at Shrub Hill and that road transport was being arranged for stations to Hereford. In pouring rain, we had to walk down to the coach which was waiting about 100 yards away. We arrived at Foregate Street well in time for the 1124, which was shown as expected at 1126. It eventually turned up around 50 minutes late.
On my return, I was on the 2059 HST from Foregate Street. On arrival at Shrub Hill, we were held in the platform for a few minutes before the Train Manager announced that due to a "train in distress" in the Evesham area, we would be going "nowhere soon" and he would go through the train to obtain details of where passengers were travelling to. It was then announced that the train was cancelled and that taxis were being arranged - in my case to Charlbury. Two other passengers in the taxi were travelling to Pershore and Evesham. At Evesham, there were blue lights flashing all around the station, but I could not see the actual train involved in the fire incident. It may have been the 1944 from Great Malvern, but I gained the impression from staff at Worcester that it could have been the 1822 from Paddington. Because, as that was "delayed", the 1750 from Paddington was extended to run through to Foregate Street - it normally reverses into a siding at Shrub Hill and the 1822 overtakes it. It arrived in Worcester around 35 minutes late, but in time to depart on its return journey at 2059.
As we passed Moreton-in-Marsh station a HST was in the down platform and I noted later on JourneyCheck that the 2050 from Paddington terminated at Oxford.
It remains to be seen which train was involved. If it was the 1944 from Great Malvern, then it should have been a class 180 (Adelante), but, Adelantes appear to be in difficulty again. On 20th November I see that the 1732 from Oxford was "formed by 2 coaches instead of 5" and I travelled on the 1728 ex Worcester which was a 3-car Turbo instead of an Adelante. Earlier in the day on 21st November, I had noted that the 0954 from Great Malvern was a 3-car Turbo instead of an Adelante, although I did see 180104 and 180108 during my journey and extended wait at Foregate Street in the morning.
| Re: Incident at Evesham 21/11/2012 Posted by trainer at 09:11, 22nd November 2012 | |
Thanks for those replies. I hadn't realised there were so many insomniacs (or night workers) on here.
I hope no-one was hurt in the incident. I have searched around the local news sites and can find no details, but it has been cleared from the NR site this morning.| Re: Incident at Evesham 21/11/2012 Posted by JayMac at 01:50, 22nd November 2012 | |
According to Network Rail, it was a train fire on 1P63 1944 Great Malvern to Paddington. Passengers de-trained at Evesham. Fire brigade in attendance.
No other detail I can find on severity or rolling stock type. The 1944 is a non HST service so either a Turbo or Adelante.
| Re: Incident at Evesham 21/11/2012 Posted by Southern Stag at 01:02, 22nd November 2012 | |
Fire Brigade called to Evesham station, the 1944 Great Malvern-London Paddington terminating there. Not sure if it was the train or the station that required the Fire Brigade.
| Re: Incident at Evesham 21/11/2012 Posted by Chris from Nailsea at 00:17, 22nd November 2012 | |
FGW JourneyCheck merely offers
Line problem: between Oxford and Worcester Shrub Hill.
Owing to emergency services dealing with a prior incident between Oxford and Worcester Shrub Hill all lines are blocked.
Owing to emergency services dealing with a prior incident between Oxford and Worcester Shrub Hill all lines are blocked.
| Evesham station - services, footbridge, facilities, incidents and events (merged posts) Posted by trainer at 22:49, 21st November 2012 | |
To add to the chaos of the day NR Enquiries has posted cancellation of services until further notice between Oxford and Worcester. No tweets yet, they say (not that I'm on twitter anyway) so no details. Anyone in the area with more news?
| Re: Person hit by train near Evesham - 14 September 2012 Posted by Chris from Nailsea at 23:09, 20th September 2012 | |
From the Evesham Journal:
Man killed on railway named
An Evesham man died after being hit by a train on a level crossing near Evesham.
Jeremy Brown, aged 38, of Windmeres, Evesham, died as a result of multiple injuries and a massive cerebral trauma after the collision at the Littleton and Badsey CCTV controlled level crossing, between Honeybourne and Evesham.
Services on the Cotswold line were temporarily cancelled between London and Worcester, but were back up and running by 2.15pm.
A British Transport Police spokesman said: ^The incident was reported to BTP at 1.16pm and was also attended by officers from West Mercia Constabulary.
^Local paramedics attended and the body was located and [the man] pronounced dead at the scene. The incident is being treated as non-suspicious and a file will be prepared for the coroner.^
The train involved was the 11.20 London Paddington to Great Malvern service.
An inquest into the death of Mr Brown was opened and adjourned by the Worcestershire Coroner.
An Evesham man died after being hit by a train on a level crossing near Evesham.
Jeremy Brown, aged 38, of Windmeres, Evesham, died as a result of multiple injuries and a massive cerebral trauma after the collision at the Littleton and Badsey CCTV controlled level crossing, between Honeybourne and Evesham.
Services on the Cotswold line were temporarily cancelled between London and Worcester, but were back up and running by 2.15pm.
A British Transport Police spokesman said: ^The incident was reported to BTP at 1.16pm and was also attended by officers from West Mercia Constabulary.
^Local paramedics attended and the body was located and [the man] pronounced dead at the scene. The incident is being treated as non-suspicious and a file will be prepared for the coroner.^
The train involved was the 11.20 London Paddington to Great Malvern service.
An inquest into the death of Mr Brown was opened and adjourned by the Worcestershire Coroner.
| Re: Person hit by train near Evesham - 14 September 2012 Posted by Steve Bray at 23:32, 14th September 2012 | |
My Mum was travelling from Malvern to Heathrow this afternoon on the 1344 from Great Malvern, and ended up being routed via Birmingham to Euston. Had she got off at Shrub Hill, she could have taken the 1441 to Paddington. It seems that services were back up and running very quickly after this event compared with the usual several hours of delays that similar incidents create.
| Re: Person hit by train near Evesham - 14 September 2012 Posted by Chris from Nailsea at 22:40, 14th September 2012 | |
From the Evesham Journal:
Trains to and from London cancelled after man dies on level crossing near Evesham
A man has died after being hit by a train on a level crossing near Evesham.
The collision happened at the Littleton and Badsey CCTV controlled level crossing at 1.07pm today between Honeybourne and Evesham.
As a result all other services on the Cotswold line were temporarily cancelled but were back up and running at 2.15pm.
A British Transport Police spokesman said: ^The incident was reported to BTP at 1.16pm and was also attended by officers from West Mercia Constabulary. Local paramedics attended and the body of an as-yet-unidentified man was located and pronounced dead at the scene.
^Officers are currently working to establish the man^s identity. The incident is being treated as non-suspicious and a file will be prepared for the coroner.^
The train involved was the 1120hrs London Paddington ^ Great Malvern service.
A man has died after being hit by a train on a level crossing near Evesham.
The collision happened at the Littleton and Badsey CCTV controlled level crossing at 1.07pm today between Honeybourne and Evesham.
As a result all other services on the Cotswold line were temporarily cancelled but were back up and running at 2.15pm.
A British Transport Police spokesman said: ^The incident was reported to BTP at 1.16pm and was also attended by officers from West Mercia Constabulary. Local paramedics attended and the body of an as-yet-unidentified man was located and pronounced dead at the scene.
^Officers are currently working to establish the man^s identity. The incident is being treated as non-suspicious and a file will be prepared for the coroner.^
The train involved was the 1120hrs London Paddington ^ Great Malvern service.
| Re: Person hit by train near Evesham - 14 September 2012 Posted by Ollie at 16:44, 14th September 2012 | |
Unfortunately so, 11:20 Paddington to Great Malvern - this is the second fatality this week, and again it involved a class 180.
| Evesham station - services, footbridge, facilities, incidents and events (merged posts) Posted by TonyK at 16:34, 14th September 2012 | |
FGW report cancellation of the 15:22 Great Malvern to Oxford, and changes to other services involving Malvern. The reason is given as a person hit by a train.
| Re: A bad evening at Evesham (Fri Aug 31) Posted by CLPGMS at 23:28, 1st September 2012 | |
I was rather fortunate on 31st August as I travelled on the 1559 from WOF. This was the last up train to pass through Evesham before the signalling failure occurred. The 1421 PAD-WOF was the last down train.
From information on the internet, It appeared that the Adelante forming the 1551 PAD-WOS terminated at MIM and then formed, in effect, an 1806 return. This means that it was not available at Worcester to form its normal 1849 departure (Kingham's 1956).
The following down train (1732 ex OXF) was cancelled and extra stops inserted in the 1722 ex PAD. This was shown as terminating at MIM, presumably with the intention of returning to London in the path of the 1849 ex WOF. However, I was surprised to see on NREs that it had departed from MIM, even though shown as Cancelled for all of the following stations. A few minutes later, the message on JourneyCheck changed to reveal that the train was running through to Hereford, so the signalling problem had, at least to some extent, been overcome.
At this point, I ceased trying to figure out what was happening. However, there was a Turbo unit at Worcester (the one from the 1421 ex PAD) which could have provided one up service although either the 1849 ex WOF or the 1944 ex GMV would probably have had to be cancelled.
Can anyone please fill in the details?
| Re: A bad evening at Evesham (Fri Aug 31) Posted by stebbo at 21:19, 1st September 2012 | |
Went to collect my daughter and boyfriend from Kingham yesterday evening and the Cathedrals Express was scheduled to run through to Hereford. Arrived at Kingham about 10 minutes late. Don't know what happened although some of my daughter's friends from Hereford who were also on the train were hopeful of getting through.
On the London bound platform FGW advertised the cancellation of the 1956 service to Paddington and an elderly lady came over to Platform 1 to seek assistance of which there was no chance at that time of the evening. Whilst she was wandering around by the closed ticket office the platform indicator changed to show the train had been reinstated but as there was no announcement she didn't know until I pointed out that it might be worth going back to platform 2 and waiting. Don't know if she got the train or had to wait an hour or more - if it came it was late but by then she had several companions.
Centralised announcements (or lack of) are less than helpful if trains are disrupted.
Incidentally I see the toilets are locked at Kingham when there's no station staff but the local bus driver for the Chipping Norton bus has a key to access them.
| Re: A bad evening at Evesham (Fri Aug 31) Posted by Louis94 at 18:25, 31st August 2012 | |
Complete failure of all signalling at Evesham
| Re: A bad evening at Evesham (Fri Aug 31) Posted by Worcester_Passenger at 18:23, 31st August 2012 | |
JourneyCheck is reporting
Line problem: at Evesham.
Owing to signalling problems at Evesham all lines are blocked.
Impact:
Train services running through this station may be cancelled, delayed by up to 30 mins or diverted at short notice. An estimate for the resumption of normal services will be provided as soon as the problem has been fully assessed.
17:32 Oxford to Great Malvern due 19:23
This train will be cancelled.
This is due to signalling problems.
15:51 London Paddington to Worcester Shrub Hill due 18:08
This train has been delayed at Reading and is now 12 minutes late.
This train will be terminated at Moreton-In-Marsh at 17:38.
This train will no longer call at Honeybourne, Evesham, Pershore and Worcester Shrub Hill.
This is due to signalling problems.
17:22 London Paddington to Hereford due 20:27
This train will be terminated at Moreton-In-Marsh at 18:53.
This train will call additionally at Combe, Finstock, Ascott-Under-Wychwood and Shipton.
This train will no longer call at Honeybourne, Evesham, Pershore, Worcester Shrub Hill, Worcester Foregate Street, Malvern Link, Great Malvern, Colwall, Ledbury and Hereford.
This is due to signalling problems.
17:28 Worcester Foregate Street to London Paddington due 20:06
This train will be started from Moreton-In-Marsh at 18:06.
This train will no longer call at Worcester Foregate Street, Worcester Shrub Hill, Pershore, Evesham and Honeybourne.
This is due to signalling problems.
17:50 London Paddington to Worcester Shrub Hill due 20:03
This train will be terminated at Moreton-In-Marsh at 19:26.
This train will no longer call at Evesham, Pershore and Worcester Shrub Hill.
This is due to signalling problems.
19:44 Great Malvern to London Paddington due 22:39
This train will be started from Oxford at 21:32.
This train will no longer call at Great Malvern, Malvern Link, Worcester Foregate Street, Worcester Shrub Hill, Pershore, Evesham, Honeybourne, Moreton-In-Marsh, Kingham, Charlbury and Hanborough.
This is due to signalling problems.
Owing to signalling problems at Evesham all lines are blocked.
Impact:
Train services running through this station may be cancelled, delayed by up to 30 mins or diverted at short notice. An estimate for the resumption of normal services will be provided as soon as the problem has been fully assessed.
17:32 Oxford to Great Malvern due 19:23
This train will be cancelled.
This is due to signalling problems.
15:51 London Paddington to Worcester Shrub Hill due 18:08
This train has been delayed at Reading and is now 12 minutes late.
This train will be terminated at Moreton-In-Marsh at 17:38.
This train will no longer call at Honeybourne, Evesham, Pershore and Worcester Shrub Hill.
This is due to signalling problems.
17:22 London Paddington to Hereford due 20:27
This train will be terminated at Moreton-In-Marsh at 18:53.
This train will call additionally at Combe, Finstock, Ascott-Under-Wychwood and Shipton.
This train will no longer call at Honeybourne, Evesham, Pershore, Worcester Shrub Hill, Worcester Foregate Street, Malvern Link, Great Malvern, Colwall, Ledbury and Hereford.
This is due to signalling problems.
17:28 Worcester Foregate Street to London Paddington due 20:06
This train will be started from Moreton-In-Marsh at 18:06.
This train will no longer call at Worcester Foregate Street, Worcester Shrub Hill, Pershore, Evesham and Honeybourne.
This is due to signalling problems.
17:50 London Paddington to Worcester Shrub Hill due 20:03
This train will be terminated at Moreton-In-Marsh at 19:26.
This train will no longer call at Evesham, Pershore and Worcester Shrub Hill.
This is due to signalling problems.
19:44 Great Malvern to London Paddington due 22:39
This train will be started from Oxford at 21:32.
This train will no longer call at Great Malvern, Malvern Link, Worcester Foregate Street, Worcester Shrub Hill, Pershore, Evesham, Honeybourne, Moreton-In-Marsh, Kingham, Charlbury and Hanborough.
This is due to signalling problems.
That's a pretty drastic list.
NRES is reporting
Because of this, buses are replacing trains between Moreton-in-Marsh and Worcester Shrub Hill, with journey times extended by up to 30 minutes. This will continue until further notice.
Ticket Acceptance
Passengers may use their tickets on the following train operators until further notice:
CrossCountry services between Cheltenham Spa and Bristol Parkway
Arriva Trains Wales between Newport and Hereford
Not sure how using CrossCountry or ATW helps - using FGW via Swindon might be more useful, given that most of our tickets are only valid via Evesham.Ticket Acceptance
Passengers may use their tickets on the following train operators until further notice:
CrossCountry services between Cheltenham Spa and Bristol Parkway
Arriva Trains Wales between Newport and Hereford
| Evesham station - services, footbridge, facilities, incidents and events (merged posts) Posted by stebbo at 18:19, 31st August 2012 | |
Seems there's signalling problems at Evesham tonight and a lot of Worcester/Hereford services are being turned around at Moreton in Marsh
| Re: Evesham Booking Office Posted by Oxman at 00:14, 5th May 2012 | |
You don't know whether to laugh or cry!
Yes, Evesham is an FGW managed station, so the article is completely off the mark - LM's proposal's are irrelevant. What is more worrying is that the the TSSA rep doesn't seem to know this. Particularly surprising given that the the local union rep is based at Evesham. And to suggest that the closure of the ticket office might result in the closure of the station is blatant scaremongering.
They do themselves no favours.
| Re: Evesham Booking Office Posted by JayMac at 21:22, 4th May 2012 | |
I'd like to see London Midland try to close Evesham station's booking office. First Great Western might well have something to say about that, seeing as they manage it!
Poorly researched article.
| Re: Evesham Booking Office Posted by Btline at 21:14, 4th May 2012 | |
What a bewildering article. There must be a mistake.
Although the future of ticketing = fewer ticket offices
A more efficient railway with lower costs = fewer ticket offices
Perhaps if LM got their act together and started running a service to Birmingham (that would be hugely popular with A46 commuters), there would be more passengers and less of a call for the ticket office to be axed.
| Evesham station - services, footbridge, facilities, incidents and events (merged posts) Posted by Nottage_Halt at 20:19, 4th May 2012 | |
The local rag - "Evesham Observer" reports that TSSA is definite that the Booking Office at Evesham (currently open weekday mornings) is to be closed - by London Midland - and replaced by automatic ticket vending machines.
It's on Page 7 here:
http://www.eveshamobserver.co.uk/paper/
Any thoughts. I believed FGW was the operator of Evesham Station. And the closure sucks. Auto vending machine will be no substitute.
Nick
| Re: Call for action over dangerous crossing at Evesham Posted by Nottage_Halt at 20:09, 13th February 2012 | |
The crossing could be made a whole lot safer for vehicular traffic if the mahoosive pot-hole that's appeared within the Network Rail boundary on the Up (Littleton) side of the crossing was filled in. I've reported it to the County Council, but no improvement. I guess the CC don't speak to NR and vice versa.
| Re: Call for action over dangerous crossing at Evesham Posted by Buckham at 12:48, 13th February 2012 | |
Ran past the level crossing on Sunday. The damage to Ali Fould's shop was not as severe as the report implied - only one Window boarded up and everything else looked intact.
| Re: Call for action over dangerous crossing at Evesham Posted by ChrisB at 11:35, 11th February 2012 | |
Hnmmm, time to build a concrete catchment designed for over-the-limit teenagers. They'll get the message eventually. (tongue-in-cheek)
| Evesham station - services, footbridge, facilities, incidents and events (merged posts) Posted by Chris from Nailsea at 23:37, 10th February 2012 | |
From the Tewkesbury Admag:
Business owners have warned that someone could be seriously injured if driver^s continue to deliberately speed up in order to launch their car over a rail crossing near Evesham.
The warning comes after five teenagers were injured in a car that overturned and ended up on its roof outside Blackminster Business Park near Evesham on Wednesday last week.
The car, which smashed into a number of large wooden flower barrels ^ one flying into a nearby shop ^ lost control just after the rail crossing on Station Road, Blackminster.
The male driver and four female passengers were taken to the Alexandra Hospital in Redditch. One patient was treated for head and leg injuries and the remaining four were treated for minor cuts and bruises.
The front wall and windows of Interiors by Ali Foulds were seriously damaged.
Ali Foulds, owner of the shop, said: ^It was lucky we weren^t open and they are lucky to be alive. I don^t understand why they don^t put a speed trap up. People fly over the level crossing. Maybe they should consider reducing the speed limit.^
Ms Fould^s told the Journal about a similar incident. ^About six months ago another car lost control, hitting the hedge directly opposite the business park. A business there has since constructed a fence to protect its property.^
Paul Middleton, owner of Blackminster Business Park, heard the accident happen and told the Journal that cars often raced over the rail crossing.
He said: ^They are launching themselves over the level crossing and then losing control of their vehicle. This will happen again. I have seen the accident on CCTV. The car came over the railway line, straight down the road, hit the footpath and then the flower barrel. If he hadn^t hit the barrels who knows where he would have ended up.^
Police are investigating.
The warning comes after five teenagers were injured in a car that overturned and ended up on its roof outside Blackminster Business Park near Evesham on Wednesday last week.
The car, which smashed into a number of large wooden flower barrels ^ one flying into a nearby shop ^ lost control just after the rail crossing on Station Road, Blackminster.
The male driver and four female passengers were taken to the Alexandra Hospital in Redditch. One patient was treated for head and leg injuries and the remaining four were treated for minor cuts and bruises.
The front wall and windows of Interiors by Ali Foulds were seriously damaged.
Ali Foulds, owner of the shop, said: ^It was lucky we weren^t open and they are lucky to be alive. I don^t understand why they don^t put a speed trap up. People fly over the level crossing. Maybe they should consider reducing the speed limit.^
Ms Fould^s told the Journal about a similar incident. ^About six months ago another car lost control, hitting the hedge directly opposite the business park. A business there has since constructed a fence to protect its property.^
Paul Middleton, owner of Blackminster Business Park, heard the accident happen and told the Journal that cars often raced over the rail crossing.
He said: ^They are launching themselves over the level crossing and then losing control of their vehicle. This will happen again. I have seen the accident on CCTV. The car came over the railway line, straight down the road, hit the footpath and then the flower barrel. If he hadn^t hit the barrels who knows where he would have ended up.^
Police are investigating.
| Re: Line problem in the Evesham area - Sun 27 Feb 2011 Posted by ChrisB at 18:11, 8th March 2011 | |
The works cleared late afternoon
| Re: Line problem in the Evesham area - Sun 27 Feb 2011 Posted by Andypandy at 22:20, 27th February 2011 | |
20:10 Great Malvern to London Paddington due 23:13
This train will be terminated at Worcester Shrub Hill.It will no longer call at: Pershore, Evesham, Honeybourne, Moreton-In-Marsh, Kingham, Charlbury, Hanborough, Oxford, Didcot Parkway, Reading, Slough and London Paddington.This is due to a passenger having been taken ill earlier.
Last Updated: 27/02/2011 20:51
| Re: Line problem in the Evesham area - Sun 27 Feb 2011 Posted by Chris from Nailsea at 12:25, 27th February 2011 | |
An update, from FGW:
Line problem in the Evesham area.
Train services between Oxford and Worcester Shrub Hill are being disrupted due to over-running engineering works in the Evesham area. Engineers are working as fast as possible to restore services to normal. Short notice alterations and delays of up to 60 minutes can be expected.
Replacement road transport is in operation between Oxford and Worcester Shrub Hill in both directions calling at Oxford, Hanborough, Charlbury, Kingham, Moreton-in-Marsh, Honeybourne, Evesham, Pershore and Worcester Shrub Hill.
Last Updated: 27/02/2011 12:09
Train services between Oxford and Worcester Shrub Hill are being disrupted due to over-running engineering works in the Evesham area. Engineers are working as fast as possible to restore services to normal. Short notice alterations and delays of up to 60 minutes can be expected.
Replacement road transport is in operation between Oxford and Worcester Shrub Hill in both directions calling at Oxford, Hanborough, Charlbury, Kingham, Moreton-in-Marsh, Honeybourne, Evesham, Pershore and Worcester Shrub Hill.
Last Updated: 27/02/2011 12:09
| Evesham station - services, footbridge, facilities, incidents and events (merged posts) Posted by Chris from Nailsea at 12:00, 27th February 2011 | |
From FGW live updates:
Line problem in the Evesham area.
Train services between Oxford and Worcester Shrub Hill are being disrupted due to over-running engineering works in the Evesham area. Engineers are working as fast as possible to restore services to normal. Short notice alterations and delays of up to 30 minutes can be expected.
Replacement road transport is in operation between Oxford and Worcester Shrub Hill in both directions calling at Oxford, Hanborough, Charlbury, Kingham, Moreton-in-Marsh, Honeybourne, Evesham, Pershore and Worcester Shrub Hill.
Last Updated: 27/02/2011 11:39
Train services between Oxford and Worcester Shrub Hill are being disrupted due to over-running engineering works in the Evesham area. Engineers are working as fast as possible to restore services to normal. Short notice alterations and delays of up to 30 minutes can be expected.
Replacement road transport is in operation between Oxford and Worcester Shrub Hill in both directions calling at Oxford, Hanborough, Charlbury, Kingham, Moreton-in-Marsh, Honeybourne, Evesham, Pershore and Worcester Shrub Hill.
Last Updated: 27/02/2011 11:39
| Re: Evesham Emergency Engineering Works (20/02/2008) Posted by Btline at 20:16, 20th February 2008 | |
I wonder whether doulbe track could have helped this (eg trains recovering)?
Let me think?
Yes!!!!!!!!!!!!
| Re: Evesham Emergency Engineering Works (20/02/2008) Posted by Lee at 17:14, 20th February 2008 | |
Broken rail according to oxford Mail article by willc
Here are 2 willc article links regarding this.
http://www.oxfordmail.net/news/headlines/display.var.2058970.0.broken_rail_disrupts_trains.php
http://www.oxfordmail.net/news/headlines/display.var.2060236.0.rail_route_reopens.php
The route is now open, but trains are out of position.
| Re: Evesham Emergency Engineering Works (20/02/2008) Posted by IanL at 16:52, 20th February 2008 | |
Broken rail according to oxford Mail article by willc
| Re: Evesham Emergency Engineering Works (20/02/2008) Posted by devon_metro at 09:59, 20th February 2008 | |
Singnalling problems apparantly.
| Evesham station - services, footbridge, facilities, incidents and events (merged posts) Posted by Lee at 09:53, 20th February 2008 | |
Another emerging problem by the look of it :
Line problem in the Evesham area.
Train services between Moreton-In-Marsh and Worcester Shrub Hill are being disrupted due to emergency engineering works in the Evesham area.Engineers are working as fast as possible to restore services to normal. Short notice alterations, cancellations and delays of up to 60 minutes can be expected.
07:51 London Paddington to Great Malvern due 10:42
This train will be terminated at Moreton-In-Marsh.It will no longer call at: Honeybourne, Evesham, Pershore, Worcester Shrub Hill, Worcester Foregate Street, Malvern Link and Great Malvern.This is due to signalling problems.
09:37 Worcester Foregate Street to London Paddington due 11:58
This train will be started from Honeybourne.It will no longer call at: Worcester Foregate Street, Worcester Shrub Hill, Pershore and Evesham.This is due to signalling problems.
