Commercial Fixed Wing
Dispatch Dispatcher
Communication Breakdown; Workload; Time Pressure; Situational Awareness; Human-Machine Interface; Distraction
Deviation / Discrepancy - Procedural Other / Unknown
Flight Crew Diverted
Chart Or Publication; Company Policy
I came into work at approximately XA:49 for a XB:00 start. I received a briefing from the morning Dispatcher on the day's events and weather conditions. The morning Dispatcher logged out of the computer at approximately XA:53. It can take 3 minutes or more to fully log out of all applications including INTERNET; and three Dispatch tools. I began the login process at approximately XA:56. It can take an additional 3 minutes or more just to get into Microsoft Windows; then another 1-2 minutes to access the Dispatch tool; another 1-2 minutes to access the performance tools and another minute to open up the Company Flight Planning tool. Internet and other applications such as the Flight Schedule monitors can increase login time. By the time I gained access to the Dispatch tool; I had an ACARS message almost 10 minutes old from an aircraft telling me he had loss of cabin pressure and declared an emergency descent and diverting. I had no knowledge or way of knowing of his situation or plans for 10 full minutes while the morning Dispatcher logged out and I logged in. The crew then asked for performance data for landing at the divert airport. I had to then power up the performance tool and take another 2-3 minutes to get him the data he needed. The entire logout/login process is time consuming and valuable minutes and seconds are wasted filling in countless usernames and passwords to gain access to critical tools that could have greatly aided the diverting flight during an emergency.
An Air Carrier Dispatcher describes the shift change login process which consumed ten minutes; during which time he is unable to communicate with his assigned aircraft; one of which in this event diverted for loss of cabin pressure.