Narrative:

We were cleared into the visual approach for runway 4R in hnl and the controller switched us to the tower. As we approached the runway, we called the tower, and we got no response. 2 mi out, I called tower again, with still no response. Tower seemed very busy and he acknowledged other aircraft, but never replied to our situation. Around 1 mi out, I tried calling again, with still no response. As we approached 1 1/2 mi and 600 ft AGL with still no landing clearance, I executed a go around. We were then vectored around to land on runway 8L hnl. The factors that contributed to the situation were the busy period and time of yr. The tower was busier than usual and the increase of lndgs and taking off of aircraft kept him busy.

Google
 

Original NASA ASRS Text

Title: DH8 ACR PIC EXECUTES A GAR WHEN HE IS UNABLE TO ESTABLISH COM WITH TWR.

Narrative: WE WERE CLRED INTO THE VISUAL APCH FOR RWY 4R IN HNL AND THE CTLR SWITCHED US TO THE TWR. AS WE APCHED THE RWY, WE CALLED THE TWR, AND WE GOT NO RESPONSE. 2 MI OUT, I CALLED TWR AGAIN, WITH STILL NO RESPONSE. TWR SEEMED VERY BUSY AND HE ACKNOWLEDGED OTHER ACFT, BUT NEVER REPLIED TO OUR SIT. AROUND 1 MI OUT, I TRIED CALLING AGAIN, WITH STILL NO RESPONSE. AS WE APCHED 1 1/2 MI AND 600 FT AGL WITH STILL NO LNDG CLRNC, I EXECUTED A GAR. WE WERE THEN VECTORED AROUND TO LAND ON RWY 8L HNL. THE FACTORS THAT CONTRIBUTED TO THE SIT WERE THE BUSY PERIOD AND TIME OF YR. THE TWR WAS BUSIER THAN USUAL AND THE INCREASE OF LNDGS AND TAKING OFF OF ACFT KEPT HIM BUSY.

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.