Narrative:

In contact with dulles approach, we were inbound for landing. The first officer was confused with traffic landing on the parallel runway. Once the traffic conflict was resolved, the controller never told us to go to tower. Because the first officer was new, a bit more monitoring was required during landing. Upon landing rollout, I requested the reverse taxi high speed, but then we both noticed we were still on approach frequency. My first officer then switched to ground, but no instruction was given to call the tower once at the gate. Once at the gate, we both went up to the tower. The controller we talked to explained they were also training and assured us that tower probably cleared us to land without our acknowledgement. No conflict was noted.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ARRIVING J32 FLT CREW IS NOT ISSUED A FREQ CHANGE TO TWR AND LANDS WITHOUT CLRNC. NO CONFLICT OCCURRED.

Narrative: IN CONTACT WITH DULLES APCH, WE WERE INBOUND FOR LNDG. THE FO WAS CONFUSED WITH TFC LNDG ON THE PARALLEL RWY. ONCE THE TFC CONFLICT WAS RESOLVED, THE CTLR NEVER TOLD US TO GO TO TWR. BECAUSE THE FO WAS NEW, A BIT MORE MONITORING WAS REQUIRED DURING LNDG. UPON LNDG ROLLOUT, I REQUESTED THE REVERSE TAXI HIGH SPD, BUT THEN WE BOTH NOTICED WE WERE STILL ON APCH FREQ. MY FO THEN SWITCHED TO GND, BUT NO INSTRUCTION WAS GIVEN TO CALL THE TWR ONCE AT THE GATE. ONCE AT THE GATE, WE BOTH WENT UP TO THE TWR. THE CTLR WE TALKED TO EXPLAINED THEY WERE ALSO TRAINING AND ASSURED US THAT TWR PROBABLY CLRED US TO LAND WITHOUT OUR ACKNOWLEDGEMENT. NO CONFLICT WAS NOTED.

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.