HDG TRACK DEV OCCURS WHEN THE PIC HAS THE FO ENTER THE WRONG DATA INTO THE FMC DURING A RADAR VECTOR PROC FROM COS; CO.

Date: 2002-02 · Aircraft: A320 · Phase: climb

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy|other-fms-use-clrnc-interp

Synopsis

HDG TRACK DEV OCCURS WHEN THE PIC HAS THE FO ENTER THE WRONG DATA INTO THE FMC DURING A RADAR VECTOR PROC FROM COS; CO.

Narrative

RECEIVED AMENDED CLRNC FOR RADAR VECTORS TO THE BRK 110 DEG RADIAL; 45 DME DIRECT HGO AS FILED. I PUT THIS FIX IN THE FMGC AS PBD01. AFTER TKOF; DEP CTL GAVE US A 080 DEG HDG TO INTERCEPT THE 110 DEG RADIAL OUT OF BRK. I HAD THE FO SEQUENCE THE FMGC SO PBD01 WAS THE 'FROM' WAYPOINT AND I SELECTED LNAV. THE FMGC SHOWED AN INTERCEPT JUST BEYOND PBD01. JUST AS WE NEARED THIS POINT; ATC ADVISED US WE HAD OVERSHOT THE 110 DEG RADIAL AND CLRED US DIRECT TO GLD. I HAD NEGLECTED TO HAVE THE FO ENTER BRK AS A FIX SO THE RADIAL COULD BE PROPERLY INTERCEPTED; AND I THINK I ASSUMED THE 110 DEG RADIAL WAS OUT OF PBD01. CRM FACTORS INCLUDED: APU FAILURE AT THE GATE AND A FLAP PROB BEFORE TKOF MADE ME RUSH TO GET AIRBORNE. ALSO; AT THIS TIME I HAD THE FLT ATTENDANTS REMAIN SEATED DUE TO THE ROUGH RIDE. ATC DID NOT SEEM TOO CONCERNED AND THERE WAS NO TFC CONFLICT THAT I COULD TELL. IN DISCUSSING THIS WITH MY FO; WE DID NOT PUT BRK AND THE RADIAL IN RAW DATA BECAUSE WE THOUGHT WE WERE CLOSE TO THE INT POINT. THIS WAS A MISTAKE. ALSO; I DISCOVERED THERE WAS SOME DISCREPANCY IN THE CLRNC WE BOTH COPIED. I HEARD RADAR VECTORS TO THE BRK 110 DEG RADIAL; 45 DME AND HE HEARD RADAR VECTORS TO INTERCEPT THE 110 DEG RADIAL TO THE 45D FIX.

More incidents for this aircraft family →

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