Narrative:

Taxied onto active runway and almost collided with a landing aircraft. Prior to taking the active runway, I stopped on the taxiway and observed the runway and asked if my passenger observed an aircraft. Neither of us saw the landing aircraft. However, when I took the runway I observed the aircraft on a go around and I taxied clear of the runway onto the grass. The other single engine craft cleared our aircraft by about 50'. I don't know how I missed seeing the landing aircraft, unless he was lost in the runway lights. A collision was never a reality since there was adequate area to taxi clear of the runway, which I did. Callback conversation with reporter revealed the following: the small aircraft on approach apparently did not have landing lights on prior to starting go around and possibly blended into the runway lights. Reporter admitted he was on 122.9 instead of published CTAF 122.8, which he apparently did not know existed. He had not broadcast his intentions even on that frequency. Thought the other aircraft would be on their company frequency. Did not talk to other aircraft and no FAA involvement. Analyst counseled reporter to be on and use CTAF for his own safety.

Related reports:

Google
 

Original NASA ASRS Text

Title: GA SMA AT NON TWR ARPT ENTERED RWY RESULTING IN ATX SMA ON SHORT APCH HAVING TO EXECUTE GO AROUND.

Narrative: TAXIED ONTO ACTIVE RWY AND ALMOST COLLIDED WITH A LNDG ACFT. PRIOR TO TAKING THE ACTIVE RWY, I STOPPED ON THE TXWY AND OBSERVED THE RWY AND ASKED IF MY PAX OBSERVED AN ACFT. NEITHER OF US SAW THE LNDG ACFT. HOWEVER, WHEN I TOOK THE RWY I OBSERVED THE ACFT ON A GO AROUND AND I TAXIED CLEAR OF THE RWY ONTO THE GRASS. THE OTHER SINGLE ENG CRAFT CLRED OUR ACFT BY ABOUT 50'. I DON'T KNOW HOW I MISSED SEEING THE LNDG ACFT, UNLESS HE WAS LOST IN THE RWY LIGHTS. A COLLISION WAS NEVER A REALITY SINCE THERE WAS ADEQUATE AREA TO TAXI CLR OF THE RWY, WHICH I DID. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: THE SMA ON APCH APPARENTLY DID NOT HAVE LNDG LIGHTS ON PRIOR TO STARTING GO AROUND AND POSSIBLY BLENDED INTO THE RWY LIGHTS. RPTR ADMITTED HE WAS ON 122.9 INSTEAD OF PUBLISHED CTAF 122.8, WHICH HE APPARENTLY DID NOT KNOW EXISTED. HE HAD NOT BROADCAST HIS INTENTIONS EVEN ON THAT FREQ. THOUGHT THE OTHER ACFT WOULD BE ON THEIR COMPANY FREQ. DID NOT TALK TO OTHER ACFT AND NO FAA INVOLVEMENT. ANALYST COUNSELED RPTR TO BE ON AND USE CTAF FOR HIS OWN SAFETY.

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