Dispatcher report reference aircraft with no TCASII listed on flight plan but responds to TCASII RA....

Attributes
ACN	221049
Time
Date	199209
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : rdu
State Reference	NC
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tower : rdu tracon : bos
Operator	common carrier : air carrier
Make Model Name	Light Transport
Navigation In Use	Other
Flight Phase	descent other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	other personnel
Qualification	other other : other
ASRS Report	221049
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : far other anomaly other other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other

Narrative:

The flight I dispatched was returning to the hub. While on descent (in steps) the TCASII alarm sounded. The aircraft at that time was in the clouds. Even though the basic WX was clear except for isolated cloud banks, the captain decided to deviate from his assigned altitude by approximately 500 ft. After clearing the airspace he returned to his assigned altitude (I agree with his action). When the captain got back to operations there was a message to call the ATC tower. He called me and 3-WAYED the call to ATC. ATC stated there was not TCASII listed on the clearance and the aircraft had it installed. After following up on it, I found out the maintenance control supervisor didn't make an entry into the computer showing TCASII installed, so the computer generated flight plan didn't show the TCASII for ATC. The captain and I both overlooked the error on the release. I also found 7 other entries that were not made on other aircraft. Workload is a main contributor to the problem. Not enough time between flts dispatched to fully view the releases entirely. Not enough time between flts on the ground for the crews to view their releases either.

Original NASA ASRS Text

Title: DISPATCHER RPT REF ACFT WITH NO TCASII LISTED ON FLT PLAN BUT RESPONDS TO TCASII RA. ATC CALLS WITH FOLLOW-UP.

Narrative: THE FLT I DISPATCHED WAS RETURNING TO THE HUB. WHILE ON DSCNT (IN STEPS) THE TCASII ALARM SOUNDED. THE ACFT AT THAT TIME WAS IN THE CLOUDS. EVEN THOUGH THE BASIC WX WAS CLR EXCEPT FOR ISOLATED CLOUD BANKS, THE CAPT DECIDED TO DEVIATE FROM HIS ASSIGNED ALT BY APPROX 500 FT. AFTER CLRING THE AIRSPACE HE RETURNED TO HIS ASSIGNED ALT (I AGREE WITH HIS ACTION). WHEN THE CAPT GOT BACK TO OPS THERE WAS A MESSAGE TO CALL THE ATC TWR. HE CALLED ME AND 3-WAYED THE CALL TO ATC. ATC STATED THERE WAS NOT TCASII LISTED ON THE CLRNC AND THE ACFT HAD IT INSTALLED. AFTER FOLLOWING UP ON IT, I FOUND OUT THE MAINT CTL SUPVR DIDN'T MAKE AN ENTRY INTO THE COMPUTER SHOWING TCASII INSTALLED, SO THE COMPUTER GENERATED FLT PLAN DIDN'T SHOW THE TCASII FOR ATC. THE CAPT AND I BOTH OVERLOOKED THE ERROR ON THE RELEASE. I ALSO FOUND 7 OTHER ENTRIES THAT WERE NOT MADE ON OTHER ACFT. WORKLOAD IS A MAIN CONTRIBUTOR TO THE PROBLEM. NOT ENOUGH TIME BTWN FLTS DISPATCHED TO FULLY VIEW THE RELEASES ENTIRELY. NOT ENOUGH TIME BTWN FLTS ON THE GND FOR THE CREWS TO VIEW THEIR RELEASES EITHER.

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.

Dispatcher report reference aircraft with no TCASII listed on flight plan but responds to TCASII RA. ATC calls with follow-up.