Etihad A321neo Loses Cabin Pressure Near Kolkata, Emergency Descent

(KOLKATA, INDIA) Etihad Airways Flight EY-222 from Abu Dhabi to Kolkata performed an emergency descent on October 18, 2025 after the crew detected a cabin pressure problem while approaching the city. The Airbus A321neo, registration A6-LRA, had been cruising at FL330 (33,000 feet) when the issue surfaced around 7:30 PM local time, roughly 30 minutes from its destination. The pilots initiated a swift descent to FL100 (10,000 feet), a standard safety level when cabin pressure is lost, and later landed normally at 7:58 PM. No injuries were reported.

According to the airline’s procedures described by people familiar with the event, the crew’s immediate shift to an emergency descent reflected the textbook response to a cabin pressure loss: get the aircraft to a breathable altitude as fast as safely possible. Passengers reported the descent began without warning, leaving some shaken as the aircraft suddenly dropped. Although the maneuver surprised many on board, the seat belt sign was already on and everyone was strapped in, which helped prevent injuries during the rapid change in altitude.

Air traffic controllers at Kolkata were also caught off guard by the sudden change in the aircraft’s profile and received notification from the captain a couple of minutes after the descent began. That timeline, while startling to those watching the radar and to passengers feeling the aircraft descend, aligned with the flight crew’s first duty to control the aircraft and address the cabin pressure problem before updating controllers and the cabin.

The Airbus A321neo touched down normally, and the sense of tension gave way to relief as travelers began speaking with each other after the safe landing. Maintenance teams met the aircraft and carried out an engineering inspection, which led to a delay of about an hour for a subsequent departure. Etihad Airways later emphasized that safety remains its top priority, a position consistent with industry practice after a pressurization event and emergency descent.

What happened on board

• The incident occurred at about 7:30 PM local time while the aircraft was cruising at FL330 (33,000 feet).
• The crew initiated an emergency descent to FL100 (10,000 feet) after detecting a cabin pressure issue.
• The descent began quickly and without a passenger announcement, which is common when time is critical and the crew must act first, speak second.
• The seat belt sign was on, all 169 passengers were buckled, and the aircraft remained under control.
• The flight landed normally in Kolkata at 7:58 PM, and no injuries were reported.

Passengers described silent prayers and a quiet cabin during the descent. That human reaction underscores the shock of a sudden altitude change, even when the aircraft and crew are following the correct safety steps. People processed the moment in real time—holding armrests, looking for reassurance from cabin crew, and scanning fellow travelers’ faces. After touchdown, conversation returned as the reality of a safe landing settled in.

The swift descent also created a brief mismatch between the crew’s immediate workload and the expectations of others tracking the flight. Controllers saw the aircraft start down before a radio call came in, and passengers felt the descent before any explanation. In time-critical events like a cabin pressure problem, priorities are clear: stabilize the aircraft, descend to a safe altitude, then communicate.

“Act fast to get to a safer altitude, stabilize the situation, and verify the aircraft’s condition before the next flight.”

After landing and next steps

Following the safe landing, engineers conducted a thorough inspection of the aircraft. That work pushed the next departure by about one hour as Etihad Airways ensured the aircraft was ready for service. While the airline did not disclose technical details, the careful inspection after a pressurization event is consistent with the attention such situations receive across the industry.

For travelers, unexpected events can raise questions about schedules, missed connections, and how airlines handle the aftermath. According to analysis by VisaVerge.com, clear communication from airlines during irregular operations helps passengers adjust plans with less stress, especially when a post-incident inspection extends ground time. In Kolkata that evening, the priority remained: maintain safety, complete checks, and resume operations once experts were satisfied.

India’s civil aviation regulator sets the framework under which airlines operate, and safety oversight remains the core. Readers seeking official background on flight safety oversight in India can consult the Directorate General of Civil Aviation (DGCA), which provides regulatory information for carriers and crews operating in Indian airspace. See the DGCA official website.

Key takeaways

• The crew followed standard emergency procedures by descending rapidly to a breathable altitude (FL100) after detecting a pressurization issue.
• Because the seat belt sign was on and passengers were buckled, injuries were avoided during the rapid descent.
• The aircraft landed normally at 7:58 PM, and maintenance teams completed an inspection before the aircraft returned to service.
• Effective post-incident processes—pilot training, engineering reviews, and regulator oversight—helped manage the situation without escalation.

Practical advice for travelers

• Keep your seat belt fastened while seated; it can prevent injuries during unexpected altitude changes.
• Listen for crew instructions and follow them promptly.
• Stay calm; trained crews prioritize aircraft control and passenger safety first, then communicate as the situation stabilizes.

On a busy evening in Kolkata, an unexpected emergency descent tested systems built to handle the rare loss of cabin pressure. The result—swift action, a safe landing at 7:58 PM, and no injuries—reflects a safety-first approach that passengers may not see every day but rely on when it counts.