A DISPATCHER FOR A REGIONAL ACR DISCUSSES THE PROBS ASSOCIATED WITH GETTING ACCURATE REVISIONS TO TKOF WT AND BAL DATA TO FLT CREWS.

Date: 2005-09 · Aircraft: SF 340B

Anomalies: deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy

Synopsis

A DISPATCHER FOR A REGIONAL ACR DISCUSSES THE PROBS ASSOCIATED WITH GETTING ACCURATE REVISIONS TO TKOF WT AND BAL DATA TO FLT CREWS.

Narrative

THIS VIOLATION OCCURRED BECAUSE OF A COM BREAKDOWN OR 'GLITCH.' AS OUR OP IS CURRENTLY CONFIGURED; THE ACCURACY OF WT AND BALANCE FIGURES DEPENDS ON COORD AMONG GATE AGENTS; BAGGAGE HANDLERS; AND ASSISTANT DISPATCHERS. WHEN THIS VIOLATION OCCURRED; THE RESPONSIBLE ASSISTANT DISPATCHER WAS TRYING TO COM TO THE FLT CREW REGARDING DISCREPANCIES AMONG THE VARIOUS TYPES OF DATA ENTRY ITEMS ON HIS COMPUTER SCREEN. I BECAME INVOLVED WHEN THE ASSISTANT DISPATCHER WHO HAD PLANNED THIS LOAD CAME TO ME FOR HELP IN RESTORING COM WITH THE FLT CREW -- THE FLT WAS UNDER MY OPERATIONAL CTL; AND HEADED FOR JAMESTOWN; ND. WHEN I CHKED MY PLOT (CO FLT MONITORING SYS); THE ACFT HAD PUSHED BACK; MY DISPLAY (COMPUTER PROGRAM) INDICATED IT WAS STILL ON THE GND IN MINNEAPOLIS. IN OTHER WORDS; HE WAS 'OUT' BUT NOT 'OFF.' REPEATED ATTEMPTS TO RAISE THE FLT CREW ON THE RADIO WERE TO NO AVAIL -- IT IS NOT UNUSUAL FOR AIRCREWS TO BE VERY BUSY AT PUSH TIME; AND THE CROSS TFC ON THE FREQUENCIES THEY MONITOR COULD VERY EASILY BE SUCH THAT OUR HAILS WERE NOT GETTING THROUGH. OUR FIRST IDEA WAS TO GET THE PLANE BACK TO THE GATE FOR A BAG CHECK -- THE QUESTION BEING WHICH SET THE LOAD FIGURES WERE ACCURATE: THE 'FINALIZED' FIGURES BASED ON SOP ROUTINE? LAST-SECOND ENTRIES MADE BY THE GATE AGENT? A 'GUESSTIMATE' BASED ON WHAT RAMP PERSONNEL RECALLED SEEING ON THE BAGGAGE CART? WAS IT POSSIBLE THE ACFT HAD BEEN LOADED IN SUCH A FASHION THAT NO ACCURATE WT AND BAL DATA WAS ON HAND? THE ASSISTANT DISPATCHER WAS TRYING TO RECONSTRUCT EVENTS IN ORDER TO PIN DOWN PRECISELY HOW THE AIRPLANE HAD ACTUALLY BEEN LOADED. THE ASSISTANT DISPATCHER -- WHO ALSO HOLDS A COMMERCIAL PLT'S RATING -- THOUGHT THE FLT WAS LIGHTER THAN THE OFFICIAL LOAD PLAN INDICATED. THE REAL CONCERN WAS WHETHER THE LOAD WAS DISTRIBUTED ACCORDING THE THAT PLAN; OR WHETHER THE ACFT WAS OUT OF ITS CTR OF GRAVITY LIMIT. UNSTATED BETWEEN US WAS THE FEAR THAT THE ACFT (A SAAB 340); IF LOADED IMPROPERLY; COULD EVEN TAKE OFF WITHIN THE LOAD ENVELOPE BUT BURN FUEL OFF INTO AN OUT-OF-LIMIT CONDITION AT SOME POINT ENRTE. PROPER LOAD PLANNING -- ASSUMING THE CABIN CREW AND BAGGAGE HANDLERS FOLLOW THAT LOAD PLAN ENSURES THAT THIS WILL NOT HAPPEN. IT WAS CLR TO BOTH OF US THAT THE FLT CREW WAS MOST LIKELY CONVINCED THEY HAD PROPER NUMBERS; AND EITHER UNAWARE OF OR UNCONCERNED ABOUT WHATEVER DISCREPANCIES THERE MIGHT HAVE BEEN. THE FLT BECAME AIRBORNE WHILE WE WERE STILL TRYING TO REACH THEM ON THE RADIO TO GET THEM BACK TO THE GATE. MY UNDERSTANDING OF OUR PROC AT THIS POINT IS THAT; IN THE EVENT THE FLT CREW EXPERIENCED ANY PITCH INSTABILITY ON TAKEOFF OR CLB; THE PIC COULD REQUEST A 'BAG AUDIT.' THIS WOULD BE A FORMAL INSPECTION OF THE ACFT AS LOADED; AND COULD TRIGGER SUCH ACTIONS AS SAFETY COUNSELING; RETRAINING; MAINT INSPECTIONS; COMPANY RPTING; OR THE REMOVAL OF PAX OR CARGO. IT IS NOT SOMETHING MANAGEMENT LIKES TO GET INTO. SINCE WE HAD NO INDICATION THE FLT CREW HAD ENCOUNTERED ANY DIFFICULTY IN THE TAKEOFF; WE CONCLUDED THAT A QUICK 'BAG CHK' SHOULD BE PERFORMED AT THE DEST; SINCE THE PLANE WAS SCHEDULED TO CONTINUE ON FROM THERE ON ONE LAST LEG OF FLYING. AT THE VERY LEAST; WE MIGHT GAIN SOME INFO THAT WOULD HELP DETERMINE HOW THE MISTAKE WAS MADE; AND WHICH FIGURES WERE CORRECT. IT WOULD ALSO PREVENT THE FLT FROM VERY POSSIBLY TAKING OFF A SECOND TIME IN AN OUT-OF-LIMIT CONDITION. THE BAG CHECK REVEALED A 150 LB DISCREPANCY BETWEEN THE FINAL FIGURES AND THE ACTUAL LOADING OF THE ACFT -- THE FLT WAS 150 LBS LIGHTER THAN THE NUMBERS SHOWED IT TO BE. IT TURNED OUT TO BE LOADED WITHIN CTR OF GRAVITY LIMITS; BUT THE TRUTH OF THE MATTER WAS NOBODY KNEW THAT AT THE TIME IT TOOK OFF. UNDOUBTEDLY; AMONG THE CONTRIBUTING FACTORS HERE WAS THE FACT THAT THERE HAD BEEN A FLURRY OF 'ELEVENTH HOUR' ACFT SWAPS -- AIRPLANES FUELED FOR ONE TRIP WERE SUDDENLY ASSIGNED TO DIFFERENT LEGS. DIFFERENCES IN ACFT EMPTY WEIGHT; A PAX ADDED OR REMOVED FROM THE MANIFEST; GATE CHANGES; LACK OF UNDERSTANDING OF FLT MECHANICS ON THEPART OF RAMP AND GATE PERSONNEL (IN PARTICULAR THE PHYSICS OF WT AND BAL AS THEY APPLY TO AIRLINE TRANSPORT LOADING PRACTICES); 'USER SURLY' COMPUTER INTERFACES AND NON-INTUITIVE DATA ENTRY PROCS MAY WELL HAVE ADDED TO THE CONFUSION. THE ORGANIZATIONAL CULTURE DOES PLACE AND EMPHASIS ON STAYING ON-SCHEDULE; AND THIS TIME-PRESSURE CAN TRANSLATE INTO 'SHORT CUTTING' OR CUTTING CORNERS ESPECIALLY WHEN PROCS AND THE REASONS BEHIND THEM ARE NOT WELL UNDERSTOOD. THE FACT THAT ASSISTANT DISPATCHERS -- WHO ARE DEDICATED TO THE LOAD CTL FUNCTION -- HAVE LIMITED COM OPTIONS CAN TEND TO FRUSTRATE THEIR ATTEMPTS TO REACH CREWS. IF THEY NEED TO RADIO A FLT; THEY MUST WORK WITH A DISPATCHER -- THEY HAVE NO RADIO EQUIPMENT AT THEIR WORKSTATIONS. OUR AIRLINE HAS AN ASAP PROGRAM IN PLACE -- HOWEVER; IT IS NOT OPEN TO PARTICIPATION BY DISPATCHERS OR ASSISTANT DISPATCHERS AT THIS TIME. WHILE SOME LOAD CTL ISSUES HAVE FOUND THEIR WAY INTO ASAP RPTS; THIS ASPECT OF OUR OP AND THE CHALLENGES IT REPRESENTS MIGHT BENEFIT FROM THE ADDITIONAL SCRUTINY A MORE INCLUSIVE ASAP PROCESS COULD BRING TO BEAR. AN INTERNAL RPT ON THE INCIDENT WAS FILED BY THE ASSISTANT DISPATCHER.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.