A319 experiences track deviation when FMS fails to download diano intersection.

Attributes
ACN	726768
Time
Date	200702
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : zny.artcc
State Reference	NY
Altitude	msl single value : 17000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zny.artcc
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	726768
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : critical non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance Company Aircraft
Primary Problem	Ambiguous

Narrative:

We loaded the computer for our route to syr. We did not notice that the ptw 320 radial intersection with V499 was not the fix diano. So en route we missed the turn to that intersection. Center called us on it and gave us a heading. It appeared there was no other traffic. It was clear at that altitude. That fix is not downloaded when the rest of the flight plan is so that fix it is a gotcha! New york center called us and asked if we were on the ptw 320 radial. I said we were right of course and he gave us a heading of 310. He did not sound pleased and asked us to verify our route. I did and found the error in the computer. He left us on the heading for a while and then sent us direct to diano. It would be nice if the system downloaded this intersection into the computer when it loads the rest of the flight plan. This type of intersection is difficult to deal with. We should have looked over the route more closely to verify the missing intersection.

Original NASA ASRS Text

Title: A319 EXPERIENCES TRACK DEV WHEN FMS FAILS TO DOWNLOAD DIANO INTXN.

Narrative: WE LOADED THE COMPUTER FOR OUR ROUTE TO SYR. WE DID NOT NOTICE THAT THE PTW 320 RADIAL INTERSECTION WITH V499 WAS NOT THE FIX DIANO. SO ENRTE WE MISSED THE TURN TO THAT INTERSECTION. CENTER CALLED US ON IT AND GAVE US A HEADING. IT APPEARED THERE WAS NO OTHER TRAFFIC. IT WAS CLEAR AT THAT ALTITUDE. THAT FIX IS NOT DOWNLOADED WHEN THE REST OF THE FLIGHT PLAN IS SO THAT FIX IT IS A GOTCHA! NEW YORK CENTER CALLED US AND ASKED IF WE WERE ON THE PTW 320 RADIAL. I SAID WE WERE RIGHT OF COURSE AND HE GAVE US A HEADING OF 310. HE DID NOT SOUND PLEASED AND ASKED US TO VERIFY OUR ROUTE. I DID AND FOUND THE ERROR IN THE COMPUTER. HE LEFT US ON THE HEADING FOR A WHILE AND THEN SENT US DIRECT TO DIANO. IT WOULD BE NICE IF THE SYSTEM DOWNLOADED THIS INTERSECTION INTO THE COMPUTER WHEN IT LOADS THE REST OF THE FLIGHT PLAN. THIS TYPE OF INTERSECTION IS DIFFICULT TO DEAL WITH. WE SHOULD HAVE LOOKED OVER THE ROUTE MORE CLOSELY TO VERIFY THE MISSING INTERSECTION.

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.