Narrative:

It was a nice calm january day; and I decided to take my RV4 out for a local flight around the lakes area. Returning to my home base from the west at pattern altitude; I announced on the CTAF that I was 3 miles west entering crosswind for runway 23. I then reported entering downwind for runway 23 (6;500 ft long runway). As I was downwind I noticed an airplane in the run-up area for runway 23; and another aircraft taxiing down to and nearing the run-up area for 23. I hadn't heard anyone else on the radio; and; the aircraft in the run-up area didn't appear to be getting ready to taxi out for take-off; so I decided to make a 'short approach' thinking I did not want to hold up the aircraft getting ready to go. I need less than 3;000 ft to land on the 6;500 ft runway. So; abeam the end of the runway I announced turning base for runway 23. Shortly after I turned final and less than 100 ft AGL; I noticed a pilatus pc-12 going by me on my right side; and making a go-around. I also decided to make a go around as I was a bit flustered and distracted. As I was making the go-around; and following the pilatus around the pattern; I was trying to figure out what just happened; and how did I miss the aircraft on final. My thoughts immediately turned to the radio since I had heard no other traffic. I noticed that I was on the right frequency; so I reached for the volume knob; and sure enough I had it turned all the way down. The primary problem was that I had the volume on my radio turned down and just assumed there was no other traffic; and that the guys taxing just weren't saying anything yet. I often times turn it down when I am away from the airport. I need to ensure that I turn it back up when headed back to the airport. A contributing factor was my focused attention on the two aircraft at or near the run-up area. I should have made a closer look for aircraft on final.

Google
 

Original NASA ASRS Text

Title: An RV4 pilot turned his radio volume down during flight and after returning to his home CTAF airport had an airborne conflict with a PC-12 because he did not hear traffic position/intention reporting.

Narrative: It was a nice calm January day; and I decided to take my RV4 out for a local flight around the lakes area. Returning to my home base from the west at pattern altitude; I announced on the CTAF that I was 3 miles west entering crosswind for Runway 23. I then reported entering downwind for Runway 23 (6;500 FT long runway). As I was downwind I noticed an airplane in the run-up area for Runway 23; and another aircraft taxiing down to and nearing the run-up area for 23. I hadn't heard anyone else on the radio; and; the aircraft in the run-up area didn't appear to be getting ready to taxi out for take-off; so I decided to make a 'short approach' thinking I did not want to hold up the aircraft getting ready to go. I need less than 3;000 FT to land on the 6;500 FT runway. So; abeam the end of the runway I announced turning base for Runway 23. Shortly after I turned final and less than 100 FT AGL; I noticed a Pilatus PC-12 going by me on my right side; and making a go-around. I also decided to make a go around as I was a bit flustered and distracted. As I was making the go-around; and following the Pilatus around the pattern; I was trying to figure out what just happened; and how did I miss the aircraft on final. My thoughts immediately turned to the radio since I had heard no other traffic. I noticed that I was on the right frequency; so I reached for the volume knob; and sure enough I had it turned all the way down. The primary problem was that I had the volume on my radio turned down and just assumed there was no other traffic; and that the guys taxing just weren't saying anything yet. I often times turn it down when I am away from the airport. I need to ensure that I turn it back up when headed back to the airport. A contributing factor was my focused attention on the two aircraft at or near the run-up area. I should have made a closer look for aircraft on final.

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