Narrative:

After a normal taxi; checklist completion and normal takeoff; during the climb I looked to the ACARS to pull up WX and noticed the ACARS prompt was present rather than the menu mode. After calling up the menu; I noticed the message light flashing. Load planning had sent us 2 messages indicating a center of gravity issue and to block rows displayed within the final weight manifest message. Upon inspection of the final weight manifest message; we noticed that row 21 was to be blocked. We informed our flight attendants to move the passenger once the seatbelt sign was extinguished. They accomplished this quickly and we proceeded normally. I believe that when the power xfer from APU to engine generators occurred; the ACARS reset and did not display the normal menu; resulting in our inability to notice messages. However; the final weight manifest did print; indicating to us that we were legal to depart. Only on further review; after receiving the load planning messages; did we notice the embedded note to block row 21. I think that 2 issues combined to cause this problem. First; some aircraft in the fleet do not need to reboot ACARS after a power xfer; resulting in normal ACARS information being displayed. Secondly; it doesn't seem right that load planning can send final weights that aren't final. If no final weight manifest had been sent; we would have looked to the ACARS screen to query load planning and would have noticed the messages. Since a final weight was sent; we concluded that it was legal.

Google
 

Original NASA ASRS Text

Title: B737-500 FLT CREW FAILS TO MOVE PAX FROM ROW 21 AS REQUIRED FOR WEIGHT AND BALANCE WHEN LOAD PLANNING MSG IS NOT RECOGNIZED DUE TO ACARS IN WRONG MODE FOLLOWING AN ELECTRICAL POWER TRANSFER.

Narrative: AFTER A NORMAL TAXI; CHKLIST COMPLETION AND NORMAL TKOF; DURING THE CLB I LOOKED TO THE ACARS TO PULL UP WX AND NOTICED THE ACARS PROMPT WAS PRESENT RATHER THAN THE MENU MODE. AFTER CALLING UP THE MENU; I NOTICED THE MESSAGE LIGHT FLASHING. LOAD PLANNING HAD SENT US 2 MESSAGES INDICATING A CTR OF GRAVITY ISSUE AND TO BLOCK ROWS DISPLAYED WITHIN THE FINAL WT MANIFEST MESSAGE. UPON INSPECTION OF THE FINAL WT MANIFEST MESSAGE; WE NOTICED THAT ROW 21 WAS TO BE BLOCKED. WE INFORMED OUR FLT ATTENDANTS TO MOVE THE PAX ONCE THE SEATBELT SIGN WAS EXTINGUISHED. THEY ACCOMPLISHED THIS QUICKLY AND WE PROCEEDED NORMALLY. I BELIEVE THAT WHEN THE PWR XFER FROM APU TO ENG GENERATORS OCCURRED; THE ACARS RESET AND DID NOT DISPLAY THE NORMAL MENU; RESULTING IN OUR INABILITY TO NOTICE MESSAGES. HOWEVER; THE FINAL WT MANIFEST DID PRINT; INDICATING TO US THAT WE WERE LEGAL TO DEPART. ONLY ON FURTHER REVIEW; AFTER RECEIVING THE LOAD PLANNING MESSAGES; DID WE NOTICE THE EMBEDDED NOTE TO BLOCK ROW 21. I THINK THAT 2 ISSUES COMBINED TO CAUSE THIS PROB. FIRST; SOME ACFT IN THE FLEET DO NOT NEED TO REBOOT ACARS AFTER A PWR XFER; RESULTING IN NORMAL ACARS INFO BEING DISPLAYED. SECONDLY; IT DOESN'T SEEM RIGHT THAT LOAD PLANNING CAN SEND FINAL WTS THAT AREN'T FINAL. IF NO FINAL WT MANIFEST HAD BEEN SENT; WE WOULD HAVE LOOKED TO THE ACARS SCREEN TO QUERY LOAD PLANNING AND WOULD HAVE NOTICED THE MESSAGES. SINCE A FINAL WT WAS SENT; WE CONCLUDED THAT IT WAS LEGAL.

Data retrieved from NASA's ASRS site as of May 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.