United Airlines CEO sorry for 'horrific' passenger removal

'I want you to know that we take full responsibility and we will work to make it right'


Reuters April 12, 2017
Chief Executive Officer of United Airlines Oscar Munoz in New York, US. PHOTO: REUTERS

United Airlines Chief Executive Officer Oscar Munoz on Tuesday issued an apology for the treatment of a passenger dragged from aboard one of its flights before takeoff on Sunday.

"I want you to know that we take full responsibility and we will work to make it right," Munoz said in a statement, reversing earlier decisions not to apologize directly for the incident.

United Airlines under fire after passenger dragged from plane

United Airlines sparked outrage on Monday for the treatment of a passenger who was physically dragged off a plane the airline had overbooked, and one of the security officers involved in the incident was placed on leave pending an investigation.

Videos posted online by other passengers showed a man screaming as officers yanked him from his seat on United Flight 3411 before it departed from Chicago O’Hare International Airport to Louisville, Kentucky, on Sunday.

 

Our Publications

COMMENTS (2)

Jadugar | 4 years ago | Reply Just an apology by the Company CEO doesn't make things right. The big Cooperation must realize and make changes that such behaviour will/should not be tolerated in the future. As for me NO UNITED EVER
Hasan | 4 years ago | Reply This is the (third) apology from CEO Munoz. The first was a shameless statement saying the guards did right. The second was a blatant & astonishing statement that passenger should have cooperated even if he paid for the 'over-booked' flight. Only after social media backlash resulted in US 1.5 billion dollars loss in company shares, did the CEO make a u-turn and submitted an apology. But we all know an apology made due to financial loss is not an apology, it is a cover up.
Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ