37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1692688 |
Time | |
Date | 201910 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | FLL.Airport |
State Reference | FL |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Caravan Undifferentiated |
Operating Under FAR Part | Part 135 |
Flight Phase | Taxi |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Ground |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7.0 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Critical Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Narrative:
I told aircraft X; who landed on runway 28L to taxi via [taxiway] east and B5; and hold short of runway 28R to get to parking. The pilot read back that he would hold short of runway 28R. There was moderate traffic volume and it was nighttime. There were numerous taxiway closures due to construction; creating an unsafe situation in my opinion. I taxied several other aircraft that called for taxi. When I scanned back to observe aircraft X; he had taxied past the hold short bars and was on the south edge of runway 28R. At the same time; aircraft Y had just rotated on runway 28R. A collision was narrowly averted. I believe that the lack of the runway safety hold lights being on; combined with a very confusing runway crossing point due to poor planning for the runway being opened with so many taxiway closures were contributing factors to the event. The pilot also advised that one of the runway 28R hold signs were unlit. Serious and swift safety steps should be taken to prevent a future safety event or disaster from happening. Runway 28R should not have been opened with so many associated taxiways closed. The runway occupancy safety lights must be swiftly returned to service. Runway lights and signs that are unlit should be fixed as quickly as possible.
Original NASA ASRS Text
Title: FLL Tower Controller reported that taxiway closures and unlit runway and taxiway signs resulted in a runway incursion and a critical ground conflict.
Narrative: I told Aircraft X; who landed on Runway 28L to taxi via [Taxiway] E and B5; and hold short of Runway 28R to get to parking. The pilot read back that he would hold short of Runway 28R. There was moderate traffic volume and it was nighttime. There were numerous taxiway closures due to construction; creating an unsafe situation in my opinion. I taxied several other aircraft that called for taxi. When I scanned back to observe Aircraft X; he had taxied past the hold short bars and was on the south edge of Runway 28R. At the same time; Aircraft Y had just rotated on Runway 28R. A collision was narrowly averted. I believe that the lack of the runway safety hold lights being on; combined with a very confusing runway crossing point due to poor planning for the runway being opened with so many taxiway closures were contributing factors to the event. The pilot also advised that one of the Runway 28R hold signs were unlit. Serious and swift safety steps should be taken to prevent a future safety event or disaster from happening. Runway 28R should not have been opened with so many associated taxiways closed. The Runway occupancy safety lights must be swiftly returned to service. Runway lights and signs that are unlit should be fixed as quickly as possible.
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.