Mdt corp aircraft has wrong frequency and is out of contact with ATC.

Attributes
ACN	209252
Time
Date	199205
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : mad
State Reference	CT
Altitude	msl bound lower : 15000 msl bound upper : 16000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zbw tracon : abq
Operator	general aviation : corporate
Make Model Name	Medium Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	arrival other enroute airway : zbw
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi
Experience	flight time last 90 days : 110 flight time total : 8500 flight time type : 2000
ASRS Report	209252
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	conflict : airborne less severe non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	other other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were switched from ny center to bos center over dpk VOR (134.0). We checked in on bos frequency first officer (PNF) then started making a flight phone call and I maintained ATC communications. I received and acknowledged a clearance from 16000 to 15000 from center after leveling at 15000 the first officer concluded his flight phone call (approximately 2 min total time off frequency). I remarked that it was odd we were crossing mad at 15000 and 350 KIAS instead of the normal 11000 and 250 KIAS. Then ny center called us and told us to return to bos on 134.0. We expressed amazement to one another because we thought we were on that frequency. We switched to 134.0 bos told us we had checked in over dpk and subsequently had left the frequency. They said we had totally disrupted their airspace. Neither one of us could recall switching UHF frequencys. This occurrence happened at the end of a 12 hour day. We flew from madrid to gander to phl to bdl. We fly the phl-bdl route very frequently. We were very tired and of course complacent because we feel we know the route so well. I don't think we actually violated any far's, but of course I don't know exactly what happened to all of bos center's traffic we displaced, and we still don't know how we managed to change the UHF frequencys.

Original NASA ASRS Text

Title: MDT CORP ACFT HAS WRONG FREQ AND IS OUT OF CONTACT WITH ATC.

Narrative: WE WERE SWITCHED FROM NY CTR TO BOS CTR OVER DPK VOR (134.0). WE CHKED IN ON BOS FREQ FO (PNF) THEN STARTED MAKING A FLT PHONE CALL AND I MAINTAINED ATC COMS. I RECEIVED AND ACKNOWLEDGED A CLRNC FROM 16000 TO 15000 FROM CTR AFTER LEVELING AT 15000 THE FO CONCLUDED HIS FLT PHONE CALL (APPROX 2 MIN TOTAL TIME OFF FREQ). I REMARKED THAT IT WAS ODD WE WERE XING MAD AT 15000 AND 350 KIAS INSTEAD OF THE NORMAL 11000 AND 250 KIAS. THEN NY CTR CALLED US AND TOLD US TO RETURN TO BOS ON 134.0. WE EXPRESSED AMAZEMENT TO ONE ANOTHER BECAUSE WE THOUGHT WE WERE ON THAT FREQ. WE SWITCHED TO 134.0 BOS TOLD US WE HAD CHKED IN OVER DPK AND SUBSEQUENTLY HAD LEFT THE FREQ. THEY SAID WE HAD TOTALLY DISRUPTED THEIR AIRSPACE. NEITHER ONE OF US COULD RECALL SWITCHING UHF FREQS. THIS OCCURRENCE HAPPENED AT THE END OF A 12 HR DAY. WE FLEW FROM MADRID TO GANDER TO PHL TO BDL. WE FLY THE PHL-BDL RTE VERY FREQUENTLY. WE WERE VERY TIRED AND OF COURSE COMPLACENT BECAUSE WE FEEL WE KNOW THE RTE SO WELL. I DON'T THINK WE ACTUALLY VIOLATED ANY FAR'S, BUT OF COURSE I DON'T KNOW EXACTLY WHAT HAPPENED TO ALL OF BOS CTR'S TFC WE DISPLACED, AND WE STILL DON'T KNOW HOW WE MANAGED TO CHANGE THE UHF FREQS.

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.