Narrative:

While flying with standard rose mode on the EFIS navigation display using VOR-DME navigation, I began descending to cross rhome at 9000 ft as instructed by center. Approaching bpr we were instructed to contact approach control. Just prior to turning, the first officer alerted me that we were high. Turning to intercept the bpr 108 degree radial and descending as quickly as possible we called approach and advised that we would be unable to make the restriction. He made a comment relating to our turn being made early and said 'there are good reasons for these restrictions.' we crossed rhome at about 11000 ft and approach issued us a vector and a lower altitude. Factors affecting this incident include: tiredness from a restless and short nights sleep along with getting up at early body time at the end of 4 day trip. A cluttered STAR chart which led me to mistake DME mileage at boids (13 DME) for rhome (5 DME). Twice! First officer was performing other descent and approach functions and missed my mistake even though I verbalized it twice. He did alert me when he noticed our situation but by then it was impossible to make the restriction. Our handoff came at a time when there was no time to do anything but check-in and report our situation to ATC. My failure to xchk the first officer's map display which clearly showed our proximity to rhome. This event underscores the importance of both the PF and the PNF constantly checking themselves and each other especially in the dynamic and busy descent and approach phase. I believe that the names of intxns should appear at the fix symbol and also with the additional information that is tagged to the fix by use of an arrow.

Google
 

Original NASA ASRS Text

Title: CLRED TO CROSS RHODES INTXN AT 9000 FT BUT ONLY GOT TO 11000 FT.

Narrative: WHILE FLYING WITH STANDARD ROSE MODE ON THE EFIS NAV DISPLAY USING VOR-DME NAV, I BEGAN DSNDING TO CROSS RHOME AT 9000 FT AS INSTRUCTED BY CTR. APCHING BPR WE WERE INSTRUCTED TO CONTACT APCH CTL. JUST PRIOR TO TURNING, THE FO ALERTED ME THAT WE WERE HIGH. TURNING TO INTERCEPT THE BPR 108 DEG RADIAL AND DSNDING AS QUICKLY AS POSSIBLE WE CALLED APCH AND ADVISED THAT WE WOULD BE UNABLE TO MAKE THE RESTRICTION. HE MADE A COMMENT RELATING TO OUR TURN BEING MADE EARLY AND SAID 'THERE ARE GOOD REASONS FOR THESE RESTRICTIONS.' WE CROSSED RHOME AT ABOUT 11000 FT AND APCH ISSUED US A VECTOR AND A LOWER ALT. FACTORS AFFECTING THIS INCIDENT INCLUDE: TIREDNESS FROM A RESTLESS AND SHORT NIGHTS SLEEP ALONG WITH GETTING UP AT EARLY BODY TIME AT THE END OF 4 DAY TRIP. A CLUTTERED STAR CHART WHICH LED ME TO MISTAKE DME MILEAGE AT BOIDS (13 DME) FOR RHOME (5 DME). TWICE! FO WAS PERFORMING OTHER DSCNT AND APCH FUNCTIONS AND MISSED MY MISTAKE EVEN THOUGH I VERBALIZED IT TWICE. HE DID ALERT ME WHEN HE NOTICED OUR SITUATION BUT BY THEN IT WAS IMPOSSIBLE TO MAKE THE RESTRICTION. OUR HDOF CAME AT A TIME WHEN THERE WAS NO TIME TO DO ANYTHING BUT CHK-IN AND RPT OUR SITUATION TO ATC. MY FAILURE TO XCHK THE FO'S MAP DISPLAY WHICH CLRLY SHOWED OUR PROX TO RHOME. THIS EVENT UNDERSCORES THE IMPORTANCE OF BOTH THE PF AND THE PNF CONSTANTLY CHKING THEMSELVES AND EACH OTHER ESPECIALLY IN THE DYNAMIC AND BUSY DSCNT AND APCH PHASE. I BELIEVE THAT THE NAMES OF INTXNS SHOULD APPEAR AT THE FIX SYMBOL AND ALSO WITH THE ADDITIONAL INFO THAT IS TAGGED TO THE FIX BY USE OF AN ARROW.

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.