Narrative:

Cleared the lga VOR/DME-G runway 22 turned on 4 mi outside FAF. Noticed a slight movement on HSI map, which we had entered the VOR approach in earlier. Flying the LNAV course on the HSI, no associated messages from EICAS or FMS, no flags on any instruments. When we finally saw runway 22 we were 2 mi north and approach control directed a missed approach to 3000 ft and vectored for another approach VOR DME-G to runway 22, which was uneventful. After landing, the HSI map had drifted 2.5 mi away from the actual runway. This was a very insidious event during the busy time of approach at the FAF. Some notification of our primary navigation being boldly displayed when it is out of tolerance, would be helpful in preventing this problem in the future. Supplemental information from acn 372125: in the base turn from normal descent, and sudden 2 1/2 mi map shift occurred in FMS, with no associated messages/flags. Computer/autoplt flew approximately 2 mi left of runway, and lga tower directed missed approach, handoff to TRACON. We re-flew same approach on raw data. After landing, map was shifted 2 1/2 mi west. This is insidious, particularly when it occurs during a busy period, as transitioning to final. Callback conversation with reporter acn #372128 revealed the following information: the reporter said that he was flying a B757-200 equipped with honeywell fmcs when the map shift occurred. He said that this was the first map shift that he has experienced in the several yrs that he has flown the aircraft. He did have the raw data tuned, but not displayed and he admitted that the first officer as the PNF should have had the ILS displayed on his HSI in accordance with company procedure. After landing the EFIS map was in error by 2 1/2 NM to the west. He entered the problem in the logbook and further discussed it with maintenance technicians. They could not pinpoint the cause of the error so maintenance personnel changed the fmcs and some related equipment. The reporter talked to his chief pilot about the problem also. He has not been told of the cause as yet. He has decided to carefully back up his approach displays with raw data in the future, he said. He said that this episode was deeply disturbing to him and his first officer.

Google
 

Original NASA ASRS Text

Title: THE FLC OF AN ACR B757 EXPERIENCED A MAP SHIFT DURING AN APCH TO LGA. THE ATCT LCL CTLR DIRECTED THE FLC TO GAR AND THEY SUCCESSFULLY COMPLETED A RAW DATA APCH LATER. THE EFIS MAP DISPLAY WAS 2 PT 5 NM OFF TO THE W AFTER THE FLT WAS IN THE GATE. THE RPTR ADMITTED THAT THEY WERE NOT MONITORING THE RAW DATA DURING THEIR INITIAL APCH.

Narrative: CLRED THE LGA VOR/DME-G RWY 22 TURNED ON 4 MI OUTSIDE FAF. NOTICED A SLIGHT MOVEMENT ON HSI MAP, WHICH WE HAD ENTERED THE VOR APCH IN EARLIER. FLYING THE LNAV COURSE ON THE HSI, NO ASSOCIATED MESSAGES FROM EICAS OR FMS, NO FLAGS ON ANY INSTS. WHEN WE FINALLY SAW RWY 22 WE WERE 2 MI N AND APCH CTL DIRECTED A MISSED APCH TO 3000 FT AND VECTORED FOR ANOTHER APCH VOR DME-G TO RWY 22, WHICH WAS UNEVENTFUL. AFTER LNDG, THE HSI MAP HAD DRIFTED 2.5 MI AWAY FROM THE ACTUAL RWY. THIS WAS A VERY INSIDIOUS EVENT DURING THE BUSY TIME OF APCH AT THE FAF. SOME NOTIFICATION OF OUR PRIMARY NAV BEING BOLDLY DISPLAYED WHEN IT IS OUT OF TOLERANCE, WOULD BE HELPFUL IN PREVENTING THIS PROB IN THE FUTURE. SUPPLEMENTAL INFO FROM ACN 372125: IN THE BASE TURN FROM NORMAL DSCNT, AND SUDDEN 2 1/2 MI MAP SHIFT OCCURRED IN FMS, WITH NO ASSOCIATED MESSAGES/FLAGS. COMPUTER/AUTOPLT FLEW APPROX 2 MI L OF RWY, AND LGA TWR DIRECTED MISSED APCH, HDOF TO TRACON. WE RE-FLEW SAME APCH ON RAW DATA. AFTER LNDG, MAP WAS SHIFTED 2 1/2 MI W. THIS IS INSIDIOUS, PARTICULARLY WHEN IT OCCURS DURING A BUSY PERIOD, AS TRANSITIONING TO FINAL. CALLBACK CONVERSATION WITH RPTR ACN #372128 REVEALED THE FOLLOWING INFO: THE RPTR SAID THAT HE WAS FLYING A B757-200 EQUIPPED WITH HONEYWELL FMCS WHEN THE MAP SHIFT OCCURRED. HE SAID THAT THIS WAS THE FIRST MAP SHIFT THAT HE HAS EXPERIENCED IN THE SEVERAL YRS THAT HE HAS FLOWN THE ACFT. HE DID HAVE THE RAW DATA TUNED, BUT NOT DISPLAYED AND HE ADMITTED THAT THE FO AS THE PNF SHOULD HAVE HAD THE ILS DISPLAYED ON HIS HSI IN ACCORDANCE WITH COMPANY PROC. AFTER LNDG THE EFIS MAP WAS IN ERROR BY 2 1/2 NM TO THE W. HE ENTERED THE PROB IN THE LOGBOOK AND FURTHER DISCUSSED IT WITH MAINT TECHNICIANS. THEY COULD NOT PINPOINT THE CAUSE OF THE ERROR SO MAINT PERSONNEL CHANGED THE FMCS AND SOME RELATED EQUIP. THE RPTR TALKED TO HIS CHIEF PLT ABOUT THE PROB ALSO. HE HAS NOT BEEN TOLD OF THE CAUSE AS YET. HE HAS DECIDED TO CAREFULLY BACK UP HIS APCH DISPLAYS WITH RAW DATA IN THE FUTURE, HE SAID. HE SAID THAT THIS EPISODE WAS DEEPLY DISTURBING TO HIM AND HIS FO.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.