 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLA controller described a TCAS RA event after VFR traffic conflicted with IFR traffic in a busy departure corridor; the reporter claiming sct should not climb VFR into ZLA's airspace without coordination.
| Attributes | |
| ACN | 935236 |
| Time | |
| Date | 201102 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | LAX.Airport |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | PA-46 Malibu/Malibu Mirage/Malibu Matrix |
| Flight Phase | Cruise |
| Flight Plan | VFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
An A320 was climbing out of sct's airspace; 130 and below; into ZLA's sector 21/22's airspace (140-230) when an RA went off with a PA46 who was flying VFR through the departure corridor and had been advised of such. Traffic had been called to the A320 and who had been vectored off of the departure procedure to avoid the PA46; as well as have been given a speed to increase its climb rate through 150; but the RA still went off. The A320's rate of climb seemed to ensure that it would top the PA46; which it did; but the RA happened regardless. Recommendation; sct approach climbs all departures into ZLA's sky; which is an unusual procedure and very unusual at any center. Sct approach could have been made aware of the VFR potential traffic; even though it was outside of their sky so they could give traffic advisories as we did. The VFR traffic could also have been vectored away from the departure corridor; which is unpopular amongst VFR pilots but which would provide a safer situation.
Original NASA ASRS Text
Title: ZLA Controller described a TCAS RA event after VFR traffic conflicted with IFR traffic in a busy departure corridor; the reporter claiming SCT should not climb VFR into ZLA's airspace without coordination.
Narrative: An A320 was climbing out of SCT's airspace; 130 and below; into ZLA's Sector 21/22's airspace (140-230) when an RA went off with a PA46 who was flying VFR through the departure corridor and had been advised of such. Traffic had been called to the A320 and who had been vectored off of the departure procedure to avoid the PA46; as well as have been given a speed to increase its climb rate through 150; but the RA still went off. The A320's rate of climb seemed to ensure that it would top the PA46; which it did; but the RA happened regardless. Recommendation; SCT Approach climbs all departures into ZLA's sky; which is an unusual procedure and very unusual at any center. SCT Approach could have been made aware of the VFR potential traffic; even though it was outside of their sky so they could give traffic advisories as we did. The VFR traffic could also have been vectored away from the departure corridor; which is unpopular amongst VFR pilots but which would provide a safer situation.
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.