<< >> NASA ASRS Report 676583, November 2005

B767-200 flight crew reports ATC display of J80 near saags intersection does not match FMC database location.

Attributes
ACN	676583
Time
Date	200511
Local Time Of Day	0601 To 1200
Place
Locale Reference	intersection : saags
State Reference	MO
Altitude	msl single value : 36000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zme.artcc
Operator	common carrier : air carrier
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Route In Use	enroute airway : j80.airway
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	676583
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	676573
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory flight crew : returned to intended or assigned course
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	FAA Flight Crew Human Performance Navigational Facility Aircraft Chart Or Publication Airspace Structure
Primary Problem	Airspace Structure

Narrative:

En route approximately 10 mi east of saggs; ATC asked if we were off course or tracking J80. The aircraft was flying the magenta line and on LNAV and VNAV. ATC said that over the past few days there have been several company B767/757 aircraft only tracking south of J80. I contacted dispatch and passed on this information. Center said they would contact company to see if there was a database problem. Over the radio there was a question asked by another aircraft; 'why was capitol VOR (cap) replaced with spinner VOR (spi) which redefines J80 between kansas city VOR (mci)?' this geographical change of the vors may be creating a navigation database error.

Related reports:

• When cleared to descend via a STAR; the flight crew of an A3...
• B737-300 first officer notes an intersection is not in the F...
• A300 flight crew departing jfk on the kennedy departure disc...
• An air carrier aircraft's FMC did not accept a flight plan a...
• B757-200 enters the holding pattern at arnes intersection wi...

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

Original NASA ASRS Text

Title: B767-200 FLT CREW RPTS ATC DISPLAY OF J80 NEAR SAAGS INTXN DOES NOT MATCH FMC DATABASE LOCATION.

Narrative: ENRTE APPROX 10 MI E OF SAGGS; ATC ASKED IF WE WERE OFF COURSE OR TRACKING J80. THE ACFT WAS FLYING THE MAGENTA LINE AND ON LNAV AND VNAV. ATC SAID THAT OVER THE PAST FEW DAYS THERE HAVE BEEN SEVERAL COMPANY B767/757 ACFT ONLY TRACKING S OF J80. I CONTACTED DISPATCH AND PASSED ON THIS INFO. CTR SAID THEY WOULD CONTACT COMPANY TO SEE IF THERE WAS A DATABASE PROB. OVER THE RADIO THERE WAS A QUESTION ASKED BY ANOTHER ACFT; 'WHY WAS CAPITOL VOR (CAP) REPLACED WITH SPINNER VOR (SPI) WHICH REDEFINES J80 BTWN KANSAS CITY VOR (MCI)?' THIS GEOGRAPHICAL CHANGE OF THE VORS MAY BE CREATING A NAV DATABASE ERROR.

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.