<< >> NASA ASRS Report 723685, January 2007

A B757-200 pilot reports the FMC database is not complete enough to navigate some rtes and to provide emergency diversion airport information.

Attributes
ACN	723685
Time
Date	200701
Local Time Of Day	0001 To 0600
Place
Locale Reference	navaid : mgm.vortac
State Reference	AL
Altitude	msl single value : 25000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zhu.artcc tower : psp.tower
Operator	common carrier : air carrier
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	723685
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : less severe non adherence : clearance
Independent Detector	aircraft equipment other aircraft equipment : fmc other flight crewa
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Aircraft Company
Primary Problem	Aircraft

Narrative:

The first hint of this problem was in a message telling us to 'build fixes' if they weren't in the database. Then it happened to me. Center amends our route; to fly direct pfm; then deeds. Cannot comply -- pfm not in database. Center then asks us to fly direct pam; then deeds. Cannot comply -- pam not in database. Center is somewhat incredulous. On arrival; mia; we are told to fly direct copra. Cannot comply -- copra not in database -- this is a charted approach! No there is not time to 'heads down' in the terminal area and build copra. It is an ILS/DME fix; D10.9 imfa; you can't build it from the localizer antenna or fix it laterally. As for emergency/medical diverts along the gulf coast; tlh not in database; mob not in database; pns not in database; pfn not in database. We have alternate charts for tlh but no database. If this has been caused by cost saving efforts; it is a mistake. This degradation is impairing our ability to navigate and comply with ATC clearances.

Related reports:

• B737 flight crew reports loss of all number information on t...
• Air carrier pilot reported difficulty reaching medlink in re...
• While ferrying a DA20 the captain discovered that he did not...
• Enroute controller experiencing an emergency descent acknowl...
• Air carrier has cowling unlatch, emergency landing. Finds ai...
• Ce-560XL captain reported loss of both his and first officer...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A B757-200 PLT REPORTS THE FMC DATABASE IS NOT COMPLETE ENOUGH TO NAVIGATE SOME RTES AND TO PROVIDE EMER DIVERSION ARPT INFO.

Narrative: THE FIRST HINT OF THIS PROB WAS IN A MESSAGE TELLING US TO 'BUILD FIXES' IF THEY WEREN'T IN THE DATABASE. THEN IT HAPPENED TO ME. CENTER AMENDS OUR ROUTE; TO FLY DIRECT PFM; THEN DEEDS. CANNOT COMPLY -- PFM NOT IN DATABASE. CENTER THEN ASKS US TO FLY DIRECT PAM; THEN DEEDS. CANNOT COMPLY -- PAM NOT IN DATABASE. CENTER IS SOMEWHAT INCREDULOUS. ON ARRIVAL; MIA; WE ARE TOLD TO FLY DIRECT COPRA. CANNOT COMPLY -- COPRA NOT IN DATABASE -- THIS IS A CHARTED APPROACH! NO THERE IS NOT TIME TO 'HEADS DOWN' IN THE TERMINAL AREA AND BUILD COPRA. IT IS AN ILS/DME FIX; D10.9 IMFA; YOU CAN'T BUILD IT FROM THE LOC ANTENNA OR FIX IT LATERALLY. AS FOR EMER/MEDICAL DIVERTS ALONG THE GULF COAST; TLH NOT IN DATABASE; MOB NOT IN DATABASE; PNS NOT IN DATABASE; PFN NOT IN DATABASE. WE HAVE ALTERNATE CHARTS FOR TLH BUT NO DATABASE. IF THIS HAS BEEN CAUSED BY COST SAVING EFFORTS; IT IS A MISTAKE. THIS DEGRADATION IS IMPAIRING OUR ABILITY TO NAVIGATE AND COMPLY WITH ATC CLEARANCES.

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