 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier departure from las experienced TCAS RA with general aviation traffic at 12;000 ft; reporter alleges ATC failed to provide adequate planning/spacing to prevent the conflict; no FAA record filed.
| Attributes | |
| ACN | 852150 |
| Time | |
| Date | 200909 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | LAS.Airport |
| State Reference | NV |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Cirrus Aircraft Undifferentiated |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Person 2 | |
| Function | Captain Pilot Flying |
| Events | |
| Anomaly | Conflict Airborne Conflict |
| Miss Distance | Horizontal 1500 Vertical 200 |
Narrative:
Climbout on the cowboy departure; assigned radar vectors heading 090; climb to FL190. Vectored at about 8;000 ft to heading 120; maintain 250 KTS. At about 10;000 ft we received a TCAS TA. Located the threat and observed on TCAS at 12;000 ft level; neither one of us could get a visual. At approximately 11;500; we got a RA and the captain (pilot flying) responded with a nose down pushover. I think I saw the TCAS target at +200. We descended about 500 ft and got a 'monitor vertical speed'. During the maneuver ATC (las departure) transmitted 'maintain present altitude; cirrus at 12K'. I responded we were already in a RA descent. We then continued the climb and advised ATC of the near miss. The controller was very busy. However; in hindsight; the vector and airspeed assignment were bad and assured a conflict. The controller never issued an alert or guidance until too late. We never got a visual on the cirrus; due to its size and the sun position. The cirrus never changed altitude; apparently never seeing us either. Our plots were merged on the TCAS. Had we not performed evasive maneuvers per the RA; I'm afraid the outcome might have been very bad. The controller issued a bad vector and failed to monitor traffic.
Original NASA ASRS Text
Title: Air carrier departure from LAS experienced TCAS RA with general aviation traffic at 12;000 FT; Reporter alleges ATC failed to provide adequate planning/spacing to prevent the conflict; no FAA record filed.
Narrative: Climbout on the Cowboy departure; assigned radar vectors heading 090; climb to FL190. Vectored at about 8;000 FT to heading 120; maintain 250 KTS. At about 10;000 FT we received a TCAS TA. Located the threat and observed on TCAS at 12;000 FT level; neither one of us could get a visual. At approximately 11;500; we got a RA and the Captain (pilot flying) responded with a nose down pushover. I think I saw the TCAS target at +200. We descended about 500 FT and got a 'monitor vertical speed'. During the maneuver ATC (Las Departure) transmitted 'maintain present altitude; Cirrus at 12K'. I responded we were already in a RA descent. We then continued the climb and advised ATC of the near miss. The Controller was very busy. However; in hindsight; the vector and airspeed assignment were bad and assured a conflict. The Controller never issued an alert or guidance until too late. We never got a visual on the Cirrus; due to its size and the sun position. The Cirrus never changed altitude; apparently never seeing us either. Our plots were merged on the TCAS. Had we not performed evasive maneuvers per the RA; I'm afraid the outcome might have been very bad. The Controller issued a bad vector and failed to monitor traffic.
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.