Narrative:

We were on a 230 degree heading climbing to 17000 ft and ZNY cleared us direct colts neck VOR direct white intersection climb to 24000 ft. The identify for colts neck is col and was entered into the FMC and executed. The aircraft started a turn to 250 degrees and at the same time we had a frequency change to another ZNY frequency. When we checked in the controller told us to turn to a 170 degree heading and stop the climb at 19000 ft. We complied immediately and noticed the col identify was showing 1900 mi distance. We put in the latitude/longitude for colts neck and the FMC did show a left turn for about a 160 degree heading and 15 mi. There was no indication of a conflict with other traffic -- nor any TCASII advisories. There apparently are 2 col's in the computer and the wrong col was accepted by our FMC. Callback conversation with reporter revealed the following information: reporter said he was sure he had inserted 'col' in the flight crew and not 'cul.' he cannot explain the FMC error. He is unaware of any steps his air carrier has taken to track down and alleviate the problem.

Google
 

Original NASA ASRS Text

Title: OFF LGA, WHEN CLRED DIRECT COL, FMC DIRECTS A HDG OF 250 DEGS WHILE THE VOR IS 170 DEG FROM PRESENT POS. FMC ALSO SHOWED COL TO BE 1900 MI DISTANT.

Narrative: WE WERE ON A 230 DEG HDG CLBING TO 17000 FT AND ZNY CLRED US DIRECT COLTS NECK VOR DIRECT WHITE INTXN CLB TO 24000 FT. THE IDENT FOR COLTS NECK IS COL AND WAS ENTERED INTO THE FMC AND EXECUTED. THE ACFT STARTED A TURN TO 250 DEGS AND AT THE SAME TIME WE HAD A FREQ CHANGE TO ANOTHER ZNY FREQ. WHEN WE CHKED IN THE CTLR TOLD US TO TURN TO A 170 DEG HDG AND STOP THE CLB AT 19000 FT. WE COMPLIED IMMEDIATELY AND NOTICED THE COL IDENT WAS SHOWING 1900 MI DISTANCE. WE PUT IN THE LATITUDE/LONGITUDE FOR COLTS NECK AND THE FMC DID SHOW A L TURN FOR ABOUT A 160 DEG HDG AND 15 MI. THERE WAS NO INDICATION OF A CONFLICT WITH OTHER TFC -- NOR ANY TCASII ADVISORIES. THERE APPARENTLY ARE 2 COL'S IN THE COMPUTER AND THE WRONG COL WAS ACCEPTED BY OUR FMC. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR SAID HE WAS SURE HE HAD INSERTED 'COL' IN THE FLC AND NOT 'CUL.' HE CANNOT EXPLAIN THE FMC ERROR. HE IS UNAWARE OF ANY STEPS HIS ACR HAS TAKEN TO TRACK DOWN AND ALLEVIATE THE PROB.

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.