37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1242670 |
Time | |
Date | 201503 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | IAH.Airport |
State Reference | TX |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
I observed this error while working ln (08L). This incident happened on local control (08R).aircraft X was on approach to land runway 08R and slowing. Field visibility was 1/4 SM and ceiling OVC002. Aircraft Y was behind him with an overtake situation. I noticed the overtake and asked the local controller (local control) if the monitor was taking care of that. The reply was nope they haven't said a word. After IFR separation was lost the final monitor controller called the local control controller and said are you going to break him out? The local control controller said isn't that your job. The final monitor did nothing with the aircraft; and the local control controller turned around and told the flm (front line manager) what should I do with these two? The flm did not respond or give any answer so the controller let him land.this is a common problem at this facility where the final monitors do not pay attention to the traffic. They are reactive and not proactive to the aircraft situations. This is also an issue because final doesn't know if they should be breaking out the aircraft and the local control controller wasn't sure if they should break the aircraft out. During this configuration and with the weather like it was; the final monitor has separation responsibility till one mile final. The final monitors need refresher on what their roles and responsibilities are. The tower should also be reminded of our responsibility during this situation via a briefing.
Original NASA ASRS Text
Title: IAH Local Controller (LC) describes a situation where the other LC and other final monitor had a loss of separation; due to the final monitor not slowing the aircraft and/or the other local not sending the aircraft around. The other local asked the Front Line Manager what to do; but got no response.
Narrative: I observed this error while working LN (08L). This incident happened on LC (08R).Aircraft X was on approach to land runway 08R and slowing. Field visibility was 1/4 SM and ceiling OVC002. Aircraft Y was behind him with an overtake situation. I noticed the overtake and asked the Local controller (LC) if the monitor was taking care of that. The reply was nope they haven't said a word. After IFR separation was lost the final monitor controller called the LC controller and said are you going to break him out? The LC controller said isn't that your job. The final monitor did nothing with the aircraft; and the LC controller turned around and told the FLM (Front Line Manager) what should I do with these two? The FLM did not respond or give any answer so the controller let him land.This is a common problem at this facility where the final monitors do not pay attention to the traffic. They are reactive and not proactive to the aircraft situations. This is also an issue because final doesn't know if they should be breaking out the aircraft and the LC controller wasn't sure if they should break the aircraft out. During this configuration and with the weather like it was; the final monitor has separation responsibility till one mile final. The final monitors need refresher on what their roles and responsibilities are. The tower should also be reminded of our responsibility during this situation via a briefing.
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.