Narrative:

On taxi out we were behind a heavy so we decided to rerun numbers for a normal thrust setting. After the numbers came back the first officer (first officer) reset the numbers and thrust settings and we ran through the numbers to confirm them. After takeoff we received a SELCAL aural alert and found a message stating the flaps settings had changed. We then went back and also noticed the different flap setting (8) than what we had originally departed with under flex numbers (20). The issue arose from changing the numbers and receiving different flap settings from acars but the SELCAL to notify us of the change did not announce until after departure. We noted the message timestamp on both the newest tld and ACARS message about the change in flaps setting were both before takeoff and must have been posted prior to departure. The issue is with our new acars system not working properly we have had SELCAL posted under the advisory messages continuously from door close until after takeoff on most flights this trip. Even after deleting; reading; and rereading all messages; wx responses; and take off data blocks we could not extinguish the SELCAL advisory. This was accomplished again prior to our runway number change on this flight to ensure we didn't have a dispatch message or anything prior to departure but we failed to reconfirm all the messages since we didn't get an aural alert. ACARS system update isnt working when it comes to SELCAL aural alerts and advisory messages. Posting advisory message without unread messages in the acars from door close until after departure on multiple aircraft and multiple days.we need to fix this ACARS system. Needing to send numbers a second time for non-reduced numbers is burdensome and unsafe. Also having an ACARS that isn't extinguishing the SELCAL message properly is unsafe and led to a situation such as this. Personally I will be pulling over and setting the brake prior to takeoff anytime we change the numbers; runway; or performance data in the future as this airport is notorious for these issues. I also would suggest that flap settings; thrust settings; and v-speeds should be in a different color font on the acars screen to help distinguish them from other text on the screen.

Google
 

Original NASA ASRS Text

Title: CRJ200 Crew reported a problem with the ACARS that prevented the system from providing timely takeoff data and SELCAL aural alerts.

Narrative: On taxi out we were behind a heavy so we decided to rerun numbers for a normal thrust setting. After the numbers came back the FO (First Officer) reset the numbers and thrust settings and we ran through the numbers to confirm them. After takeoff we received a SELCAL aural alert and found a message stating the flaps settings had changed. We then went back and also noticed the different flap setting (8) than what we had originally departed with under flex numbers (20). The issue arose from changing the numbers and receiving different flap settings from acars but the SELCAL to notify us of the change did not announce until after departure. We noted the message timestamp on both the newest TLD and ACARS message about the change in flaps setting were both before takeoff and must have been posted prior to departure. The issue is with our new acars system not working properly we have had SELCAL posted under the advisory messages continuously from door close until after takeoff on most flights this trip. Even after deleting; reading; and rereading all messages; wx responses; and take off data blocks we could not extinguish the SELCAL advisory. This was accomplished again prior to our runway number change on this flight to ensure we didn't have a dispatch message or anything prior to departure but we failed to reconfirm all the messages since we didn't get an aural alert. ACARS system update isnt working when it comes to SELCAL aural alerts and advisory messages. Posting advisory message without unread messages in the acars from door close until after departure on multiple aircraft and multiple days.We need to fix this ACARS system. Needing to send numbers a second time for non-reduced numbers is burdensome and unsafe. Also having an ACARS that isn't extinguishing the SELCAL message properly is unsafe and led to a situation such as this. Personally I will be pulling over and setting the brake prior to takeoff anytime we change the numbers; runway; or performance data in the future as this airport is notorious for these issues. I also would suggest that Flap settings; thrust settings; and V-speeds should be in a different color font on the acars screen to help distinguish them from other text on the screen.

Data retrieved from NASA's ASRS site 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.