Narrative:

We received our dispatch release; WX briefing and NOTAMS via our normal computer connection prior to departure. As we prepared for takeoff; our flight engineer computed our takeoff performance using data provided him via the airport's ATIS. ATIS informed us the departing runway would be runway 17L. When we contacted ground control; we were told to stand by. We stood by monitoring ground control and heard air carrier Y call and request taxi. Ground informed air carrier Y they were in the process of turning the airport around. Flight engineer then picked up the updated ATIS broadcast. He noted that the winds had shifted and the airport was using runway 34R for departures. There was no mention on the ATIS requiring aircraft departing runway 34R to taxi forward from the normal runway entry point to the displaced threshold before applying takeoff power. After a short wait; ground control called us back and asked if we were ready to taxi. We answered in the affirmative and were told to taxi up to runway 34R and we would be following the second regional jet for takeoff. We observed the 2 rj's take off and monitored tower's instructions to them. At no time did we heard tower instruct the 2 prior departures to taxi forward prior to applying takeoff power. After the 2 rj's had taken off; we were given takeoff clearance. We were not instructed to taxi forward prior to applying takeoff power. We applied takeoff power; and made a normal takeoff. We were informed later that day; our power-up for takeoff blew over construction barricades and 'made quite a mess.' we flew the same flight the remainder of the week. Each day; we heard tower instruct other aircraft departing runway 34R to taxi forward to the displaced threshold prior to applying takeoff power; and noted tower instructed us to do the same. I would suggest that; if a temporary special procedure is to be used; the airport broadcast that procedure over the ATIS. This information was not available to us via the NOTAMS we received. Supplemental information from acn 662973: NOTAMS indicated a displaced threshold for runway 34R. The takeoff data computed by the so did not take into account the displaced threshold. I had him correct the data which changed the V1 speed and stop distance. The captain was aware of these changes and that it was because of the displaced threshold. When we were cleared for takeoff by slc tower; we were not given instructions to taxi up to the displaced threshold for takeoff. However; I assumed the captain would taxi up to the displaced threshold because we had just discussed it. Instead; he began to add power after aligning for takeoff. At first; I thought he was adding only enough to taxi down the runway. When he added more power; I questioned him if he was going to wait until the displaced threshold. He mumbled something I could not understand and while adding still more power; told me I had the aircraft (it was my takeoff). By this time; we were approaching the displaced threshold. I waited until then to call for standard power. While I feel power was added early; I did not realize that excessive power was used early enough to cause the barricades to be blown over.

Related reports:

Google
 

Original NASA ASRS Text

Title: DC10 BLOWS OVER BARRICADE BEHIND DISPLACED THRESHOLD ON TKOF FROM RWY 34R AT SLC.

Narrative: WE RECEIVED OUR DISPATCH RELEASE; WX BRIEFING AND NOTAMS VIA OUR NORMAL COMPUTER CONNECTION PRIOR TO DEP. AS WE PREPARED FOR TKOF; OUR FE COMPUTED OUR TKOF PERFORMANCE USING DATA PROVIDED HIM VIA THE ARPT'S ATIS. ATIS INFORMED US THE DEPARTING RWY WOULD BE RWY 17L. WHEN WE CONTACTED GND CTL; WE WERE TOLD TO STAND BY. WE STOOD BY MONITORING GND CTL AND HEARD ACR Y CALL AND REQUEST TAXI. GND INFORMED ACR Y THEY WERE IN THE PROCESS OF TURNING THE ARPT AROUND. FE THEN PICKED UP THE UPDATED ATIS BROADCAST. HE NOTED THAT THE WINDS HAD SHIFTED AND THE ARPT WAS USING RWY 34R FOR DEPS. THERE WAS NO MENTION ON THE ATIS REQUIRING ACFT DEPARTING RWY 34R TO TAXI FORWARD FROM THE NORMAL RWY ENTRY POINT TO THE DISPLACED THRESHOLD BEFORE APPLYING TKOF PWR. AFTER A SHORT WAIT; GND CTL CALLED US BACK AND ASKED IF WE WERE READY TO TAXI. WE ANSWERED IN THE AFFIRMATIVE AND WERE TOLD TO TAXI UP TO RWY 34R AND WE WOULD BE FOLLOWING THE SECOND REGIONAL JET FOR TKOF. WE OBSERVED THE 2 RJ'S TAKE OFF AND MONITORED TWR'S INSTRUCTIONS TO THEM. AT NO TIME DID WE HEARD TWR INSTRUCT THE 2 PRIOR DEPS TO TAXI FORWARD PRIOR TO APPLYING TKOF PWR. AFTER THE 2 RJ'S HAD TAKEN OFF; WE WERE GIVEN TKOF CLRNC. WE WERE NOT INSTRUCTED TO TAXI FORWARD PRIOR TO APPLYING TKOF PWR. WE APPLIED TKOF PWR; AND MADE A NORMAL TKOF. WE WERE INFORMED LATER THAT DAY; OUR PWR-UP FOR TKOF BLEW OVER CONSTRUCTION BARRICADES AND 'MADE QUITE A MESS.' WE FLEW THE SAME FLT THE REMAINDER OF THE WK. EACH DAY; WE HEARD TWR INSTRUCT OTHER ACFT DEPARTING RWY 34R TO TAXI FORWARD TO THE DISPLACED THRESHOLD PRIOR TO APPLYING TKOF PWR; AND NOTED TWR INSTRUCTED US TO DO THE SAME. I WOULD SUGGEST THAT; IF A TEMPORARY SPECIAL PROC IS TO BE USED; THE ARPT BROADCAST THAT PROC OVER THE ATIS. THIS INFO WAS NOT AVAILABLE TO US VIA THE NOTAMS WE RECEIVED. SUPPLEMENTAL INFO FROM ACN 662973: NOTAMS INDICATED A DISPLACED THRESHOLD FOR RWY 34R. THE TKOF DATA COMPUTED BY THE SO DID NOT TAKE INTO ACCOUNT THE DISPLACED THRESHOLD. I HAD HIM CORRECT THE DATA WHICH CHANGED THE V1 SPD AND STOP DISTANCE. THE CAPT WAS AWARE OF THESE CHANGES AND THAT IT WAS BECAUSE OF THE DISPLACED THRESHOLD. WHEN WE WERE CLRED FOR TKOF BY SLC TWR; WE WERE NOT GIVEN INSTRUCTIONS TO TAXI UP TO THE DISPLACED THRESHOLD FOR TKOF. HOWEVER; I ASSUMED THE CAPT WOULD TAXI UP TO THE DISPLACED THRESHOLD BECAUSE WE HAD JUST DISCUSSED IT. INSTEAD; HE BEGAN TO ADD PWR AFTER ALIGNING FOR TKOF. AT FIRST; I THOUGHT HE WAS ADDING ONLY ENOUGH TO TAXI DOWN THE RWY. WHEN HE ADDED MORE PWR; I QUESTIONED HIM IF HE WAS GOING TO WAIT UNTIL THE DISPLACED THRESHOLD. HE MUMBLED SOMETHING I COULD NOT UNDERSTAND AND WHILE ADDING STILL MORE PWR; TOLD ME I HAD THE ACFT (IT WAS MY TKOF). BY THIS TIME; WE WERE APCHING THE DISPLACED THRESHOLD. I WAITED UNTIL THEN TO CALL FOR STANDARD PWR. WHILE I FEEL PWR WAS ADDED EARLY; I DID NOT REALIZE THAT EXCESSIVE PWR WAS USED EARLY ENOUGH TO CAUSE THE BARRICADES TO BE BLOWN OVER.

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