Narrative:

We were cleared to 11000 ft and handed off to dayton approach. We were to the northeast of ind headed to dayton with unobstructed view of the dayton airport area. I tuned in 134.35 and reported in, I received a clearance to 6000 ft. Captain asked if we were to expect a visual to runway 24R, I said 'no she didn't say that, we're just cleared to 6000 ft.' (an altitude that made sense at this point in the flight.) this was the first 'link.' we should have re-acknowledged clearance since captain didn't hear the conversation clearly. We heard chatter on the radio. It sounded as if they were clearing aircraft for runway 7. The captain even said something about the oddity of this. (Why weren't the 'bells' ringing in my head!) as we approached our altitude I asked the captain if he had the field and did he want me to report it. (This sometimes expedites the approach on such clear nights.) this is when we realized we had a problem for there was no reply after 3 attempts to talk to approach. We could still hear chatter but now we realized it was fading. The captain said to call the dayton tower, 119.9. I did and asked them if approach was on 134.35. They said 134.45! A couple clicks of the communication receiver and dayton approach came in loud and clear and screaming. They said they had been trying to get us for 30 or 40 mi. An uneventful visual approach to runway 24R was to follow. Complacency on my part was a major contributing factor. Just because it's a calm clear night, flying into the same airport we've flown into hundreds if not thousands of times before at XX00 am doesn't mean we should relax and be nonchalant if another crew member doesn't hear a clearance from ATC with his own ears. I will not interpolate what I heard. Obviously, I heard someone else's clearance.

Related reports:

Google
 

Original NASA ASRS Text

Title: FREQ CHANGE WRONG STARTS A CHAIN OF EVENTS THROUGH REPLY TO WRONG CALL SIGN, ALTDEV ALT EXCURSION.

Narrative: WE WERE CLRED TO 11000 FT AND HANDED OFF TO DAYTON APCH. WE WERE TO THE NE OF IND HEADED TO DAYTON WITH UNOBSTRUCTED VIEW OF THE DAYTON ARPT AREA. I TUNED IN 134.35 AND RPTED IN, I RECEIVED A CLRNC TO 6000 FT. CAPT ASKED IF WE WERE TO EXPECT A VISUAL TO RWY 24R, I SAID 'NO SHE DIDN'T SAY THAT, WE'RE JUST CLRED TO 6000 FT.' (AN ALT THAT MADE SENSE AT THIS POINT IN THE FLT.) THIS WAS THE FIRST 'LINK.' WE SHOULD HAVE RE-ACKNOWLEDGED CLRNC SINCE CAPT DIDN'T HEAR THE CONVERSATION CLRLY. WE HEARD CHATTER ON THE RADIO. IT SOUNDED AS IF THEY WERE CLRING ACFT FOR RWY 7. THE CAPT EVEN SAID SOMETHING ABOUT THE ODDITY OF THIS. (WHY WEREN'T THE 'BELLS' RINGING IN MY HEAD!) AS WE APCHED OUR ALT I ASKED THE CAPT IF HE HAD THE FIELD AND DID HE WANT ME TO RPT IT. (THIS SOMETIMES EXPEDITES THE APCH ON SUCH CLR NIGHTS.) THIS IS WHEN WE REALIZED WE HAD A PROB FOR THERE WAS NO REPLY AFTER 3 ATTEMPTS TO TALK TO APCH. WE COULD STILL HEAR CHATTER BUT NOW WE REALIZED IT WAS FADING. THE CAPT SAID TO CALL THE DAYTON TWR, 119.9. I DID AND ASKED THEM IF APCH WAS ON 134.35. THEY SAID 134.45! A COUPLE CLICKS OF THE COM RECEIVER AND DAYTON APCH CAME IN LOUD AND CLR AND SCREAMING. THEY SAID THEY HAD BEEN TRYING TO GET US FOR 30 OR 40 MI. AN UNEVENTFUL VISUAL APCH TO RWY 24R WAS TO FOLLOW. COMPLACENCY ON MY PART WAS A MAJOR CONTRIBUTING FACTOR. JUST BECAUSE IT'S A CALM CLR NIGHT, FLYING INTO THE SAME ARPT WE'VE FLOWN INTO HUNDREDS IF NOT THOUSANDS OF TIMES BEFORE AT XX00 AM DOESN'T MEAN WE SHOULD RELAX AND BE NONCHALANT IF ANOTHER CREW MEMBER DOESN'T HEAR A CLRNC FROM ATC WITH HIS OWN EARS. I WILL NOT INTERPOLATE WHAT I HEARD. OBVIOUSLY, I HEARD SOMEONE ELSE'S CLRNC.

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.