Regional Jet 700 ER/LR (CRJ700)
Flight Crew Air Transport Pilot (ATP)
Confusion; Situational Awareness
Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors
On arrival for landing; I had a little trouble getting a landing data assessment to come up on the ACARS until I entered the correct code for a displaced threshold 05-SW578F. Again when doing our takeoff data; the ACARS would only give us data with 05-SW578F entered. I misinterpreted this to mean the takeoff data was based on a takeoff from the displaced threshold; and not the full length. So when cleared to back taxi; cleared for takeoff; I only went as far as the displaced threshold.About ten minutes into the flight; I was thinking why only have numbers from the threshold. I pulled out the old release; and checked it against the takeoff release; and saw my mistake. The landing distance for that code included the displaced threshold. The takeoff distance for that same code did not include the displaced threshold; it was for full length. I made a poor interpretation of the takeoff data code; and did not look at the planned runway length on the release TLR together with the ACARS perf.It not very common to get these runway code corrections; so Threat and Error Management would be well used by slowing down and double checking both release and ACARS data.
Neither of us had been to this airport before and the displaced threshold was a NOTAMed addition which caused the ACARS to require a special coded input for runway performance. This tripped us up on both arrival and departure. Additionally the displaced threshold was not as well-lit as the runway. Finally; we had another aircraft waiting to enter the runway after us; creating a minor sense of urgency.
CRJ-700 flight crew reported taking off with less than planned useable runway length.