37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1231740 |
Time | |
Date | 201501 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | IND.TRACON |
State Reference | IN |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Widebody Low Wing 3 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 4.4 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
I just arrived at the position for a morning shift. First transmission of the day; after a relief briefing from the midnight crew. I had two departures; one off runway 23L and one off 23R aircraft X off runway 23L on an assigned heading 210 with a first fix of cvg which is approximately a 140 degree heading; and aircraft Y off runway 23R on runway heading; with the MAREO3 departure; a 080 heading; with aircraft X a couple miles ahead. This is a somewhat common practice on the midnight shift to expedite traffic; with the 23R runway heading departure getting a right turn over the airport to the east. This practice is almost exclusively for [name removed] aircraft only. I turned aircraft Y left direct mareo intersection which turned aircraft Y into aircraft X's flight path. I had not sat down yet and the preference sets were still from the previous controller; which confused me. We have automatic leader direction changes in our stars equipment here and I made a terrible assumption that aircraft Y was off runway 23L; not runway 23R. There had been no previous coordination from the tower or in the briefing of this unusual operation. I sat down; changed to my preference sets and immediately recognized the error. I instructed aircraft Y to remain on runway heading and turned aircraft X to a 140 heading. I watched both targets and their tracks to see if aircraft Y had turned. It appeared to me that they hadn't. Upon arriving at work today I was informed that traffic analysis and review program (tarp) had gone off and aircraft Y had started a left turn; and I had an operational error. I would like to have the stars equipment offset the leaders from all parallel runways to the direction away from the airport from that runway to eliminate confusion. Side by side departures off runway 23; where the data tags overlap always crisscross; which I have never liked. I would also recommend mandatory coordination for this type of midnight operation.
Original NASA ASRS Text
Title: IND Controller describes a loss of separation due to an aircraft turning later than expected and a midnight shift procedure that runs aircraft close together. Discussion about the direction of leader lines and possible offsets were recommended by the Controller.
Narrative: I just arrived at the position for a morning shift. First transmission of the day; after a relief briefing from the midnight crew. I had two departures; one off Runway 23L and one off 23R Aircraft X off RWY 23L on an assigned heading 210 with a first fix of CVG which is approximately a 140 degree heading; and Aircraft Y off Runway 23R on runway heading; with the MAREO3 departure; a 080 heading; with Aircraft X a couple miles ahead. This is a somewhat common practice on the midnight shift to expedite traffic; with the 23R runway heading departure getting a right turn over the airport to the east. This practice is almost exclusively for [name removed] aircraft only. I turned Aircraft Y left direct MAREO intersection which turned Aircraft Y into Aircraft X's flight path. I had not sat down yet and the preference sets were still from the previous controller; which confused me. We have automatic leader direction changes in our stars equipment here and I made a terrible assumption that Aircraft Y was off Runway 23L; not runway 23R. There had been no previous coordination from the tower or in the briefing of this unusual operation. I sat down; changed to my preference sets and immediately recognized the error. I instructed Aircraft Y to remain on runway heading and turned Aircraft X to a 140 heading. I watched both targets and their tracks to see if Aircraft Y had turned. It appeared to me that they hadn't. Upon arriving at work today I was informed that Traffic Analysis and Review Program (TARP) had gone off and Aircraft Y had started a left turn; and I had an operational error. I would like to have the stars equipment offset the leaders from all parallel runways to the direction away from the airport from that runway to eliminate confusion. Side by side departures off Runway 23; where the data tags overlap always crisscross; which I have never liked. I would also recommend mandatory coordination for this type of midnight operation.
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.