Narrative:

We were late arriving after departing late due to lightening [at the departure airport] that had closed the ramp and the same storms forced a routing increasing the flight time. Schedule was not an issue and we were not pushing the field to make up time. Once arrived in the area; it was VMC with 10SM visibility (actually closer to 20SM). We were cleared a visual approach approximately 16 miles from runway 33L at 6;000 feet MSL after being instructed to descend to 4;000. Pilot flying (PF) was just a bit slow to descend out of 6;000 feet and pilot monitoring (pm) prompted PF to start down.the aircraft continued to be high on profile and PF called for flaps 1 and selected lvl chg 203 knots. Pm had the VOR frequency to note the 10 DME/3;000 feet restriction and was instructed to contact tower approximately 8 NM out. While the gear was down; the PF failed to select a lower speed in the window; which caused the auto throttles to increase power; although the aircraft was already high on profile. The pm failed to notice the 203 in the speed window. Pm became task saturated; resulting in pm's failure to switch to tower while directing PF to disconnect the auto throttles; pull the nose up to get below 195 knots; in order to select flaps 15 and continue on profile.crew was able to track flaps on speed and accomplished the before landing checklist. The runway was clear and everything looked like a normal approach from 1;000 feet AGL. Once turning off of the runway; the crew noticed they were still on approach frequency as they switched to ground. Ground didn't mention anything except taxi instructions to the gate.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737NG flight crew reported becoming distracted; high on profile; and landing without clearance from the tower.

Narrative: We were late arriving after departing late due to lightening [at the departure airport] that had closed the ramp and the same storms forced a routing increasing the flight time. Schedule was not an issue and we were not pushing the field to make up time. Once arrived in the area; it was VMC with 10SM visibility (actually closer to 20SM). We were cleared a visual approach approximately 16 miles from runway 33L at 6;000 feet MSL after being instructed to descend to 4;000. Pilot Flying (PF) was just a bit slow to descend out of 6;000 feet and Pilot Monitoring (PM) prompted PF to start down.The aircraft continued to be high on profile and PF called for flaps 1 and selected LVL CHG 203 knots. PM had the VOR frequency to note the 10 DME/3;000 feet restriction and was instructed to contact Tower approximately 8 NM out. While the gear was down; the PF failed to select a lower speed in the window; which caused the auto throttles to increase power; although the aircraft was already high on profile. The PM failed to notice the 203 in the speed window. PM became task saturated; resulting in PM's failure to switch to Tower while directing PF to disconnect the auto throttles; pull the nose up to get below 195 knots; in order to select flaps 15 and continue on profile.Crew was able to track flaps on speed and accomplished the Before Landing Checklist. The runway was clear and everything looked like a normal approach from 1;000 feet AGL. Once turning off of the runway; the Crew noticed they were still on Approach frequency as they switched to Ground. Ground didn't mention anything except taxi instructions to the gate.

Data retrieved from NASA's ASRS site 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.