Latest news with #Flightradar24.com
The Print
2 days ago
- General
- The Print
‘More careful than colourful'—ThePrint's reporting on the Air India crash put facts first
This Readers Editor column considers ThePrint's approach to its reporting on AI-171 and the subsequent preliminary findings of the investigation by the Aircraft Accident Investigation Bureau (AIBB) released on 12 July 2025. When you're reporting on something as devastating, sensitive—and immediate—as the Air India-171 crash last month, it is crucial to remember the value of good journalism, amid the endless theories on the reasons for the accident. Good journalism requires good hygiene. That means you have to write clean copy and provide the audience with a clear picture of the events you report. You have to cut out all the frills, the speculation, the 'extras'—which might make your reporting more lively and interesting to read, but don't always give readers accurate, factual, verified information. ThePrint's coverage was descriptive but factual and based on reliable sources. When you go through the articles or watch the videos, you will notice that the reporters are being selective in their choice of words. After reading or watching most of the reporting, I'd say it was more careful than colourful. The day of crash The afternoon of 12 June was just another normal day at ThePrint. I remember that it was a Thursday because I was at ThePrint's office in New Delhi for my weekly meeting with colleagues. It was fairly quiet as afternoons go, with reporters out on assignments, and those in the office staring at the computer monitors or mobile phones. Suddenly, it came to life. I saw people rush to watch the television monitors, and as I joined them, I beheld a sea of serious faces around me. The AI-171 had crash-landed at Ahmedabad airport. Nisheeth Upadhyay, Editor News Operations, realised it was huge. 'Whenever a commercial flight crashes it is a huge deal. We knew this was a big story.' The immediate response was to put out a 'Breaking News' story with the little information available. Next was to check for an accurate reading of the flight's movements up to its fall to the ground. Since I don't work on the editorial side of operations at ThePrint, I began to feel a little redundant, and in people's way. So, I sat on the sidelines and watched. A quick edit meeting was convened and everyone present in the office came together to suggest immediate story ideas. 'We felt, instinctively, that we should report the news as it came through and could be confirmed, but also do stories that added value,' Upadhyay said. 'From the moment it happened, there was so much noise in the media and social media—everyone was playing expert. 'At ThePrint, we were clear: Be sensitive, give the information, don't analyse—just plain, simple facts and information that can be confirmed. No conjecture.'' The difficulty that arose was the lack of access to the facts of the accident—or to any immediate information from the site of the crash in Ahmedabad—ThePrint doesn't have its own correspondent in the Gujarat capital. In stepped, Rama Lakshmi, Editor, Opinion and Ground Reports, and her team to fill the void. 'We had to keep reader interest going,' said Lakshmi. She also had previous experience covering airplane crashes, which helped. 'I put on my reporter's cap and looked for different angles to the story until our reporters reached the accident spot,'' she added. The reporters in the Delhi Ground Reports team filed reports on past history and the context of the incident. From other commercial flight crashes in India and Air India's current fleet of aircraft, accounts of survivors in Ahmedabad, stories of people who suffered in similar plan crashes, to another sole survivor of an air crash, the revamp of Ahmedabad runway, and the last social media post of some victims—these were some of the early stories put out by ThePrint. Interviewing victims & tackling misinformation The most pressing concern was to get on-ground reporting from Ahmedabad. ThePrint's nearest reporting team was in Mumbai. 'We were unsure of flights taking off from Mumbai and being able to land in Ahmedabad,' recalled Manasi Phadke, Deputy Editor based in Mumbai, who reached the city the next morning. Luckily, the Delhi-Ahmedabad evening flight was on schedule, so National Photo editor Praveen Jain and Senior Correspondent Krishan Murari flew out. 'I have covered earlier air crashes—Charkhi Dadri, for example. So I knew what it was like on the ground,' said Jain. In 1996, a midair collision between two commercial aircraft over Charkhi Dadri outside Delhi killed 349 people. Krishan Murari had never reported on an air crash or any accident of this proportion. He'd reported on Operation Sindoor and the Pahalgam terrorist attack in May. AI-171 presented a different challenge. 'After Operation Sindoor, coming to this, I realised you need a completely different kind of vocabulary. You have to be far more sensitive. I'd call it compassionate journalism,' he said. Praveen Jain and Krishan Murari reached Ahmedabad within 12 hours of the crash and visited the site, the hospital, and the mortuary. 'It was very hot outside, and even inside, the temperature was higher than it should have been. There was an overwhelming smell of the charred bodies,' Murari added. Together, they filed a number of stories over the next few days. Here are some of them: Meet the forensic dentist racing against time so kin of Air India crash victims can say final goodbye Air India crash: Inside Ahmedabad hospital morgue, bodies await DNA ID as doctors race against heat, time Confusion, debris & bodies at Air India crash site. Rescue worker first thought it was cylinder blast Air India crash: All 4 hostel buildings of BJ Medical College emptied amid site investigation This Air India crash eyewitness cheated death by a whisker—'a blast, then a fireball, just 200 m away' Manasi Phadke found the lack of official information to be one of the major stumbling blocks in her first few days of reporting. 'The media was the least important for them, so we had to source information wherever we could,'' she said, 'We had to be very careful, not speculate.' So, she had to piece together information. Here are some of the stories she filed: 11 DNA matches 48 hrs after Air India crash: Process of releasing victims' bodies to families begins The crash, the rescue & aftermath—Inside the first 36 hours at ground zero of Air India crash Behind the scenes of Gujarat's Air India crash response—4 IAS officers, 36 DNA experts & 230 teams Medical college's exam hall turns into DNA sampling centre. For victims' kin, it's the longest test yet After a week's search, family working in hostel mess cremates mother & 2-yr-old killed in Air India crash Phadke, Jain and Murari turned to doctors, workers, and the families of the victims. 'Families presented a challenge, a lot of them were angry. You can't just walk up to them and say, 'Kya hua?'. 'We had to be sensitive—I didn't use the camera immediately—I waited till they were at ease,' recalled Praveen Jain. As far as possible, he tried to click pictures from a distance. Even, then, one family member of a victim scolded him for taking pictures and Jain immediately apologised. Phadke said she had to make people feel comfortable before they spoke. Some like to speak – 'I am still in touch with at least one relative,' she said, adding, 'You have to talk around the subject, be conversational.' Also read: Inside ThePrint's mailbox—readers bring us praise, critique, and everything in between Unpacking investigation report Back in Delhi, Bismee Taskin, Principal Correspondent, was keeping an eye out for government communications. 'My job was to get in touch with the DGCA, the civil aviation ministry. To confirm information, verify it with at least two reliable sources,' she explained. She was also in touch with former pilots of Air India. When the preliminary report was released on 12 July, she reported it. 'Preliminary report is like an FIR,' said Taskin, 'No conclusions should be based on it. You have to wait till the final report for probable cause.' Taskin's stories, therefore, were straightforward, simply putting out what the report stated. Have a look: Air India crash spotlights 2018 advisory on Boeing switches installed with locking feature disengaged Air India crash preliminary report: A look at what fuel switches are designed to do & built-in safeguards Throughout the last month and a half, victims' families, aviation experts and the average reader want to know what brought the aircraft down? Why did it crash? There are so many technical details to it—and a lay person, with no understanding of them was prey to various theories doing the rounds. Nisheeth Upadhyay is, in his own words, an 'aviation nut''. Thus, it was possible for him to understand the complex (mal)functioning of an aircraft and to explain it in simple language. 'I was very careful not to act as an authority on the subject, just to describe what we knew had happened and to explain,'' he said, 'No aviation experting.'' On the preliminary report, which led to so much speculation and finger-pointing to pilot error in some foreign news media such as the Wall Street Journal, Upadhyay said only the final report mattered: 'There is not enough evidence to attribute blame. And so, ThePrint's line was that—there's not enough information to reach a conclusion.' I would recommend you watch his videos: they are clear, concise, and to the point, factual—without unnecessary opinion or speculation. I know I learned a great deal from them. The common thread in ThePrint's reporting—from the ground and Delhi—was to keep it simple, stick to verified facts and attribute views clearly. I have one suggestion newsrooms like ThePrint could consider: After tough assignments in the field, reporters may need some assistance in dealing with the traumas they witness. It can be overwhelming, especially for young reporters. Counselling is one option, and a few days' leave may help them cope better. Shailaja Bajpai is ThePrint's Readers' Editor. Please write in with your views and complaints to (Edited by Ratan Priya)
Indian Express
17-07-2025
- Indian Express
Imphal-bound IndiGo flight returns to Delhi due to technical snag
An IndiGo aircraft enroute to Imphal returned to the national capital on Thursday morning due to a technical snag after being airborne for an hour. 'A minor technical snag was detected soon after take-off on flight 6E 5118 operating from Delhi to Imphal on 17 July 2025. As a precautionary step, the pilots decided to turn-back and landed safely at Indira Gandhi International Airport, Delhi,' the airline said in a statement. In line with the mandatory procedures, the aircraft underwent necessary checks and resumed the journey shortly thereafter, IndiGo said and regretted the inconvenience caused to the passengers. According to information available with flight tracking website the A321 aircraft operating the flight 6E 5118 was airborne for an hour before it returned to Delhi.
The Hindu
17-07-2025
- The Hindu
Imphal-bound IndiGo plane returns to Delhi due to technical snag
An IndiGo aircraft enroute to Imphal returned to the national capital on Thursday (July 17, 2025) morning due to a technical snag after being airborne for an hour. "A minor technical snag was detected soon after take-off on flight 6E 5118 operating from Delhi to Imphal on 17 July 2025. As a precautionary step, the pilots decided to turn-back and landed safely at Indira Gandhi International Airport, Delhi," the airline said in a statement. In line with the mandatory procedures, the aircraft underwent necessary checks and resumed the journey shortly thereafter, IndiGo said and regretted the inconvenience caused to the passengers. According to information available with flight tracking website the A321 aircraft operating the flight 6E 5118 was airborne for an hour before it returned to Delhi.
Daily Mirror
16-07-2025
- Daily Mirror
Passengers 'cause huge delay with attempt to enter cockpit over aircon fury'
A SpiceJet captain was forced to take the Boeing 737 back to the terminal during a scheduled flight from Delhi to Mumbai, India, the airline said in a statement Two unruly passengers caused a seven-hour flight delay after allegedly attempting to get into the cockpit of a plane, it was claimed. The pair is accused of making their attempt while the aircraft was taxiing for departure on Monday. Cabin crew and passengers pleaded with them to return to their seats, the airline said in a statement. The captain was forced to take the Boeing 737 back to the terminal, as reported by Luxury Travel Daily. The jet was travelling from Delhi to Mumbai, India. A video taken inside the cabin has gone viral, with passengers heard complaining about the delay. "You cannot stop a plane like this; this is illegal," one passenger is heard saying. From the rear of the cabin another passenger says "AC chala de, hum baith jayenge", which translates as "switch the AC on, we will sit down", according to India Today. Several passengers are then heard asking the cabin crew to summon CISF security and remove the disruptive flyers. "Those who don't want to go, make sure they get down," says one of the passengers. The SpiceJet flight, originally scheduled to depart at 12.30pm from Indira Gandhi International Airport, was delayed until 7.21pm, according to data from flight tracking service A spokesperson for the airline said: "Two unruly passengers were offloaded from SpiceJet flight SG 9282 operating from Delhi to Mumbai. The two attempted to forcefully approach the cockpit and caused a disruption while the aircraft was taxiing. "Despite repeated requests by the cabin crew, fellow passengers, and the Captain, they refused to return to their seats. In the interest of the safety of all passengers and crew, the Captain decided to return the aircraft to the bay, and the passengers were offloaded. They were subsequently handed over to the CISF." The airline said the decision to return to the terminal was made in the interest of passenger and crew safety. No injuries were reported. The issue of passengers delaying plane departures is not new, but it certainly causes airlines a huge amount of grief. Even small disruptions can lead airlines to miss departure slots, pushing back their eventual take-off times significantly. Thanks to the compensation rights of passengers and airport fees, such delays can land plane operators with big bills. Back in 2023, an Indian man travelling from New York to Delhi allegedly urinated on a co-passenger on an American Airlines flight, NDTV reported. A similar incident had taken place in 2022 when a drunk man allegedly urinated on an elderly woman in the business class of an Air India flight.
The Hindu
15-07-2025
- The Hindu
Two SpiceJet passengers try to enter cockpit forcefully, offloaded at Delhi airport
Two unruly passengers were offloaded from a SpiceJet flight at the Delhi airport on Monday (July 14, 2025) after they attempted to forcefully enter the cockpit when the aircraft was taxiing. SpiceJet said the aircraft, which was to fly to Mumbai, returned to the bay and the two passengers were offloaded and later handed over to the CISF. "On July 14, 2025, two unruly passengers were offloaded from SpiceJet flight SG 9282 operating from Delhi to Mumbai. "The two attempted to forcefully approach the cockpit and caused a disruption while the aircraft was taxiing," the airline said in a statement. According to SpiceJet, despite repeated requests by the cabin crew, fellow passengers, and the captain, the two passengers refused to return to their seats. The flight SG 9282, originally scheduled to depart at 12.30 p.m., departed at 7.21 p.m., as per information available on flight tracking website
