Narrative:

I was flying my aircraft C175A from riw to U25. Initial takeoff was aborted due to a stuck fuel sender float (tank had been drained to comply to recent cessna service bulletin). When float had been freed second takeoff was commenced. While taxiing to runway 28 I had radio tuned to AWOS on one frequency and 122.8 on the other, listening to the AWOS, as the winds had been gusting to 21 KTS, which is unusual for this airport. During the pre-taxi, I listened to ZLC on 133.25, as is my normal practice. I heard what I assumed was a commuter aircraft although I did not hear where he was. When I reached the taxiway hold line prior to taking runway 28, I stopped and angled the aircraft so as to see the approach path to runway 28. I then saw a commuter approximately 1/4 mi out, with his landing lights on and the gear and flaps down. I then realized that I was switched to the AWOS frequency rather than 122.8. I also realized that I was past the hold line, but not on the runway surface. I switched to the 122.8 frequency and elected to remain stationary. The aircraft proceeded to land, passing over the runway end about 75 ft high. I then heard 'do you have a radio in that thing?' obviously from the commuter. I answered in the affirmative. This was not a runway incursion, but it could have been due to my failure to have the proper frequency active. The commuter obviously had me in full view and had tried to advise me of his being on final. In my opinion, the commuter should not have continued his landing, but should have initiated a go around since he had no direct knowledge that I saw him, and the fact that I was beyond the hold line was an indication that I was rolling for takeoff. Had I not looked, as is my standard procedure, I could well have taxied onto the active runway directly into the path of the commuter aircraft. Even though he was well above me, the fact is that a hazardous situation could have developed. I shall use more vigilance in monitoring the unicom or CTAF while on txwys so as to be constantly aware of aircraft approaching for a landing. I shall also make it a standard practice to not continue with a landing when there is another aircraft in a non standard position ready to take the active runway, unless I am in direct and constant communication with that aircraft. Fortunately, this was really a 'non incident' but the potential was there for a serious accident. I am well aware of the activity there. The field has no tower, and aircraft are switching between ZLC and 122.8 as they approach riw. I always respond when on 122.8. This is not a busy airport. It is easy to become complacent about other traffic and one must never begin to assume that the other fellow knows what you are doing!

Related reports:

Google
 

Original NASA ASRS Text

Title: A C175 PLT TAXIED PAST THE HOLD SHORT LINE DURING TAXI FOR TKOF.

Narrative: I WAS FLYING MY ACFT C175A FROM RIW TO U25. INITIAL TKOF WAS ABORTED DUE TO A STUCK FUEL SENDER FLOAT (TANK HAD BEEN DRAINED TO COMPLY TO RECENT CESSNA SVC BULLETIN). WHEN FLOAT HAD BEEN FREED SECOND TKOF WAS COMMENCED. WHILE TAXIING TO RWY 28 I HAD RADIO TUNED TO AWOS ON ONE FREQ AND 122.8 ON THE OTHER, LISTENING TO THE AWOS, AS THE WINDS HAD BEEN GUSTING TO 21 KTS, WHICH IS UNUSUAL FOR THIS ARPT. DURING THE PRE-TAXI, I LISTENED TO ZLC ON 133.25, AS IS MY NORMAL PRACTICE. I HEARD WHAT I ASSUMED WAS A COMMUTER ACFT ALTHOUGH I DID NOT HEAR WHERE HE WAS. WHEN I REACHED THE TXWY HOLD LINE PRIOR TO TAKING RWY 28, I STOPPED AND ANGLED THE ACFT SO AS TO SEE THE APCH PATH TO RWY 28. I THEN SAW A COMMUTER APPROX 1/4 MI OUT, WITH HIS LNDG LIGHTS ON AND THE GEAR AND FLAPS DOWN. I THEN REALIZED THAT I WAS SWITCHED TO THE AWOS FREQ RATHER THAN 122.8. I ALSO REALIZED THAT I WAS PAST THE HOLD LINE, BUT NOT ON THE RWY SURFACE. I SWITCHED TO THE 122.8 FREQ AND ELECTED TO REMAIN STATIONARY. THE ACFT PROCEEDED TO LAND, PASSING OVER THE RWY END ABOUT 75 FT HIGH. I THEN HEARD 'DO YOU HAVE A RADIO IN THAT THING?' OBVIOUSLY FROM THE COMMUTER. I ANSWERED IN THE AFFIRMATIVE. THIS WAS NOT A RWY INCURSION, BUT IT COULD HAVE BEEN DUE TO MY FAILURE TO HAVE THE PROPER FREQ ACTIVE. THE COMMUTER OBVIOUSLY HAD ME IN FULL VIEW AND HAD TRIED TO ADVISE ME OF HIS BEING ON FINAL. IN MY OPINION, THE COMMUTER SHOULD NOT HAVE CONTINUED HIS LNDG, BUT SHOULD HAVE INITIATED A GAR SINCE HE HAD NO DIRECT KNOWLEDGE THAT I SAW HIM, AND THE FACT THAT I WAS BEYOND THE HOLD LINE WAS AN INDICATION THAT I WAS ROLLING FOR TKOF. HAD I NOT LOOKED, AS IS MY STANDARD PROC, I COULD WELL HAVE TAXIED ONTO THE ACTIVE RWY DIRECTLY INTO THE PATH OF THE COMMUTER ACFT. EVEN THOUGH HE WAS WELL ABOVE ME, THE FACT IS THAT A HAZARDOUS SIT COULD HAVE DEVELOPED. I SHALL USE MORE VIGILANCE IN MONITORING THE UNICOM OR CTAF WHILE ON TXWYS SO AS TO BE CONSTANTLY AWARE OF ACFT APCHING FOR A LNDG. I SHALL ALSO MAKE IT A STANDARD PRACTICE TO NOT CONTINUE WITH A LNDG WHEN THERE IS ANOTHER ACFT IN A NON STANDARD POS READY TO TAKE THE ACTIVE RWY, UNLESS I AM IN DIRECT AND CONSTANT COM WITH THAT ACFT. FORTUNATELY, THIS WAS REALLY A 'NON INCIDENT' BUT THE POTENTIAL WAS THERE FOR A SERIOUS ACCIDENT. I AM WELL AWARE OF THE ACTIVITY THERE. THE FIELD HAS NO TWR, AND ACFT ARE SWITCHING BTWN ZLC AND 122.8 AS THEY APCH RIW. I ALWAYS RESPOND WHEN ON 122.8. THIS IS NOT A BUSY ARPT. IT IS EASY TO BECOME COMPLACENT ABOUT OTHER TFC AND ONE MUST NEVER BEGIN TO ASSUME THAT THE OTHER FELLOW KNOWS WHAT YOU ARE DOING!

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.