37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1665901 |
Time | |
Date | 201907 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | Final Approach |
Flight Plan | None |
Person 1 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 8 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC |
Narrative:
Aircraft X released off lgb airport by manhattan/laker combined sector; training in progress. I was working the controller in charge position; when the trainer working position advised me of a possible situation in progress. I observed the trainee/trainer issuing a safety/traffic alert to the departing IFR aircraft and observed opposite direction traffic at co-altitude. Once the situation had been resolved I felt the situation appeared to be a near midair collision and was unaware of traffic being issued by the tower. I contacted lgb tower to figure out if they had issued traffic and were doing anything to ensure separation. The lgb controller didn't seem to be aware there was even a situation and didn't seem to care that we and pilots in control of both aircraft had to take evasive action; after further communication with the departing aircraft we determined no traffic was issued to the IFR aircraft prior to transfer of communication despite the unsafe situation. I have still not been made aware of any traffic issued to the other aircraft that lgb tower was in communication with but it did appear that aircraft also took evasive action and turned hard south to avoid collision while our departing IFR aircraft turned north west.lgb tower control needs to maintain communication with both aircraft and issue and resolve any conflicts prior to transferring communications. I feel the tower controller needs immediate remedial training and be explained duty priority; then be able to demonstrate this ability before being returned to active duty.
Original NASA ASRS Text
Title: SCT TRACON Controller reported an unsafe situation with traffic off of LGB and traffic inbound to LGB.
Narrative: Aircraft X released off LGB airport by Manhattan/Laker combined sector; training in progress. I was working the Controller in Charge position; when the trainer working position advised me of a possible situation in progress. I observed the trainee/trainer issuing a safety/traffic alert to the departing IFR aircraft and observed opposite direction traffic at co-altitude. Once the situation had been resolved I felt the situation appeared to be a near midair collision and was unaware of traffic being issued by the tower. I contacted LGB Tower to figure out if they had issued traffic and were doing anything to ensure separation. The LGB Controller didn't seem to be aware there was even a situation and didn't seem to care that we and pilots in control of both aircraft had to take evasive action; after further communication with the departing aircraft we determined no traffic was issued to the IFR aircraft prior to transfer of communication despite the unsafe situation. I have still not been made aware of any traffic issued to the other aircraft that LGB Tower was in communication with but it did appear that aircraft also took evasive action and turned hard south to avoid collision while our departing IFR aircraft turned north west.LGB Tower Control needs to maintain communication with both aircraft and issue and resolve any conflicts prior to transferring communications. I feel the Tower Controller needs immediate remedial training and be explained duty priority; then be able to demonstrate this ability before being returned to active duty.
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.