 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737 flight crew used their company's procedure to calculate takeoff data for a high altitude airport. They subsequently chose a better flap setting for the runway and still used all the runway to become airborne; almost hitting the runway end identifier lights. They reported that the situation was not uncommon to use all the runway to become airborne when using the company generated takeoff data.
| Attributes | |
| ACN | 1365879 |
| Time | |
| Date | 201606 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZZ.Airport |
| State Reference | FO |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| 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 Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 240 Flight Crew Total 20100 Flight Crew Type 12000 |
| Person 2 | |
| Function | Pilot Not Flying Check Pilot |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 40 Flight Crew Total 13000 Flight Crew Type 7000 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Weight And Balance |
Narrative:
During our takeoff roll out of ZZZZ; we used approximately 99.8% of the runway (which is over 12;000 feet!) and almost hit the runway end indicator lights. I'm assuming we probably missed them by about 2-3 feet if that much. We ran the numbers and reviewed them several times prior to takeoff. The engine spool up and takeoff roll was uneventful. The difference between V1 and vr was around 20 knots or so if I remember correctly. Had I not rotated at exactly vr we would have run over the runway end indicator lights even though they're is several hundred feet of overrun which is not on our charts. Had we not seen the REIL's and rotated when we did; we would have hit them. The lights tend to blend in with the overrun. To say this takeoff got our attention is an understatement. I've noticed the sabre data is getting to the point where we use every available inch of runway on many of our departures. I never remember this happening under the old system. It is uncomfortable to say the least.
Original NASA ASRS Text
Title: A B737 flight crew used their company's procedure to calculate takeoff data for a high altitude airport. They subsequently chose a better flap setting for the runway and still used all the runway to become airborne; almost hitting the runway end identifier lights. They reported that the situation was not uncommon to use all the runway to become airborne when using the company generated takeoff data.
Narrative: During our takeoff roll out of ZZZZ; we used approximately 99.8% of the runway (which is OVER 12;000 feet!) and ALMOST hit the runway end indicator lights. I'm assuming we probably missed them by about 2-3 feet if that much. We ran the numbers and reviewed them several times prior to takeoff. The engine spool up and takeoff roll was uneventful. The difference between V1 and VR was around 20 knots or so if I remember correctly. Had I not rotated at EXACTLY VR we would have run over the runway end indicator lights even though they're is several hundred feet of overrun which is NOT on our charts. Had we not seen the REIL's and rotated when we did; we would have hit them. The lights tend to blend in with the overrun. To say this takeoff got our attention is an understatement. I've noticed the SABRE data is getting to the point where we use every available inch of runway on many of our departures. I never remember this happening under the old system. It is uncomfortable to say the least.
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.