A320 crew had no communication with a new approach controller after a frequency handoff error.

Attributes
ACN	517034
Time
Date	200107
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : dca.airport
State Reference	DC
Altitude	msl single value : 5000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : dca.tracon tracon : abe.tracon
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach descent : intermediate altitude
Route In Use	arrival : 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 : 50 flight time total : 19600 flight time type : 950
ASRS Report	517034
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : atp pilot : cfi
Experience	flight time last 90 days : 150 flight time total : 4700 flight time type : 1000
ASRS Report	516916
Events
Anomaly	non adherence : company policies non adherence : far non adherence : published procedure other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance none taken : detected after the fact other
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance

Narrative:

Cleared balance direct dca VOR, at 5000 ft MSL, anticipating mount vernon visual approach to runway 1. Several mi northeast of VOR when ATC said what we heard as 'air carrier abcd change to my frequency 120.2,' the first officer read back 120.2, changed frequency, and attempted to check in. My attention was focused on traffic, and the first officer and myself discussed the approach. There was still no response from ATC. When only a few mi from the dca VOR, I asked the first officer 'don't they usually turn you by now?' 'I wonder if they intend to take us across the airport?' the first officer recalled getting no response from ATC on 120.2 and returned to the previous frequency. The controller stated he had given us 120.42 and 'apologized for his accent.' we were then given a left turn heading 140 degrees and in the turn, a right turn heading 250 degrees. There was no traffic conflict but our proximity to P56 was too close for my comfort level.

Original NASA ASRS Text

Title: A320 CREW HAD NO COM WITH A NEW APCH CTLR AFTER A FREQ HDOF ERROR.

Narrative: CLRED BAL DIRECT DCA VOR, AT 5000 FT MSL, ANTICIPATING MOUNT VERNON VISUAL APCH TO RWY 1. SEVERAL MI NE OF VOR WHEN ATC SAID WHAT WE HEARD AS 'ACR ABCD CHANGE TO MY FREQ 120.2,' THE FO READ BACK 120.2, CHANGED FREQ, AND ATTEMPTED TO CHK IN. MY ATTN WAS FOCUSED ON TFC, AND THE FO AND MYSELF DISCUSSED THE APCH. THERE WAS STILL NO RESPONSE FROM ATC. WHEN ONLY A FEW MI FROM THE DCA VOR, I ASKED THE FO 'DON'T THEY USUALLY TURN YOU BY NOW?' 'I WONDER IF THEY INTEND TO TAKE US ACROSS THE ARPT?' THE FO RECALLED GETTING NO RESPONSE FROM ATC ON 120.2 AND RETURNED TO THE PREVIOUS FREQ. THE CTLR STATED HE HAD GIVEN US 120.42 AND 'APOLOGIZED FOR HIS ACCENT.' WE WERE THEN GIVEN A L TURN HDG 140 DEGS AND IN THE TURN, A R TURN HDG 250 DEGS. THERE WAS NO TFC CONFLICT BUT OUR PROX TO P56 WAS TOO CLOSE FOR MY COMFORT LEVEL.

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.