37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1759796 |
Time | |
Date | 202009 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Tower |
State Reference | US |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Traffic Management Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Landing Without Clearance |
Narrative:
My last session working before end of shift. Started working all local control [local control] combined; was moved to tmu [traffic management unit] for re-certification mid-session and then put back into local control combined for end of session. There was a consistent mix of arrivals and departures. Nothing complex or high workload but consistently keeping you engaged. Throughout my session there were moments when departure strips were being passed late from ground control [ground control] and I had to retrieve or wait for them to be passed; that occurred around the time aircraft X should've been checking in. I believe social distancing was a partial factor in the movement of strips. I remember observing aircraft X on the stars [standard terminal automation replacement system] display and continuing my scan of arrivals/departures and out the window. I was missing a strip or two compared to the aircraft nearing the end of runway xxr and it did not register with me that aircraft X did not check on with me. The aircraft X was part of my scan and I did plan for their arrival and time on runway reference departures and other aircraft. I do not recall if I had turned the data block blue on the stars display to show the aircraft had been cleared to land.suggestion: digital strips/flight boards to assist in social distancing and decrease workload/heads downtime. Would also include inbound aircraft and not just departing aircraft.
Original NASA ASRS Text
Title: Tower Controller reported not being sure if a landing clearance was given to an arrival aircraft.
Narrative: My last session working before end of shift. Started working all LC [Local Control] combined; was moved to TMU [Traffic Management Unit] for re-certification mid-session and then put back into LC combined for end of session. There was a consistent mix of arrivals and departures. Nothing complex or high workload but consistently keeping you engaged. Throughout my session there were moments when departure strips were being passed late from GC [Ground Control] and I had to retrieve or wait for them to be passed; that occurred around the time Aircraft X should've been checking in. I believe social distancing was a partial factor in the movement of strips. I remember observing Aircraft X on the STARS [Standard Terminal Automation Replacement System] display and continuing my scan of arrivals/departures and out the window. I was missing a strip or two compared to the aircraft nearing the end of Runway XXR and it did not register with me that Aircraft X did not check on with me. The Aircraft X was part of my scan and I did plan for their arrival and time on runway reference departures and other aircraft. I do not recall if I had turned the data block blue on the STARS display to show the aircraft had been cleared to land.Suggestion: Digital strips/flight boards to assist in social distancing and decrease workload/heads downtime. Would also include inbound aircraft and not just departing aircraft.
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.