Flight Crew Air Transport Pilot (ATP)
Flight Crew Last 90 Days 240; Flight Crew Total 20100; Flight Crew Type 12000
Human-Machine Interface; Confusion; Situational Awareness
Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
General None Reported / Taken
Airport; Company Policy; Environment - Non Weather Related; Human Factors; Procedure; Weather
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.
Reporter stated he had not been to this airport before; and that a Check Airman was in the other seat since this was his checkout. He stated that Sabre indicated flaps 1 for takeoff; but they chose to use flaps 5. He reiterated that the takeoff numbers were run several times and that all else seemed normal; except the length of the takeoff roll. He stated that Sabre often times provides takeoff data where the aircraft uses the entire runway to become airborne. Runway 13L was NOTAM'd 3;500 ft short at the departure end; but was not in the 'numbers' generated by company methods. Runway Length was actually about 9;000 feet. Stated that the company data was predicated on the full runway being available and speeds were based on flaps 1 from Company data.
Departing in a 737-700; we used up the entire 12;500 ft of runway for our takeoff roll. The aircraft lifted off at the very end of the runway and I would estimate we were only several feet above the runway end lights. ZZZZ field elevation is [over 8;000 ft]. Our takeoff weight was about 3000 [pounds] below our MTOW. Planned takeoff data showed Flaps 1; bleeds on; with [a] slight headwind. Actual takeoff data gave us Flaps 5; bleeds on. I used zero for the wind to be more conservative (both data messages are attached). I do not recall the actual wind the tower gave us with our takeoff clearance; but it was not a tailwind.Engine and takeoff acceleration seemed normal (for the altitude) but we still used all of the runway. At the 'rotate' call we were rapidly approaching the runway end lights. The PF (other pilot) made a normal rotation; just clearing the lights. At cruise we discussed if we had done anything wrong or if we should have done something differently to not use so much runway. Everything we did was correct. I wanted to bring to attention the fact that in this event Sabre planned us very close to actual runway length. The flight was below planned takeoff weight; on a cool day with a high altimeter setting; using a greater flap setting than Sabre had initially planned for us; all favorable conditions for takeoff performance. The pilots have no knowledge of how much runway Sabre is planning on using. If I had known it was this close; I would have requested new data with a different bleed and/or flap configuration.
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.