 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An A319 captain recounts a number of controller errors which contributed to a loss of separation and a TCAS RA.
| Attributes | |
| ACN | 911406 |
| Time | |
| Date | 201009 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZOA.ARTCC |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance |
Narrative:
ATC requested an expedited climb through 13;000 ft to clear traffic. Leaving approximately 11;500 ft ATC issued a right turn for traffic but used the wrong call sign immediately followed by a TCAS RA descend command. Pilot not flying (first officer) advised ATC we were descending to comply with the RA and they requested we not descend to avoid another target below us. Pilot not flying saw original target aircraft pass just above and to the right. TCAS reported 'clear of conflict' as both target passed behind our flight. ATC then cleared us back on course but issued the wrong fix requiring confirmation.a few minutes later ATC issued a frequency change but; once again; used the incorrect call sign requiring verification. No safety alert was issued by ATC during the event.to recount; ATC recognized the threat of the traffic but failed to ensure adequate separation. ATC further requested we ignore the TCAS RA. ATC must emphasize proper action; including the requirement for timeliness; when a traffic conflict is identified.
Original NASA ASRS Text
Title: An A319 Captain recounts a number of Controller errors which contributed to a loss of separation and a TCAS RA.
Narrative: ATC requested an expedited climb through 13;000 FT to clear traffic. Leaving approximately 11;500 FT ATC issued a right turn for traffic but used the wrong call sign immediately followed by a TCAS RA Descend command. Pilot not flying (First Officer) advised ATC we were descending to comply with the RA and they requested we not descend to avoid another target below us. Pilot not flying saw original target aircraft pass just above and to the right. TCAS reported 'Clear of Conflict' as both target passed behind our flight. ATC then cleared us back on course but issued the wrong fix requiring confirmation.A few minutes later ATC issued a frequency change but; once again; used the incorrect call sign requiring verification. No Safety Alert was issued by ATC during the event.To recount; ATC recognized the threat of the traffic but failed to ensure adequate separation. ATC further requested we ignore the TCAS RA. ATC must emphasize proper action; including the requirement for timeliness; when a traffic conflict is identified.
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.