HDG; TRACK DEV; AND MISIDENTIFICATION OF INTXN CLRED TO CREATES THE NEED FOR A HIGH RATE OF DSCNT BY A B737-300 FOR CROSSING BRDON INTXN 50 NW OF IIU VORTAC.

Date: 2004-12 · Aircraft: B737-300 · Phase: descent

Anomalies: deviation-altitude-undershoot|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|other-fix-id

Synopsis

HDG; TRACK DEV; AND MISIDENTIFICATION OF INTXN CLRED TO CREATES THE NEED FOR A HIGH RATE OF DSCNT BY A B737-300 FOR CROSSING BRDON INTXN 50 NW OF IIU VORTAC.

Narrative

WE WERE ON THE CHERI TWO; PAST TTH; WE ASKED FOR DIRECT TO CHERI; EXPECTED ILS 35L. CTR CTLR GAVE US DIRECT TO BRDON. WE WERE UNFAMILIAR WITH BRDON; COULD NOT FIND IT ON THE CHERI TWO ARR. I LOOKED AT THE ILS 35L APCH PLATE AND NOTICED BRBON; 21.8 DME ON THE ILS 35L. CTR TOLD US TO CROSS BRDON AT 11000 FT. I THOUGHT BRDON WAS KIND OF FAR S BUT WE WERE USING RWY 35L SO IT SORT OF FIT. THE FO CHKED IN WITH APCH AND SAID SOMETHING TO THE EFFECT; 'WERE GOING TO BRBON; CROSSING AT 11000 FT.' EVENTUALLY APCH CALLED AND SAID WE WERE ONLY 11 MILES FROM BRDON AND WE SHOWED AT LEAST 50 MILES TO OUR POINT. I STARTED DOWN AT A HIGH RATE TO MAKE THE RESTRICTION WHILE THE FO TYPED IN THE CORRECT POINT. EVERYTHING PAST BRDON WAS NORMAL. HAVING TWO INTERSECTIONS; ONE LETTER DIFFERENT; 70 MILES APART IS AN INVITATION FOR A MISTAKE. THE B AND D ARE ALSO TOO CLOSE TO NOTICE THE DIFFERENCE WHEN WRITING DOWN THE FIX. I EVENTUALLY FOUND BRDON; NOT ON A HIGH CHART; NOT ON THE ARR; OR APCH CHART; BUT ON A LOW CHART. FINDING BRBON ON THE APCH TO THE RWY WE WERE USING REALLY SET US UP.

More incidents for this aircraft family →

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