MEL restrs not applied to aircraft operating weights due to computer software failure.

Attributes
ACN	427920
Time
Date	199902
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : zzz
State Reference	US
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-200
Flight Phase	ground : parked ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	other personnel
Qualification	other
Person 2
Affiliation	company : air carrier
Function	other personnel other
Qualification	other other : other
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other flight crewa other other : unspecified
Resolutory Action	none taken : detected after the fact other
Consequence	Other
Supplementary
Air Traffic Incident	other

Narrative:

Received my briefing from late night dispatcher. No mention of anti-skid MEL for my aircraft. I calculated the flight plan. The MEL never appeared on the release. I released the flight and had no communication from the crew. I received a call at home from the dispatcher who relieved me. He had received a call from the crew on the next leg of flight. They questioned why the MEL was not on their flight plan. After inquiring with maintenance it was determined that an MEL did exist and should have been on the flight plan. Performance penalties should have been applied and were not because I was unaware of MEL. The crew should have questioned the release, but did not. The next crew lead to our discovery of the computer problem. Our 'maintenance computer' did not send correct information to our new flight plan computer system. (My flight was only one that had a problem.) management was advised and now we have a 'backup' system and we must verify each MEL with maintenance.

Original NASA ASRS Text

Title: MEL RESTRS NOT APPLIED TO ACFT OPERATING WTS DUE TO COMPUTER SOFTWARE FAILURE.

Narrative: RECEIVED MY BRIEFING FROM LATE NIGHT DISPATCHER. NO MENTION OF ANTI-SKID MEL FOR MY ACFT. I CALCULATED THE FLT PLAN. THE MEL NEVER APPEARED ON THE RELEASE. I RELEASED THE FLT AND HAD NO COM FROM THE CREW. I RECEIVED A CALL AT HOME FROM THE DISPATCHER WHO RELIEVED ME. HE HAD RECEIVED A CALL FROM THE CREW ON THE NEXT LEG OF FLT. THEY QUESTIONED WHY THE MEL WAS NOT ON THEIR FLT PLAN. AFTER INQUIRING WITH MAINT IT WAS DETERMINED THAT AN MEL DID EXIST AND SHOULD HAVE BEEN ON THE FLT PLAN. PERFORMANCE PENALTIES SHOULD HAVE BEEN APPLIED AND WERE NOT BECAUSE I WAS UNAWARE OF MEL. THE CREW SHOULD HAVE QUESTIONED THE RELEASE, BUT DID NOT. THE NEXT CREW LEAD TO OUR DISCOVERY OF THE COMPUTER PROB. OUR 'MAINT COMPUTER' DID NOT SEND CORRECT INFO TO OUR NEW FLT PLAN COMPUTER SYS. (MY FLT WAS ONLY ONE THAT HAD A PROB.) MGMNT WAS ADVISED AND NOW WE HAVE A 'BACKUP' SYS AND WE MUST VERIFY EACH MEL WITH MAINT.

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.