Narrative:

I operated the advanced technology medium large transport from newark to boston. I rejected the takeoff on ry 22R at 80 KTS for a stablizer trim takeoff warning. The rejected takeoff was uneventful with no assistance required. Upon clearing the runway we took the stabilizer trim out of the original proper setting and reset it. We completed all the required checklists and then rechked the takeoff warning by advancing the throttle quickly and once again it checked ok (this before takeoff continuity check was successfully completed on the initial taxi checklist). The subsequent takeoff was normal and the takeoff warning functioned properly. I believe the roughness of the 22R runway vibrated the stabilizer trim out of the original proper setting. Supplemental information from acn 160137. Upon further evaluation of the stabilizer setting after the aborted takeoff we found the stabilizer trim was in fact set properly the entire time. The captain concluded, and I fully supported the conclusion, that a glitch in the CAWS computer had set off the warning. The medium large transport notorious for computer glitches. It is part of everyday operations of the aircraft. Apart from redesigning the entire electrical warning system on the aircraft I know of no sure fire way to avoid this situation from reoccurring. Computer malfunctions are a part of the new high tech aircraft we fly. We must accept that fact, and look for further advancements in technology to minimize their occurrences.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR MLG FLC ABORTS TKOF AT EWR DUE STAB TRIM WARNING HORN.

Narrative: I OPERATED THE ADVANCED TECHNOLOGY MLG FROM NEWARK TO BOSTON. I REJECTED THE TKOF ON RY 22R AT 80 KTS FOR A STABLIZER TRIM TKOF WARNING. THE REJECTED TKOF WAS UNEVENTFUL WITH NO ASSISTANCE REQUIRED. UPON CLRING THE RWY WE TOOK THE STABILIZER TRIM OUT OF THE ORIGINAL PROPER SETTING AND RESET IT. WE COMPLETED ALL THE REQUIRED CHKLISTS AND THEN RECHKED THE TKOF WARNING BY ADVANCING THE THROTTLE QUICKLY AND ONCE AGAIN IT CHKED OK (THIS BEFORE TKOF CONTINUITY CHK WAS SUCCESSFULLY COMPLETED ON THE INITIAL TAXI CHKLIST). THE SUBSEQUENT TKOF WAS NORMAL AND THE TKOF WARNING FUNCTIONED PROPERLY. I BELIEVE THE ROUGHNESS OF THE 22R RWY VIBRATED THE STABILIZER TRIM OUT OF THE ORIGINAL PROPER SETTING. SUPPLEMENTAL INFO FROM ACN 160137. UPON FURTHER EVALUATION OF THE STAB SETTING AFTER THE ABORTED TKOF WE FOUND THE STABILIZER TRIM WAS IN FACT SET PROPERLY THE ENTIRE TIME. THE CAPT CONCLUDED, AND I FULLY SUPPORTED THE CONCLUSION, THAT A GLITCH IN THE CAWS COMPUTER HAD SET OFF THE WARNING. THE MLG NOTORIOUS FOR COMPUTER GLITCHES. IT IS PART OF EVERYDAY OPS OF THE ACFT. APART FROM REDESIGNING THE ENTIRE ELECTRICAL WARNING SYSTEM ON THE ACFT I KNOW OF NO SURE FIRE WAY TO AVOID THIS SITUATION FROM REOCCURRING. COMPUTER MALFUNCTIONS ARE A PART OF THE NEW HIGH TECH ACFT WE FLY. WE MUST ACCEPT THAT FACT, AND LOOK FOR FURTHER ADVANCEMENTS IN TECHNOLOGY TO MINIMIZE THEIR OCCURRENCES.

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