FALCON 50 CORPORATE FLC DOES NOT NOTICE CHANGE IN ROUTING AND PROGRAMS THE ORIGINAL RTE IN THE FMS.

Date: 1996-05 · Aircraft: Falcon 50 · Phase: climb

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy

Synopsis

FALCON 50 CORPORATE FLC DOES NOT NOTICE CHANGE IN ROUTING AND PROGRAMS THE ORIGINAL RTE IN THE FMS.

Narrative

I FILED AN IFR FLT PLAN THROUGH COMMERCIAL SVC. THE COMPUTER PICKED THE HASSA 4 DEP WITH THE DAGGET TRANSITION. WHEN I PICKED UP THE CLRNC; THE CTLR GAVE ME THE POMONA 6 DEP WITH THE DAGGET TRANSITION. IT JUST NEVER REGISTERED THAT THIS WAS A CHANGE FROM WHAT THE COMPUTER SAID. I MADE A MISTAKE AND PUT THE HASSA 4 INTO THE FMS. AS WE TAXIED OUT; THE PF READ THE CLRNC AS THE POMONA 6 DEP. I STILL DID NOT CATCH THE MISTAKE I MADE. WE TOOK OFF AND PROCEEDED TO FOLLOW THE HASSA 4 DEP. DEP CTL CLRED US DIRECT TO POMONA VOR AND THE REST OF THE POMONA 6 DEP. I READ THIS BACK TO HIM; BUT I STILL DID NOT CATCH THE FACT THAT I HAD THE HASSA 4 PROGRAMMED INTO THE FMS. AS WE CROSSED THE POMONA VOR AND STARTED OUT ON THE RADIAL FOR THE HASSA 4 THE CTLR ASKED IF WE WERE ON THE POMONA 6 DEP. THAT IS WHEN I REALIZED WHAT I HAD DONE. I TOLD HIM THAT WE WERE ON THE HASSA 4 DEP. HE GAVE US A VECTOR AND LATER CLRED US DIRECT TO DAGGET WITHOUT ANY INCIDENT. THE CTLR SEEMED NICE AND HELPFUL. I WAS ONLY EMBARRASSED THAT IT TOOK SO LONG FOR ME TO CATCH MY MISTAKE. THE PROB I THINK CAME WHEN I PROGRAMMED THE FMS INSTEAD OF WAITING FOR THE PF TO PROGRAM IT HIMSELF SO THAT BOTH OF US COULD DOUBLE-CHK OUR ROUTING. FROM NOW ON OUR POLICY IS TO VERIFY THE ROUTING BY HAVING EACH PERSON SET UP HIS SIDE OF THE ACFT AND CHKING EACH OTHER IF THERE ARE ANY DISCREPANCIES.

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