Gso approach controller failed to change air carrier X to rdu approach controller frequency. Operati...

Attributes
ACN	139058
Time
Date	199003
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : rdu
State Reference	NC
Altitude	msl bound lower : 9000 msl bound upper : 9000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : gso tracon : rdu
Operator	common carrier : air carrier
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Flight Phase	cruise other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 3600 flight time type : 1000
ASRS Report	139058
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 120 flight time total : 3200 flight time type : 180
ASRS Report	138945
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure Operational Deviation

Narrative:

Air carrier X was instructed by gso to depart the VOR heading 085 degrees at 9000' for the arrival gate into rdu. After proceeding for about 30 mi, I queried gso approach about a handoff to rdu. They told us to contact rdu approach (we had not been contacted by gso approach before I queried them). Rdu responded with the fact that they had been trying to reach us for quite a while. Supplemental information from acn 138945: we called gso, who immediately sent us to the rdu frequency. Upon contact with rdu approach, the controller acted as if he had been trying to reach us. We had contacted rdu immediately after being handed off by gso. Both pilots are absolutely certain that gso had not given us to rdu prior to our initiative mentioned above. The gso frequency was not congested and we were not distracted by any flying duties, etc, and we are sure we would have heard the call. Sometimes it is difficult to guess where our arriving aircraft is going to fit into the arrival flow, so it makes it hard to know when to expect the handoff. Obviously we did not get handed off in as timely a manner as rdu approach would have liked.

Original NASA ASRS Text

Title: GSO APCH CTLR FAILED TO CHANGE ACR X TO RDU APCH CTLR FREQ. OPERATIONAL DEVIATION.

Narrative: ACR X WAS INSTRUCTED BY GSO TO DEPART THE VOR HDG 085 DEGS AT 9000' FOR THE ARR GATE INTO RDU. AFTER PROCEEDING FOR ABOUT 30 MI, I QUERIED GSO APCH ABOUT A HDOF TO RDU. THEY TOLD US TO CONTACT RDU APCH (WE HAD NOT BEEN CONTACTED BY GSO APCH BEFORE I QUERIED THEM). RDU RESPONDED WITH THE FACT THAT THEY HAD BEEN TRYING TO REACH US FOR QUITE A WHILE. SUPPLEMENTAL INFO FROM ACN 138945: WE CALLED GSO, WHO IMMEDIATELY SENT US TO THE RDU FREQ. UPON CONTACT WITH RDU APCH, THE CTLR ACTED AS IF HE HAD BEEN TRYING TO REACH US. WE HAD CONTACTED RDU IMMEDIATELY AFTER BEING HANDED OFF BY GSO. BOTH PLTS ARE ABSOLUTELY CERTAIN THAT GSO HAD NOT GIVEN US TO RDU PRIOR TO OUR INITIATIVE MENTIONED ABOVE. THE GSO FREQ WAS NOT CONGESTED AND WE WERE NOT DISTRACTED BY ANY FLYING DUTIES, ETC, AND WE ARE SURE WE WOULD HAVE HEARD THE CALL. SOMETIMES IT IS DIFFICULT TO GUESS WHERE OUR ARRIVING ACFT IS GOING TO FIT INTO THE ARR FLOW, SO IT MAKES IT HARD TO KNOW WHEN TO EXPECT THE HDOF. OBVIOUSLY WE DID NOT GET HANDED OFF IN AS TIMELY A MANNER AS RDU APCH WOULD HAVE LIKED.

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.

Gso approach controller failed to change air carrier X to rdu approach controller frequency. Operational deviation.