37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1441548 |
Time | |
Date | 201704 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | SNA.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Helicopter |
Flight Phase | Cruise |
Route In Use | None |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Citation II S2/Bravo (C550) |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was on a control position for nearly an hour and 45 minutes then was told by the controller in charge (controller in charge) to take over his position. I now was controller in charge after a busy session on radar. I went around the room and made sure traffic was not an issue for the controllers. I asked the controller on tustin if he was ok or needed a handoff or spacing from the traffic management unit (tmu) because and average amount of IFR traffic was coming in. He declined. After about 10 min I heard this controller make comments that alerted me to a problem. When I went to the sector I noticed the citation making a left turn into an MVA and alerted the controller to it. I asked what was wrong and he said some issue with a VFR military helo not communicating near his arrival final to sna. At that point I alerted him to another IFR arrival on final nearing the VFR helo; he tried to take action to turn the aircraft. He then said the citation had an RA. I am not sure if the other aircraft involved had RA.staffing problems and no supervisors when needed. Controller should have asked for help earlier or resolved the potential conflict earlier before it became complex. Don't take a controller who has already been on a busy position off that one and make them controller in charge or to another position for that matter.
Original NASA ASRS Text
Title: SCT TRACON Controller in Charge reported that another Controller was having separation problems with aircraft; was asked if the needed help and Controller denied help. Reporter stated staffing issues and no Supervisor in the area at the time.
Narrative: I was on a control position for nearly an hour and 45 minutes then was told by the Controller in Charge (CIC) to take over his position. I now was CIC after a busy session on RADAR. I went around the room and made sure traffic was not an issue for the controllers. I asked the controller on Tustin if he was ok or needed a handoff or spacing from the Traffic Management Unit (TMU) because and average amount of IFR traffic was coming in. He declined. After about 10 min I heard this controller make comments that alerted me to a problem. When I went to the sector I noticed the Citation making a left turn into an MVA and alerted the controller to it. I asked what was wrong and he said some issue with a VFR military helo not communicating near his arrival final to SNA. At that point I alerted him to another IFR arrival on final nearing the VFR helo; he tried to take action to turn the aircraft. He then said the Citation had an RA. I am not sure if the other aircraft involved had RA.Staffing problems and no supervisors when needed. Controller should have asked for help earlier or resolved the potential conflict earlier before it became complex. Don't take a controller who has already been on a busy position off that one and make them CIC or to another position for that matter.
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.