37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 845685 |
Time | |
Date | 200907 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Route In Use | Direct |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Military 3 Air Traffic Control Non Radar 0 Air Traffic Control Radar 20 Air Traffic Control Supervisory 0 Air Traffic Control Time Certified In Pos 1 (mon) 6 Air Traffic Control Time Certified In Pos 1 (yrs) 18 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Miss Distance | Horizontal 5000 Vertical 500 |
Narrative:
I had cleared aircraft 2 for an ILS runway 05 at ZZZ airport. While I was involved with unrelated coordination; the flight data position requested a release off of runway 23 at ZZZ. Without even thinking about it; I told him to let the aircraft go on course. I did not realize I had made an error until flight data released the departure and put the strip in front of me. By this time; the arrival was on advisory frequency. After a moment of initial panic; I instructed the controller in charge to get on a tunable radio and contact the arrival on advisory frequency. He was able to cancel the approach clearance and issue alternate instructions; but not before separation was lost. While I take full responsibility for the error; if I had been working the data position; I would not even have asked the radar controller for a release in this situation. I believe the massive influx of newer; inexperienced controllers is impacting the system nationwide.
Original NASA ASRS Text
Title: Arrival Controller experiences operational error when releasing a departure in conflict with an arrival.
Narrative: I had cleared aircraft 2 for an ILS RWY 05 at ZZZ airport. While I was involved with unrelated coordination; the flight data position requested a release off of RWY 23 at ZZZ. Without even thinking about it; I told him to let the aircraft go on course. I did not realize I had made an error until flight data released the departure and put the strip in front of me. By this time; the arrival was on advisory frequency. After a moment of initial panic; I instructed the CIC to get on a tunable radio and contact the arrival on advisory frequency. He was able to cancel the approach clearance and issue alternate instructions; but not before separation was lost. While I take full responsibility for the error; if I had been working the data position; I would not even have asked the RADAR controller for a release in this situation. I believe the massive influx of newer; inexperienced controllers is impacting the system nationwide.
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.