37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 960827 |
Time | |
Date | 201107 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Aircraft 1 | |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Dash 8 Series Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
I was assigned controller in charge for the day watch. I was relieved from the radar sector by a low time controller who had been on vacation for over 2 weeks and only back to work for 3 days. The controller indicated they might want help; so after a brief biological break; I came back and plugged in to assist. The controller had created a complex traffic situation involving two other aircraft; of which one did not acquire a data block. I was assisting the controller with vectoring a dash 8 to the localizer from the west and did not notice the C182 less than 3 miles east of the final. The dash 8 was descending from 5;000 to 3;000 cleared for the ILS runway 16R; while the C182 was level on the opposite downwind at 4;000; but inside 3 miles from the final. I told the controller to turn the C182 to a heading of 030 for traffic; the controller gave the instruction; but the pilot read back heading 360. The controller reiterated the 030 heading; but did not emphasize 'immediately' or call traffic. Leading factors; in my opinion; the controller did not take the hand off on the dash 8 from the center in a timely manner; thus creating a difficult situation in vectoring the aircraft to final. Additionally; the controller released an aircraft from a satellite airport to do practice approaches at a major airport a bad time and without appropriate positive control. The controller didn't recognize the limited data block and effectively control the aircraft; therefore becoming an eminent situation with another IFR aircraft head on at 4;000. This created a distraction for me; as I had to give additional instruction to the controller to get them to react to that situation. Additionally; I was responsible for the operation and had to answer the telephone while assisting the controller. I informed the controller that they might have had a deal. The controller appeared very flustered and was having difficulty formulating control instructions. I immediately saw the distress and relieved the controller. Recommendation; next time I'll work it myself. This controller was certified right before going on an extended vacation; which in my opinion; might not have been appropriate.
Original NASA ASRS Text
Title: Tower CIC described an unsafe situation when observing a newly certified controller who was having extreme difficulties formulating control instructions; appearing to be flustered.
Narrative: I was assigned CIC for the day watch. I was relieved from the RADAR sector by a low time controller who had been on vacation for over 2 weeks and only back to work for 3 days. The Controller indicated they might want help; so after a brief biological break; I came back and plugged in to assist. The Controller had created a complex traffic situation involving two other aircraft; of which one did not acquire a Data Block. I was assisting the Controller with vectoring a Dash 8 to the localizer from the west and did not notice the C182 less than 3 miles east of the final. The Dash 8 was descending from 5;000 to 3;000 cleared for the ILS Runway 16R; while the C182 was level on the opposite downwind at 4;000; but inside 3 miles from the final. I told the Controller to turn the C182 to a heading of 030 for traffic; the Controller gave the instruction; but the pilot read back heading 360. The Controller reiterated the 030 heading; but did not emphasize 'immediately' or call traffic. Leading factors; in my opinion; the Controller did not take the hand off on the Dash 8 from the Center in a timely manner; thus creating a difficult situation in vectoring the aircraft to final. Additionally; the Controller released an aircraft from a satellite airport to do practice approaches at a major airport a bad time and without appropriate positive control. The Controller didn't recognize the limited Data Block and effectively control the aircraft; therefore becoming an eminent situation with another IFR aircraft head on at 4;000. This created a distraction for me; as I had to give additional instruction to the Controller to get them to react to that situation. Additionally; I was responsible for the operation and had to answer the telephone while assisting the Controller. I informed the Controller that they might have had a deal. The Controller appeared very flustered and was having difficulty formulating control instructions. I immediately saw the distress and relieved the Controller. Recommendation; next time I'll work it myself. This Controller was certified right before going on an extended vacation; which in my opinion; might not have been appropriate.
Data retrieved from NASA's ASRS site as of April 2012 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.