Unauthorized runway operation in the face of arrival landing traffic at a non tower airport.

Attributes
ACN	214072
Time
Date	199206
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : ane
State Reference	MN
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : msp
Operator	general aviation : personal
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Retractable Gear
Flight Phase	climbout : takeoff ground : holding
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach landing other
Flight Plan	VFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument
Experience	flight time last 90 days : 55 flight time total : 1811 flight time type : 860
ASRS Report	214072
Person 2
Affiliation	Other
Function	flight crew : single pilot
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : published procedure non adherence other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Miss Distance	horizontal : 1000 vertical : 200
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I had been cleared for departure by msp TRACON, which has a remote transmitter at ane. I had been monitoring local advisory frequency, and traffic was scarce. I had run up 100 ft from the runway, and upon getting ready to go, glanced up for incoming traffic and saw none; so proceeded to taxi rapidly onto runway. Making a last check, I saw an aircraft on final just as I entered the runway. It was too late to stop, so I continued to takeoff. I believe the landing aircraft was able to continue to land, without any problem, as my acceleration in the small aircraft X was good, and landing traffic was an small aircraft Y. However, it was a surprise to me to discover the other plane so close. I normally would have held until no one was on final. I still don't know whether the small aircraft Y wasn't announcing position, or if my radio was mis-set, but I should have stopped at runway threshold and cleared the approach, instead of just confirming what I thought was a clear runway environment.

Original NASA ASRS Text

Title: UNAUTHORIZED RWY OP IN THE FACE OF ARR LNDG TFC AT A NON TWR ARPT.

Narrative: I HAD BEEN CLRED FOR DEP BY MSP TRACON, WHICH HAS A REMOTE XMITTER AT ANE. I HAD BEEN MONITORING LCL ADVISORY FREQ, AND TFC WAS SCARCE. I HAD RUN UP 100 FT FROM THE RWY, AND UPON GETTING READY TO GO, GLANCED UP FOR INCOMING TFC AND SAW NONE; SO PROCEEDED TO TAXI RAPIDLY ONTO RWY. MAKING A LAST CHK, I SAW AN ACFT ON FINAL JUST AS I ENTERED THE RWY. IT WAS TOO LATE TO STOP, SO I CONTINUED TO TKOF. I BELIEVE THE LNDG ACFT WAS ABLE TO CONTINUE TO LAND, WITHOUT ANY PROBLEM, AS MY ACCELERATION IN THE SMA X WAS GOOD, AND LNDG TFC WAS AN SMA Y. HOWEVER, IT WAS A SURPRISE TO ME TO DISCOVER THE OTHER PLANE SO CLOSE. I NORMALLY WOULD HAVE HELD UNTIL NO ONE WAS ON FINAL. I STILL DON'T KNOW WHETHER THE SMA Y WASN'T ANNOUNCING POS, OR IF MY RADIO WAS MIS-SET, BUT I SHOULD HAVE STOPPED AT RWY THRESHOLD AND CLRED THE APCH, INSTEAD OF JUST CONFIRMING WHAT I THOUGHT WAS A CLR RWY ENVIRONMENT.

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.