Narrative:

When we departed hro, we experienced an unusual noise and vibration as the landing gear rested in the gear well. Due to the WX, return to hro was not an option. We continued to ixd. We experienced no further indication of a problem and did what troubleshooting we could en route. We were very interested in what would happen during gear extension. We were on top of a broken to scattered cloud layer when approach control cleared us for a visual approach to runway 36 at ixd, cautioned us to watch for jet traffic just off runway 18C ixd and handed us off to ixd tower. Tower acknowledged our call and requested a call on a 2 mi right base or final. We were about 5 NM out at this time. The PNF acknowledged the request. We had the departing traffic on TCASII and were trying to acquire a visual. I was staying above and east of the traffic. Being occupied with acquiring a visual (which I did), remaining clear of the clouds, maintaining adequate separation with the departing traffic, and monitoring the gear extension for a problem all while on a close in high approach. I failed to monitor the PNF for the required call 2 mi out. At the end of our rollout, the tower said they missed our call at 2 mi. The PNF asked me if they had requested the call. I said yes and realized he had not heard the request and neither of us could recall getting a clearance to land. Fortunately this did not create a traffic conflict. No one else was landing or departing. I can only recommend as the workload increases and problems arise, one must increase their diligence and never take for granted that the other crew member heard all of the message just because they acknowledged it.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC OF A CPR JET FAILED TO OBTAIN LNDG CLRNC DUE TO DISTRS OF ACFT EQUIP PROB, TFC WATCH AND A HIGH CLOSE IN VISUAL APCH THROUGH A BROKEN LAYER OF CLOUDS.

Narrative: WHEN WE DEPARTED HRO, WE EXPERIENCED AN UNUSUAL NOISE AND VIBRATION AS THE LNDG GEAR RESTED IN THE GEAR WELL. DUE TO THE WX, RETURN TO HRO WAS NOT AN OPTION. WE CONTINUED TO IXD. WE EXPERIENCED NO FURTHER INDICATION OF A PROB AND DID WHAT TROUBLESHOOTING WE COULD ENRTE. WE WERE VERY INTERESTED IN WHAT WOULD HAPPEN DURING GEAR EXTENSION. WE WERE ON TOP OF A BROKEN TO SCATTERED CLOUD LAYER WHEN APCH CTL CLRED US FOR A VISUAL APCH TO RWY 36 AT IXD, CAUTIONED US TO WATCH FOR JET TFC JUST OFF RWY 18C IXD AND HANDED US OFF TO IXD TWR. TWR ACKNOWLEDGED OUR CALL AND REQUESTED A CALL ON A 2 MI R BASE OR FINAL. WE WERE ABOUT 5 NM OUT AT THIS TIME. THE PNF ACKNOWLEDGED THE REQUEST. WE HAD THE DEPARTING TFC ON TCASII AND WERE TRYING TO ACQUIRE A VISUAL. I WAS STAYING ABOVE AND E OF THE TFC. BEING OCCUPIED WITH ACQUIRING A VISUAL (WHICH I DID), REMAINING CLR OF THE CLOUDS, MAINTAINING ADEQUATE SEPARATION WITH THE DEPARTING TFC, AND MONITORING THE GEAR EXTENSION FOR A PROB ALL WHILE ON A CLOSE IN HIGH APCH. I FAILED TO MONITOR THE PNF FOR THE REQUIRED CALL 2 MI OUT. AT THE END OF OUR ROLLOUT, THE TWR SAID THEY MISSED OUR CALL AT 2 MI. THE PNF ASKED ME IF THEY HAD REQUESTED THE CALL. I SAID YES AND REALIZED HE HAD NOT HEARD THE REQUEST AND NEITHER OF US COULD RECALL GETTING A CLRNC TO LAND. FORTUNATELY THIS DID NOT CREATE A TFC CONFLICT. NO ONE ELSE WAS LNDG OR DEPARTING. I CAN ONLY RECOMMEND AS THE WORKLOAD INCREASES AND PROBS ARISE, ONE MUST INCREASE THEIR DILIGENCE AND NEVER TAKE FOR GRANTED THAT THE OTHER CREW MEMBER HEARD ALL OF THE MESSAGE JUST BECAUSE THEY ACKNOWLEDGED IT.

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.