A319 dispatcher did not notify departure load planner of fuel xfer valves inoperative open, that was...

Attributes
ACN	561206
Time
Date	200209
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : den.airport
State Reference	CO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air taxi
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	other personnel
Qualification	other
ASRS Report	561206
Person 2
Affiliation	company : air carrier
Function	other personnel other
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper documentation maintenance problem : non compliance with mel non adherence : published procedure non adherence : far non adherence : company policies
Independent Detector	other other : 1
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Company Maintenance Human Performance Aircraft
Primary Problem	Maintenance Human Performance

Narrative:

While working the flight plan for air carrier flight #XXXX. Aircraft had an MEL that required an alternate type code in the load planner weight manifest due to the both wing tank(south) fuel xfer valves inoperative open. The air carrier procedure calls for the load planner to be notified by the corresponding dispatcher to make the change in the weight manifest. I idented the MEL and associated provisions. During my first attempts to contact load planning, the phone was busy. I attempted to make contact a second time, and again with a result of a busy signal. I made a notation on my work sheet that a call needed to be made. I then proceeded to continue working on additional flts. Eventually, I came to the return portion of the flight from boi to denver. It was at that point that I realized I had not made positive contact with load planning for flight XXXX, denver to boi. I believe the MEL is worded correctly and in such a way to give proper direction. The problem was my inability to make positive contact with someone. A possible preventive measure would be to institute a way to send a hard copy message to the affected station so that in the event of a missed phone call, there would be some back-up to get the message through.

Original NASA ASRS Text

Title: A319 DISPATCHER DID NOT NOTIFY DEP LOAD PLANNER OF FUEL XFER VALVES INOP OPEN, THAT WAS REQUIRED BY THE MEL.

Narrative: WHILE WORKING THE FLT PLAN FOR ACR FLT #XXXX. ACFT HAD AN MEL THAT REQUIRED AN ALTERNATE TYPE CODE IN THE LOAD PLANNER WT MANIFEST DUE TO THE BOTH WING TANK(S) FUEL XFER VALVES INOP OPEN. THE ACR PROC CALLS FOR THE LOAD PLANNER TO BE NOTIFIED BY THE CORRESPONDING DISPATCHER TO MAKE THE CHANGE IN THE WT MANIFEST. I IDENTED THE MEL AND ASSOCIATED PROVISIONS. DURING MY FIRST ATTEMPTS TO CONTACT LOAD PLANNING, THE PHONE WAS BUSY. I ATTEMPTED TO MAKE CONTACT A SECOND TIME, AND AGAIN WITH A RESULT OF A BUSY SIGNAL. I MADE A NOTATION ON MY WORK SHEET THAT A CALL NEEDED TO BE MADE. I THEN PROCEEDED TO CONTINUE WORKING ON ADDITIONAL FLTS. EVENTUALLY, I CAME TO THE RETURN PORTION OF THE FLT FROM BOI TO DENVER. IT WAS AT THAT POINT THAT I REALIZED I HAD NOT MADE POSITIVE CONTACT WITH LOAD PLANNING FOR FLT XXXX, DENVER TO BOI. I BELIEVE THE MEL IS WORDED CORRECTLY AND IN SUCH A WAY TO GIVE PROPER DIRECTION. THE PROB WAS MY INABILITY TO MAKE POSITIVE CONTACT WITH SOMEONE. A POSSIBLE PREVENTIVE MEASURE WOULD BE TO INSTITUTE A WAY TO SEND A HARD COPY MESSAGE TO THE AFFECTED STATION SO THAT IN THE EVENT OF A MISSED PHONE CALL, THERE WOULD BE SOME BACK-UP TO GET THE MESSAGE THROUGH.

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.

A319 dispatcher did not notify departure load planner of fuel xfer valves inoperative open, that was required by the MEL.