37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1285997 |
Time | |
Date | 201508 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SEA.Tower |
State Reference | WA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2 |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Runway |
Narrative:
Aircraft Y was instructed to line up and wait and was told that traffic would cross downfield. Aircraft Z was given a crossing clearance across runway 16L at north and told that traffic was holding in position. Immediately thereafter aircraft X was given a crossing clearance and told of the holding traffic. I then assigned visual separation to the preceding departure; changed them to departure; and then scanned my line-up for strip accuracy and potential crossing holes. I then looked up at aircraft Y; scanned the runway; which was clear; and gave aircraft Y his take-off clearance. I did not see that aircraft X had not crossed the runway yet; and after my scan down the runway they started their crossing. At which point aircraft Y said they saw the red lights and were aborting their take-off for traffic crossing in front of them.the only changes that I would make are based on my actions. There were contributing factors at play that I did not take as seriously as I should have.
Original NASA ASRS Text
Title: Controller and pilots report of being cleared for takeoff and an aircraft that was cleared to cross the runway did in a slow manner. Controller thought aircraft had already crossed and then cleared the carrier. Carrier started takeoff roll and observed red lights down field and aborted takeoff.
Narrative: Aircraft Y was instructed to line up and wait and was told that traffic would cross downfield. Aircraft Z was given a crossing clearance across RWY 16L at N and told that traffic was holding in position. Immediately thereafter aircraft X was given a crossing clearance and told of the holding traffic. I then assigned visual separation to the preceding departure; changed them to departure; and then scanned my line-up for strip accuracy and potential crossing holes. I then looked up at aircraft Y; scanned the runway; which was clear; and gave aircraft Y his take-off clearance. I did not see that aircraft X had not crossed the runway yet; and after my scan down the runway they started their crossing. At which point aircraft Y said they saw the red lights and were aborting their take-off for traffic crossing in front of them.The only changes that I would make are based on my actions. There were contributing factors at play that I did not take as seriously as I should have.
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.