Narrative:

We were flying from halifax, nova scotia (yhz), to newark (ewr) on a STAR and given a descent clearance to 14000 ft. I'm not sure today if this was the altitude ATC gave us, but it was an even middle-teen altitude and I was sure of the altitude on the day of this incident -- that was not the issue. While descending routinely, it was the first officer's leg and I was filling out our crew declaration customs form. I noticed that my first officer was also filling out her customs form, so I would occasionally look up to monitor our flight situation. The autoplt was on and descending initially, but had somehow disengaged without us knowing why. The autoplt aural warning announcing disengagement only occurs below 2500 ft AGL and not at any other altitudes above that. I have already experienced several unannounced and unknown disengagements of the autoplt during climbs, cruise, and dscnts and caught them during normal monitoring of the autoplt while it was flying. Because our descent was shallow and because we were both filling out our customs forms, no one noticed we had descended through our assigned altitude until we were 500 ft below it. My first officer corrected promptly and no traffic was on TCASII. Being a saturday, it was a light traffic day on the ATC frequency. ZBW didn't mention the altitude deviation. I still don't know why the autoplt disengaged. I'm concerned that this primus 1000 does not announce disengagement above 2500 ft. I have talked to several crew members who have experienced similar unexplained disengagements. In the future, I will pay closer attention to monitoring the autoplt so that a deviation does not occur in the future as a result of an unexplained and unannounced disengagement and supervise my first officer's more closely during autoflt. A simple change in the primus 1000 software would probably solve this announcement problem. Callback conversation with reporter revealed the following information: reporter indicated that he has had another disconnect incident since his initial report on the EMB145 autoplt problem. The company has been informed of the inadequate warning system and he is intending to inform his airline union safety committee. The only warning that the crew receives from an autoplt disconnect in-flight above 2500 ft is when the little light goes out in the corner quadrant of the autoplt 'push to engage' button. One must be very alert to this light being lit and it is difficult at best to note any change in the status of the autoplt.

Google
 

Original NASA ASRS Text

Title: AN EMB-145 FLC OVERSHOT THEIR ALT WHEN THEY WERE UNAWARE THAT THE AUTOPLT HAD DISCONNECTED AND FAILED TO LEVEL THE ACFT AT 14000 FT. THE AUTOPLT DESIGN WAS CRITICIZED FOR NOT HAVING A WARNING SYS ALERT WHEN DISCONNECT OCCURS OVER 2500 FT AGL. BOTH PLTS WERE FILLING OUT CUSTOMS FORMS IN DSCNT.

Narrative: WE WERE FLYING FROM HALIFAX, NOVA SCOTIA (YHZ), TO NEWARK (EWR) ON A STAR AND GIVEN A DSCNT CLRNC TO 14000 FT. I'M NOT SURE TODAY IF THIS WAS THE ALT ATC GAVE US, BUT IT WAS AN EVEN MIDDLE-TEEN ALT AND I WAS SURE OF THE ALT ON THE DAY OF THIS INCIDENT -- THAT WAS NOT THE ISSUE. WHILE DSNDING ROUTINELY, IT WAS THE FO'S LEG AND I WAS FILLING OUT OUR CREW DECLARATION CUSTOMS FORM. I NOTICED THAT MY FO WAS ALSO FILLING OUT HER CUSTOMS FORM, SO I WOULD OCCASIONALLY LOOK UP TO MONITOR OUR FLT SIT. THE AUTOPLT WAS ON AND DSNDING INITIALLY, BUT HAD SOMEHOW DISENGAGED WITHOUT US KNOWING WHY. THE AUTOPLT AURAL WARNING ANNOUNCING DISENGAGEMENT ONLY OCCURS BELOW 2500 FT AGL AND NOT AT ANY OTHER ALTS ABOVE THAT. I HAVE ALREADY EXPERIENCED SEVERAL UNANNOUNCED AND UNKNOWN DISENGAGEMENTS OF THE AUTOPLT DURING CLBS, CRUISE, AND DSCNTS AND CAUGHT THEM DURING NORMAL MONITORING OF THE AUTOPLT WHILE IT WAS FLYING. BECAUSE OUR DSCNT WAS SHALLOW AND BECAUSE WE WERE BOTH FILLING OUT OUR CUSTOMS FORMS, NO ONE NOTICED WE HAD DSNDED THROUGH OUR ASSIGNED ALT UNTIL WE WERE 500 FT BELOW IT. MY FO CORRECTED PROMPTLY AND NO TFC WAS ON TCASII. BEING A SATURDAY, IT WAS A LIGHT TFC DAY ON THE ATC FREQ. ZBW DIDN'T MENTION THE ALTDEV. I STILL DON'T KNOW WHY THE AUTOPLT DISENGAGED. I'M CONCERNED THAT THIS PRIMUS 1000 DOES NOT ANNOUNCE DISENGAGEMENT ABOVE 2500 FT. I HAVE TALKED TO SEVERAL CREW MEMBERS WHO HAVE EXPERIENCED SIMILAR UNEXPLAINED DISENGAGEMENTS. IN THE FUTURE, I WILL PAY CLOSER ATTN TO MONITORING THE AUTOPLT SO THAT A DEV DOES NOT OCCUR IN THE FUTURE AS A RESULT OF AN UNEXPLAINED AND UNANNOUNCED DISENGAGEMENT AND SUPERVISE MY FO'S MORE CLOSELY DURING AUTOFLT. A SIMPLE CHANGE IN THE PRIMUS 1000 SOFTWARE WOULD PROBABLY SOLVE THIS ANNOUNCEMENT PROB. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR INDICATED THAT HE HAS HAD ANOTHER DISCONNECT INCIDENT SINCE HIS INITIAL RPT ON THE EMB145 AUTOPLT PROB. THE COMPANY HAS BEEN INFORMED OF THE INADEQUATE WARNING SYS AND HE IS INTENDING TO INFORM HIS AIRLINE UNION SAFETY COMMITTEE. THE ONLY WARNING THAT THE CREW RECEIVES FROM AN AUTOPLT DISCONNECT INFLT ABOVE 2500 FT IS WHEN THE LITTLE LIGHT GOES OUT IN THE CORNER QUADRANT OF THE AUTOPLT 'PUSH TO ENGAGE' BUTTON. ONE MUST BE VERY ALERT TO THIS LIGHT BEING LIT AND IT IS DIFFICULT AT BEST TO NOTE ANY CHANGE IN THE STATUS OF THE AUTOPLT.

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.