Narrative:

We were in level flight at 15000' MSL and navigating the rockdale 5 arrival to hartford, ct (bdl). We were using the flight management system navigation function with the autoplt engaged in the l-nav mode. I noticed that the mileage on the FMC screen indicated that we were 190 mi from bdl. We were attempting to find the error when the center controller told us to intercept the STAR. The FMC indicated that we were on the arrival route. I switched to VOR/DME navigation and found that we were west of course and 30 mi from the bdl VORTAC. As I was turning to the east to intercept the arrival route, the controller instructed us to fly a 090 degree heading and contact hartford approach. We were vectored to the final approach and landing west/O further incident. Everything appeared in order on the fmcs except for the mileage. The route was dropped from the system after we landed, so we could not find the error. A procedure that would prevent this from happening would be to have the non flying pilot monitor the arrival by use of the VOR/DME navigation. Callback conversation with reporter revealed the following information. Was not able to determine what caused the error in the computer. Company has issued a memo that this type of error can happen and has requested flight crews to set up raw data for backup on all approachs. The FMC is normally powered from AC with dc as a backup. The captain checked the electrical source and everything was normal. Because of the system capabilities of building your route plus all the stored routes, many pilots do not have their charts available. He has now noticed many pilots at least have the charts readily available.

Google
 

Original NASA ASRS Text

Title: FMC LNAV MODE WAS READING 190 DISTANCE WHEN ACTUAL DISTANCE 30 MILES.

Narrative: WE WERE IN LEVEL FLT AT 15000' MSL AND NAVING THE ROCKDALE 5 ARR TO HARTFORD, CT (BDL). WE WERE USING THE FLT MGMNT SYS NAV FUNCTION WITH THE AUTOPLT ENGAGED IN THE L-NAV MODE. I NOTICED THAT THE MILEAGE ON THE FMC SCREEN INDICATED THAT WE WERE 190 MI FROM BDL. WE WERE ATTEMPTING TO FIND THE ERROR WHEN THE CENTER CTLR TOLD US TO INTERCEPT THE STAR. THE FMC INDICATED THAT WE WERE ON THE ARR ROUTE. I SWITCHED TO VOR/DME NAV AND FOUND THAT WE WERE W OF COURSE AND 30 MI FROM THE BDL VORTAC. AS I WAS TURNING TO THE E TO INTERCEPT THE ARR ROUTE, THE CTLR INSTRUCTED US TO FLY A 090 DEG HDG AND CONTACT HARTFORD APCH. WE WERE VECTORED TO THE FINAL APCH AND LNDG W/O FURTHER INCIDENT. EVERYTHING APPEARED IN ORDER ON THE FMCS EXCEPT FOR THE MILEAGE. THE ROUTE WAS DROPPED FROM THE SYS AFTER WE LANDED, SO WE COULD NOT FIND THE ERROR. A PROC THAT WOULD PREVENT THIS FROM HAPPENING WOULD BE TO HAVE THE NON FLYING PLT MONITOR THE ARR BY USE OF THE VOR/DME NAV. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO. WAS NOT ABLE TO DETERMINE WHAT CAUSED THE ERROR IN THE COMPUTER. COMPANY HAS ISSUED A MEMO THAT THIS TYPE OF ERROR CAN HAPPEN AND HAS REQUESTED FLT CREWS TO SET UP RAW DATA FOR BACKUP ON ALL APCHS. THE FMC IS NORMALLY POWERED FROM AC WITH DC AS A BACKUP. THE CAPT CHKED THE ELECTRICAL SOURCE AND EVERYTHING WAS NORMAL. BECAUSE OF THE SYS CAPABILITIES OF BUILDING YOUR ROUTE PLUS ALL THE STORED ROUTES, MANY PLTS DO NOT HAVE THEIR CHARTS AVAILABLE. HE HAS NOW NOTICED MANY PLTS AT LEAST HAVE THE CHARTS READILY AVAILABLE.

Data retrieved from NASA's ASRS site as of August 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.