37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1389318 |
Time | |
Date | 201609 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Regional Jet 900 (CRJ900) |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Coordinator Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1 |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance |
Narrative:
I was working cc/controller in charge so that the supervisor could build currency time on local south. While working the position the asde-X alerted to runway 17 occupied. I looked over to see a CRJ2 about 1/3 of the way down the runway on departure roll; and a CRJ9 parked on L3 around 2/3s of the way down the runway. I could not assess if the CRJ9 was across the hold bars due to the distance from the tower. By the time that I realized where the conflict was and then that the local controller was not cancelling the takeoff clearance (the CRJ2 was now more than halfway down the runway); I felt the situation was not safe to tell the local control to cancel the takeoff clearance. The CRJ2 rotated and appeared to overfly the taxiway L3 intersection by 100 feet AGL.by the time the asde alerted to the situation; it seemed that it was far too late to make a timely correction to the situation. The warning itself seems too long; and the aircraft speed at which it triggers on a departure roll seems high. A ding or other warning sound instead of the word 'warning'; or a slower speed on departure roll triggering the 'occupied' warning could increase the time available to fix a situation like this.
Original NASA ASRS Text
Title: A Tower Controller and CRJ200 Captain reported an aircraft was cleared for takeoff with another aircraft exiting the runway stopped on a taxiway but not past the hold short lines.
Narrative: I was working CC/CIC so that the supervisor could build currency time on Local South. While working the position the ASDE-X alerted to Runway 17 occupied. I looked over to see a CRJ2 about 1/3 of the way down the runway on departure roll; and a CRJ9 parked on L3 around 2/3s of the way down the runway. I could not assess if the CRJ9 was across the hold bars due to the distance from the tower. By the time that I realized where the conflict was and then that the Local Controller was not cancelling the takeoff clearance (the CRJ2 was now more than halfway down the runway); I felt the situation was not safe to tell the Local Control to cancel the takeoff clearance. The CRJ2 rotated and appeared to overfly the Taxiway L3 intersection by 100 feet AGL.By the time the ASDE alerted to the situation; it seemed that it was far too late to make a timely correction to the situation. The warning itself seems too long; and the aircraft speed at which it triggers on a departure roll seems high. A ding or other warning sound instead of the word 'warning'; or a slower speed on departure roll triggering the 'occupied' warning could increase the time available to fix a situation like this.
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.