The man who lived battles survivor's guilt
Minutes later, the plane plummeted into the BJ Medical College hostel and mess in Meghaninagar, killing 241 people on board, including Ajay. Only Viswash lived. Now back in his hometown of Bucharwadi in Diu, survival offers him no comfort. The 40-year-old businessman from Leicester reportedly battles sleeplessness. He barely speaks as he drifts through the days, lost in grief, questions and survivor's guilt.
Though back with family, Viswash remains haunted by what he lived through, and more so, by who didn't.
"He keeps asking: why only me? If I lived, why not my brother and the others?" shares Sunny Ramesh, youngest of the four siblings. The survivor's trauma runs deep. Sunny says Viswash has been "unable to sleep" since the tragedy. "How can anyone sleep if their younger brother dies like this? When Viswash realized that he had survived, he thought that Ajay must have made it too.
He was shattered when he found out that he was the sole survivor.
He is having a tough time accepting this fact," he adds.
Even as his miraculous survival made global headlines, the family has shielded him from visitors and media, avoiding talk of the crash. "We avoid asking questions about the plane crash due to his mental state. He's not ready for questions so we have kept him away from others. Right now, our only goal is to help him heal," Sunny said. When the plane crashed, Viswash was the only person who got thrown from the emergency exit window.
And by sheer chance, he landed on a mound of soil deposited near the hostel building for construction work.
You Can Also Check:
Ahmedabad AQI
|
Weather in Ahmedabad
|
Bank Holidays in Ahmedabad
|
Public Holidays in Ahmedabad
While Viswash's body survived, his mind remained trapped in that moment, says Sunny. "He is unable to forget those harrowing moments in which he lost Ajay. He is also haunted by the deaths of the other passengers," he adds. Meanwhile, police have not yet taken Viswash's statement, and Sunny says his brother will not be in any condition to provide one until he has fully recovered, both mentally and physically.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Time of India
a day ago
- Time of India
Viral Video: New footage of UPS 747-8F engine pod strike during landing at Taiwan International Airport surface
Months after the Air India flight AI171, Boeing 787-8, crashed into a medical college hostel in Ahmedabad, India, another footage of a UPS Boeing 747-8F surfaced on social media, experiencing an engine pod strike during landing at Taiwan Taoyuan International Airport (RCTP) on Wednesday. Since the clip surfaced online, it quickly went viral and started making the rounds on the internet. A UPS Airlines Boeing 747 8 freighter had a dramatic landing in Taiwan yesterday after departing from Hong Kong International Airport (HKG). While attempting to land at Taipei Taoyuan International Airport (TPE), the aircraft experienced an engine pod strike, sending a burst of sparks into the night sky. The impact caused visible damage to the engine pod. The incident happened during the plane's third landing attempt, as strong, gusty winds created extremely difficult conditions for the crew on Wednesday night. UPS Airlines flight 5X61 faced an engine damage issue; the video went viral According to Simple Flying, UPS Airlines flight 5X61 is a regularly scheduled cargo flight that starts in Hong Kong. While its final destination is Muhammad Ali International Airport (SDF) in Louisville, Kentucky, it has stops en route in Taipei and at Ted Stevens Anchorage International Airport (ANC) in the US federal state of Alaska. This airline uses both Boeing 747-400F and 747-8F cargo aircraft on this long route. On Wednesday, the flight left Hong Kong at 17:50 local time and was in the air for two hours and 20 minutes, around an hour longer than normal. Initially, because of the strong gusting winds prevailing in Taipei, the aircraft had to make three approaches before making a successful landing. However, during the landing, the aircraft's number four engine, located on the outer right wing, made contact with the runway, causing a burst of sparks to fly into the air. New footage of a UPS Boeing 747-8F experiencing an engine pod strike during landing at Taiwan Taoyuan International Airport (RCTP).📸 by Jal_kana Viral video shows the dramatic damage to the aircraft The viral video shows how challenging the weather conditions were for aircraft landing in Taipei the previous night. According to the Aviation Safety Network, the windshear affecting the area during the incident was linked to Typhoon Podul. The severe weather conditions significantly disrupted airport operations in Taipei. Data from Flight Aware revealed that a total of 180 departures and 141 arrivals were delayed on the same day. However, the dramatic nature of the aircraft's touchdown has left netizens in shock. Netizens react to the viral aeroplane video As soon as the video surfaced on the internet, it quickly went viral and grabbed attention. One X (formerly called Twitter) user wrote, "That looks like a very strong crosswind!" "Totally, looks like the pilots tried to save left side but hit the right engine," another added. "Tough !!!! Whatever it came down on its wheels so good job" "Is that just crosswinds or a control surface jam (rudder stuck?)" To stay updated on the stories that are going viral, follow Indiatimes Trending.
Time of India
a day ago
- Time of India
Snake enters car and is rescued near Amloh road in Ludhiana
Representative image LUDHIANA: There was a commotion after a snake suddenly entered the car of a bank manager near Amloh Road on Wednesday afternoon. As per reports, Bank Manager Hardeep Singh parked his car near Amloh Chowk on GT Road and was busy working inside the bank when, at the same time, Ajay , who owns a nearby tea shop, saw the snake entering the car. Reports suggest that Ajay immediately informed the manager. As soon as the news spread, some people tried to get the snake out, but it did not come out. After this, the rescue team was called. Manik Kapoor, in charge of the rescue team, pulled out the snake after much effort. "The snake that entered the car was 4 feet long." Manik said that if the snake was not removed on time, it could have been a bigger danger. A rescue team member said that the snake was hiding in the overgrown grass near the bank on the highway and entered the car in search of a safe place. He added that after several hours of effort, the snake was caught and would be released safely in the forest. Manik Kapoor appealed to people that due to the reduction of forests, animals are coming to human settlements, so check carefully before getting into a vehicle. He added that if bitten by a snake, one should go to the hospital immediately and seek medical help. Manik said that during rainy days, snakes often enter vehicles, houses, or shops in search of a dry and warm place. He advised people not to ignore any suspicious movement and to seek expert help immediately. Meanwhile, the bank manager breathed a sigh of relief and thanked the rescue team. Stay updated with the latest local news from your city on Times of India (TOI). Check upcoming bank holidays , public holidays , and current gold rates and silver prices in your area. "Get the latest news updates on Times of India, including reviews of the movie Coolie and War 2 ."
Indian Express
2 days ago
- Indian Express
Pilots were blamed until computer issue was found: US aviation attorney on his previous cases
Mike Andrews, Principal Attorney at US law firm Beasley Allen concluded his second visit to Gujarat during which he met several victim families of the AI 171 crash in Vadodara, Surat, Diu and Ahmedabad. With contracts signed with the firm, over 80 families who lost loved ones in the Boeing 787 8 crash will seek raw data to understand what could have led to the crash. In an exclusive interview with The Indian Express, Andrews talked about similarities between the AI 171 crash and past such cases, takeaways from the crash site, and more. Excerpts: Similarities with earlier cases In the earlier instances, if something went wrong, the pilots were blamed. Until it was determined that it was a computer issue. In the July 25 Munich flight that had an engine failure, it came back and landed. They all survived, no one blamed the pilot. On July 31, a flight left from Los Angeles to Santiago and the RAT (Ram Air Turbine) deployed right after takeoff. That's never supposed to happen unless there's a failure of some sort. And we've been told that there are some very specific parameters that would call for the RAT, the failure of both engines, which is an exceedingly rare-Hydraulic failure, electrical failure. That plane circled long enough to dump a lot of fuel… came back for landing, and everyone was safe. They did not blame the pilots. They survived. In the 2019 case of Tokyo to Osaka (Boeing 787 Dreamliner) All Nippon Airways, just as the plane is about to land, it lost both engines. The plane landed. They were safe, no one was killed, the pilots were not blamed. Because the pilots survived. And critically, in that incident, from the flight data recorder (FDR) the digital record, not the cockpit voice as the digital record is really what matters, it was revealed that the TCMA system (Thrust Control Malfunction Accommodation system) malfunctioned. So the question we've had consistently is we know that there's a computer problem. Was it the same thing here? Because if it happens in reverse, if it happens on takeoff, you get this situation. You have a loss of engines and you have the inability to gain altitude thrust and power. You have a crash. That's what happens. RAT deployment issue It was almost simultaneous with the take off. That's a big question for us, because the timeline that we can get from the flight data recorder is very specific. When the weight of the airplane is on the landing gear, there's a switch that's depressed. When the plane takes off, the weight comes up, the gear drops, and the switch goes off. It knows at least that landing gear is off the ground, and there's a switch in the front gear and in both of the main gears. The computer is recording that. We think the RAT deploys almost immediately after that switch is initiated, when it begins to take off. And so that is critical for us because, again, we've been told that the RAT only deploys if you have failures. So what caused the RAT to deploy? We've heard the narrative that focusses on pilot error here on the switches. It's important to remember how a switch works. So the computer in this plane is looking at the current that is flowing. There's no camera on the switch. There's nothing that is looking at and saying, 'Oh, the switch moved. There's also not something that's called a proximity sensor. There's not one of those on one of these switches either. So it doesn't know if the bottom part is moved or the top part of it. It doesn't know either. So the question becomes, was the switch actually moved, or did the current change? Because the computer is going to register that one way or the other. Now, is the computer smart enough to know that the switch has not moved, that it's just a current change? That is why you can't take it out of context. And so the context of exactly what happened here around the comments that are made, around the switch changes, around the timing of the RAT deployment– that's the real story. The more out of context, the more pinpoint you take the data, the less of the truth you get. On meeting the lone survivor Vishwash Kumar in Diu I went there to see him not as an attorney. We went to his home, we met the parents, saw the home, and as we were there talking, they sort of made an indication, if we would like to meet him. Which is completely unexpected. And I asked no questions, and I gave him my word that any communication would be private. And so anything that was said or not said during that, it was a very brief interaction, will always be private. Even with the language barrier, you can read people. This is a humble family. These are hardworking people. Again, the last folks who ever thought that anything like this would ever happen. Because not only is he a survivor, he's a victim. And they lost another family. It was a very profound experience… Instance of findings in an air crash case changing after the law firm's intervention I can give you some vague information, because in cases that are resolved, there's confidentiality involved in those. There was a crash, a body was in the water for a period of time. It was brought up several days after the crash and the postmortem was done based on only the information that was had at the time. The facts of the crash were only known towards the end because the medical examiner is not really concerned with aircraft aviation. Sometimes, they don't even know what happened. They just want to know what happened to the body. So the family got us involved, and this was a smaller aircraft. We took possession of the salvage of the wreckage, and hired our experts to examine what happened, and how it happened. And we learned that this aircraft had a malfunction in the oxygen system on board. And so this pilot became oxygen deprived as he took off. So this guy was in a plane that was going up to about 24,000 feet where the oxygen concentration is reduced. When we fly commercially, when you get up, there's a pressurised cabin, it's providing oxygen. This had a little bit different system. When you are becoming hypoxic, you just generally kind of get sleepy. Well, that happened to him (the pilot) right after takeoff. And he had a full tank of fuel. And so the plane flew for a long way…He's alone for the ride. It continued to go until it ran out of fuel just off the coast and crashed in the water. So the initial finding was crash-related. But because of our work, we were able to go back and show the medical examiner and show the authorities, the investigating agencies…that look– We're just saying you didn't have all of the information at the time. Here's what we learned. And because of that, the findings, which were not complete, were changed. And because of that, the family then knew that it wasn't a pilot error. They knew that it was an equipment problem. Visit to the crash site in July and after exactly two months The first time we were there, there was still a big police presence. It was cordoned off at the main intersection. And we were escorted by the police to the bottom end of the accident site. Later I learned, when I went back and looked at my photographs, we were standing at the exact spot where the survivor walked out. From that perspective, we could see the burned buildings, the burned trees.. There was rubble. It was still, it was really quiet in that area. That stillness and the fact that there were no people there in itself speaks of something awful that happened, in an area where typically, you would see a lot of people. So that's one of the first takeaways. Last night, the street was open. Now the area has been largely cleaned up, at least in the roadway. They're still dealing with all the debris. The area has come back to life. There's traffic going around the curve right there. But there's still a lot of cleanup and a lot of rebuilding, a lot of work to do there. Very, very different feeling… being there with a large group of families. Some of them were telling me at the time, 'This is our first time coming to the scene and there were a lot of emotions in that group, you know, one of them was telling me, 'This is the first time I am seeing the place where my husband was killed'. And I mean, that's powerful to hear somebody say that. I don't think that's a thing like healing or closure. You've got a new normal that you're dealing with, your timeline has changed. You're not ever going to get back to that person again. And you shouldn't be, because it matters. The loss…the people… the life matters. . You're not moving on. You're moving through. Grief is not linear. It is not the same every day. It is going to be good and bad and middle and awful and great, it's an up and down mix. And so they need that group to rely upon from a psychological perspective.
