B737-700 FLT CREW RECEIVES FINAL WT AND BAL DATA FOR A DIFFERENT FLT.

Date: 2005-04 · Aircraft: B737-700 · Phase: descent

Anomalies: deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|other-bad-wt-and-bal-data

Synopsis

B737-700 FLT CREW RECEIVES FINAL WT AND BAL DATA FOR A DIFFERENT FLT.

Narrative

DURING CLBOUT FROM SJC WHEN I CALLED IN THE OUT/OFF TIMES THE OPS AGENT INFORMED ME THAT HE HAD USED A LOADING SCHEDULE FOR ANOTHER FLT. WHEN THE OPS AGENT GAVE US THE ELECTRONIC WT AND BAL LOADING SCHEDULE I CHKED THE FUEL AUDIT; OPERATING EMPTY WT; PAX COUNT; WT AND BAL INFO; CORRECT FORM (XXX); ETC. I WAS FOCUSED ON THE WT AND BAL DATA. SINCE THE DISPATCH RELEASE DATA; SUCH AS TAIL NUMBER; FLT NUMBER; ETC; ARE AUTOMATICALLY ADDED TO THE SHEET I WAS LESS FOCUSED ON THAT SECTION. DURING THE BUSY TIME THAT THE OPS AGENT BRINGS THE LOADING SCHEDULE TO THE FLT DECK THERE ARE OFTEN INTERRUPTIONS AND THERE IS THE CONSIDERATION FOR PUSHING THE ACFT ON TIME. I THINK THERE IS A TENDENCY TO BELIEVE THE COMPUTER GENERATED DATA IS MORE ACCURATE. HOWEVER; THE EXPRESSION 'GARBAGE IN; GARBAGE OUT' COMES TO MIND HERE. THE OEW WAS CORRECT AND THE WT AND BAL DATA WAS CORRECT AND MATCHED WHAT WE EXPECTED TO FIND. CLEARLY IT IS IMPORTANT TO CHK EVERY ENTRY ON THE FORM REGARDLESS OF HOW LONG IT TAKES. IT WOULD BE A GOOD IDEA TO EMPHASIZE THE LIMITATION OF THIS TECHNOLOGY. EVEN THOUGH THE CALCULATIONS ARE MORE ACCURATE THERE IS STILL THE POSSIBILITY OF 'OPERATOR ERROR.'

More incidents for this aircraft family →

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