Narrative:

Cleared descend via the jaike three arrival. Descent to 11;000 ft begun before ilene; ilene has a mandatory 13;000 ft altitude. Two equipment problems; a similar aircraft call sign; an extremely busy frequency and multiple speed change requests contributed to the deviation. The two equipment problems: the FMS would not stay in the full performance mode; periodically dropping into current mode causing the VNAV to be unavailable; therefore we did not have VNAV available for this procedure. Second; the intercom was intermittent from the left seat to the right. I could not hear the captain much of the time; as if the squelch was not sensitive enough. These two items increased our workload. Three minutes ahead of us was another aircraft on the same path a while. The controller before this one had struggled twice with getting the call signs correct; and I took one call of theirs earlier; again; increasing attention required and stress. Finally we had approximately 5 speed change requests in the 2-3 minutes before the altitude deviation from 280; down to 250; up to 290 and back to 250. The deviation occurred shortly after crossing jaike at the 13;000 ft mandatory altitude. We were calculating the descent rate needed to reach wacki at 11;000; and has just been given another airspeed reduction from 290 to 250. The pilot flying called for 11;000 in the altitude alerter; which I did (and should have questioned; but did not.) the pilot flying started down and asked me to verify the 250 speed request. When I asked the controller if he wanted 250 at wacki the controller said yes; and that we should not have started down yet. The pilot flying and I immediately recognized the error and the pilot flying called ATC and asked if we should go back up; he said no; the current altitude was ok. We were 600 ft low about 3-4 miles early. Having two fixes with 13;000 ft mandatory altitudes 26 miles apart; followed by a descent to 11;000 in 8 miles contributed as well. We were simply overloaded with too many numbers and calculations happening simultaneously. I was very frustrated with myself for not catching this error before it happened. While trying to find the live ATC feed to hear for review and clarity I came across this article published in july. It turns out this is a very common mistake. 'TRACON is concerned over the growing number of deviations from the published altitudes on the jaike three. Failure to comply with these published altitude restrictions will result in loss of separation between adjacent traffic thereby creating a significant safety hazard. During a recent controller shift; 4 out of 7 airplanes (57%) failed to comply with the 'at' 13;000 restriction at ilene (i.e. Descended early after passing jaike at 13;000 ft.' knowing other pilots also make this mistake is not an excuse for me to make it. However; if most pilots are making the exact same mistake in the same place this is a flawed procedure. I hope this report can contribute to changes.

Google
 

Original NASA ASRS Text

Title: A BAE-125-850XP; with an inoperative VNAV FMS mode; descended 500 FT before the 13;000 FT JAIKE 3 ILENE constraint before ATC and crew saw the descent to 11;000 FT begin.

Narrative: Cleared descend via the JAIKE THREE Arrival. Descent to 11;000 FT begun before ILENE; ILENE has a mandatory 13;000 FT altitude. Two equipment problems; a similar aircraft call sign; an extremely busy frequency and multiple speed change requests contributed to the deviation. The two equipment problems: The FMS would not stay in the full performance mode; periodically dropping into current mode causing the VNAV to be unavailable; therefore we did not have VNAV available for this procedure. Second; the intercom was intermittent from the left seat to the right. I could not hear the Captain much of the time; as if the squelch was not sensitive enough. These two items increased our workload. Three minutes ahead of us was another aircraft on the same path a while. The Controller before this one had struggled twice with getting the call signs correct; and I took one call of theirs earlier; again; increasing attention required and stress. Finally we had approximately 5 speed change requests in the 2-3 minutes before the altitude deviation from 280; down to 250; up to 290 and back to 250. The deviation occurred shortly after crossing JAIKE at the 13;000 FT mandatory altitude. We were calculating the descent rate needed to reach WACKI at 11;000; and has just been given another airspeed reduction from 290 to 250. The pilot flying called for 11;000 in the altitude alerter; which I did (and should have questioned; but did not.) The pilot flying started down and asked me to verify the 250 speed request. When I asked the Controller if he wanted 250 at WACKI the Controller said yes; and that we should not have started down yet. The pilot flying and I immediately recognized the error and the pilot flying called ATC and asked if we should go back up; he said no; the current altitude was OK. We were 600 FT low about 3-4 miles early. Having two fixes with 13;000 FT mandatory altitudes 26 miles apart; followed by a descent to 11;000 in 8 miles contributed as well. We were simply overloaded with too many numbers and calculations happening simultaneously. I was very frustrated with myself for not catching this error before it happened. While trying to find the Live ATC feed to hear for review and clarity I came across this article published in July. It turns out this is a VERY common mistake. 'TRACON is concerned over the growing number of deviations from the published altitudes on the JAIKE Three. Failure to comply with these published altitude restrictions will result in loss of separation between adjacent traffic thereby creating a significant safety hazard. During a recent controller shift; 4 out of 7 airplanes (57%) failed to comply with the 'at' 13;000 restriction at ILENE (i.e. descended early after passing JAIKE at 13;000 FT.' Knowing other pilots also make this mistake is not an excuse for me to make it. However; if MOST pilots are making the exact same mistake in the same place this is a flawed procedure. I hope this report can contribute to changes.

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.