AN A319 WAS SLUGGISH ON TKOF; CLB AND AT CRUISE. FLT CREW CALCULATED THE ACFT TO BE OVERWT BY 8500 LBS. ACFT EXCEEDED BOTH MGTOW AND MAX LANDING WT.

Date: 2007-12 · Aircraft: A319

Anomalies: deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy

Synopsis

AN A319 WAS SLUGGISH ON TKOF; CLB AND AT CRUISE. FLT CREW CALCULATED THE ACFT TO BE OVERWT BY 8500 LBS. ACFT EXCEEDED BOTH MGTOW AND MAX LANDING WT.

Narrative

INFLT; WE DISCOVERED A DISCREPANCY BTWN WT AND BAL WT; AND FLT AUGMENTATION COMPUTER (FAC) CALCULATED WT OF AROUND 8500 LBS. WE ATTEMPTED TO RESOLVE THE DISCREPANCY; AND FORMULATE A PLAN OF ACTION WITH DISPATCH AND MAINT; BUT WERE UNSUCCESSFUL. WE LANDED IN ZZZ2; POSSIBLY OVERWT; WHICH WOULD MEAN THAT WE WERE ALSO OVERWT ON TKOF FROM ZZZ1. WHILE IN CRUISE AT FL370; THE FO WAS SUSPICIOUS OF THE ACFT PERFORMANCE DURING THE LAST STEP CLB; AND THEN REMEMBERED THAT AFTER TKOF; THE TRIM SEEMED TO BE WAY OUT. HE ENTERED AIDS IN THE MCDU; AND ENTERED THE ALPHA PARAMETER CALL-UP GWFL. BOTH FAC'S INDICATED CALCULATED WTS APPROX 8500 LBS HEAVIER THAN OUR WT AND BAL MCDU WT. THE FACT THAT BOTH FAC'S WERE IN AGREEMENT; AND THE AIRPLANE FELT VERY SLUGGISH; WE CONCURRED THAT THE ACFT WAS POSSIBLY OVERWT ON TKOF; AND WOULD ALSO BE OVERWT ON LNDG. OUR WT AND BAL MCDU WT ON LNDG WAS 133.0 LBS; AND FAC CALCULATED WT WAS APPROX 141.5 LBS. AGAIN; WE DID NOT KNOW FOR SURE THAT THE ACFT WAS OVERWT; BUT SUSPECTED THAT WAS THE CASE. WE SENT SEVERAL ACARS MESSAGES TO DISPATCH AND MAINT IN HOPES THAT THEY WOULD INVESTIGATE AND COORD WITH LOAD PLANNING AND MAINT TO DETERMINE THE ACTUAL WT. MAINT NEVER DID RESPOND; AND I DON'T THINK DISPATCH EVER UNDERSTOOD THE SITUATION; DESPITE SEVERAL LENGTHY AND DETAILED MESSAGES. DISPATCH ASKED AT LEAST TWICE HOW MUCH OVERWT WE WOULD BE ON LNDG. THIS LACK OF SUPPORT AND COORD CONSTITUTES A COMS FAILURE. WITH THE LACK OF RESPONSE AFTER REQUESTING OPERATIONAL (DISPATCH; MAINT; LOAD PLANNING; ETC) INPUT TO FORMULATE A PLAN OF ACTION; WE WEIGHED THE OPTIONS; CONSIDERED THE WX; AND THE FACT THAT WE STILL DID NOT KNOW FOR SURE IF WE WERE OVERWT OR NOT; AND DECIDED THE SAFEST COURSE OF ACTION WOULD BE TO LAND AS PLANNED IN ZZZ2. TO HELP MITIGATE ANY INCREASED RISK (JUST IN CASE WE WERE OVERWT); WE FOLLOWED THE QRH OVERWT LNDG PROCS. THERE WERE SEVERAL OTHER CONSIDERATIONS IN PLAY; PRIMARILY WX; AVAILABLE ALTERNATES; AND FUEL. HAD WE NOT HELD FOR BOUT 40 MINS; WE WOULD HAVE BEEN ANOTHER 4000 LBS HEAVIER ON LNDG. WHILE WE WERE HOLDING; AFTER SENDING SEVERAL MESSAGES TO DISPATCH (ASKING FOR A CLOSER ALTERNATE THAN ZZZ3); WITHOUT RESPONSE; WE FINALLY SENT A NOTICE OF 10 MINS HOLD FUEL REMAINING (SNOW PLOW STUCK ON THE RWY); THEN 5 MINS HOLD FUEL REMAINING UNTIL DIVERSION; AND ONLY THEN DID WE GET AN ACARS FROM DISPATCH SAYING THAT THERE HAD BEEN A SHIFT CHANGE AND THAT HE WAS NOW WORKING ON A CLOSER ALTERNATE. WITH ABOUT 2 MINS REMAINING; OUR ALTERNATE WAS CHANGED; WHICH ALLOWED THE NEEDED MINS TO LAND IN ZZZ2. WE GENERATED A LOAD RPT FOR MAINT TO DOCUMENT THE POSSIBLE OVERWT LNDG; MADE A LOGBOOK ENTRY; AND WHEN TALKING TO MAINT AT THE GATE; HE INDICATED THAT HE HAD ONLY 1 PREVIOUS MESSAGE CONCERNING THE PROB. THERE WAS ZERO SUPPORT DURING THIS INFLT INCIDENT; AND IT APPEARS NO ACTION HAD BEEN TAKEN BY ANYONE ON THE GND.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.