Narrative:

This was our second leg in this aircraft and had no issues prior to this event.on descent into ewr on the PHLBO3 arrival; the aircraft just prior to a crossing restriction pitched down. Even with a relatively quick reaction; the aircraft went 800 feet below the altitude restriction.we began our descent from cruise to fubar intersection normally; meeting the restriction with no issue. There was a tailwind in the descent but the aircraft was not having any problems maintaining profile. The only modification the first officer made to the arrival was the addition of speed restrictions. They were added to avoid receiving 'steep descent after dqo' and 'steep descent after somto' scratch pad messages. The first speed restriction added was at dqo. The first officer put 300 KTS next to the preprogrammed altitude restriction of 200A. The next speed restriction added was 270 at somto. Prior to dqo VNAV was not having any problem with the descent. I was watching closely as sometimes with good tailwinds on this arrival the aircraft can struggle maintaining speed. This was not the case this evening. There was a decel circle just prior to dqo which makes sense as the descent page had 310 KTS programmed and a 300/FL200A restriction. During this event; the aircraft was in VNAV pth. As the aircraft reached the decel point approximately 2 miles from the dqo VOR at an altitude just slightly above the crossing restriction; the aircraft did the opposite of what I expected it to do. I was expecting the aircraft to slightly pitch up to slow the 10 KTS and meet the FL200A crossing restriction and continue down the arrival. Instead the aircraft pitched down increasing an already high rate of descent. I made a comment to the first officer along the lines of 'what is this thing doing now'. There was a slight hesitation (I am talking 1 potato 2 potato) on both our parts as the aircraft was in VNAV pth and was now rapidly passing through the FL200A restriction just prior dqo instead of honoring the altitude. I intervened turning off the ap and pitching up; but not wanting to be aggressive on the controls ended [up] crossing dqo at FL192. The ap was turned back on and the remainder of the flight continued without any other issues with the VNAV. As a side note we did receive a message several minutes after passing dqo VOR 'steep descent after dqo'. I have not seen a message like that come up after having passed the fix.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737NG Captain reported overshooting a crossing altitude restriction when the aircraft aggressively pitched down unexpectedly on the PHLBO3 arrival into EWR.

Narrative: This was our second leg in this aircraft and had no issues prior to this event.On descent into EWR on the PHLBO3 arrival; the aircraft just prior to a crossing restriction pitched down. Even with a relatively quick reaction; the aircraft went 800 feet below the altitude restriction.We began our descent from cruise to FUBAR intersection normally; meeting the restriction with no issue. There was a tailwind in the descent but the aircraft was not having any problems maintaining profile. The only modification the First Officer made to the arrival was the addition of speed restrictions. They were added to avoid receiving 'STEEP DESCENT AFTER DQO' and 'STEEP DESCENT AFTER SOMTO' scratch pad messages. The first speed restriction added was at DQO. The FO put 300 KTS next to the preprogrammed ALT restriction of 200A. The next speed restriction added was 270 at SOMTO. Prior to DQO VNAV was not having any problem with the descent. I was watching closely as sometimes with good tailwinds on this arrival the aircraft can struggle maintaining speed. This was not the case this evening. There was a DECEL circle just prior to DQO which makes sense as the descent page had 310 KTS programmed and a 300/FL200A restriction. During this event; the aircraft was in VNAV PTH. As the aircraft reached the DECEL point approximately 2 miles from the DQO VOR at an altitude just slightly above the crossing restriction; the aircraft did the opposite of what I expected it to do. I was expecting the aircraft to slightly pitch up to slow the 10 KTS and meet the FL200A crossing restriction and continue down the arrival. Instead the aircraft pitched down increasing an already high rate of descent. I made a comment to the First Officer along the lines of 'what is this thing doing now'. There was a slight hesitation (I am talking 1 potato 2 potato) on both our parts as the aircraft was in VNAV PTH and was now rapidly passing through the FL200A restriction just prior DQO instead of honoring the altitude. I intervened turning off the AP and pitching up; but not wanting to be aggressive on the controls ended [up] crossing DQO at FL192. The AP was turned back on and the remainder of the flight continued without any other issues with the VNAV. As a side note we did receive a message several minutes after passing DQO VOR 'STEEP DESCENT AFTER DQO'. I have not seen a message like that come up after having passed the fix.

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.