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

Date: 2003-05 · Aircraft: Citation II S2/Bravo (C550) · Phase: approach

Anomalies: deviation-altitude-crossing-restriction-not-met|deviation-discrepancy-procedural-clearance

Synopsis

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.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.