Narrative:

Our clearance included the gibbz RNAV STAR into iad. When we were way above the descent path; the controller cleared us to descend via the arrival. I pushed direct to the next altitude in the FMS to try to bring back the pink vertical guidance in order to engage VNAV and that next altitude went away. Can't really explain why that happened.as a result the pilot not flying had to pull the arrival back out of the ipad and it took a while to get the correct first altitude for the descent. We descended as steeply as we could with speed brakes but we went a little past the fix before we got to the right altitude. They were all below and above altitudes; we could never get the VNAV in a position to engage so the non flying pilot had to keep putting in altitudes manually which I think we hit ok after the first one except for one problem - while hurrying down and trying to get all the altitudes put in manually we didn't reset the altimeter passing FL180. We weren't neglecting the checklist; we were just surprised that VNAV wouldn't engage and were so busy manually managing that quick descent. I think we were probably ok because the pilot not flying put the middle altitudes between the limits and I think we hit those pretty well; but it was the sloppiest descend via I've ever done with the speed not too consistent either. The controller never said anything; I hope he realized he put us in a bad position on that first descent and there was no conflict.I should have had my ipad out on the arrival and been briefing that the VNAV might not take since we were well above the TOD for that arrival. We speculated afterwards that the box didn't like direct the next altitude because it had between this and that altitude listed so it probably didn't know what I wanted and just took both altitudes out because of that. We've got to make sure we don't lose the most important chart in the ipad or put it to sleep when we might need it also. Mostly I think we were both too relaxed because we had verified and briefed all the altitudes and speeds in the box and it usually works so well. I trusted that the VNAV would work when we were beyond its limits and I should have been more keyed up for that arrival when we didn't start down on schedule. Also I should have told ATC when I began to doubt we could make that first fix. I don't know how well it would have gone over to say we are having a programming problem; unable to descend via but that thought also crossed my mind.

Related reports:

Google
 

Original NASA ASRS Text

Title: When a CE-750 flight crew failed to initiate a timely descent on the GIBBZ RNAV STAR to IAD the FMS lost all altitude and airspeed constraints and the crew distractions which resulted were significant including failure to QNH passing FL180 and forgetting to do SOP arrival checklists. Crossing restrictions were also problematic and deviations were likely if for no other reason than the altimeter setting which would have produced about 500 foot errors.

Narrative: Our clearance included the GIBBZ RNAV STAR into IAD. When we were way above the descent path; the Controller cleared us to descend via the arrival. I pushed direct to the next altitude in the FMS to try to bring back the pink vertical guidance in order to engage VNAV and that next altitude went away. Can't really explain why that happened.As a result the pilot not flying had to pull the arrival back out of the iPad and it took a while to get the correct first altitude for the descent. We descended as steeply as we could with speed brakes but we went a little past the fix before we got to the right altitude. They were all below and above altitudes; we could never get the VNAV in a position to engage so the non flying pilot had to keep putting in altitudes manually which I think we hit OK after the first one except for one problem - while hurrying down and trying to get all the altitudes put in manually we didn't reset the altimeter passing FL180. We weren't neglecting the checklist; we were just surprised that VNAV wouldn't engage and were so busy manually managing that quick descent. I think we were probably OK because the pilot not flying put the middle altitudes between the limits and I think we hit those pretty well; but it was the sloppiest descend via I've ever done with the speed not too consistent either. The Controller never said anything; I hope he realized he put us in a bad position on that first descent and there was no conflict.I should have had my iPad out on the arrival and been briefing that the VNAV might not take since we were well above the TOD for that arrival. We speculated afterwards that the box didn't like direct the next altitude because it had between this and that altitude listed so it probably didn't know what I wanted and just took both altitudes out because of that. We've got to make sure we don't lose the most important chart in the iPad or put it to sleep when we might need it also. Mostly I think we were both too relaxed because we had verified and briefed all the altitudes and speeds in the box and it usually works so well. I trusted that the VNAV would work when we were beyond its limits and I should have been more keyed up for that arrival when we didn't start down on schedule. Also I should have told ATC when I began to doubt we could make that first fix. I don't know how well it would have gone over to say we are having a programming problem; unable to descend via but that thought also crossed my mind.

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