Narrative:

We stopped at aoh for fuel on our way home to our home. A student pilot who I am teaching; was in the left seat and the pilot flying this leg. Weather en route was a factor. I was head down during most of the taxi waiting for foreflight to update the radar display. He performed the run up short of the runway with the nose of the airplane pointed at the final approach path. A minute or two later he completed the checklist; told me he was ready; then announced the final looked clear. I looked up briefly and saw nothing as well. He then announced on CTAF that we were taking off on runway 28. He proceeded to take the runway and as we got about 5 feet onto it my [student] saw the aircraft Y on short final. He called it out and stopped the airplane. Aircraft Y thankfully saw us and went around. I feel very comfortable with my student's ability to maneuver on the ground and perform the appropriate checklists. I do not believe this was a factor. Looking back; I believe the seeds of this incident were planted about half an hour before we landed. We were monitoring 121.5 on our number 1 radio and CTAF on our number 2. The ASOS is broadcast over the VOR frequency. Our number 1 radio retains the last used frequency while our number two automatically tunes to 121.5 when restarted. About half an hour before landing we heard a lot of inappropriate banter over 121.5. I turned down the volume on the number 1 radio because what was going on rendered the frequency useless and had become distracting. After starting the airplane and turning on the avionics master switch we placed CTAF in the number one radio. The airport was not busy so the lack of transmissions over the frequency didn't bother me. Once I saw the aircraft Y; I checked the volume of the number 1 radio by pulling out the on/off volume switch to check the squelch. I didn't hear anything until I increased the volume. That's when I heard the aircraft Y announce that he was going around. Soon after he asked if the [our aircraft] taking the runway was on frequency. I replied that we were and apologized for what happened. He then asked if we had heard him because he had been transmitting his position for the last 6 miles. I told him we had not and once again apologized. As to why neither my student nor I didn't see the aircraft Y further out on final is still not clear. The color of the plane helped it blend into the ground and I'm not sure if his landing light was on. I teach and practice see and avoid procedures. We conducted the run up facing the final approach path and had a good view of it. My hope is the aircraft Y pilot heard our radio transmission that we were taking off and was primed for a go around. I will make sure that from this point on I will take even more time to insure there is no traffic about to land before taking the runway. I have also learned that I need to check that the volume is turned up on whichever radio I'm using.

Related reports:

Google
 

Original NASA ASRS Text

Title: PA-28 Instructor Pilot reported a T6 executed a go-around when they took the runway and created a conflict.

Narrative: We stopped at AOH for fuel on our way home to our home. A student pilot who I am teaching; was in the left seat and the pilot flying this leg. Weather en route was a factor. I was head down during most of the taxi waiting for Foreflight to update the radar display. He performed the run up short of the runway with the nose of the airplane pointed at the final approach path. A minute or two later he completed the checklist; told me he was ready; then announced the final looked clear. I looked up briefly and saw nothing as well. He then announced on CTAF that we were taking off on runway 28. He proceeded to take the runway and as we got about 5 feet onto it my [student] saw the Aircraft Y on short final. He called it out and stopped the airplane. Aircraft Y thankfully saw us and went around. I feel very comfortable with my student's ability to maneuver on the ground and perform the appropriate checklists. I do not believe this was a factor. Looking back; I believe the seeds of this incident were planted about half an hour before we landed. We were monitoring 121.5 on our number 1 radio and CTAF on our number 2. The ASOS is broadcast over the VOR frequency. Our number 1 radio retains the last used frequency while our number two automatically tunes to 121.5 when restarted. About half an hour before landing we heard a lot of inappropriate banter over 121.5. I turned down the volume on the number 1 radio because what was going on rendered the frequency useless and had become distracting. After starting the airplane and turning on the avionics master switch we placed CTAF in the number one radio. The airport was not busy so the lack of transmissions over the frequency didn't bother me. Once I saw the Aircraft Y; I checked the volume of the number 1 radio by pulling out the on/off volume switch to check the squelch. I didn't hear anything until I increased the volume. That's when I heard the Aircraft Y announce that he was going around. Soon after he asked if the [our aircraft] taking the runway was on frequency. I replied that we were and apologized for what happened. He then asked if we had heard him because he had been transmitting his position for the last 6 miles. I told him we had not and once again apologized. As to why neither my student nor I didn't see the Aircraft Y further out on final is still not clear. The color of the plane helped it blend into the ground and I'm not sure if his landing light was on. I teach and practice see and avoid procedures. We conducted the run up facing the final approach path and had a good view of it. My hope is the Aircraft Y pilot heard our radio transmission that we were taking off and was primed for a go around. I will make sure that from this point on I will take even more time to insure there is no traffic about to land before taking the runway. I have also learned that I need to check that the volume is turned up on whichever radio I'm using.

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.