B737-300 FLT CREW USES WRONG TKOF DATA FOR RWY 34 UNDER CONSTRUCTION AT SLC.

Date: 2006-06 · Aircraft: B737-300 · Phase: takeoff

Anomalies: deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-far

Synopsis

B737-300 FLT CREW USES WRONG TKOF DATA FOR RWY 34 UNDER CONSTRUCTION AT SLC.

Narrative

ON TAXI OUT FOR RWY 34R AT SLC; TXWY H WAS UNDER CONSTRUCTION; GENERATING A PAGE WHICH MENTIONS A TEMPORARY DISPLACED THRESHOLD FOR RWY 34R. DISPLACED THRESHOLDS ARE NORMALLY USED FOR TAXI AND TKOF. ARRIVING AT RWY 34R AT TXWY H1 WE WERE TOLD TO GO INTO POS AND HOLD. WE CROSSED ONTO RWY 34R AT WHICH TIME AN MD80 DID A SLOW SPD ABORT ON TKOF ROLL AND CLRED RWY. AT THAT TIME THE TWR TOLD US WE WERE CLRED FOR TKOF AND NOT TO APPLY TKOF PWR UNTIL REACHING THE DISPLACED THRESHOLD BEFORE TXWY H3. ENRTE AND AFTER FURTHER EXAMINATION OF SLC NOTAMS IT STATES TO ENTER RWY 34R AT TXWY H1 AND NOT TO APPLY TKOF PWR UNTIL REACHING THE TEMPORARY DISPLACED THRESHOLD AT H3; AND TO USE 34RX FOR ACARS PERFORMANCE DATA. AT THAT POINT I WENT BACK INTO ACARS TO CONFIRM THAT WE HAD MET PERFORMANCE LIMITS. THERE WAS STILL 10400 FT AVAILABLE FOR TKOF FROM 34RX DISPLACED THRESHOLD; WHICH SATISFIED PERFORMANCE CRITERIA FOR OUR ALLOWABLE TKOF GROSS WT. THE HUMAN FACTORS ARE THAT I AM A NEW CAPT AT AN UNFAMILIAR ARPT. THE TECHNICAL FACTOR IS THAT ACARS SHOULD NOT BE ABLE TO PRODUCE PERFORMANCE DATA FOR A PORTION OF A RWY THAT IS NOT AVAILABLE FOR TKOF. IT WAS ALSO NOT CLRLY MARKED AT WHICH POINT TO APPLY TKOF PWR FOR RWY 34R AS IT IS IN OTHER RWYS SUCH AS SFO ON RWY 1R.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.