B767 crew had track deviation in czqx class a airspace.

Attributes
ACN	541558
Time
Date	200203
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : czqx.artcc
State Reference	NF
Altitude	msl single value : 35000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : czqx.artcc
Operator	common carrier : air carrier
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : multi engine pilot : instrument pilot : atp
Experience	flight time last 90 days : 200 flight time total : 15000
ASRS Report	541558
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : published procedure non adherence : clearance non adherence : company policies non adherence : far other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued alert
Supplementary
Problem Areas	Cabin Crew Human Performance Passenger Human Performance Flight Crew Human Performance Aircraft Company
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

At the time of this occurrence I was in the passenger cabin on break. This was as told to me upon arrival in the cockpit. After exiting the track (in radar control) with gander and just past porgy fix, controller cleared us to proceed direct to robbe. This controller handed us over to the next agency. Approximately 10-15 mins later the controller asked what fix we were cleared to. FMS computer showed mofat fix as the active waypoint with robbe as an abeam point (which we had already passed). We were unable to get an actual mileage abeam robbe since that point was behind us by the time our route was questioned. TCASII showed no aircraft in our vicinity. During this period of time we had a crew change in progress plus sending and receiving numerous ACARS messages to our dispatcher, concern a passenger that flight attendants were extremely nervous about (paranoid behavior). Supplemental information from acn 541559: TCASII showed no aircraft in our vicinity. During this period of time we had a crew change in progress plus were sending and receiving numerous ACARS messages to our dispatcher in regards to a passenger that the flight attendants were extremely concerned about (suspicious behavior).

Original NASA ASRS Text

Title: B767 CREW HAD TRACK DEV IN CZQX CLASS A AIRSPACE.

Narrative: AT THE TIME OF THIS OCCURRENCE I WAS IN THE PAX CABIN ON BREAK. THIS WAS AS TOLD TO ME UPON ARR IN THE COCKPIT. AFTER EXITING THE TRACK (IN RADAR CTL) WITH GANDER AND JUST PAST PORGY FIX, CTLR CLRED US TO PROCEED DIRECT TO ROBBE. THIS CTLR HANDED US OVER TO THE NEXT AGENCY. APPROX 10-15 MINS LATER THE CTLR ASKED WHAT FIX WE WERE CLRED TO. FMS COMPUTER SHOWED MOFAT FIX AS THE ACTIVE WAYPOINT WITH ROBBE AS AN ABEAM POINT (WHICH WE HAD ALREADY PASSED). WE WERE UNABLE TO GET AN ACTUAL MILEAGE ABEAM ROBBE SINCE THAT POINT WAS BEHIND US BY THE TIME OUR RTE WAS QUESTIONED. TCASII SHOWED NO ACFT IN OUR VICINITY. DURING THIS PERIOD OF TIME WE HAD A CREW CHANGE IN PROGRESS PLUS SENDING AND RECEIVING NUMEROUS ACARS MESSAGES TO OUR DISPATCHER, CONCERN A PAX THAT FLT ATTENDANTS WERE EXTREMELY NERVOUS ABOUT (PARANOID BEHAVIOR). SUPPLEMENTAL INFO FROM ACN 541559: TCASII SHOWED NO ACFT IN OUR VICINITY. DURING THIS PERIOD OF TIME WE HAD A CREW CHANGE IN PROGRESS PLUS WERE SENDING AND RECEIVING NUMEROUS ACARS MESSAGES TO OUR DISPATCHER IN REGARDS TO A PAX THAT THE FLT ATTENDANTS WERE EXTREMELY CONCERNED ABOUT (SUSPICIOUS BEHAVIOR).

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.