37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1343479 |
Time | |
Date | 201603 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | MCO.Airport |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | Deviation - Procedural Weight And Balance Deviation - Procedural Published Material / Policy |
Narrative:
Our aircraft departed with a serious weight and balance discrepancy that could have resulted in a serious aircraft accident if at another airport or with a shorter runway. During final weight and balance inputs; I failed to properly confirm my first officer's inputs which resulted in a large error of passenger inputs. Our load manifest matched up with the final weight and balance copy; and as usual I performed the fuel reliability check and started making my welcome aboard PA. At this point; my first officer incorrectly entered 000/67 in cabin a; when in fact it should have been 67 in cabin a; and 89 in cabin B. The total passengers should have been 156. Instead; we only inputted 67 half weights. This resulted in a weight difference of 26;800 pounds under planned! Unfortunately; I completely failed in my duties to confirm his inputs as it gave me a weight and balance (wb) solution with flaps 1; which we were anticipating. The incorrect solution was auto-uplinked; and we proceeded as normal. This was a grave error; and I fully realize the devastating consequences that could have happened had we not had a 10;000 runway in good weather. On departure; we got a mcdu scratchpad message saying 'check weight.' I then looked at our printed out copy of the first page of our wb solution and discovered the serious error. I then corrected our zero fuel weight (ZFW) to the planned ZFW to achieve proper speeds for cruise and landing.this event could have easily been prevented by verifying the final inputs on the weight and balance. I failed in my duties to verify my first officer's inputs. Unfortunately; we rushed through the process even though we were 5 minutes early. Complacency was definitely a factor as I have never seen this issue and have been flying the aircraft for a very long time. My previous four day was flown with my first officer and I found him to be exceptionally bright and competent as he has been here a little under 2 years with an impressive aviation carrier and experience. I was lulled into complacency by getting a weight and balance solution with a flaps 1 takeoff (to)/flex (which was anticipated). I became distracted with other duties (fuel reliability; welcome aboard PA; verifying passenger counts on final wb with passenger load sheet; and confirming the passenger count with the a flight attendant); and failed to confirm the final wb inputs. Unfortunately; I trusted without verifying.this is why there are two of us; and I failed in my duties. This also happened in day VMC at our home base airport. Complacency was once again a factor. I'm much more cognizant of weight and balance at [other] airports. Needless to say; this is an error that will not be repeated on either of our ends.this could have been prevented in two ways. Verify the final weight and balance inputs. This procedure is already in place. Do not allow a weight and balance solution with a margin of error so high. We got a solution; albeit a grossly egregious one. We uplinked the solution and got an [anticipated] flaps 1/flex to numbers.
Original NASA ASRS Text
Title: An A320 flight crew reported departing with a large (26;800 lbs) self-induced error in weight and balance calculations.
Narrative: Our aircraft departed with a serious weight and balance discrepancy that could have resulted in a serious aircraft accident if at another airport or with a shorter runway. During final weight and balance inputs; I failed to properly confirm my First Officer's inputs which resulted in a large error of passenger inputs. Our load manifest matched up with the final weight and balance copy; and as usual I performed the fuel reliability check and started making my welcome aboard PA. At this point; my First Officer incorrectly entered 000/67 in Cabin A; when in fact it should have been 67 in Cabin A; and 89 in Cabin B. The total passengers should have been 156. Instead; we only inputted 67 half weights. This resulted in a weight difference of 26;800 pounds under planned! Unfortunately; I completely failed in my duties to confirm his inputs as it gave me a Weight and Balance (WB) solution with Flaps 1; which we were anticipating. The incorrect solution was auto-uplinked; and we proceeded as normal. This was a grave error; and I fully realize the devastating consequences that could have happened had we not had a 10;000 runway in good weather. On departure; we got a MCDU scratchpad message saying 'Check Weight.' I then looked at our printed out copy of the first page of our WB solution and discovered the serious error. I then corrected our Zero Fuel Weight (ZFW) to the planned ZFW to achieve proper speeds for cruise and landing.This event could have easily been prevented by verifying the final inputs on the Weight and Balance. I failed in my duties to verify my First Officer's inputs. Unfortunately; we rushed through the process even though we were 5 minutes early. Complacency was definitely a factor as I have never seen this issue and have been flying the aircraft for a very long time. My previous four day was flown with my First Officer and I found him to be exceptionally bright and competent as he has been here a little under 2 years with an impressive aviation carrier and experience. I was lulled into complacency by getting a weight and balance solution with a Flaps 1 Takeoff (TO)/Flex (which was anticipated). I became distracted with other duties (Fuel reliability; Welcome aboard PA; verifying passenger counts on final WB with passenger load sheet; and confirming the passenger count with the A flight attendant); and failed to confirm the final WB inputs. Unfortunately; I trusted without verifying.This is why there are two of us; and I failed in my duties. This also happened in day VMC at our home base airport. Complacency was once again a factor. I'm much more cognizant of weight and balance at [other] airports. Needless to say; this is an error that will not be repeated on either of our ends.This could have been prevented in two ways. Verify the final weight and balance inputs. This procedure is already in place. Do not allow a weight and balance solution with a margin of error so high. We got a solution; albeit a grossly egregious one. We uplinked the solution and got an [anticipated] Flaps 1/Flex TO numbers.
Data retrieved from NASA's ASRS site 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.