B737-300 first officer notes an intersection is not in the FMC database.

Attributes
ACN	519100
Time
Date	200105
Day	Thu
Place
Locale Reference	intersection : marit
State Reference	TX
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Flight Phase	descent : approach descent : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : instrument pilot : commercial
ASRS Report	519100
Events
Anomaly	aircraft equipment problem : less severe non adherence : published procedure non adherence : far non adherence : company policies
Resolutory Action	none taken : anomaly accepted
Consequence	other
Supplementary
Problem Areas	Aircraft Company
Primary Problem	Company

Narrative:

On may/wed/01 I filed a report because I failed to make marit at 250 KTS, 10000 ft due to my own failure to fully read the release or catch the fact that marit was not on the FMC approach. It is now jul/fri/03 and this situational set-up has not changed. What is the point of having an organization to fix identifiable problems if, after 50 days, and 2 FMC database updates it is not fixed! You are allowing for a situation to occur which, from my side of the fence, looks a little negligent. How about moving the remark from the last page of the release to the front page of the release, if you can't do anything else. How about fixing the database. Let's try to keep our air crews off of the FAA's target horizon. According to mr X/mr Y, this is not on the database -- but will be on the next update on aug/thu/03.

Original NASA ASRS Text

Title: B737-300 FO NOTES AN INTXN IS NOT IN THE FMC DATABASE.

Narrative: ON MAY/WED/01 I FILED A RPT BECAUSE I FAILED TO MAKE MARIT AT 250 KTS, 10000 FT DUE TO MY OWN FAILURE TO FULLY READ THE RELEASE OR CATCH THE FACT THAT MARIT WAS NOT ON THE FMC APCH. IT IS NOW JUL/FRI/03 AND THIS SITUATIONAL SET-UP HAS NOT CHANGED. WHAT IS THE POINT OF HAVING AN ORGANIZATION TO FIX IDENTIFIABLE PROBS IF, AFTER 50 DAYS, AND 2 FMC DATABASE UPDATES IT IS NOT FIXED! YOU ARE ALLOWING FOR A SIT TO OCCUR WHICH, FROM MY SIDE OF THE FENCE, LOOKS A LITTLE NEGLIGENT. HOW ABOUT MOVING THE REMARK FROM THE LAST PAGE OF THE RELEASE TO THE FRONT PAGE OF THE RELEASE, IF YOU CAN'T DO ANYTHING ELSE. HOW ABOUT FIXING THE DATABASE. LET'S TRY TO KEEP OUR AIR CREWS OFF OF THE FAA'S TARGET HORIZON. ACCORDING TO MR X/MR Y, THIS IS NOT ON THE DATABASE -- BUT WILL BE ON THE NEXT UPDATE ON AUG/THU/03.

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.