 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reported that they mistakenly used takeoff numbers for a runway which they did not use for takeoff; they were overweight for the runway at that flap and power setting they used.
| Attributes | |
| ACN | 1630725 |
| Time | |
| Date | 201903 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | FAT.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
| Experience | Flight Crew Total 25000 |
| Person 2 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Total 12000 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Weight And Balance Deviation - Procedural FAR Deviation - Speed All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
Taxied out to [runway] 29L at kfat. [Runway] 29R was closed. Still pretty dark; short taxi; unfamiliar with airport; one taxiway leads to both thresholds. While pulling up paperwork earlier; I assumed departure would be to the east due to wind. Discussed tailwind corrections on tps and applied those with QRH input. First officer's take-off. On rotation; I noted that we were a long way down the runway. Later on climb-out; first officer re-checked tps and discovered that we had used [runway] 29R numbers instead of [runway] 29L and that we were overweight for the runway at that flap and power setting. Inattention on my part to ensure that the correct numbers for the correct runway were being used. First officer gave very thorough take off data and bugs brief and I missed that [runway] 29R numbers had been entered in the CDU. [We] should have briefed the weight restrictions on [runway] 29L more clearly. Brief parallel runway tps considerations and make a definite check that we had the correct numbers for the correct runway.
Original NASA ASRS Text
Title: B737 flight crew reported that they mistakenly used takeoff numbers for a runway which they did not use for takeoff; they were overweight for the runway at that flap and power setting they used.
Narrative: Taxied out to [Runway] 29L at KFAT. [Runway] 29R was closed. Still pretty dark; short taxi; unfamiliar with airport; one taxiway leads to both thresholds. While pulling up paperwork earlier; I assumed departure would be to the east due to wind. Discussed tailwind corrections on TPS and applied those with QRH input. First Officer's take-off. On rotation; I noted that we were a long way down the runway. Later on climb-out; First Officer re-checked TPS and discovered that we had used [Runway] 29R numbers instead of [Runway] 29L and that we were overweight for the runway at that flap and power setting. Inattention on my part to ensure that the correct numbers for the correct runway were being used. First Officer gave very thorough take off data and bugs brief and I missed that [Runway] 29R numbers had been entered in the CDU. [We] should have briefed the weight restrictions on [Runway] 29L more clearly. Brief parallel runway TPS considerations and make a definite check that we had the correct numbers for the correct runway.
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.