ACR FLC EXPERIENCES A TRACK DEV DUE; IN PART; TO CHART ISSUES AND SHORT RESPONSE-TIME CLRNC.
Synopsis
ACR FLC EXPERIENCES A TRACK DEV DUE; IN PART; TO CHART ISSUES AND SHORT RESPONSE-TIME CLRNC.
Narrative
OUR FLT WAS CLRED FROM MDT TO ORD VIA MDT..HAR..V33..J64..FWA..OX13 ARR ORD. AFTER DEPARTING AND FLYING RWY HEADING FROM RWY 31; WE RECEIVED A CLRNC TO 'FLY 360 DEG HDG.' THIS PUT US JUST W OF HAR; THE NEXT CLRNC WAS TO GO DIRECT TO HAR AND CONTINUE VIA THE FLT PLANNED RTE. SINCE THIS ACFT IS EQUIPPED WITH FMC AND WAS THE PRIMARY NAV; ONCE WE PAST HAR GOING W THE FMC DROPPED HAR AND THE SUBSEQUENT RADIAL (V33) ALONG WITH THE COMPANY COORDINATES (FMC IDENTED HAR13) FOR THE INTXN OF V33 AND J64. I QUICKLY SET UP MY COPLT; WHO WAS FLYING; WITH RAW DATA FOR HAR 321 DEG RADIAL. WHILE TRYING TO GO BACK AND FORTH WITH HIGH AND LOW ALT CHARTS TO ASCERTAIN WHERE J64 INTERSECTED V33 AND GET HIM SET UP FOR THE L TURN ONTO J64; WE RECEIVED 3 DIFFERENT ALT CHANGES AS WELL AS TFC WATCH. I REQUESTED A DIRECT TO EWC BUT WAS TOLD 'JUST STAY ON YOUR FLT PLANNED RTE.' LOW ALT CHARTS DO NOT SHOW RADIALS FROM HIGH ALT CHARTED VOR'S. WHILE I WAS TRYING TO FIGURE ALL THIS OUT; WE APCHED THE MID-POINT ON V33; MY COPLT ASKED AND RECEIVED NAVAID DATA FOR PSB TO STAY ON V33. ABOUT THIS TIME WE CHANGED OVER TO ANOTHER NEW YORK ARTCC AND ASKED AND GOT DIRECT EWC. WE ESTIMATE THAT WE WERE ABOUT 6 MI N OF COURSE FOR J64. WE CONTINUED TO ORD; THE REMAINDER OF THE FLT WAS UNEVENTFUL. CORRECTIVE ACTIONS/RECOMMENDATIONS: IN THE FUTURE I WILL TAKE MORE TIME TO PREFLT THE RTE PLANNING AND INSERT THE RAW DATA FIXES AND RADIALS ONTO MY FLT PLAN WHERE THERE ARE V ROUTES AND J ROUTES WITH NO INTXNS. IT WAS IMPOSSIBLE TO REPROGRAM THE FMC WITH THE RTE BECAUSE THERE IS NO CHARTED INTXN OF V33 AND J64. THE ONLY REASON IT WAS IN THE RTE INITIALLY WAS BECAUSE IT WAS PLOTTED OUT BY OUR COMPANY DISPATCHERS AND CODED WITH THE FAA'S APPROVAL INTO THE FMC. I WILL ALSO BE RECOMMENDING TO THE COMPANY THAT WE DEPICT THESE INTXNS ON OUR FLT PLAN PROPERLY IN CASE WE ARE NOT FLYING VIA FMC NAV DATA.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.