Narrative:

[We were] tracking a 202 course toward the rosewood (rod) VOR. Cleveland center had cleared us to climb and maintain fl 300. We were climbing approximately 800 FPM with the autopilot on. Between fl 250 and 260; we received a TCAS TA for a target at our 1 o'clock and slightly above. We were attempting establish visual contact when we received a 3000 FPM 'climb! Climb!' resolution advisory (RA) for a second target 100 feet below us with little lateral separation. I commanded 'pull-up' as the first officer (first officer) disconnected the autopilot and smartly complied with the RA. The RA cleared within ten seconds. We did not receive a 'clear of conflict' TCAS message. The targets simply disappeared from the TCAS display. I notified cleveland center that we had complied with a TCAS RA and were continuing to FL300. The center controller apologized; stating that the conflicting traffic was a flight of F-16 fighters leveling-off at fl 250; and that he wasn't sure what had happened. Upon deplaning several passengers volunteered that they had seen 'jets' through their windows at the time of the incident. The first target was 200 feet above us; the second was 100 feet below. The first officer remarked later that he had been uncomfortable complying with the 'climb!' RA since he knew there was an aircraft above us. I assured him that he had taken the correct course of action because the lower aircraft was closer to us. Given the characteristics of the general dynamics F-16 fighting falcon; I speculate that while we were unable to establish visual contact with them; they probably saw us. Conflict resulted from either a miscalculation by ATC or the military traffic's failure to level at their assigned altitude. I don't believe there is much we could have done to prevent this.

Google
 

Original NASA ASRS Text

Title: CRJ-200 Captain climbing to FL300 experiences a TCAS RA requiring a 3;000 FPM climb rate which the flying First Officer complies with. ATC advises that the traffic was two F-16's but with no explanation for the conflict.

Narrative: [We were] tracking a 202 course toward the Rosewood (ROD) VOR. Cleveland Center had cleared us to climb and maintain FL 300. We were climbing approximately 800 FPM with the autopilot on. Between FL 250 and 260; we received a TCAS TA for a target at our 1 o'clock and slightly above. We were attempting establish visual contact when we received a 3000 FPM 'Climb! Climb!' resolution advisory (RA) for a second target 100 feet below us with little lateral separation. I commanded 'pull-up' as the First Officer (FO) disconnected the autopilot and smartly complied with the RA. The RA cleared within ten seconds. We did not receive a 'clear of conflict' TCAS message. The targets simply disappeared from the TCAS display. I notified Cleveland Center that we had complied with a TCAS RA and were continuing to FL300. The Center controller apologized; stating that the conflicting traffic was a flight of F-16 fighters leveling-off at FL 250; and that he wasn't sure what had happened. Upon deplaning several passengers volunteered that they had seen 'jets' through their windows at the time of the incident. The first target was 200 feet above us; the second was 100 feet below. The FO remarked later that he had been uncomfortable complying with the 'Climb!' RA since he knew there was an aircraft above us. I assured him that he had taken the correct course of action because the lower aircraft was closer to us. Given the characteristics of the General Dynamics F-16 Fighting Falcon; I speculate that while we were unable to establish visual contact with them; THEY probably saw US. Conflict resulted from either a miscalculation by ATC or the military traffic's failure to level at their assigned altitude. I don't believe there is much we could have done to prevent this.

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