Narrative:

Traffic was departing and arriving using both runway directions at dts; runway 14/32. I elected to depart 14 as the wind was a direct crosswind. I called on unicom 'departing runway 14 to the west' and entered the 'runway in use; 14'. After I began my takeoff roll; a cessna citation at the opposite end of the runway (who decided to depart 32) decided to enter the runway. I aborted the takeoff and stopped on the runway. The citation advised he would taxi to the nearest intersection and exit the runway. I then began; again; my takeoff roll and departed. The citation pilot then said 'he was released by approach'. I informed him that I was VFR; not IFR. The citation pilot was obviously confused as to the relationship between atc; destination class D; and the implications of far 93. It was obvious the citation crew assumed that atc somehow 'controlled' the runway and traffic pattern at dts. The crew was not monitoring the unicom until they decided to depart; immediately after talking to atc for their IFR release. It is absolutely essential to monitor dts unicom while trying to deal with approach on an IFR release. At the minimum; dts should have an rco. It is very difficult to communicate with approach to obtain an IFR release as position on the airport affects transmit/receive capability with approach. Dts desperately needs a tower this has gone on entirely too long.

Google
 

Original NASA ASRS Text

Title: SA227 Captain on the takeoff roll at DTS detects a Citation entering the runway for an opposite direction takeoff. The reporter rejects his takeoff; then continues when the Citation clears the runway. The Citation Captain had been 'released' by ATC but did not monitor the CTAF while waiting.

Narrative: Traffic was departing and arriving using both runway directions at DTS; runway 14/32. I elected to depart 14 as the wind was a direct crosswind. I called on unicom 'departing runway 14 to the West' and entered the 'runway in use; 14'. After I began my takeoff roll; a Cessna citation at the opposite end of the runway (who decided to depart 32) decided to enter the runway. I aborted the takeoff and stopped on the runway. The citation advised he would taxi to the nearest intersection and exit the runway. I then began; again; my takeoff roll and departed. The citation pilot then said 'he was released by approach'. I informed him that I was VFR; not IFR. The citation pilot was obviously confused as to the relationship between atc; destination class D; and the implications of far 93. It was obvious the citation crew assumed that atc somehow 'controlled' the runway and traffic pattern at DTS. The crew was not monitoring the unicom until they decided to depart; immediately after talking to atc for their IFR release. It is absolutely essential to monitor DTS unicom while trying to deal with approach on an IFR release. At the minimum; DTS should have an RCO. It is very difficult to communicate with approach to obtain an IFR release as position on the airport affects transmit/receive capability with approach. DTS desperately needs a tower this has gone on entirely too long.

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