Narrative:

Following departure from langley AFB (klfi) en route to melbourne, fl (kmlb) on an IFR flight plan, a TCASII alert was called by another aircraft which I believe to have had in visual contact at the time. My aircraft, a military heavy transport, was not equipped with TCASII so there was no TCASII alert in my aircraft. However, the other aircraft, most probably the one I had visual contact with, did report a TCASII alert to ZDC and asked the altitude of the aircraft (most probably my aircraft). He had the alert on. At the time of occurrence, my aircraft was heading 290 degrees tracking the norfolk 290 degree radial outbound and at an assigned altitude of FL260 during an intermediate level off in what can best be described as a step climb by center en route to a final altitude of FL350. ZDC was fairly busy at the time, as evidenced by VHF radio chatter and restr climb steps of 1000 ft. Just after leveling off at FL260, my indicated altitude increased to approximately 26150 ft due to an inoperative altitude hold feature of the autoplt and an unqualified military pilot at the controls. I was in the process of descending from the 150 ft high indicated altitude back down to precisely FL260, when I had visual contact with another aircraft at my 9 O'clock position, heading north, approximately 1000 ft above. The other aircraft passed above and behind my aircraft when I heard the radio conversation from an aircraft asking ZDC about altitude separation and stating he had a TCASII alert. All 3 altimeters aboard my aircraft (pilot's, copilot's and navigator's) were properly set at 29.92 and the #1 IFF was operational and selected. The #1 CADC was also operational and selected to report the pilot's altimeter which was being flown as primary and being reported.

Google
 

Original NASA ASRS Text

Title: MIL PLT NOT TCASII EQUIPPED HEARS CONVERSATION REF TCASII ALERT FROM ANOTHER ACFT. BELIEVES HE IS THE 'INTRUDER.'

Narrative: FOLLOWING DEP FROM LANGLEY AFB (KLFI) ENRTE TO MELBOURNE, FL (KMLB) ON AN IFR FLT PLAN, A TCASII ALERT WAS CALLED BY ANOTHER ACFT WHICH I BELIEVE TO HAVE HAD IN VISUAL CONTACT AT THE TIME. MY ACFT, A MIL HVT, WAS NOT EQUIPPED WITH TCASII SO THERE WAS NO TCASII ALERT IN MY ACFT. HOWEVER, THE OTHER ACFT, MOST PROBABLY THE ONE I HAD VISUAL CONTACT WITH, DID RPT A TCASII ALERT TO ZDC AND ASKED THE ALT OF THE ACFT (MOST PROBABLY MY ACFT). HE HAD THE ALERT ON. AT THE TIME OF OCCURRENCE, MY ACFT WAS HDG 290 DEGS TRACKING THE NORFOLK 290 DEG RADIAL OUTBOUND AND AT AN ASSIGNED ALT OF FL260 DURING AN INTERMEDIATE LEVEL OFF IN WHAT CAN BEST BE DESCRIBED AS A STEP CLB BY CTR ENRTE TO A FINAL ALT OF FL350. ZDC WAS FAIRLY BUSY AT THE TIME, AS EVIDENCED BY VHF RADIO CHATTER AND RESTR CLB STEPS OF 1000 FT. JUST AFTER LEVELING OFF AT FL260, MY INDICATED ALT INCREASED TO APPROX 26150 FT DUE TO AN INOP ALT HOLD FEATURE OF THE AUTOPLT AND AN UNQUALIFIED MIL PLT AT THE CTLS. I WAS IN THE PROCESS OF DSNDING FROM THE 150 FT HIGH INDICATED ALT BACK DOWN TO PRECISELY FL260, WHEN I HAD VISUAL CONTACT WITH ANOTHER ACFT AT MY 9 O'CLOCK POS, HDG N, APPROX 1000 FT ABOVE. THE OTHER ACFT PASSED ABOVE AND BEHIND MY ACFT WHEN I HEARD THE RADIO CONVERSATION FROM AN ACFT ASKING ZDC ABOUT ALT SEPARATION AND STATING HE HAD A TCASII ALERT. ALL 3 ALTIMETERS ABOARD MY ACFT (PLT'S, COPLT'S AND NAVIGATOR'S) WERE PROPERLY SET AT 29.92 AND THE #1 IFF WAS OPERATIONAL AND SELECTED. THE #1 CADC WAS ALSO OPERATIONAL AND SELECTED TO RPT THE PLT'S ALTIMETER WHICH WAS BEING FLOWN AS PRIMARY AND BEING RPTED.

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.