How does one do that?
Let me clarify... I get a TLR that includes some intersection departures. It gives performance numbers from that intersection but does not give distance available from the intersection. I can also send a data request to Aerodata via the ACARS for pretty much any runway/intersection combo. When that data comes back it gives performance numbers AND the amount of pavement available. However, using just the paper TLR I have no way of knowing the actual distance. Does that matter if I have performance numbers for that intersection?
Also, interesting story from the other day...
8L in HNL was shortened by 3000 feet due to construction on the eastern end of the runway for about 5 days. During that time period the company elected to update our ACARS data manager which meant for about 3 hours we wouldn't be able to get takeoff data via the ACARS and instead would have to use the performance books in each airplane. (we also had TLR data but for some reason it wasn't showing the shortened runway so we couldn't use it.) There are three "normal" takeoff points on 8L. Full length (12,000 feet), RB (which is about a 500 foot reduction) and L which gives you about 7500 feet of runway. The performance book gives data for each of these points. HOWEVER... with the runway being shortened by 3000 feet all of that data was invalid. We got a message from Flight Ops saying that we could use the data for a Lima intersection departure (~7500 feet available) and just take off full length (which gave us 9000 feet of runway). At first brush this sounds fine but like
@Boris Badenov said, this doesn't take into account the second stage climb. In theory you are taking off from a point further back (full length instead of Lima) from where the data is for so you SHOULD be ok, but there are a whole lot of what ifs and unknowns with that.
We just went to 8R.