37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 742390 |
Time | |
Date | 200706 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : iad.airport |
State Reference | DC |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 230 flight time total : 5500 flight time type : 2850 |
ASRS Report | 742390 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 170 flight time total : 14020 flight time type : 1100 |
ASRS Report | 742383 |
Events | |
Anomaly | non adherence : company policies non adherence : published procedure |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Company Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
When we arrived at the gate for the flight; we were told that all flts were on hold due to a suspicious bag in the scanner in the bag room. No bags were being moved nor passenger loaded until they could clear the bag. Then we were told to wait for connecting passenger. After bout 1 hour 45 mints; we were cleared to go without an unknown number of the bags. In the meantime; we received our weights over the ACARS printer and I noted that the new weight was 25K lower than the planned weight (red flag #1). I told the captain this and was concerned because we were getting conflicting information about how many bags; connecting passenger; and cargo we would leave behind. As we start to prepare to push back; I sent for new ATIS and runway data. The runway data still had the 'P' for planned by the weight (red flag #2) and I announced this but I don't think the captain heard me. Right when this was transpiring; the purser came into the cockpit to tell us that we had 1 more passenger than seats. The captain instructed me to call operations to get the jetway bridge back and went back to see what the problem was. After we got the extra passenger off; we pushed and taxied quickly because we were so late. It should be noted that we were on day 4 of a 4-DAY and had gone over 8 hours of flying due to operational delays on day 1 and day 3. I was; therefore; tired and somewhat fatigued (woke up early every day) which dulled my senses and eye for detail. On the taxi out during the checklist; I mumbled to myself that I should contact load planning as I didn't get the 2 previous red flags resolved. However; the taxi was short and tower cleared us to take off. Since it was my leg; on the takeoff roll I announced that; 'I don't trust the weights; I'm going to add some KTS and rotate slowly.' in my mind I was going to rotate at the original planned vr of about 140 KTS and watch out for a mistrimmed aircraft. The airplane flew fine and some nose-up trim was needed for balanced flight after liftoff. A few mins after we did the 'after takeoff' checklist the captain noticed a printout on the ACARS printer which was in fact our actual weights. Upon further examination; the first weights were actually for a different flight. The flight was for one we did the day prior in the same type of aircraft. Lesson learned: I always assumed that what came over ACARS could only be for the correct flight so I didn't have the habit of checking the flight number and city pair. I will now! I got too rushed and never stopped the operation to satisfy my concern over the red flags when I could have done so. I also did not clearly articulate my concerns to the captain. This was not due to an inability to speak up because I am usually very vocal and do not hesitate; but rather from being tired and not up to my usual performance. Programming of load planning ACARS messages should never be allowed to go to the wrong aircraft and certainly not on the wrong date and city pair. It also should break out cargo and bags loads for more clarity to the crews.
Original NASA ASRS Text
Title: B767-300 FLT CREW REALIZED AFTER TKOF THAT THEY HAD DEPARTED WITH INCORRECT PERFORMANCE DATA.
Narrative: WHEN WE ARRIVED AT THE GATE FOR THE FLT; WE WERE TOLD THAT ALL FLTS WERE ON HOLD DUE TO A SUSPICIOUS BAG IN THE SCANNER IN THE BAG ROOM. NO BAGS WERE BEING MOVED NOR PAX LOADED UNTIL THEY COULD CLR THE BAG. THEN WE WERE TOLD TO WAIT FOR CONNECTING PAX. AFTER BOUT 1 HR 45 MINTS; WE WERE CLRED TO GO WITHOUT AN UNKNOWN NUMBER OF THE BAGS. IN THE MEANTIME; WE RECEIVED OUR WTS OVER THE ACARS PRINTER AND I NOTED THAT THE NEW WT WAS 25K LOWER THAN THE PLANNED WT (RED FLAG #1). I TOLD THE CAPT THIS AND WAS CONCERNED BECAUSE WE WERE GETTING CONFLICTING INFO ABOUT HOW MANY BAGS; CONNECTING PAX; AND CARGO WE WOULD LEAVE BEHIND. AS WE START TO PREPARE TO PUSH BACK; I SENT FOR NEW ATIS AND RWY DATA. THE RWY DATA STILL HAD THE 'P' FOR PLANNED BY THE WT (RED FLAG #2) AND I ANNOUNCED THIS BUT I DON'T THINK THE CAPT HEARD ME. RIGHT WHEN THIS WAS TRANSPIRING; THE PURSER CAME INTO THE COCKPIT TO TELL US THAT WE HAD 1 MORE PAX THAN SEATS. THE CAPT INSTRUCTED ME TO CALL OPS TO GET THE JETWAY BRIDGE BACK AND WENT BACK TO SEE WHAT THE PROB WAS. AFTER WE GOT THE EXTRA PAX OFF; WE PUSHED AND TAXIED QUICKLY BECAUSE WE WERE SO LATE. IT SHOULD BE NOTED THAT WE WERE ON DAY 4 OF A 4-DAY AND HAD GONE OVER 8 HRS OF FLYING DUE TO OPERATIONAL DELAYS ON DAY 1 AND DAY 3. I WAS; THEREFORE; TIRED AND SOMEWHAT FATIGUED (WOKE UP EARLY EVERY DAY) WHICH DULLED MY SENSES AND EYE FOR DETAIL. ON THE TAXI OUT DURING THE CHKLIST; I MUMBLED TO MYSELF THAT I SHOULD CONTACT LOAD PLANNING AS I DIDN'T GET THE 2 PREVIOUS RED FLAGS RESOLVED. HOWEVER; THE TAXI WAS SHORT AND TWR CLRED US TO TAKE OFF. SINCE IT WAS MY LEG; ON THE TKOF ROLL I ANNOUNCED THAT; 'I DON'T TRUST THE WTS; I'M GOING TO ADD SOME KTS AND ROTATE SLOWLY.' IN MY MIND I WAS GOING TO ROTATE AT THE ORIGINAL PLANNED VR OF ABOUT 140 KTS AND WATCH OUT FOR A MISTRIMMED ACFT. THE AIRPLANE FLEW FINE AND SOME NOSE-UP TRIM WAS NEEDED FOR BALANCED FLT AFTER LIFTOFF. A FEW MINS AFTER WE DID THE 'AFTER TKOF' CHKLIST THE CAPT NOTICED A PRINTOUT ON THE ACARS PRINTER WHICH WAS IN FACT OUR ACTUAL WTS. UPON FURTHER EXAMINATION; THE FIRST WTS WERE ACTUALLY FOR A DIFFERENT FLT. THE FLT WAS FOR ONE WE DID THE DAY PRIOR IN THE SAME TYPE OF ACFT. LESSON LEARNED: I ALWAYS ASSUMED THAT WHAT CAME OVER ACARS COULD ONLY BE FOR THE CORRECT FLT SO I DIDN'T HAVE THE HABIT OF CHKING THE FLT NUMBER AND CITY PAIR. I WILL NOW! I GOT TOO RUSHED AND NEVER STOPPED THE OP TO SATISFY MY CONCERN OVER THE RED FLAGS WHEN I COULD HAVE DONE SO. I ALSO DID NOT CLEARLY ARTICULATE MY CONCERNS TO THE CAPT. THIS WAS NOT DUE TO AN INABILITY TO SPEAK UP BECAUSE I AM USUALLY VERY VOCAL AND DO NOT HESITATE; BUT RATHER FROM BEING TIRED AND NOT UP TO MY USUAL PERFORMANCE. PROGRAMMING OF LOAD PLANNING ACARS MESSAGES SHOULD NEVER BE ALLOWED TO GO TO THE WRONG ACFT AND CERTAINLY NOT ON THE WRONG DATE AND CITY PAIR. IT ALSO SHOULD BREAK OUT CARGO AND BAGS LOADS FOR MORE CLARITY TO THE CREWS.
Data retrieved from NASA's ASRS site as of January 2009 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.