 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B767-300; cleared to climb to FL310 received TA and RA advisories triggered by an opposite direction flight.
| Attributes | |
| ACN | 1080259 |
| Time | |
| Date | 201304 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZHU.ARTCC |
| State Reference | TX |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Other Controlled |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Inflight Event / Encounter Other / Unknown |
| Miss Distance | Horizontal 2 Vertical 1000 |
Narrative:
We were cleared to climb to FL310 and were advised of opposite direction traffic while climbing out of FL280 (estimated.) if I recall correctly the traffic was 10 miles away and 1;000 feet above according to ATC. We advised ATC that the traffic was not in sight. We looked for traffic outside at first and then on TCAS but saw nothing either outside or within the 10 mile range we were in at the time. Shortly thereafter we received a 'caution traffic' TA from TCAS. It was at this time we then saw a target 1;000 feet above and outside the 5 NM ring on the TCAS. I then selected vertical speed to reduce our rate of climb to 1;000 FPM. But before I could do so we received a 'level off' command. When the V/south window opened we were very close to FL300 and at FL302 I disengaged the automation and manually leveled the aircraft until we heard the 'clear of conflict' announcement from TCAS. We then continued our climb to FL310 with no further issues. Approximately one minute later we saw the opposite direction traffic. The opposite direction traffic had taken no action and made no mention of the event over the radio. I advised ATC of the TCAS RA level off command; and the controller said 'I am surprised; I am not sure why you received that.' although we corrected our flight path we did not consider our maneuvering evasive.
Original NASA ASRS Text
Title: A B767-300; cleared to climb to FL310 received TA and RA advisories triggered by an opposite direction flight.
Narrative: We were cleared to climb to FL310 and were advised of opposite direction traffic while climbing out of FL280 (estimated.) If I recall correctly the traffic was 10 miles away and 1;000 feet above according to ATC. We advised ATC that the traffic was not in sight. We looked for traffic outside at first and then on TCAS but saw nothing either outside or within the 10 mile range we were in at the time. Shortly thereafter we received a 'caution traffic' TA from TCAS. It was at this time we then saw a target 1;000 feet above and outside the 5 NM ring on the TCAS. I then selected Vertical Speed to reduce our rate of climb to 1;000 FPM. But before I could do so we received a 'LEVEL OFF' command. When the V/S window opened we were very close to FL300 and at FL302 I disengaged the automation and manually leveled the aircraft until we heard the 'clear of conflict' announcement from TCAS. We then continued our climb to FL310 with no further issues. Approximately one minute later we saw the opposite direction traffic. The opposite direction traffic had taken no action and made no mention of the event over the radio. I Advised ATC of the TCAS RA Level Off command; and the Controller said 'I am surprised; I am not sure why you received that.' Although we corrected our flight path we did not consider our maneuvering evasive.
Data retrieved from NASA's ASRS site as of July 2013 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.