Narrative:

In sum: archer was back-taxiing on runway 14 for departure. Announced same on CTAF. King air announced on CTAF entry onto downwind for runway 32. (Winds still favored runway 14 but were changing). Archer announced 2 times back-taxi on runway 14 (no available txwys or off ramps due to construction). King air only response was to announce 'extended downwind.' archer completed back-taxi and began takeoff roll. King air announced turn to final and began final descent. King air veered to runway 32's right approximately 1000 ft from the numbers, archer turned to left after gaining 100 ft. Archer responded with call to king air on CTAF with no acknowledgement. Believe that king air never focused on fact that there was activity on runway throughout king air's approach pattern possibly because he was focused on other end of runway. After departing to northeast (WX became VFR with unlimited visibility within 15 mins) archer contacted flight watch to verify radio worked. Flight watch responded with no difficulty. It is unknown why king air never established visual with archer activity on runway or did not acknowledge radio calls. Archer believes it took only action possible (expedited takeoff and evasive action at low altitude) since construction at airport made it impossible to exit runway on the ground in that area.

Google
 

Original NASA ASRS Text

Title: UNCTLED ARPT TFC VIOLATIONS.

Narrative: IN SUM: ARCHER WAS BACK-TAXIING ON RWY 14 FOR DEP. ANNOUNCED SAME ON CTAF. KING AIR ANNOUNCED ON CTAF ENTRY ONTO DOWNWIND FOR RWY 32. (WINDS STILL FAVORED RWY 14 BUT WERE CHANGING). ARCHER ANNOUNCED 2 TIMES BACK-TAXI ON RWY 14 (NO AVAILABLE TXWYS OR OFF RAMPS DUE TO CONSTRUCTION). KING AIR ONLY RESPONSE WAS TO ANNOUNCE 'EXTENDED DOWNWIND.' ARCHER COMPLETED BACK-TAXI AND BEGAN TKOF ROLL. KING AIR ANNOUNCED TURN TO FINAL AND BEGAN FINAL DSCNT. KING AIR VEERED TO RWY 32'S R APPROX 1000 FT FROM THE NUMBERS, ARCHER TURNED TO L AFTER GAINING 100 FT. ARCHER RESPONDED WITH CALL TO KING AIR ON CTAF WITH NO ACKNOWLEDGEMENT. BELIEVE THAT KING AIR NEVER FOCUSED ON FACT THAT THERE WAS ACTIVITY ON RWY THROUGHOUT KING AIR'S APCH PATTERN POSSIBLY BECAUSE HE WAS FOCUSED ON OTHER END OF RWY. AFTER DEPARTING TO NE (WX BECAME VFR WITH UNLIMITED VISIBILITY WITHIN 15 MINS) ARCHER CONTACTED FLT WATCH TO VERIFY RADIO WORKED. FLT WATCH RESPONDED WITH NO DIFFICULTY. IT IS UNKNOWN WHY KING AIR NEVER ESTABLISHED VISUAL WITH ARCHER ACTIVITY ON RWY OR DID NOT ACKNOWLEDGE RADIO CALLS. ARCHER BELIEVES IT TOOK ONLY ACTION POSSIBLE (EXPEDITED TKOF AND EVASIVE ACTION AT LOW ALT) SINCE CONSTRUCTION AT ARPT MADE IT IMPOSSIBLE TO EXIT RWY ON THE GND IN THAT AREA.

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.