Fll controller described an abort event when the local controller failed to observed the runway when...

Attributes
ACN	912488
Time
Date	201010
Place
Locale Reference	FLL.Airport
State Reference	FL
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Landing
Flight Plan	IFR
Aircraft 2
Make Model Name	Dash 8 Series Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Flight Plan	IFR
Person 1
Function	Other / Unknown
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Non Radar 20 Air Traffic Control Time Certified In Pos 1 (yrs) 20
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy
Miss Distance	Horizontal 2500 Vertical 0

Narrative:

A B737 landed and was instructed to turn right join the parallel taxiway and contact ramp control which was acknowledged by the pilot. Without visually scanning the controller assumed the aircraft turned off at the first intersection; he hadn't. The controller then cleared the DHC8 for takeoff; the pilot rolled and shortly later the asde-X issued the alarm 'warning runway occupied'. The controller instructed the DHC8 pilot to abort the takeoff; the pilot complied and turned off the runway approximately 2;C500 short of the intersection the B737 had ultimately cleared at. At the time there were four other positions staffed including an area supervisor/controller in charge position and no one saw this event developing on the main runway even though it was not busy at the time. I believe this happened due to distractions in the work area; most notably the use of cell phones while working. The majority of controllers; as well as front line managers; use their cell phones while on position for texting; accessing the internet (ie facebook) and gaming. Additionally; but to a lesser degree; are extraneous conversations when traffic is slow and there are extra positions staffed to show time on position and eating meals or ordering take-out while on position. While there are policies on the use of cell phones in the operations area the obvious attitude that 'it won't happen to me' is very prevalent; and it exists with both senior and new people.

Original NASA ASRS Text

Title: FLL Controller described an abort event when the local controller failed to observed the runway when clearing a departure for takeoff when a landing aircraft had not exited the runway; listing distractions and failure to adhere to facility policies as causal factors.

Narrative: A B737 landed and was instructed to turn right join the parallel taxiway and contact Ramp Control which was acknowledged by the pilot. Without visually scanning the Controller assumed the aircraft turned off at the first intersection; he hadn't. The Controller then cleared the DHC8 for takeoff; the pilot rolled and shortly later the ASDE-X issued the alarm 'Warning runway occupied'. The Controller instructed the DHC8 pilot to abort the takeoff; the pilot complied and turned off the runway approximately 2;C500 short of the intersection the B737 had ultimately cleared at. At the time there were four other positions staffed including an Area Supervisor/Controller in Charge position and no one saw this event developing on the main runway even though it was not busy at the time. I believe this happened due to distractions in the work area; most notably the use of cell phones while working. The majority of Controllers; as well as Front Line Managers; use their cell phones while on position for texting; accessing the Internet (ie Facebook) and gaming. Additionally; but to a lesser degree; are extraneous conversations when traffic is slow and there are extra positions staffed to show time on position and eating meals or ordering take-out while on position. While there are policies on the use of cell phones in the operations area the obvious attitude that 'It won't happen to me' is very prevalent; and it exists with both senior and new people.

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

Fll controller described an abort event when the local controller failed to observed the runway when clearing a departure for takeoff when a landing aircraft had not exited the runway; listing distractions and failure to adhere to facility policies as causal factors.