Light Transport; Low Wing; 2 Turbojet Eng
Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Flight Crew Last 90 Days 75; Flight Crew Total 12800; Flight Crew Type 600
Distraction; Human-Machine Interface; Workload; Situational Awareness
Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew FLC Overrode Automation; Flight Crew Returned To Clearance
Aircraft; Human Factors; Procedure
While on arrival to BED (Hanscom) Airport; we were given a descent clearance to descend to and maintain FL240. Our location; at that time; was just west of EEGUL intersection. In preparation for an anticipated descend via clearance; I attempted to load a VNAV descent to cross TERIA at FL240. The first attempt to set-up the VNAV was not successful and the flight director was giving me a steeper descent profile than was necessary. At approximately the same time; Center issued a descent via the ZELKA 1 RNAV arrival. This required me to cross TERIA intersection at FL240. At this point the descent profile was loaded in the FMZ2000 Flight Management System. All that should have been required was to press the DIR button; line select FL240 at TERIA intersection; and engage VNAV to give us vertical guidance to cross TERIA intersection at FL240. Once again; the flight director gave us a steeper descent profile than was necessary. After a failed second attempt to use VNAV and being very close to TERIA intersection; at a descent rate that was higher than what was required; I disengaged the autopilot and VNAV and took over manually. At this point; we were just west of TERIA intersection and at an altitude of 23;700. I was attempting to arrest the descent and start a climb back to FL240 to cross TERIA intersection when Center advised us that the descend via clearance required us to cross TERIA intersection at FL240. We agreed and advised Center that we were dealing with a problem and we were climbing back to FL240. Center then issued a clearance to cross TERIA intersection at FL230 and descend via ZELKA 1 RNAV arrival. We continued the descent as cleared.It is my belief that what led up to the addressed situation is twofold. First; I relied too much on automation; rather than taking over and flying the aircraft before it got to this point. Second; I was paired with a First Officer who had not been in the actual aircraft in quite some time. I discovered along the way that he was starting to 'get behind the airplane' with his limited knowledge of the FMZ2000 FMS; which added to my workload as the flying pilot.To correct this situation and ensure it doesn't happen again; I think we would all be better off by not relying so much on automation.
My main error was not realizing an altitude deviation was about to occur before we got to FL240. I was distracted by my call to the FBO. I trusted the automation too much. Also; the Captain told me he had selected VNAV. I do not know if he did because after I selected the lower altitude; and he verified it; I changed my attention to going to another frequency to call the FBO. I should have observed his management of the autopilot and verified the settings before I did other things.
Corporate jet flight crew and Air Traffic Controllers reported on the cause and effects of the jet not meeting the crossing restriction at TERIA intersection on the ZELKA 1 RNAV Arrival at BED.