37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1754589 |
Time | |
Date | 202008 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach Landing |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Route In Use | Visual Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | Flap/Slat Control System |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 20.6 |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Conflict Ground Conflict Less Severe |
Narrative:
Aircraft X was arriving to runway xx left with multiple arrivals to both xx left and xx right. We were xx/xy right turns due to the wind strong out of the southwest. Air speeds on final were very consistent the whole session until aircraft X was coming in. The aircraft was at a 3 mile final showing 1;300 and 170 knots. I said out loud to the flm; who was about 6 feet to my right monitoring; that aircraft X was usually high and fast. I had no traffic conflicts if they were to go-around; so I watched them. At about a 2 mile final they were 1;100 and 160 knots and appeared to have leveled off. I waited for them to tell me they were going around; and when they did I assigned runway heading and 3;000. They read back the altitude only. I waited a few seconds to let them get a positive rate and stable climb; then confirmed to fly runway heading for vector final approach course. They read it back. I cleared aircraft Y to cross runway 28 left at tango; since aircraft X was going around. I handed aircraft X's target off to TRACON and waited until aircraft X neared 3;000. To confirm the reason too high; too fast for the go around. They said a flap issue. I confirmed they would need no assistance; just to run a checklist. They confirmed no assistance required and confirmed needing to run their checklist. I told them to stand by while I told TRACON. I coordinated with ci-1 the reason for the go-around. As I was coordinating; aircraft Y called to confirm cross runway 28 left at tango. I confirmed they were cleared to cross; as they had stopped over the hold short line. I assume there must have been confusion on the flight deck; especially with all of the aircraft X communication going on. I then shipped aircraft X to departure. About 5 minutes later the aircraft showed up on the scope left downswing and the flm confirmed with TRACON no assistance. The aircraft landed a short time later.the only thing I would suggest is advising sooner about the flap issue; however with the lighter traffic during this pandemic; it really was no problem. As far as aircraft Y goes; strange times call for a greater degree of diligence; and they asked to confirm as they should of there is a question; just make sure to hold short first if they are going to pause to ask. Had they not been cleared it would have been a runway incursion at that point.
Original NASA ASRS Text
Title: Tower Controller reported a flight crew had to go-around after being high and fast due to a reported flap problem.
Narrative: Aircraft X was arriving to Runway XX Left with multiple arrivals to both XX Left and XX Right. We were XX/XY Right Turns due to the wind strong out of the Southwest. Air speeds on final were very consistent the whole session until Aircraft X was coming in. The aircraft was at a 3 mile final showing 1;300 and 170 knots. I said out loud to the FLM; who was about 6 feet to my right monitoring; that Aircraft X was usually high and fast. I had no traffic conflicts if they were to go-around; so I watched them. At about a 2 mile final they were 1;100 and 160 knots and appeared to have leveled off. I waited for them to tell me they were going around; and when they did I assigned runway heading and 3;000. They read back the altitude only. I waited a few seconds to let them get a positive rate and stable climb; then confirmed to fly runway heading for vector final approach course. They read it back. I cleared Aircraft Y to cross Runway 28 Left at Tango; since Aircraft X was going around. I handed Aircraft X's target off to TRACON and waited until Aircraft X neared 3;000. To confirm the reason too high; too fast for the go around. They said a flap issue. I confirmed they would need no assistance; just to run a checklist. They confirmed no assistance required and confirmed needing to run their checklist. I told them to stand by while I told TRACON. I coordinated with CI-1 the reason for the go-around. As I was coordinating; Aircraft Y called to confirm cross Runway 28 Left at Tango. I confirmed they were cleared to cross; as they had stopped over the hold short line. I assume there must have been confusion on the flight deck; especially with all of the Aircraft X communication going on. I then shipped Aircraft X to Departure. About 5 minutes later the aircraft showed up on the scope left downswing and the FLM confirmed with TRACON no assistance. The aircraft landed a short time later.The only thing I would suggest is advising sooner about the flap issue; however with the lighter traffic during this pandemic; it really was no problem. As far as Aircraft Y goes; strange times call for a greater degree of diligence; and they asked to confirm as they should of there is a question; just make sure to hold short first if they are going to pause to ask. Had they not been cleared it would have been a Runway Incursion at that point.
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.