Narrative:

I was getting ready to departure uin and a beech baron radioed the field stating he had an electrical failure. A cessna 310 was flying in the area practicing approachs to runway 04 and he was asked to visually look at the baron to confirm gear down in the air, and I was asked to taxi to a position off the taxiway D on runway 36 so I could watch him on a low pass. So I am on 36 pointed towards the active runway 13 watching the baron. He landed safely and after I confirmed he was off the active and the 310 was gone and not other aircraft was around I announced I would be taxiing to 13 for an intersection takeoff. I looked left and observed a piper cherokee? On final. I stopped my taxi about 100 yards short of runway 13 and waited for the plane to land and clear. He never once used the radio to self announce and as his plane was white and the sky was hazy he was hard to see until he was on short final. I actually had more distance from 13 than if I was holding short on taxiway D. So I don't feel there was a safety compromise here, and due to the circumstances I don't see this happening again, but in the future, I would stop the plane and get out and observe from the taxiway so I would not be on runway. Callback conversation with the reporter revealed the following information: reporter reiterated that no actual conflict occurred, but noted that the failure of the other pilot to communicate by radio at any time contributed significantly to the event. He suggests that proper uncontrolled airport traffic pattern procedures. Use the radio for position reports, and recurrent training are effective stategies at reducing the severity and frequency of runway incursion events.

Related reports:

Google
 

Original NASA ASRS Text

Title: RPTR EXPERIENCED MINOR CONFLICT WITH LNDG TFC.

Narrative: I WAS GETTING READY TO DEP UIN AND A BEECH BARON RADIOED THE FIELD STATING HE HAD AN ELECTRICAL FAILURE. A CESSNA 310 WAS FLYING IN THE AREA PRACTICING APCHS TO RWY 04 AND HE WAS ASKED TO VISUALLY LOOK AT THE BARON TO CONFIRM GEAR DOWN IN THE AIR, AND I WAS ASKED TO TAXI TO A POSITION OFF THE TXWY D ON RWY 36 SO I COULD WATCH HIM ON A LOW PASS. SO I AM ON 36 POINTED TOWARDS THE ACTIVE RWY 13 WATCHING THE BARON. HE LANDED SAFELY AND AFTER I CONFIRMED HE WAS OFF THE ACTIVE AND THE 310 WAS GONE AND NOT OTHER ACFT WAS AROUND I ANNOUNCED I WOULD BE TAXIING TO 13 FOR AN INTERSECTION TKOF. I LOOKED L AND OBSERVED A PIPER CHEROKEE? ON FINAL. I STOPPED MY TAXI ABOUT 100 YARDS SHORT OF RWY 13 AND WAITED FOR THE PLANE TO LAND AND CLEAR. HE NEVER ONCE USED THE RADIO TO SELF ANNOUNCE AND AS HIS PLANE WAS WHITE AND THE SKY WAS HAZY HE WAS HARD TO SEE UNTIL HE WAS ON SHORT FINAL. I ACTUALLY HAD MORE DISTANCE FROM 13 THAN IF I WAS HOLDING SHORT ON TXWY D. SO I DON'T FEEL THERE WAS A SAFETY COMPROMISE HERE, AND DUE TO THE CIRCUMSTANCES I DON'T SEE THIS HAPPENING AGAIN, BUT IN THE FUTURE, I WOULD STOP THE PLANE AND GET OUT AND OBSERVE FROM THE TXWY SO I WOULD NOT BE ON RWY. CALLBACK CONVERSATION WITH THE RPTR REVEALED THE FOLLOWING INFO: RPTR REITERATED THAT NO ACTUAL CONFLICT OCCURRED, BUT NOTED THAT THE FAILURE OF THE OTHER PLT TO COMMUNICATE BY RADIO AT ANY TIME CONTRIBUTED SIGNIFICANTLY TO THE EVENT. HE SUGGESTS THAT PROPER UNCONTROLLED ARPT TFC PATTERN PROCEDURES. USE THE RADIO FOR POSITION RPTS, AND RECURRENT TRAINING ARE EFFECTIVE STATEGIES AT REDUCING THE SEVERITY AND FREQUENCY OF RWY INCURSION EVENTS.

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.