Narrative:

Our flight was on a diversion to iad. ATC gave us a descent to FL220. At FL230 we got a TCASII TA from an aircraft below, climbing. At FL225 we got a TCASII RA and took evasive action, climbing to FL230 and changing our heading by 45 degrees left. Once clear of conflict, we returned to our assigned altitude and heading. Center stated he did not know about the conflict. Richmond approach had cleared the other aircraft to climb and center had not taken the handoff. No other actions were taken on our part. The other aircraft passed behind us. How can this be fixed? Approach needs to talk to center! How you could possibly get a TCASII RA at FL220 is unsafe. The FAA ATC facility was not looking out for our safety.

Google
 

Original NASA ASRS Text

Title: MD88 FLC INITIATE EVASIVE TCASII MANEUVER. CONFLICTING ACFT ALLEGEDLY PENETRATING ZDC FROM RIC WITHOUT A HDOF.

Narrative: OUR FLT WAS ON A DIVERSION TO IAD. ATC GAVE US A DSCNT TO FL220. AT FL230 WE GOT A TCASII TA FROM AN ACFT BELOW, CLBING. AT FL225 WE GOT A TCASII RA AND TOOK EVASIVE ACTION, CLBING TO FL230 AND CHANGING OUR HDG BY 45 DEGS L. ONCE CLR OF CONFLICT, WE RETURNED TO OUR ASSIGNED ALT AND HDG. CTR STATED HE DID NOT KNOW ABOUT THE CONFLICT. RICHMOND APCH HAD CLRED THE OTHER ACFT TO CLB AND CTR HAD NOT TAKEN THE HDOF. NO OTHER ACTIONS WERE TAKEN ON OUR PART. THE OTHER ACFT PASSED BEHIND US. HOW CAN THIS BE FIXED? APCH NEEDS TO TALK TO CTR! HOW YOU COULD POSSIBLY GET A TCASII RA AT FL220 IS UNSAFE. THE FAA ATC FACILITY WAS NOT LOOKING OUT FOR OUR SAFETY.

Data retrieved from NASA's ASRS site as of July 2007 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.