Narrative:

We experienced a runway incursion/traffic conflict during the departure phase of our flight from dfw. During our takeoff roll, we observed an erj-145 crossing the departure path of runway 13L as the erj made its final descent for landing on runway 17L. After being cleared for takeoff, the captain taxied onto runway 13L and xferred the flight controls to me. I then proceeded to apply power for takeoff and commenced my takeoff roll. Shortly after V1 was called, we observed the erj crossing the departure end of runway 13L from left to right at a distance of approximately 3000-4000 ft. Upon observing the landing traffic, I rotated aggressively and climbed rapidly to avoid any possibility of a collision. Shortly after our initial climb, dfw tower informed us that we had not been cleared for takeoff to which I replied to tower that we had received a takeoff clearance. The controller then xferred us to departure control, and we continued the flight to eld without any further incident. Although the 2 aircraft were never in position to collide with one another, the possibility of a collision would have been much greater had I applied power for takeoff sooner or the arriving erj had been closer to touchdown. Contributing factors to the conflict were high workload on both us and the controller, and our failure to observe the conflicting traffic as it made its approach to landing. Also, not hearing the conversation between the tower controller and the landing traffic contributed to the event that transpired shortly thereafter. In my opinion, the controller's inability to maintain situational awareness was a direct factor to the incident and the primary cause. From a crew standpoint, actions that may have prevented the situation would have been better visual scanning for the landing traffic and a more attentive ear to the tower frequency. Also, by limiting the controller's workload to allow for a more effective flow of traffic and prevent repetitive actions that contribute to the conflicting clrncs.

Google
 

Original NASA ASRS Text

Title: UNAUTH TKOF CREATES A POTENTIAL AIRBORNE CONFLICT BTWN A BE1900 OFF RWY 13L AND AN ERJ LNDG ON RWY 17L AT DFW, TX.

Narrative: WE EXPERIENCED A RWY INCURSION/TFC CONFLICT DURING THE DEP PHASE OF OUR FLT FROM DFW. DURING OUR TKOF ROLL, WE OBSERVED AN ERJ-145 XING THE DEP PATH OF RWY 13L AS THE ERJ MADE ITS FINAL DSCNT FOR LNDG ON RWY 17L. AFTER BEING CLRED FOR TKOF, THE CAPT TAXIED ONTO RWY 13L AND XFERRED THE FLT CTLS TO ME. I THEN PROCEEDED TO APPLY PWR FOR TKOF AND COMMENCED MY TKOF ROLL. SHORTLY AFTER V1 WAS CALLED, WE OBSERVED THE ERJ XING THE DEP END OF RWY 13L FROM L TO R AT A DISTANCE OF APPROX 3000-4000 FT. UPON OBSERVING THE LNDG TFC, I ROTATED AGGRESSIVELY AND CLBED RAPIDLY TO AVOID ANY POSSIBILITY OF A COLLISION. SHORTLY AFTER OUR INITIAL CLB, DFW TWR INFORMED US THAT WE HAD NOT BEEN CLRED FOR TKOF TO WHICH I REPLIED TO TWR THAT WE HAD RECEIVED A TKOF CLRNC. THE CTLR THEN XFERRED US TO DEP CTL, AND WE CONTINUED THE FLT TO ELD WITHOUT ANY FURTHER INCIDENT. ALTHOUGH THE 2 ACFT WERE NEVER IN POS TO COLLIDE WITH ONE ANOTHER, THE POSSIBILITY OF A COLLISION WOULD HAVE BEEN MUCH GREATER HAD I APPLIED PWR FOR TKOF SOONER OR THE ARRIVING ERJ HAD BEEN CLOSER TO TOUCHDOWN. CONTRIBUTING FACTORS TO THE CONFLICT WERE HIGH WORKLOAD ON BOTH US AND THE CTLR, AND OUR FAILURE TO OBSERVE THE CONFLICTING TFC AS IT MADE ITS APCH TO LNDG. ALSO, NOT HEARING THE CONVERSATION BTWN THE TWR CTLR AND THE LNDG TFC CONTRIBUTED TO THE EVENT THAT TRANSPIRED SHORTLY THEREAFTER. IN MY OPINION, THE CTLR'S INABILITY TO MAINTAIN SITUATIONAL AWARENESS WAS A DIRECT FACTOR TO THE INCIDENT AND THE PRIMARY CAUSE. FROM A CREW STANDPOINT, ACTIONS THAT MAY HAVE PREVENTED THE SIT WOULD HAVE BEEN BETTER VISUAL SCANNING FOR THE LNDG TFC AND A MORE ATTENTIVE EAR TO THE TWR FREQ. ALSO, BY LIMITING THE CTLR'S WORKLOAD TO ALLOW FOR A MORE EFFECTIVE FLOW OF TFC AND PREVENT REPETITIVE ACTIONS THAT CONTRIBUTE TO THE CONFLICTING CLRNCS.

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.