37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 869024 |
Time | |
Date | 201001 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Gulfstream IV / G350 / G450 |
Operating Under FAR Part | Part 91 |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Handoff / Assist |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
A PA28; was turned southbound off of the bur localizer for overtaking traffic a B737. A GLF4; departed lax for vny. I transmitted to the GLF4 4 miles south of the airspace boundary and found that he was not on frequency. Both aircraft were at 4;000 and converging. I instructed my assist that we needed to talk to the GLF4 and he initiated a call to the adjacent radar sector. I then issued the traffic to the PA28 at 5 miles apart. During the call my assist asked the other controller to switch that GLF4 and I told him to turn the aircraft. At 3 miles apart the PA28 reported the GLF4 in sight; I instructed the PA28 to maintain visual separation and he agreed; when that transmission ended the aircraft were less than 3 miles apart. When I finally talked to the GLF4 he was inside my airspace. Recommendation; turning the PA28 southbound off of the localizer ended up not being a very farsighted idea; by committing him to south or southwesterly heading; as opposed to southeast; I left myself no room to maneuver when the GLF4 did not check in to the frequency. Also when I advised my assist that we needed to talk to the GLF4 I should have included specific instructions to insure safety.
Original NASA ASRS Text
Title: SCT Controller experienced a loss of separation event between opposite direction traffic at 4;000; listing ill advised issued turns and a late frequency transfer from an adjacent sector as causal factors.
Narrative: A PA28; was turned southbound off of the BUR LOC for overtaking traffic a B737. A GLF4; departed LAX for VNY. I transmitted to the GLF4 4 miles south of the airspace boundary and found that he was not on frequency. Both aircraft were at 4;000 and converging. I instructed my assist that we needed to talk to the GLF4 and he initiated a call to the adjacent RADAR sector. I then issued the traffic to the PA28 at 5 miles apart. During the call my assist asked the other controller to switch that GLF4 and I told him to turn the aircraft. At 3 miles apart the PA28 reported the GLF4 in sight; I instructed the PA28 to maintain visual separation and he agreed; when that transmission ended the aircraft were less than 3 miles apart. When I finally talked to the GLF4 he was inside my airspace. Recommendation; turning the PA28 southbound off of the LOC ended up not being a very farsighted idea; by committing him to south or southwesterly heading; as opposed to southeast; I left myself no room to maneuver when the GLF4 did not check in to the frequency. Also when I advised my assist that we needed to talk to the GLF4 I should have included specific instructions to insure safety.
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.