37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 875388 |
Time | |
Date | 201002 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | CLE.TRACON |
State Reference | OH |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Approach Trainee |
Qualification | Air Traffic Control Developmental |
Person 2 | |
Function | Approach Instructor |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Air carrier X was first on final and air carrier Y was 5 miles behind them on the ILS just outside the FAF. Air carrier X was on the tower frequency when the city of cleveland closed the landing runway due to 'poor' breaking. I was in the process of climbing and/or descending all my traffic for holding when the tower coordinated to put air carrier X back on the downwind. I had air carrier Y climb to the lowest free altitude that I had at the time; 5000; and when air carrier X checked in I climbed them to 6000; the next free altitude. Without verifying that air carrier X climbed through 5000 I turned air carrier Y right direct the holding fix and that's when the proximity event took place. My trainer was then able to step in and resolve the conflict. Recommendation; during the event my trainer was busy coordinating with the tower and not listening to what I was doing; while the person that was supposed to open the inner was trying to get me to do something that I didn't understand. There wasn't a lot of traffic that warranted and inner controller since we were holding at all the fixes and only had about 6 planes in the airspace; however we did need a coordinator due the constantly changing conditions and the complexity of the situation.
Original NASA ASRS Text
Title: CLE TRACON Controller receiving training described a loss of separation event when the landing runway was closed because of braking issues; the Reporter indicating the Instructor failed to hear an incorrect vector instruction because of coordination involvement/s.
Narrative: Air Carrier X was first on final and Air Carrier Y was 5 miles behind them on the ILS just outside the FAF. Air Carrier X was on the Tower frequency when the City Of Cleveland closed the landing runway due to 'poor' breaking. I was in the process of climbing and/or descending all my traffic for holding when the Tower coordinated to put Air Carrier X back on the downwind. I had Air Carrier Y climb to the lowest free altitude that I had at the time; 5000; and when Air Carrier X checked in I climbed them to 6000; the next free altitude. Without verifying that Air Carrier X climbed through 5000 I turned Air Carrier Y right direct the holding fix and that's when the proximity event took place. My Trainer was then able to step in and resolve the conflict. Recommendation; during the event my Trainer was busy coordinating with the Tower and not listening to what I was doing; while the person that was supposed to open the inner was trying to get me to do something that I didn't understand. There wasn't a lot of traffic that warranted and inner Controller since we were holding at all the fixes and only had about 6 planes in the airspace; however we did need a coordinator due the constantly changing conditions and the complexity of the situation.
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.