Narrative:

On the third day of a 4 day trip, we departed sfo for ind 1 1/2 hours late because of an aircraft change (mechanical). After an ATC hold in ind we took off 2 1/2 hours late for newark. En route we were rerted because of WX south to richmond, va, direct pxt, warrd 3 arrival ewr. We programmed our navigation system for the warrd 3, including the expected crossing altitudes. We were cleared for the arrival and then to cross 20 mi southwest of eno at and maintain FL240. Using the fix page I created the uncharted fix, inserted it on the legs page prior to eno, then entered the crossing altitude of FL240. After the computer calculated the descent information, I selected capture on the descent page and began a 1000 FPM descent. Great! But in doublechking my actions, I discovered that the crossing fix should have been placed prior to 'canny' because canny is only 13 mi southwest of eno. I then sluggishly (fatigue) reselected the crossing fix from the fix page and inserted it before canny, and deleted it after canny. Very soon after completing this reprogramming, canny jumped to the top of the legs page, indicating that we had crossed the uncharted fix. Simultaneously, ATC cleared us to continue descent to FL190. The controller made no other comments, although we noted crossing the 20 mi fix descending through FL270 instead of 240. Remainder of the arrival and ILS 22L at ewr was routine. Obviously my lack of experience on the advanced cockpit medium large transport, fatigue, and lack of a meal in over 9 hours were contributing factors, but I believe the real problem is ATC's lack of understanding of the time it takes to reprogram our navigation system. It would be very helpful if they would clear us via the expected fixes and altitudes on departures and arrs (this is done much more consistently on the west coast than in the east). If the charted arrs don't work, change the SID/STAR charts. It if is absolutely necessary to change a crossing fix, try to make it a fix on the arrival (like 'canny') rather than an uncharted fix, so only the altitude needs to be programmed, and if an uncharted fix must be used, reference it to the next fix on the arrival, not the VOR. Many of my fellow advanced cockpit medium large transport pilots tell me they don't use the magic box during descent -- I'm beginning to see why -- but what a waste. Supplemental information from acn 189585: it was about 0x50 in the morning and we were both tired. This was the third day of a 4 day trip.

Google
 

Original NASA ASRS Text

Title: ACR FLC COMPLAINS OF ATC ARR PROC WHEN XING RESTRICTIONS ARE AMENDED TO ALTS AND XING POINTS OTHER THAN DISPLAYED ON THE STAR CHARTS, RESULTING IN TASK INDUCED REPROGRAMMING DELAYS AND POSSIBLE MISPROGRAMMING. ALTDEV ALT UNDERSHOT.

Narrative: ON THE THIRD DAY OF A 4 DAY TRIP, WE DEPARTED SFO FOR IND 1 1/2 HRS LATE BECAUSE OF AN ACFT CHANGE (MECHANICAL). AFTER AN ATC HOLD IN IND WE TOOK OFF 2 1/2 HRS LATE FOR NEWARK. ENRTE WE WERE RERTED BECAUSE OF WX S TO RICHMOND, VA, DIRECT PXT, WARRD 3 ARR EWR. WE PROGRAMMED OUR NAV SYS FOR THE WARRD 3, INCLUDING THE EXPECTED XING ALTS. WE WERE CLRED FOR THE ARR AND THEN TO CROSS 20 MI SW OF ENO AT AND MAINTAIN FL240. USING THE FIX PAGE I CREATED THE UNCHARTED FIX, INSERTED IT ON THE LEGS PAGE PRIOR TO ENO, THEN ENTERED THE XING ALT OF FL240. AFTER THE COMPUTER CALCULATED THE DSCNT INFO, I SELECTED CAPTURE ON THE DSCNT PAGE AND BEGAN A 1000 FPM DSCNT. GREAT! BUT IN DOUBLECHKING MY ACTIONS, I DISCOVERED THAT THE XING FIX SHOULD HAVE BEEN PLACED PRIOR TO 'CANNY' BECAUSE CANNY IS ONLY 13 MI SW OF ENO. I THEN SLUGGISHLY (FATIGUE) RESELECTED THE XING FIX FROM THE FIX PAGE AND INSERTED IT BEFORE CANNY, AND DELETED IT AFTER CANNY. VERY SOON AFTER COMPLETING THIS REPROGRAMMING, CANNY JUMPED TO THE TOP OF THE LEGS PAGE, INDICATING THAT WE HAD CROSSED THE UNCHARTED FIX. SIMULTANEOUSLY, ATC CLRED US TO CONTINUE DSCNT TO FL190. THE CTLR MADE NO OTHER COMMENTS, ALTHOUGH WE NOTED XING THE 20 MI FIX DSNDING THROUGH FL270 INSTEAD OF 240. REMAINDER OF THE ARR AND ILS 22L AT EWR WAS ROUTINE. OBVIOUSLY MY LACK OF EXPERIENCE ON THE ADVANCED COCKPIT MLG, FATIGUE, AND LACK OF A MEAL IN OVER 9 HRS WERE CONTRIBUTING FACTORS, BUT I BELIEVE THE REAL PROBLEM IS ATC'S LACK OF UNDERSTANDING OF THE TIME IT TAKES TO REPROGRAM OUR NAV SYS. IT WOULD BE VERY HELPFUL IF THEY WOULD CLR US VIA THE EXPECTED FIXES AND ALTS ON DEPS AND ARRS (THIS IS DONE MUCH MORE CONSISTENTLY ON THE W COAST THAN IN THE E). IF THE CHARTED ARRS DON'T WORK, CHANGE THE SID/STAR CHARTS. IT IF IS ABSOLUTELY NECESSARY TO CHANGE A XING FIX, TRY TO MAKE IT A FIX ON THE ARR (LIKE 'CANNY') RATHER THAN AN UNCHARTED FIX, SO ONLY THE ALT NEEDS TO BE PROGRAMMED, AND IF AN UNCHARTED FIX MUST BE USED, REF IT TO THE NEXT FIX ON THE ARR, NOT THE VOR. MANY OF MY FELLOW ADVANCED COCKPIT MLG PLTS TELL ME THEY DON'T USE THE MAGIC BOX DURING DSCNT -- I'M BEGINNING TO SEE WHY -- BUT WHAT A WASTE. SUPPLEMENTAL INFO FROM ACN 189585: IT WAS ABOUT 0X50 IN THE MORNING AND WE WERE BOTH TIRED. THIS WAS THE THIRD DAY OF A 4 DAY TRIP.

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