Incident Overview
On an unspecified date, a Boeing 737 was cleared for takeoff on runway 18L at Dallas/Fort Worth International Airport. After landing on runway 18R, another Boeing 737 took the high-speed exit onto taxiway Whiskey Mike and received clearance to cross runway 18L. Both aircraft crews observed a potential collision and initiated evasive maneuvers.
Sequence of Events
The departing aircraft continued its takeoff, then returned to the airport and landed. Upon inspection, damage was found on the skin of the underside of its tail. The taxiing aircraft proceeded to the gate and deplaned its passengers. No further details on injuries or damage extent were provided.
Air Traffic Control Factors
At the time of the incursion, the West air traffic control tower's ground control west one and local west one controller positions were combined. The supervisor-in-charge of the west tower was operating the flight data position while simultaneously performing supervisory duties. Additionally, a National Air Traffic Controllers Association representative had entered the tower cab and was meeting with the supervisor-in-charge. In an interview, the incident controller stated that he did not scan runway 18L before clearing the taxiing aircraft to cross.
Regulatory Context
FAA Order 7110.65, Air Traffic Control Handbook, paragraph 3-1-3, 'Use of Active Runways,' specifies that 'the local controller has primary responsibility for operations conducted on the active runway and must control the use of those runways.' Paragraph 3-1-12, 'Visually Scanning Runways,' states that 'local controllers shall visually scan runways to the maximum extent possible.' No causal link between these regulations and the incident was explicitly stated in the source.
Aftermath
Following the incident, the departing aircraft landed with tail damage, and the taxiing aircraft completed its movement to the gate. The source did not provide additional details on subsequent investigations or actions taken.