Site icon Aakash News and Media Syndicate

Army Officer Charged for Assaulting SpiceJet Staff Over Baggage Fees

video-army-officer-thrashes-spicejet-staff-over-extra-cabin-luggage-charge.avif

Incident Overview

In a disturbing event at Srinagar airport, an army officer has been accused of violently assaulting SpiceJet employees over excess cabin luggage charges. The altercation resulted in severe injuries to four staff members, including a spinal fracture and a broken jaw. The incident has sparked significant concern about airport security and passenger conduct.

Details of the Assault

The confrontation began when the officer, whose identity remains undisclosed, was informed by SpiceJet staff that his cabin baggage exceeded the 7 kg limit and would incur additional charges. The officer, carrying 16 kg of luggage, refused to comply and attempted to bypass security protocols by forcefully entering the aerobridge. This led to a physical altercation where he allegedly used a queue stand as a weapon against the staff.

Response and Investigation

Central Industrial Security Force (CISF) personnel quickly intervened to manage the situation. The army has acknowledged the incident and is cooperating with civil authorities in their investigation. SpiceJet has filed a First Information Report (FIR) with local police and provided CCTV footage as evidence. The airline is also pursuing measures to place the officer on its no-fly list.

Impact on Airline Operations

Despite the violent encounter, CISF ensured that flight operations were not disrupted. The injured employees were immediately taken to a hospital for treatment. SpiceJet has expressed strong condemnation of the violence and is committed to seeking legal recourse.

Official Statements and Future Actions

SpiceJet has communicated with the Civil Aviation Ministry regarding the assault and requested appropriate action against the officer. The airline emphasized its zero-tolerance policy towards violence against its employees and vowed to pursue all legal avenues to address this incident.

Exit mobile version