Narrative:

Inbound to teb on the JAIKE3 RNAV STAR we were given a 'descend via' clearance. As part of our arrival brief we verified all fixes and crossing restrictions in the FMS. Filed for the fak transition; we were taken off route then given another fix on the arrival; ott; and shortly thereafter given a heading and sent back to the arrival after several minutes on the heading. To comply with the 'descend via' clearance; we set the bottom altitude in the altitude selector; verified that TOD was ahead of us; and armed vpath. Vpath captured and the aircraft began the descent. Not long after we were handed off to philadelphia approach and given several speed restrictions before being turned over to new york approach. As we crossed jaike we saw that we were at 15;000 feet and descending as opposed to the 13;000 feet required by the STAR. Not long after we noticed our error; approach asked if we were descending to 13;000 and asked us to expedite. Separation requirements were never violated and neither our flight nor any other was in any danger nor was the flow of traffic impeded. We cancelled vpath and increased our descent in the vertical speed mode. We reviewed the automation inputs and selections and verified they were correct. We have no idea as to why the aircraft did not comply. We are unclear as to what anomaly caused the aircraft to miss this crossing restriction. We both verified the inputs to the FMS and altitude selector and the aircraft did descend toward 13;000 but not a rate to meet the crossing restriction at jaike. That said; we were also complacent in not monitoring the descent and cross-checking the aircraft position with the requirements of the arrival. Distractions played a role as speed changes; heading changes; and frequency changes were also occurring during this time. Additionally; both pilots were fatigued from two (three for the pm) consecutive early morning wake-ups for early am departures. Maintenance issues the previous night contributed to fatigue. Always; always; verify that the aircraft is doing exactly what you expect it to do. Never assume the automation is infallible and incapable of succumbing to the occasional gremlin. Both pilots should cross the aircraft's position and progress when approaching crossing restrictions.

Related reports:

Google
 

Original NASA ASRS Text

Title: Captain reported failing to make a mandatory crossing altitude on an RNAV Arrival.

Narrative: Inbound to TEB on the JAIKE3 RNAV STAR we were given a 'Descend Via' clearance. As part of our arrival brief we verified all fixes and crossing restrictions in the FMS. Filed for the FAK transition; we were taken off route then given another fix on the arrival; OTT; and shortly thereafter given a heading and sent back to the arrival after several minutes on the heading. To comply with the 'Descend Via' clearance; we set the bottom altitude in the altitude selector; verified that TOD was ahead of us; and armed VPATH. VPATH captured and the aircraft began the descent. Not long after we were handed off to Philadelphia Approach and given several speed restrictions before being turned over to New York Approach. As we crossed JAIKE we saw that we were at 15;000 feet and descending as opposed to the 13;000 feet required by the STAR. Not long after we noticed our error; Approach asked if we were descending to 13;000 and asked us to expedite. Separation requirements were never violated and neither our flight nor any other was in any danger nor was the flow of traffic impeded. We cancelled VPATH and increased our descent in the Vertical Speed mode. We reviewed the automation inputs and selections and verified they were correct. We have no idea as to why the aircraft did not comply. We are unclear as to what anomaly caused the aircraft to miss this crossing restriction. We both verified the inputs to the FMS and Altitude Selector and the aircraft did descend toward 13;000 but not a rate to meet the crossing restriction at JAIKE. That said; we were also complacent in not monitoring the descent and cross-checking the aircraft position with the requirements of the arrival. Distractions played a role as speed changes; heading changes; and frequency changes were also occurring during this time. Additionally; both pilots were fatigued from two (three for the PM) consecutive early morning wake-ups for early AM departures. Maintenance issues the previous night contributed to fatigue. Always; always; verify that the aircraft is doing exactly what you expect it to do. Never assume the automation is infallible and incapable of succumbing to the occasional gremlin. Both pilots should cross the aircraft's position and progress when approaching crossing restrictions.

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.