GeneralHr Library

Mid Air Leadership Lessons

Source | LinkedIn : By Sangeeta Sundaram

I was on a United Airlines flight from San Francisco to Paris in late August 2016. After a short and intense work week in the US, all I wanted to do was catch up on my sleep. It felt like only a few hours since our take off, when the attendant came up and straightened my seat and said we were landing. I felt confused, had I slept all through the 10.5 hours flight? Why does it look dark outside when we were to be landing morning hours in Paris? And when I looked at the watch, we had been airborne only 6+ hours, so how the hell were we landing so soon. Looking at my confusion, my co-passenger informed me that as there was an issue with the flight navigation system, we were landing in Washington D.C. We had no idea how long the wait would be.

A few minutes after getting off the aircraft we were given hotel, food and taxi vouchers along with boarding passes for next evening. Lugging our bags we all went to our respective hotels. Some changed their flights, others like me informed their associates in Paris about meeting time change, cancellations etc. I was exhausted after the ordeal. I had not heard positive things about United recently and this experience definitely made me wonder if I should fly the airline in the future.

Next day at the airport, all the faces looked familiar at the check in queue. The crew was the same on the aircraft. It was as if we had been in a time warp for the last 24 hours. A true déjà vu moment. About an hour after being airborne, the captain made an announcement saying that he would like to share the reasons for previous evening’s detour and asked those interested to tune into a special channel where one can hear the on goings in the cockpit. Many of us were curious to learn what had happened and why we had spent a day in D.C.

The Captain started by giving a background on the crew in the cockpit, the details of the kind of aircraft that was being used, the redundancies built in to manage malfunctions and emergencies etc. He then shared that they started observing some abnormalities in the flight control monitors after 4.5 hours flying. The monitors on the left side of the plane were showing different data from the right, which perplexed the crew. First it showed an electrical malfunction. Then a fuel leak. Soon they lost all the ability to auto pilot and were using manual navigation. After conferencing in all the various maintenance and operations, they established that there was no electrical problem or a fuel leak, but there was certainly a software failure, which was giving different information. This by itself was not an emergency, but definitely something that made them uncomfortable. The reason for the software failure was unclear. It was a potential risk when we were about to coast off over the Atlantic, so he decided it was better off landing some place than risking the journey.

The question next was, where to land? The flight was closest to Toronto and they did get a clearance. However, the team felt that it would not be the best base as they would have to depend on Air Canada for assistance. So the next choice was going to Chicago. This plan had to be aborted as O’Hare was already dealing with 2 planes with issues. The next choice was New Jersey. Here too they ran into issues on logistics, as there were no hotels with enough rooms to accommodate 269 passengers. Hence the choice to fly to D.C. which had the hotel space and the necessary ground support.

Read On…

Show More

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button