Narrative:

I was PF with the captain working the radios. VFR prevailed with moderate turbulence. The final approach controller at clt cleared us for a visual approach to runway 36R. The captain read back the clearance to ATC, set '.000' in the altitude alerter (as per company policy), and I repeated 'cleared for the visual,' pointing to the altitude alerter. After landing and clearing the runway, we both noticed the active communication was still set to the final approach controller, and the altitude alerter was still set on '.000' not the usual '49000' which indicates 'cleared to land.' I switched to tower frequency, advised clear of the runway, and was given further instructions as if the incident had not occurred. There was no discussion of the matter with ATC. The captain and I discussed the matter and concluded that indeed we had not been cleared to land. We also agreed that ATC never switched us to the tower controller. Fatigue on my part may have been a contributing factor. Although it was day #1 of my trip, I had not slept well the previous evening. A jump seat observer was also present, although the matter was never discussed with him. The FAA and company authority/authorized observer was apparently a student at an aeronautical university, conducting research of some sort. The student's purpose was never made entirely clear to me, although he was recording our 'on/in/out/off' times. I had heard through the 'rumor mill' that these students were doublechking the times we called in for each flight (we are not ACARS equipped), and this was causing resentment among the pilot group. This observer may have caused distraction, although he didn't say a word during the whole flight.

Google
 

Original NASA ASRS Text

Title: A BA32 LANDED CLT WITHOUT LNDG CLRNC FROM TWR.

Narrative: I WAS PF WITH THE CAPT WORKING THE RADIOS. VFR PREVAILED WITH MODERATE TURB. THE FINAL APCH CTLR AT CLT CLRED US FOR A VISUAL APCH TO RWY 36R. THE CAPT READ BACK THE CLRNC TO ATC, SET '.000' IN THE ALT ALERTER (AS PER COMPANY POLICY), AND I REPEATED 'CLRED FOR THE VISUAL,' POINTING TO THE ALT ALERTER. AFTER LNDG AND CLRING THE RWY, WE BOTH NOTICED THE ACTIVE COM WAS STILL SET TO THE FINAL APCH CTLR, AND THE ALT ALERTER WAS STILL SET ON '.000' NOT THE USUAL '49000' WHICH INDICATES 'CLRED TO LAND.' I SWITCHED TO TWR FREQ, ADVISED CLR OF THE RWY, AND WAS GIVEN FURTHER INSTRUCTIONS AS IF THE INCIDENT HAD NOT OCCURRED. THERE WAS NO DISCUSSION OF THE MATTER WITH ATC. THE CAPT AND I DISCUSSED THE MATTER AND CONCLUDED THAT INDEED WE HAD NOT BEEN CLRED TO LAND. WE ALSO AGREED THAT ATC NEVER SWITCHED US TO THE TWR CTLR. FATIGUE ON MY PART MAY HAVE BEEN A CONTRIBUTING FACTOR. ALTHOUGH IT WAS DAY #1 OF MY TRIP, I HAD NOT SLEPT WELL THE PREVIOUS EVENING. A JUMP SEAT OBSERVER WAS ALSO PRESENT, ALTHOUGH THE MATTER WAS NEVER DISCUSSED WITH HIM. THE FAA AND COMPANY AUTH OBSERVER WAS APPARENTLY A STUDENT AT AN AERONAUTICAL UNIVERSITY, CONDUCTING RESEARCH OF SOME SORT. THE STUDENT'S PURPOSE WAS NEVER MADE ENTIRELY CLR TO ME, ALTHOUGH HE WAS RECORDING OUR 'ON/IN/OUT/OFF' TIMES. I HAD HEARD THROUGH THE 'RUMOR MILL' THAT THESE STUDENTS WERE DOUBLECHKING THE TIMES WE CALLED IN FOR EACH FLT (WE ARE NOT ACARS EQUIPPED), AND THIS WAS CAUSING RESENTMENT AMONG THE PLT GROUP. THIS OBSERVER MAY HAVE CAUSED DISTR, ALTHOUGH HE DIDN'T SAY A WORD DURING THE WHOLE FLT.

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.