37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 854982 |
Time | |
Date | 200910 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Component | |
Aircraft Component | Traffic Collision Avoidance System (TCAS) |
Person 1 | |
Function | First Officer Pilot Not Flying |
Experience | Flight Crew Last 90 Days 212 Flight Crew Total 14750 Flight Crew Type 6004 |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 210 Flight Crew Total 18700 Flight Crew Type 5400 |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Critical Conflict Airborne Conflict |
Narrative:
We were passing through 12;400' when our descent clearance was revised to 11;000' for 'traffic at 2-3 o'clock; 10;000.' the target; an airliner; announced they had us in sight. ATC then cleared them to climb to our altitude; 11;000; and maintain visual separation. We then gained visual contact with the traffic. It was clear he would cross in front of us; fairly close by. (His range was decreasing; but as he was not on a constant bearing from us; it was clear we would not actually hit.) ATC queried the traffic; something like; 'how's it looking? You gonna be able to maintain separation' the pilot wasn't sure; and said as much. They were almost at our 12 o'clock; and we would pass just behind them. So; ATC gave them a descent to 10;000' which they started immediately. Just after the descent clearance; we could see the aircraft nose over; his altitude read 10;900' with a downward trend arrow. Just then our TCAS gave an RA; 'descend; crossing; descend' the captain said something to the effect of; 'I'm not doing that. He's descending; we'll descend right into him' and did not follow the TCAS RA. Then; inexplicably; the TCAS RA intensified; still commanding a descent. Well; by then; the jet (clearly in sight; and clearly below us; and clearly descending) was no longer a factor. The captain clicked off the autopilot; initiating a response (even though we knew the TCAS guidance was wrong.) very quickly; 'clear of conflict' sounded. We reported our TCAS RA. I was conflicted about writing this report; but I did want to draw attention to TCAS. The way I see it; had we been in IMC and; therefore; forced to follow TCAS direction; this event would have been alarming! We would have lost what little separation we had; in my opinion. Descending into an airplane that is clearly descending? TCAS software clearly did not give appropriate guidance; nor did it self correct when the initial guidance was so clearly wrong. I lost a bit of faith in TCAS today.
Original NASA ASRS Text
Title: A B757-200 experienced an apparently inappropriate TCAS RA when they encountered an aircraft cleared to climb through their altitude; based on visual separation criteria.
Narrative: We were passing through 12;400' when our descent clearance was revised to 11;000' for 'traffic at 2-3 o'clock; 10;000.' The target; an airliner; announced they had us in sight. ATC then cleared them to climb to our altitude; 11;000; and maintain visual separation. We then gained visual contact with the traffic. It was clear he would cross in front of us; fairly close by. (His range was decreasing; but as he was not on a constant bearing from us; it was clear we would not actually hit.) ATC queried the traffic; something like; 'How's it looking? You gonna be able to maintain separation' The pilot wasn't sure; and said as much. They were almost at our 12 o'clock; and we would pass just behind them. So; ATC gave them a descent to 10;000' which they started immediately. Just after the descent clearance; we could see the aircraft nose over; his altitude read 10;900' with a downward trend arrow. Just then our TCAS gave an RA; 'Descend; crossing; descend' The Captain said something to the effect of; 'I'm not doing that. He's descending; we'll descend right into him' and did not follow the TCAS RA. Then; inexplicably; the TCAS RA intensified; still commanding a descent. Well; by then; the jet (clearly in sight; and clearly below us; and clearly descending) was no longer a factor. The Captain clicked off the autopilot; initiating a response (even though we knew the TCAS guidance was wrong.) Very quickly; 'Clear of conflict' sounded. We reported our TCAS RA. I was conflicted about writing this report; but I DID want to draw attention to TCAS. The way I see it; had we been in IMC and; therefore; forced to follow TCAS direction; this event would have been alarming! We would have lost what little separation we had; in my opinion. Descending into an airplane that is clearly descending? TCAS software clearly did not give appropriate guidance; nor did it self correct when the initial guidance was so clearly wrong. I lost a bit of faith in TCAS today.
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.