When approaching destination; B767 flight crew discovered that numerous arrivals were not in the FMS...

Attributes
ACN	777671
Time
Date	200803
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : dfw.airport
State Reference	TX
Altitude	msl single value : 34000
Aircraft 1
Controlling Facilities	artcc : zfw.artcc
Operator	common carrier : air carrier
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Plan	IFR
Aircraft 2
Flight Phase	cruise : level
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	777671
Events
Anomaly	aircraft equipment problem : less severe
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Aircraft Maintenance Human Performance
Primary Problem	Aircraft

Narrative:

Just flew B767 with the new FMC database. The database was in the correct date range for the flight. There was a previous write-up that the FMC database was missing the riivr 1 and the civet 5 arrs into lax. The signoff was 'tech services notified for honeywell update FMC system operations check normal.' on our flight; when the arrival routing for dfw was selected; there were only 4 arrs listed in the database of all the arrs at dfw. None of the 'major' arrs were listed like the bowie; cedar creek; glen rose or bonham. The FMC only contained the dumpy 2; jaggo 2; jonez 4 and jumbo 2 arrs. When trying to enter specific waypoints to the route to match the STAR; some waypoints resulted in the FMC response of 'not in database.' for example for the cedar creek arrival tacke; deitz and hornz all generated the not in database message. Other STAR fixes that also generated a not in database message were curley and karla. Logbook entries were made upon arrival at dfw for this problem. The extent of the database errors is unknown. At high density airports it is essential that crews have the means to select and/or change arrs expeditiously if changed by ATC due to the flow of traffic. This database would make that very laborious if not impossible.

Original NASA ASRS Text

Title: WHEN APPROACHING DEST; B767 FLT CREW DISCOVERED THAT NUMEROUS ARRIVALS WERE NOT IN THE FMS DATABASE.

Narrative: JUST FLEW B767 WITH THE NEW FMC DATABASE. THE DATABASE WAS IN THE CORRECT DATE RANGE FOR THE FLT. THERE WAS A PREVIOUS WRITE-UP THAT THE FMC DATABASE WAS MISSING THE RIIVR 1 AND THE CIVET 5 ARRS INTO LAX. THE SIGNOFF WAS 'TECH SVCS NOTIFIED FOR HONEYWELL UPDATE FMC SYS OPS CHK NORMAL.' ON OUR FLT; WHEN THE ARR ROUTING FOR DFW WAS SELECTED; THERE WERE ONLY 4 ARRS LISTED IN THE DATABASE OF ALL THE ARRS AT DFW. NONE OF THE 'MAJOR' ARRS WERE LISTED LIKE THE BOWIE; CEDAR CREEK; GLEN ROSE OR BONHAM. THE FMC ONLY CONTAINED THE DUMPY 2; JAGGO 2; JONEZ 4 AND JUMBO 2 ARRS. WHEN TRYING TO ENTER SPECIFIC WAYPOINTS TO THE RTE TO MATCH THE STAR; SOME WAYPOINTS RESULTED IN THE FMC RESPONSE OF 'NOT IN DATABASE.' FOR EXAMPLE FOR THE CEDAR CREEK ARR TACKE; DEITZ AND HORNZ ALL GENERATED THE NOT IN DATABASE MESSAGE. OTHER STAR FIXES THAT ALSO GENERATED A NOT IN DATABASE MESSAGE WERE CURLEY AND KARLA. LOGBOOK ENTRIES WERE MADE UPON ARR AT DFW FOR THIS PROB. THE EXTENT OF THE DATABASE ERRORS IS UNKNOWN. AT HIGH DENSITY ARPTS IT IS ESSENTIAL THAT CREWS HAVE THE MEANS TO SELECT AND/OR CHANGE ARRS EXPEDITIOUSLY IF CHANGED BY ATC DUE TO THE FLOW OF TFC. THIS DATABASE WOULD MAKE THAT VERY LABORIOUS IF NOT IMPOSSIBLE.

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.

When approaching destination; B767 flight crew discovered that numerous arrivals were not in the FMS database.