37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1287183 |
Time | |
Date | 201508 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B747-400 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Component | |
Aircraft Component | Other Documentation |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Weight And Balance Deviation - Speed All Types Ground Event / Encounter Ground Strike - Aircraft |
Narrative:
While completing our cockpit preparation for departure; we were advised that we would be ready for a possible early departure. After we received the departure ATIS and clearance first officer entered the required information into the aero data CDU page. We were advised that our cargo weight would be 10;000 pounds less than planned. I advised our operations and received T/I. First officer; began to load the aero data CDU page to request take off performance. Shortly thereafter; we were advised again; that we would have even less cargo and that we would be ready to depart early.we were flying an augmented crew of 3; 2 jumpseaters and 1 fme. After receiving the final weight and balance and aero data information I requested first officer to read to me the zero fuel weight; take off data and trim as provided on the weight and balance and aero data print out. I entered the data as required. At this point it was odd to see that the V1; vr and V2 speeds did not populate in small fonts as normal. This is my first check that something is not correct. I then mentioned this information to my first officer and relief pilot. I again verified all the information was entered correctly. It was.we proceeded to enter the speeds produce by aero data as they are extremely accurate.as the rush for the on time departure became more evident. First officer briefed the departure and required items. We approached runway 27 for departure and we were cleared for takeoff. The takeoff roll seemed a bit sluggish but not unreasonable.after calling out V1; and then vr; first officer (the PF) mentioned 'this did not seem right'; so I added power and he rotated the aircraft.after arriving cruise flight we talked about what had happened and what went wrong. It turns out; first officer entered the cargo weight in the aero data instead of the actual zero fuel weight. This turned out to give us a significant difference in performance. As a result; the tail briefly contacted the runway at liftoff.contributing factors: this was the first day of our pairing. All 3 crewmembers had to commute.
Original NASA ASRS Text
Title: A fatigued B747-400 crew was advised their departure time was being moved up and in the process several weight and balance reductions were received. The First Officer incorrectly entered the cargo weight in the FMS Aero Data zero fuel weight field causing V Speed errors near 30 KTS low. After landing a tail strike was discovered.
Narrative: While completing our cockpit preparation for departure; we were advised that we would be ready for a possible early departure. After we received the departure ATIS and clearance First Officer entered the required information into the Aero Data CDU page. We were advised that our cargo weight would be 10;000 LBS less than planned. I advised our operations and received T/I. First Officer; began to load the Aero Data CDU page to request take off performance. Shortly thereafter; we were advised again; that we would have even less cargo and that we would be ready to depart early.We were flying an augmented crew of 3; 2 jumpseaters and 1 FME. After receiving the final weight and balance and Aero Data information I requested First Officer to read to me the Zero Fuel Weight; Take off Data and Trim as provided on the Weight and Balance and Aero Data Print out. I entered the data as required. At this point it was odd to see that the V1; Vr and V2 speeds did not populate in small fonts as normal. This is my first check that something is not correct. I then mentioned this information to my First Officer and Relief Pilot. I again verified all the information was entered correctly. It was.We proceeded to enter the speeds produce by Aero Data as they are extremely accurate.As the rush for the on time departure became more evident. First Officer briefed the departure and required items. We approached runway 27 for Departure and we were cleared for takeoff. The takeoff roll seemed a bit sluggish but not unreasonable.After calling out V1; and then VR; First Officer (The PF) mentioned 'This did not seem right'; so I added power and he rotated the aircraft.After arriving cruise flight we talked about what had happened and what went wrong. It turns out; First Officer entered the cargo weight in the Aero Data instead of the actual Zero Fuel Weight. This turned out to give us a significant difference in performance. As a result; the tail briefly contacted the runway at liftoff.Contributing factors: This was the first day of our pairing. All 3 crewmembers had to commute.
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.