B737-800 FLT CREW HAS A TRACK/HDG DEV WHILE ENRTE BECAUSE AN ENRTE FIX WAS NOT IN THE FMS DATABASE.

Date: 2007-01 · Aircraft: B737-800 · Phase: cruise

Anomalies: aircraft-equipment-problem-less-severe|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance

Synopsis

B737-800 FLT CREW HAS A TRACK/HDG DEV WHILE ENRTE BECAUSE AN ENRTE FIX WAS NOT IN THE FMS DATABASE.

Narrative

THE ACFT WAS LATE ARRIVING IN SJC DUE TO SNOW IN SLC. AS A RESULT; WE WERE IN A RUSH TO GET THE ACFT OUT TO MAKE AN ON-TIME DEP. I CHKED THE FO'S FMS PROGRAMMING OF THE RTE (HE WAS THE PF) UP TO THE POINT OF CONFIRMING THE DEP PROC AND FIRST COUPLE OF POINTS. BUT I NEVER GOT AROUND TO CHKING THE FULL RTE. OUR CLRNC WAS LOUPE 1.LIN..JSICA..ILC.J58.MLF. APPARENTLY THE FO NEVER PROGRAMMED JSICA INTO THE RTE BECAUSE AFTER LIN THE ACFT PROCEEDED DIRECT TO ILC. ZOA CALLED US AND QUESTIONED OUR ROUTING AND IT WAS THEN THAT WE DISCOVERED OUR ERROR. JSICA WAS NOT IN THE DATABASE FOR OUR FMS AND WHEN HE TYPED IT IN; HE APPARENTLY GOT DISTR AND DID NOT NOTICE THAT THE COMPUTER DID NOT ACCEPT THE INPUT. AFTER QUESTIONING OUR INTENTIONS AS TO OUR PROPOSED RTE; OAK CLRED US DIRECT TO HBU AND DID NOT SHOW ANY CONCERN ABOUT OUR POS RELATIVE TO OTHER ACFT. SUPPLEMENTAL INFO FROM ACN 723874: AS I CHKED THE FMS WE WERE FLYING TO ILC. WHEN WE PUT IN JSICA IN THE FMS IT WAS NOT IN THE DATABASE. WHEN I LOADED THE FMS WITH THE RTE OF FLT; I DID NOT SEE THIS MESSAGE ON THE GND. WE ENDED UP BEING S OF COURSE BY APPROX 5 MI. WE HAD TO MANUALLY PUT IN THE COORDINATES FOR JSICA.

More incidents for this aircraft family →

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