Narrative:

Cpr X tracking direct djb VOR after takeoff from toledo express airport (approximately) 105 degree heading had been leveled at FL230 on our way to FL410, night flight, lower cloud deck, VMC with excellent visibility, controled by ZOB. ZOB cleared us direct hoxie intersection, FL230, expect climb shortly. We acknowledged clearance. Hoxie intersection was not programmed in our long range navigation units (INS and FMS). We maintained present heading until we entered hoxie coordinates in the INS and pulled up the display (approximately 20-45 seconds). We had just initiated a left turn (track to hoxie 080 degrees, approximately) when center issued us an immediate turn to heading 050 degrees at the same time he issued air carrier Y an immediate turn to heading 240 dgs. We executed the tower and observed no traffic near by. We held heading 050 degrees for a very brief time and were then cleared direct hoxie and issued climb clearance. Approximately 10-15 mins after this occurred ZOB (different sector) gave us a phone # to contact on arrival at our destination. We immediately called them on the aircraft phone, but the connection was very poor and they gave us another phone # and told us to contact them the following morning. Callback conversation with reporter revealed the following: reporter stated he contacted the center the next day. Less than standard separation had occurred between the air carrier Y and the reporter's aircraft, 4.8 mi horizontal. The ARTCC supervisor asked why cpr X did not turn direct hoxie when it was issued. Reporter explained they started a turn as soon as they had it programmed and figured out a heading. No action taken against reporter by FAA.

Google
 

Original NASA ASRS Text

Title: CPR X HAD LESS THAN STANDARD SEPARATION FROM ACR Y. SYSTEM ERROR.

Narrative: CPR X TRACKING DIRECT DJB VOR AFTER TKOF FROM TOLEDO EXPRESS ARPT (APPROX) 105 DEG HDG HAD BEEN LEVELED AT FL230 ON OUR WAY TO FL410, NIGHT FLT, LOWER CLOUD DECK, VMC WITH EXCELLENT VISIBILITY, CTLED BY ZOB. ZOB CLRED US DIRECT HOXIE INTXN, FL230, EXPECT CLB SHORTLY. WE ACKNOWLEDGED CLRNC. HOXIE INTXN WAS NOT PROGRAMMED IN OUR LONG RANGE NAV UNITS (INS AND FMS). WE MAINTAINED PRESENT HDG UNTIL WE ENTERED HOXIE COORDINATES IN THE INS AND PULLED UP THE DISPLAY (APPROX 20-45 SECS). WE HAD JUST INITIATED A LEFT TURN (TRACK TO HOXIE 080 DEGS, APPROX) WHEN CENTER ISSUED US AN IMMEDIATE TURN TO HDG 050 DEGS AT THE SAME TIME HE ISSUED ACR Y AN IMMEDIATE TURN TO HDG 240 DGS. WE EXECUTED THE TWR AND OBSERVED NO TFC NEAR BY. WE HELD HDG 050 DEGS FOR A VERY BRIEF TIME AND WERE THEN CLRED DIRECT HOXIE AND ISSUED CLB CLRNC. APPROX 10-15 MINS AFTER THIS OCCURRED ZOB (DIFFERENT SECTOR) GAVE US A PHONE # TO CONTACT ON ARR AT OUR DEST. WE IMMEDIATELY CALLED THEM ON THE ACFT PHONE, BUT THE CONNECTION WAS VERY POOR AND THEY GAVE US ANOTHER PHONE # AND TOLD US TO CONTACT THEM THE FOLLOWING MORNING. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR STATED HE CONTACTED THE CENTER THE NEXT DAY. LESS THAN STANDARD SEPARATION HAD OCCURRED BTWN THE ACR Y AND THE RPTR'S ACFT, 4.8 MI HORIZ. THE ARTCC SUPVR ASKED WHY CPR X DID NOT TURN DIRECT HOXIE WHEN IT WAS ISSUED. RPTR EXPLAINED THEY STARTED A TURN AS SOON AS THEY HAD IT PROGRAMMED AND FIGURED OUT A HDG. NO ACTION TAKEN AGAINST RPTR BY FAA.

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.