37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1620620 |
Time | |
Date | 201902 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | GRR.Airport |
State Reference | MI |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Departure Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
I was working south arrival radar; we were landing and departing 8R and 17 (crossing runways). Departures climb to 040; arrivals descend to 050 until they pass the tower's departure pie. I had aircraft Y on a right downwind heading from the southeast to land 8R; level at 050. Local told me he had a departure (aircraft X) rolling on rwy 17; and wanted to know if he should leave him runway heading or turn him southwest-bound towards his first fix. I did not realize he was departing 17; thinking he was departing 8R; the same one I was vectoring toward. I told him to leave him runway heading. Then I asked the tower if I could descend aircraft Y; the tower approved the request; and I descended aircraft Y to 030. Then aircraft X's target popped up south of the field; and I realized he was departing runway 17; and the two jets were on a collision course; with aircraft X climbing to 040; through aircraft Y's altitude of 030. Traffic was issued; both jets had traffic in sight and were instructed to maintain visual separation. Both aircraft received ras (resolution advisories) and luckily responded to those.listen to the coordination.
Original NASA ASRS Text
Title: Grand Rapids Radar Controller reported a loss of separation when a departure and arrival were at incorrect altitudes to maintain required separation standards.
Narrative: I was working South Arrival Radar; we were landing and departing 8R and 17 (crossing runways). Departures climb to 040; arrivals descend to 050 until they pass the Tower's departure pie. I had Aircraft Y on a right downwind heading from the southeast to land 8R; level at 050. Local told me he had a departure (Aircraft X) rolling on Rwy 17; and wanted to know if he should leave him runway heading or turn him southwest-bound towards his first fix. I did not realize he was departing 17; thinking he was departing 8R; the same one I was vectoring toward. I told him to leave him runway heading. Then I asked the Tower if I could descend Aircraft Y; the Tower approved the request; and I descended Aircraft Y to 030. Then Aircraft X's target popped up south of the field; and I realized he was departing RWY 17; and the two jets were on a collision course; with Aircraft X climbing to 040; through Aircraft Y's altitude of 030. Traffic was issued; both jets had traffic in sight and were instructed to maintain visual separation. Both aircraft received RAs (resolution advisories) and luckily responded to those.Listen to the coordination.
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.