Narrative:

Runway 22R has a displaced threshold. After clearance for takeoff and about 100' into the takeoff roll, takeoff clearance was cancelled. After we stopped, takeoff clearance was reissued. Since we were still 200-300' short of the start of the runway still on the yellow arrows) and fairly light weight, I elected not to taxi back for another takeoff. Subsequent review of the takeoff data reminded me that I should have done the taxi-back since the takeoff data was predicated on the sue of the displacement area. I suppose I confused arrows with chevrons. Some fields have chevrons and I believe takeoff data is not predicated on the use of that area for takeoff. Perhaps the stressing of that difference in performance review sessions would prevent another such mistake.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR MLG MADE A TKOF FROM THE DISPLACED LNDG THRESHOLD THINKING THE TKOF DATA WAS PREDICATED ON THIS SHORTER RWY.

Narrative: RWY 22R HAS A DISPLACED THRESHOLD. AFTER CLRNC FOR TKOF AND ABOUT 100' INTO THE TKOF ROLL, TKOF CLRNC WAS CANCELLED. AFTER WE STOPPED, TKOF CLRNC WAS REISSUED. SINCE WE WERE STILL 200-300' SHORT OF THE START OF THE RWY STILL ON THE YELLOW ARROWS) AND FAIRLY LIGHT WT, I ELECTED NOT TO TAXI BACK FOR ANOTHER TKOF. SUBSEQUENT REVIEW OF THE TKOF DATA REMINDED ME THAT I SHOULD HAVE DONE THE TAXI-BACK SINCE THE TKOF DATA WAS PREDICATED ON THE SUE OF THE DISPLACEMENT AREA. I SUPPOSE I CONFUSED ARROWS WITH CHEVRONS. SOME FIELDS HAVE CHEVRONS AND I BELIEVE TKOF DATA IS NOT PREDICATED ON THE USE OF THAT AREA FOR TKOF. PERHAPS THE STRESSING OF THAT DIFFERENCE IN PERFORMANCE REVIEW SESSIONS WOULD PREVENT ANOTHER SUCH MISTAKE.

Data retrieved from NASA's ASRS site as of July 2007 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.