logo
Final probe shows rail flaw detection delay caused North-East Express derailment, ET Infra

Final probe shows rail flaw detection delay caused North-East Express derailment, ET Infra

Time of India19 hours ago

Advt
Advt
By ,
PTI
The failure to promptly detect the flaws in the rail caused the derailment of the North-East Express at Raghunathpur Station in Danapur Division of East Central Railway on October 11, 2023, according to a final investigation report.At least four people were killed and several others were injured in the accident in Bihar's Buxar district.The report was submitted by Suvomoy Mitra , the then Commissioner of Railway Safety (Eastern Circle)."Stricker monitoring should be exercised in controlling the various processes involved in manufacture of rails. Railway may consider exploring possibilities of Real Time Monitoring of the health of track, one of the recommendations of the report recently submitted to the Railway Board," it added.The Railways in its action taken report said that continuous improvement and upgradation are being done by it and the rail manufacturing plant of SAIL/Bhilai for ensuring better quality of steel making and rail rolling.It mentioned several steps taken to improve the chemical and metallurgical properties of rails too.Regarding proper monitoring of track health, it said that various modules in the Track Management System (TMS) are operational."These include monitoring of USFD (Ultrasonic Flaw Detection) testing of rails and welds. USFD operators regularly feed the USFD testing data of rail and weld during daily USFD testing on TMS," the Railways said."These USFD testing data are monitored regularly at all concerned levels for necessary maintenance," it added.Addressing the concern of the CRS for real-time monitoring of the health of tracks, the Railways said that three technologies are under trial for broken rail detection systems in various zonal railways.These are the Continuous Broken Rail Detection System (NGRT), which is under trial in North Eastern Railway, Acoustic Domain Technology Rail Acoustic, which is undergoing testing in North Central Railway and Vibration Energy-based Broken Rail Detection System whose trial is in progress in North Central Railway.The CRS has further recommended that proper mechanisms should be available with the Railways for the identification of fatigue cracks developed in rails.The Railways has said that it has come up with a new technology known as Phased Array Ultrasonic Single Rail Tester (PAUT SRT) and Zonal Railways/ PSUs have been advised for the adoption of this new method for rails testing.Commenting on the condition of the engine and coaches, the CRS said that the locomotives and coaches of all running trains should be closely examined and defective rolling stock should not be permitted, more so in Mail Express Trains with high speed."Records of maintenance of Coaches and Loco may be computerized similar to what has been done for Track Monitoring System (TMS) so that the data can be readily accessed for analysis and scrutiny," the probe body said.In response, the Railways said that they already have a laid-down procedure to regularly examine all coaches.The CRS also advised the Railways to consider installing a Cab Voice Recorder in the Loco to record the conversation between the crew during/just before any accident."Crew Voice and Video Recording System (CVVRS) is installed in 479 locomotives and is under implementation by CRIS in all locomotives," the ministry said in its response.The CRS emphasised on the need for formal training or guidelines for videography and photography of the accident site, including drone camera of locomotive, coaches and track.The Railway Ministry said that guidelines for videography and photography at the accident site have already been issued by various orders.

Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

Ahmedabad plane crash: Not emergency contacts, most flyers had listed own numbers
Ahmedabad plane crash: Not emergency contacts, most flyers had listed own numbers

Time of India

time3 hours ago

  • Time of India

Ahmedabad plane crash: Not emergency contacts, most flyers had listed own numbers

Ahmedabad plane crash (Photo: PTI) AHMEDABAD: When tragedy strikes, the smallest gaps in systems become painfully visible. As volunteers at the help desk raced to notify families after the AI 171 crash, they hit an unexpected wall. Most calls were met with an eerie silence. The reason: in most of the cases, the only number provided was the passenger's own. With phones lost in the wreckage and no alternative contacts available, authorities scrambled to locate the next of kin. This delayed delivery of the news complicated the coordination of support. "This was a huge challenge," a senior official involved in the communication efforts said. "In nearly 70% of the cases, we found the only number listed was that of the passenger. When we tried to contact kin, the calls went unanswered." Since the tragedy made headlines, many relatives came forward on their own looking, the official added. In the absence of emergency numbers, authorities had to rely on local administration officials. "We contacted collectors and got them to visit the listed addresses to inform relatives."

‘Normal occurrence of diversion by F-35B': IAF on British jet emergency landing at T'puram airport
‘Normal occurrence of diversion by F-35B': IAF on British jet emergency landing at T'puram airport

The Print

time5 hours ago

  • The Print

‘Normal occurrence of diversion by F-35B': IAF on British jet emergency landing at T'puram airport

In a late night post on X, the IAF also shared a photo of the fighter jet, and said it is 'providing all necessary support for the rectification and subsequent return of the aircraft'. The jet was operating from UK Aircraft Carrier, HMS Prince of Wales, and it was undertaking 'routine flying' outside Indian ADIZ (Air Defence Identification Zone), according to the IAF. New Delhi, Jun 15 (PTI) A day after a British F-35B fighter jet of the Royal Navy made an emergency landing at Thiruvananthapuram International Airport, the Indian Air Force (IAF) on Sunday said it is 'fully aware' of it and facilitated the aircraft for flight safety reasons. Earlier in the day, sources said the British aircraft made the emergency landing at the Kerala airport after running low on fuel. The jet landed safely at around 9.30 pm on Saturday, they said. The IAF on Sunday said it is 'fully aware' of it. 'A normal occurrence of diversion by F-35B. The IAF is fully aware and facilitated the aircraft for flight safety reasons. All assistance being given, and the IAF is in coordination with all agencies,' an IAF spokesperson said in a brief statement. The aircraft is currently parked at the airport. The IAF in its post on X also said, 'A Royal Navy F-35B fighter recovered off an emergency landing at Thiruvananthapuram International Airport on the night of 14 June 25.' 'Operating from UK Aircraft Carrier, HMS Prince of Wales, it was undertaking routine flying outside Indian ADIZ with Thiruvananthapuram earmarked as the emergency recovery airfield. On having declared a diversion off an emergency, the F35B was detected and identified by the IAF's IACCS network and cleared for the recovery,' it added. PTI KND KVK KVK This report is auto-generated from PTI news service. ThePrint holds no responsibility for its content.

British Airways Chennai flight returns to London mid-air due to technical snag
British Airways Chennai flight returns to London mid-air due to technical snag

The Print

time5 hours ago

  • The Print

British Airways Chennai flight returns to London mid-air due to technical snag

The development comes days after an Air India Boeing Dreamliner crashed in Ahmedabad killing 241 passengers and crew members on board. The flight landed safely with crew and passengers disembarking as they normally would, British Airways said in a statement. Mumbai, Jun 15 (PTI) A Chennai-bound British Airways Boeing Dreamliner returned to London due to a technical snag on Sunday. The airline, however, did not share other details such as the departure time of the flight, the number of passengers and crew on board and for how long the aircraft remained airborne before it returned to London. 'The aircraft returned to Heathrow as a standard precaution after reports of a technical issue,' British Airways said. However, as per the live flight tracking website British Airways flight BA35 was scheduled to depart at 1240 pm and had to arrive in Chennai at 3.30 am. It departed from London Heathrow at 1.16 pm but left after a delay of over 35 minutes. The flight BA35 operated with a Boeing 787-8 remained airborne for nearly two hours before returning to London Heathrow, according to data from The aircraft remained in multiple holding patterns before returning to Heathrow Airport, as per the website. 'Our teams are working hard to get their journeys back on track as soon as possible. Meanwhile, a Hydrabad-bound Lufthansa flight from Frankfurt also made an air turnback to Frankfurt on Sunday, as per However, the reason for its diversion back to Frankfurt was not known. Flight LH 752 operated by a Boeing 787-9 Dreamliner aircraft departed from Frankfurt at14.29 instead of its scheduled departure time of 13.05 pm, The flight was to arrive in Hyderabad at 1.20 am, as per the website. PTI IAS HIG This report is auto-generated from PTI news service. ThePrint holds no responsibility for its content.

DOWNLOAD THE APP

Get Started Now: Download the App

Ready to dive into the world of global news and events? Download our app today from your preferred app store and start exploring.
app-storeplay-store