37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1255419 |
Time | |
Date | 201504 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Experience | Flight Crew Last 90 Days 240 Flight Crew Total 15000 Flight Crew Type 6000 |
Person 2 | |
Function | Captain Pilot Flying |
Experience | Flight Crew Last 90 Days 250 Flight Crew Total 10000 Flight Crew Type 2000 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Weight And Balance Deviation - Speed All Types |
Narrative:
We planned on departing 15R and programmed the fmgcs accordingly. We also obtained performance for 15L in case we got switched to that runway for departure. The we later ordered performance for 15L; expecting to receive an updated zero fuel weight (ZFW) and takeoff weight; in case tower launched us from there. Mid taxi we did get switched to 15L and changed runways and entered the flaps and speeds from the performance printout for that runway and intersection; and then we completed the checklists.the takeoff was normal with the nose raised at vr and smoothly transitioned to flight; with a substantial amount of runway remaining. After liftoff I notice V2 had dropped below vls; lowest selectable speed; and managed speed had moved to the upper end of the speed tape. When leveled off at cruise I took another look at our performance printouts and discovered the last performance numbers we received from sabre; were for 138.3 and not our final weight of 156.2. Minimum takeoff gross weight (mtog) for that intersection was 169.7. It appears we took off with v-speed for well below our actual weight; which explains the unusual speed bug behavior. What remains a question is how we ended up with sabre performance for a weight so far below our actual take-off weight.
Original NASA ASRS Text
Title: An A320 crew; relying on incorrect V speeds and weights; rotated and did not take off. The Captain maintained the takeoff attitude and let the aircraft fly itself off the runway. Once established in cruise; the crew compared the performance printouts and discovered the last performance numbers received from Sabre; were for 138.3 and not the final weight of 156.2.
Narrative: We planned on departing 15R and programmed the FMGCs accordingly. We also obtained performance for 15L in case we got switched to that runway for departure. The we later ordered performance for 15L; expecting to receive an updated Zero Fuel Weight (ZFW) and takeoff weight; in case tower launched us from there. Mid taxi we did get switched to 15L and changed runways and entered the flaps and speeds from the performance printout for that runway and intersection; and then we completed the checklists.The takeoff was normal with the nose raised at VR and smoothly transitioned to flight; with a substantial amount of runway remaining. After liftoff I notice V2 had dropped below VLS; lowest selectable speed; and managed speed had moved to the upper end of the speed tape. When leveled off at cruise I took another look at our performance printouts and discovered the last performance numbers we received from Sabre; were for 138.3 and not our final weight of 156.2. Minimum Takeoff Gross Weight (MTOG) for that intersection was 169.7. It appears we took off with V-speed for well below our actual weight; which explains the unusual speed bug behavior. What remains a question is how we ended up with Sabre performance for a weight so far below our actual take-off weight.
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.