Narrative:

While in descent on the panoche two arrival to oakland, ca, we were advised to expect a crossing restr of 8000 ft at bored intersection. According to the panoche two STAR, an 8000 ft crossing is normally an altitude assigned to turboprop aircraft while jet aircraft are assigned a 10000 ft crossing altitude. We did not notice the error and continued with our descent. Approximately 30 NM south of bored, the controller instructed us to cross bored at 8000 ft. Our altitude was approximately 24000 ft. We continued our descent and when it became evident to the controller that we were not going to make the restr we were given the choice of making a 360 degree turn or making sure we made the restr. We initially tried to make the restr and when we realized it wouldn't be safely possible we requested the turn. After 2 requests, the controller leveled us at 14000 ft, turned us off the arrival and vectored us back to bored. He then reissued the crossing restr, which we complied with, and a normal flight continued from there. One of the contributing factors to this difficulty in complying with the restrs was an FMS database error relevant to our distance from bored intersection. Our kln 90B gave erroneous readings as to our location and we were not backing up the distance readout with standard VHF/DME equipment. Even though the descent was inappropriate for our aircraft type, we could have possibly made the restr if we had received more accurate position information. The controller never referenced our actual distance nor did we query him on our distance from bored. We have since updated and checked our database information. We have also established a company policy requiring standard back up information for the electronic data being received during all flight regimes. Along with the backup information, we strongly emphasize the need for constant xchking of all available information.

Related reports:

Google
 

Original NASA ASRS Text

Title: C550 INBOUND TO OAK IS UNABLE TO COMPLY WITH ISSUED XING ALT.

Narrative: WHILE IN DSCNT ON THE PANOCHE TWO ARR TO OAKLAND, CA, WE WERE ADVISED TO EXPECT A XING RESTR OF 8000 FT AT BORED INTXN. ACCORDING TO THE PANOCHE TWO STAR, AN 8000 FT XING IS NORMALLY AN ALT ASSIGNED TO TURBOPROP ACFT WHILE JET ACFT ARE ASSIGNED A 10000 FT XING ALT. WE DID NOT NOTICE THE ERROR AND CONTINUED WITH OUR DSCNT. APPROX 30 NM S OF BORED, THE CTLR INSTRUCTED US TO CROSS BORED AT 8000 FT. OUR ALT WAS APPROX 24000 FT. WE CONTINUED OUR DSCNT AND WHEN IT BECAME EVIDENT TO THE CTLR THAT WE WERE NOT GOING TO MAKE THE RESTR WE WERE GIVEN THE CHOICE OF MAKING A 360 DEG TURN OR MAKING SURE WE MADE THE RESTR. WE INITIALLY TRIED TO MAKE THE RESTR AND WHEN WE REALIZED IT WOULDN'T BE SAFELY POSSIBLE WE REQUESTED THE TURN. AFTER 2 REQUESTS, THE CTLR LEVELED US AT 14000 FT, TURNED US OFF THE ARR AND VECTORED US BACK TO BORED. HE THEN REISSUED THE XING RESTR, WHICH WE COMPLIED WITH, AND A NORMAL FLT CONTINUED FROM THERE. ONE OF THE CONTRIBUTING FACTORS TO THIS DIFFICULTY IN COMPLYING WITH THE RESTRS WAS AN FMS DATABASE ERROR RELEVANT TO OUR DISTANCE FROM BORED INTXN. OUR KLN 90B GAVE ERRONEOUS READINGS AS TO OUR LOCATION AND WE WERE NOT BACKING UP THE DISTANCE READOUT WITH STANDARD VHF/DME EQUIP. EVEN THOUGH THE DSCNT WAS INAPPROPRIATE FOR OUR ACFT TYPE, WE COULD HAVE POSSIBLY MADE THE RESTR IF WE HAD RECEIVED MORE ACCURATE POS INFO. THE CTLR NEVER REFED OUR ACTUAL DISTANCE NOR DID WE QUERY HIM ON OUR DISTANCE FROM BORED. WE HAVE SINCE UPDATED AND CHKED OUR DATABASE INFO. WE HAVE ALSO ESTABLISHED A COMPANY POLICY REQUIRING STANDARD BACK UP INFO FOR THE ELECTRONIC DATA BEING RECEIVED DURING ALL FLT REGIMES. ALONG WITH THE BACKUP INFO, WE STRONGLY EMPHASIZE THE NEED FOR CONSTANT XCHKING OF ALL AVAILABLE INFO.

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.