![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1222657 |
| Time | |
| Date | 201412 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ABI.Airport |
| State Reference | TX |
| Environment | |
| Flight Conditions | Marginal |
| Aircraft 1 | |
| Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Flight Phase | Final Approach |
| Route In Use | None |
| Person 1 | |
| Function | Supervisor / CIC |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 18 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Weather was marginal so abi was doing localizer approaches to 17R; 17L is closed for construction. I was controller in charge; traffic was very light. The local controller; had aircraft X on a 3-4 mile final 17R cleared to land and aircraft Y calling off 82TS; a private field 2NM northeast of abi; requesting touch and goes. The controller's response to aircraft Y was this; 'make ah...enter a left field...mid ah...left mid downwind for the left ah...downwind'. Controller is not looking out the window and not watching the traffic; aircraft Y turns west for a base to 17R and I had to tell the controller that aircraft Y is cutting off aircraft X. She turns around and now sees the situation and turns aircraft Y right to heading 360; right toward the traffic. Aircraft Y immediately reports the traffic on final in sight and request a clearance for a localizer approach instead of VFR pattern work. Even though separation was not lost and only because I brought it to her attention (1 mile at best); this was an unsafe situation brought on by the local controller's lack of attention; awareness and knowledge. These kind of situations are occurring on a daily basis. Management is being made aware; but the unsafe events continue. Remedial training on maintaining awareness while on position; on how to sequence aircraft and how not to; and/or proper phraseology to avoid confusing instructions.
Original NASA ASRS Text
Title: ABI Local Controller almost had a separation loss due to not paying attention.
Narrative: Weather was marginal so ABI was doing Localizer approaches to 17R; 17L is closed for construction. I was CIC; traffic was very light. The local controller; had Aircraft X on a 3-4 mile final 17R cleared to land and Aircraft Y calling off 82TS; a private field 2NM NE of ABI; requesting touch and goes. The controller's response to Aircraft Y was this; 'Make ah...enter a left field...mid ah...left mid downwind for the left ah...downwind'. Controller is not looking out the window and not watching the traffic; Aircraft Y turns west for a base to 17R and I had to tell the controller that Aircraft Y is cutting off Aircraft X. She turns around and now sees the situation and turns Aircraft Y right to heading 360; right toward the traffic. Aircraft Y immediately reports the traffic on final in sight and request a clearance for a Localizer approach instead of VFR pattern work. Even though separation was not lost and only because I brought it to her attention (1 mile at best); this was an unsafe situation brought on by the local controller's lack of attention; awareness and knowledge. These kind of situations are occurring on a daily basis. Management is being made aware; but the unsafe events continue. Remedial training on maintaining awareness while on position; on how to sequence aircraft and how not to; and/or proper phraseology to avoid confusing instructions.
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.