IndiGo Flight 6E-451 Returns to Bengaluru After a Handwritten Hijack Threat Note Is Found in the Toilet

Introduction

A routine evening flight from Bengaluru to Lucknow turned into a full airport emergency on Saturday, November 7, 2026, when a handwritten note threatening to hijack the aircraft was found inside the plane’s toilet while it was still in the air. IndiGo flight 6E-451, carrying 178 passengers, turned back to Kempegowda International Airport shortly after take-off, where security teams searched the aircraft and the airport declared a full emergency as a precaution. After hours of checks found nothing suspicious, the threat was declared a hoax and the emergency was lifted. No one was hurt, but the scare disrupted the journeys of nearly 180 people and set off an investigation to find out who wrote the note and why. This is the story of what happened on board flight 6E-451, how the crew and the airport responded, and what is still not known about the incident that brought one of India’s busiest airports to a standstill on a Saturday evening — a night that ended with a hoax, a police inquiry and a long list of unanswered questions about the IndiGo flight 6E-451 hijack threat in Bengaluru in November 2026.

1. What happened on flight 6E-451

IndiGo flight 6E-451 was an ordinary domestic service, the kind that flies between two Indian cities every day without attracting any attention. On the evening of Saturday, November 7, 2026, it was scheduled to carry its passengers from Bengaluru, in the southern state of Karnataka, to Lucknow, the capital of Uttar Pradesh in the north. The flight was operated by an Airbus A320, the workhorse aircraft of IndiGo’s fleet, and it departed from Terminal 1 of Kempegowda International Airport at around 5.50 in the evening, local time. Nothing about the departure suggested that anything was wrong. The aircraft pushed back, took off and climbed away from Bengaluru on its planned route toward Lucknow, with 178 passengers on board and the cabin crew beginning the normal service for a flight of about two hours. It was only after the aircraft had been in the air for roughly half an hour that the evening changed completely, when a passenger who had gone to use the toilet came back with news that stopped the flight in its tracks and sent it back to where it had started.

1.1 The departure from Bengaluru

Kempegowda International Airport, known to travellers by its code BLR, is one of the busiest airports in India, and Terminal 1 handles a constant stream of domestic departures through the day. Flight 6E-451 left from that terminal at about 5.50 pm Indian Standard Time on Saturday, November 7, 2026, according to reports of the incident. The aircraft was an Airbus A320 registered VT-ITP, according to flight tracking records, and it was bound for Chaudhary Charan Singh International Airport in Lucknow. There were 178 passengers on board. The flight had been in the air for only a short time when the discovery was made, which meant the aircraft was still relatively close to Bengaluru when the decision to turn back was taken. That closeness mattered, because it allowed the pilots to return to their departure airport quickly rather than diverting to an unfamiliar airfield, and it meant the emergency response at Kempegowda could be organised while the aircraft was still on its way back.

1.2 The note found in the toilet

About thirty minutes into the journey, a passenger who entered the aircraft’s toilet spotted a handwritten note that had been left there, according to reports from the scene. The message on the note was short and direct. It said, in the wording reported by several news outlets, that the flight was going to be hijacked at exactly 6.30, and that anyone who ignored the warning would see the consequences. The exact wording varied slightly between reports, but the meaning was the same in every version: a hijacking was threatened for a specific time, and the note was written as a warning that was meant to be taken seriously. The passenger who found the note did not keep it to themselves. They alerted the cabin crew immediately, and from that moment the flight stopped being a routine service and became a security emergency in the air. Whether the note was left by a passenger on board or had been placed there before departure was not clear at the time, and that question would become one of the central lines of the investigation that followed.

2. The crew’s response in the air

The cabin crew on flight 6E-451 had to make a series of fast decisions with very little information. They had a handwritten note, a specific time mentioned in it, and a cabin full of passengers who did not yet know anything was wrong. The way they handled those minutes followed the standard pattern that airlines train for: inform the person in command, keep the passengers calm, and let the pilot and the authorities on the ground decide what happens next. The crew’s first step was to tell the pilot-in-command about the note, and the pilot then contacted air traffic control to report the threat and ask for permission to return to Bengaluru. The speed of that response mattered, because the note had named a time of 6.30 in the evening, and the aircraft was already approaching that hour as it flew on toward Lucknow.

2.1 Alerting the pilot and air traffic control

As soon as the cabin crew were told about the note, they passed the information to the pilot-in-command, according to reports of the incident. The pilot then alerted air traffic control and explained that a security threat had been reported on board. This is the point at which an incident on an aircraft becomes a matter for the airport and the security agencies on the ground, because the pilot cannot search the aircraft or investigate a threat while flying it, and the airport needs time to prepare its response before the aircraft arrives. Air traffic control gave the flight priority clearance to return to Bengaluru, which meant other traffic was moved out of its way so that it could land as soon as possible. The exchange between the cockpit and the ground was short and practical, and it set in motion the emergency procedures that would dominate the rest of the evening at Kempegowda International Airport.

2.2 The decision to turn back

The decision to return to Bengaluru was taken by the pilots in line with the airline’s standard operating procedure for a security threat, according to IndiGo’s own statement about the incident. Turning back was the safest option available. The aircraft was still close to its departure airport, the threat named a specific time that was approaching, and the airport at Bengaluru was the place best prepared to receive the aircraft and search it properly. Flight tracking data showed that the aircraft remained in the air for 51 minutes before it landed back at Kempegowda, according to Flightradar24, which means the return journey took roughly twenty minutes after the note was discovered. The pilots’ decision to turn around rather than continue to Lucknow was the single most important choice of the evening, because it brought the aircraft back to a fully prepared airport instead of carrying a possible threat onward to its destination.

3. The full emergency at Kempegowda airport

While flight 6E-451 was turning back toward Bengaluru, the airport on the ground was preparing for its arrival. Airport authorities declared a full emergency as a precautionary measure, a step that mobilises fire services, medical teams, police and security agencies and clears the way for the aircraft to land and be isolated from other traffic. A full emergency does not mean that an incident has definitely happened; it means that the airport is treating the situation as if it could become serious, so that every resource is ready in advance rather than being called after the event. At Kempegowda, that preparation was visible within minutes, and by the time the aircraft touched down, the airport’s emergency machinery was already in place and waiting.

3.1 What a full emergency means

A full emergency at an airport is the highest level of alert short of an accident actually taking place. It is declared when an aircraft is known or believed to be in danger, and it brings together the airport’s fire and rescue services, medical teams, the Central Industrial Security Force, the local police and the airport’s own operations staff. Runways are cleared, other aircraft are held or moved, and emergency vehicles take up positions near the runway so that they can reach the aircraft within moments of landing. In the case of flight 6E-451, the full emergency was declared at Terminal 1, according to reports, and it remained in force until the aircraft had been searched and declared safe. The declaration was a precaution, and it was the right one: with a hijack threat naming a specific time, the airport could not afford to wait and see whether the threat was real before preparing for the worst.

3.2 The isolated bay and the security cordon

When flight 6E-451 landed safely back at Kempegowda, it was not taken to a normal parking stand. Instead, the aircraft was moved to an isolated bay, away from the terminal and from other aircraft, where security agencies could work on it without putting other passengers or aircraft at risk. The Central Industrial Security Force and the Bengaluru police cordoned off the area around the aircraft, according to reports, and nobody was allowed near it until the security checks were complete. This is standard practice for a suspected hijack or bomb threat: the aircraft is kept apart so that, if there is a device on board, the damage is contained, and so that investigators can control exactly who goes in and out. For the 178 passengers on board, the isolated bay was the first visible sign of how seriously the threat was being taken, and it was where they would spend the next part of their evening while the checks went on around them.

4. The security checks on the ground

Once the aircraft was parked in the isolated bay, the security operation on the ground began in earnest. Anti-sabotage teams and bomb disposal experts boarded the aircraft and began a systematic search of the cabin, the toilets, the overhead bins, the cargo hold and every other space where something could have been hidden. The passengers were taken off the aircraft so that the search could be carried out properly, and their baggage was also checked. The operation took time, because a thorough search of a full Airbus A320 cannot be rushed, and because the teams had to be certain rather than merely hopeful that nothing dangerous was on board. The airport’s emergency remained in force throughout the search, and no one was allowed to treat the threat as a hoax until the checks had proved it.

4.1 Anti-sabotage teams board the aircraft

The teams that searched flight 6E-451 were the specialists who are called whenever an aircraft is threatened. Anti-sabotage checks involve a careful, compartment-by-compartment inspection of the aircraft, often with the help of sniffer dogs trained to detect explosives, and they cover the places a passenger could reach as well as the places only crew can access. The teams would have been looking for anything that did not belong on the aircraft, and in particular for anything that could have been connected to the threat in the note. The search was carried out while the aircraft sat in the isolated bay, with the area around it cordoned off by the Central Industrial Security Force and the Bengaluru police. Reports of the incident say that security personnel and aviation authorities took charge of the aircraft as soon as it landed and began the checks immediately, which is why the emergency was able to be lifted the same evening rather than dragging on into the night.

4.2 No suspicious object found

The searches found nothing. No suspicious object was discovered anywhere on the aircraft, according to sources at Bangalore International Airport Limited, the company that operates Kempegowda International Airport. With nothing found, the threat was declared a hoax, and the emergency was lifted by the authorities. The speed with which the aircraft was declared safe was a relief to everyone involved, but it also raised the obvious question of why anyone would write such a note in the first place. A hoax threat is not a harmless prank: it closes runways, mobilises hundreds of emergency workers, delays hundreds of passengers and costs airlines and airports a great deal of money. The fact that nothing was found did not end the matter. It simply changed it from a security emergency into a criminal investigation, with the hunt for the person who wrote the note becoming the next phase of the story.

5. IndiGo’s statement and the airline’s protocol

IndiGo, India’s largest airline by market share, issued a statement about the incident on the evening of November 7, 2026, and its wording followed the careful, procedural language that airlines use when a security threat is reported on one of their flights. The airline confirmed that a security threat had been reported on board flight 6E-451, operating from Bengaluru to Lucknow on November 7, 2026, and said that the relevant authorities had been informed immediately and that the pilots had decided to return to the origin airport to carry out the necessary security checks, as per protocol. The statement also expressed regret for the inconvenience caused to customers and said the airline was making every effort to minimise it, including offering refreshments to the passengers and sharing regular updates with them. The statement did not describe the note in detail, did not speculate about who wrote it, and did not say when the flight would resume, which is normal for an airline statement issued while an incident is still being handled.

5.1 What the airline said

The exact words of IndiGo’s statement were reported by several news outlets, and they are worth reading closely because they show how the airline wanted the incident to be understood. The airline said that a security threat was reported on board the flight, that the relevant authorities were informed immediately, and that the pilots decided to return to origin to carry out the necessary security checks, as per protocol. The statement also said that the airline regretted the inconvenience caused to its customers and that it was making all efforts to minimise it, including offering refreshments and sharing regular updates. The emphasis in the statement was on procedure: the threat was reported, the authorities were told, the pilots followed the protocol, and the passengers were looked after. That emphasis is deliberate, because it reassures the public that the airline’s systems worked as they were designed to, even though the threat itself turned out to be false.

5.2 How airlines handle threats in the air

Airlines around the world train their crews for exactly this kind of situation, and the response on flight 6E-451 followed the pattern that is taught in every cabin crew course. When a threat is reported, the crew inform the pilot, the pilot informs air traffic control, and the aircraft is taken to the nearest suitable airport where security teams can take over. The crew are trained not to search for a device themselves, not to move anything suspicious, and not to alarm the passengers more than necessary, because a wrong move in the air can make a bad situation worse. On the ground, the airport takes over, and the airline’s job becomes looking after the passengers and working with the police. The system is designed to treat every threat as real until it is proved otherwise, which is why a handwritten note in a toilet can close down part of an international airport for hours even when it turns out to be a hoax.

6. The investigation into who wrote the note

With the aircraft declared safe and the emergency lifted, the focus of the incident shifted to a single question: who wrote the note? An investigation was launched to trace the origin of the threatening message and to identify the person responsible, according to reports of the incident. That investigation would involve the Bengaluru police, the Central Industrial Security Force and the aviation security agencies, and it would draw on the passenger list, the airport’s closed-circuit television footage, and the note itself, which would be examined for fingerprints and handwriting. The note was the only physical evidence of the crime, and finding its author would depend on working backwards from the moment it was found to the moment it was written, and from the hand that wrote it to the person it belonged to.

6.1 Tracing the note’s origin

The investigators have several ways of tracing a handwritten note left on an aircraft. The first is the passenger list, which tells them who was on board and where each person was sitting, and that can narrow the search to the people who used the toilet in the relevant part of the flight. The second is the airport’s camera footage, which can show who boarded the aircraft and what they were carrying, although it cannot show what happened inside the toilet itself. The third is the note, which can be tested for fingerprints and compared with handwriting samples if a suspect is identified. The fourth is the timing: the note was found about thirty minutes into the flight, which means it was probably written either on board or shortly before departure, and that narrows the window in which it could have been placed. None of these lines of inquiry is certain to produce an answer, and as of the time of writing no suspect had been publicly named and no arrest had been reported, so the investigation remains open and its outcome is unconfirmed.

6.2 The penalties for a hoax threat

A hoax hijack threat is a serious criminal offence in India, and the person who wrote the note on flight 6E-451 could face severe consequences if they are caught. Indian aviation security law treats threats against aircraft as crimes in their own right, whether or not the threat is carried out, and the penalties can include imprisonment and heavy fines. The law also allows the person responsible to be placed on a no-fly list, which would bar them from flying with Indian airlines. The reason the law is so strict is that a hoax costs the same as a real threat in the moment: the airport does not know it is a hoax until the checks are done, so the emergency response, the disruption and the expense are all real. The investigation into the note on flight 6E-451 is therefore not a formality. It is the part of the story that will decide whether the person behind the scare is held to account, and it is one of the main things to watch in the days after the incident.

7. What happened to the passengers

The 178 passengers on flight 6E-451 had bought tickets for an ordinary evening flight to Lucknow, and instead they found themselves at the centre of a security emergency. Their experience began with the discovery of the note, continued through the turn back to Bengaluru and the wait in the isolated bay, and ended with the news that the threat was a hoax and that their journey could resume. IndiGo said it offered refreshments to the passengers and kept them updated while the checks were carried out, but the passengers still lost hours of their evening, missed connections and appointments in Lucknow, and spent part of their night waiting in an airport they had already left once. For most of them, the story ended with a delayed arrival rather than a cancelled trip, but the disruption was real, and it is the part of the incident that is easiest to forget when the headlines move on to the investigation.

7.1 The wait on the ground in Bengaluru

After the aircraft landed and was moved to the isolated bay, the passengers were taken off the plane so that the anti-sabotage teams could search it. They would have been held in a secure area of the airport while the checks went on, and they would have had no way of knowing how long the wait would last, because the search could not be hurried and its result could not be predicted. IndiGo said it provided refreshments and regular updates, which is the standard way airlines look after passengers during a security delay, but the wait was still an anxious one, especially for anyone travelling with children or with onward connections from Lucknow. The passengers’ evening was, in effect, put on hold while the airport worked out whether the threat was real, and the relief when the aircraft was declared safe would have been mixed with frustration at the hours that had been lost.

7.2 The onward journey to Lucknow

Once the aircraft was declared safe and the emergency was lifted, the question became what would happen to the flight itself. Reports of the incident said that the flight resumed its journey to Lucknow later in the night, after the security clearance had been given, which would mean the same aircraft, or a replacement, eventually carried the passengers to their destination. However, flight tracking records for the flight show its status as cancelled and diverted, which suggests that the original service may have been formally cancelled and the passengers moved to a later departure, and that detail has not been fully confirmed in the reporting so far. What is clear is that the passengers did not spend the night in Bengaluru because of the threat itself, and that the airline’s priority after the checks was to get them to Lucknow. Whether they arrived on the same aircraft or on another flight, and at what time they finally landed, are details that remain unconfirmed, and they are part of the wider picture of how the evening ended for the people on board.

8. What remains unconfirmed and what to watch next

The outline of the incident on flight 6E-451 is now clear: a note was found, the aircraft returned, the airport declared a full emergency, the checks found nothing, and the threat was declared a hoax. But several important details are still not known, and they will decide how this story is remembered. The first is the identity of the person who wrote the note, and whether the police will be able to find them. The second is the motive: whether the note was a prank, an attempt to delay the flight, a protest, or something else entirely. The third is the exact sequence of the evening, including the time the aircraft landed and the time the passengers finally reached Lucknow. And the fourth is what the aviation authorities will do next, whether in the form of charges, a no-fly listing, or new guidance to airlines about threats found on board. Until those questions are answered, the story of flight 6E-451 is incomplete, and the coming days will fill in the gaps.

8.1 Questions still open

The most important open question is who wrote the note and why. No suspect had been publicly named at the time of writing, and no arrest had been reported, so it is not known whether the note was written by a passenger on the flight, by someone who had access to the aircraft before departure, or by a person who had already left the aircraft. It is also not known whether the note was the work of one person or more than one, and whether the 6.30 time mentioned in it had any significance beyond being a round number that would create alarm. A second open question is the exact timing of the return and the onward journey: the aircraft was airborne for 51 minutes according to flight tracking data, but the time it landed, the time the checks were completed, and the time the passengers finally left for Lucknow have not been reported in full. A third open question is whether anyone was detained for questioning, either at the airport or afterwards, and whether the police have any leads from the passenger list or the camera footage.

8.2 What to watch next

There are several things to watch in the days after the incident. The first is any statement from the Bengaluru police or the aviation security agencies about the investigation, including whether a suspect has been identified or arrested. The second is any further statement from IndiGo, either about the flight’s eventual departure or about any action it will take against the person responsible. The third is whether the aviation regulator, the Directorate General of Civil Aviation, issues any comment or guidance, since a hoax hijack threat is the kind of incident that can prompt a review of procedures. The fourth is the final account of the passengers’ journey, including when they reached Lucknow and whether they were moved to another flight. And the fifth is whether this incident is followed by similar threats elsewhere, which would suggest a pattern rather than a single isolated act. Any one of those developments would add an important chapter to the story, and together they will decide whether the scare on flight 6E-451 is remembered as a one-off hoax or as the start of something larger.

The coming weeks will provide the answers.

Comments

comments