B737-500 flight crew has riivr and hasbo on the riivr two arrival into lax fail to automatic load in...

Attributes
ACN	810163
Time
Date	200810
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	msl single value : 20000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zla.artcc
Operator	common carrier : air carrier
Make Model Name	B737-500
Operating Under FAR Part	Part 121
Flight Phase	descent : vacating altitude descent : approach
Route In Use	arrival star : riivr
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 195 flight time type : 6000
ASRS Report	810163
Events
Anomaly	aircraft equipment problem : less severe
Independent Detector	aircraft equipment other aircraft equipment : fmc other flight crewa
Resolutory Action	flight crew : overrode automation
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance Aircraft
Primary Problem	Ambiguous

Narrative:

The last 2 fixes of riivr two arrival (habso and riivr) did not come up automatically in FMC legs page. First officer typed them in manually and we got an 'insufficient fuel' alert. This alert was confusing us until we realized that the mileage shown to each of these fixes was more than 1800 NM away. We were actually less than 50 NM away from these fixes. First officer tried to reinsert fixes several times; but the same false mileage information kept coming up. Finally we entered the latitude/long for each fix instead of the 5 letter name as provided on the STAR. This corrected the displayed routing and mileage information in the FMC. After landing; we double-checked the FMC database effective dates which were correct. There may be other fixes in the ATC system and FMC database with the same names as these 2 fixes. If that is the case; the FMC displays them and not the correct fixes when on the riivr two arrival. Check with ATC and see if there are other fixes named 'riivr' and 'habso' that are about 1800-2400 NM from lax. Have them renamed and all databases updated. Incorrect FMC database.

Original NASA ASRS Text

Title: B737-500 FLT CREW HAS RIIVR AND HASBO ON THE RIIVR TWO ARRIVAL INTO LAX FAIL TO AUTO LOAD INTO THE FMC WHEN THE PROCEDURE WAS SELECTED. SUBSEQUENT MANUAL ENTRY OF THE LAT/LONG SOLVED THE PROBLEM.

Narrative: THE LAST 2 FIXES OF RIIVR TWO ARR (HABSO AND RIIVR) DID NOT COME UP AUTOMATICALLY IN FMC LEGS PAGE. FO TYPED THEM IN MANUALLY AND WE GOT AN 'INSUFFICIENT FUEL' ALERT. THIS ALERT WAS CONFUSING US UNTIL WE REALIZED THAT THE MILEAGE SHOWN TO EACH OF THESE FIXES WAS MORE THAN 1800 NM AWAY. WE WERE ACTUALLY LESS THAN 50 NM AWAY FROM THESE FIXES. FO TRIED TO REINSERT FIXES SEVERAL TIMES; BUT THE SAME FALSE MILEAGE INFO KEPT COMING UP. FINALLY WE ENTERED THE LAT/LONG FOR EACH FIX INSTEAD OF THE 5 LETTER NAME AS PROVIDED ON THE STAR. THIS CORRECTED THE DISPLAYED ROUTING AND MILEAGE INFO IN THE FMC. AFTER LNDG; WE DOUBLE-CHKED THE FMC DATABASE EFFECTIVE DATES WHICH WERE CORRECT. THERE MAY BE OTHER FIXES IN THE ATC SYS AND FMC DATABASE WITH THE SAME NAMES AS THESE 2 FIXES. IF THAT IS THE CASE; THE FMC DISPLAYS THEM AND NOT THE CORRECT FIXES WHEN ON THE RIIVR TWO ARR. CHK WITH ATC AND SEE IF THERE ARE OTHER FIXES NAMED 'RIIVR' AND 'HABSO' THAT ARE ABOUT 1800-2400 NM FROM LAX. HAVE THEM RENAMED AND ALL DATABASES UPDATED. INCORRECT FMC DATABASE.

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

B737-500 flight crew has riivr and hasbo on the riivr two arrival into lax fail to automatic load into the FMC when the procedure was selected. Subsequent manual entry of the latitude/long solved the problem.