 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier MD80 flight crew took off without having that runway's takeoff performance system data. The data was computed for another runway.
| Attributes | |
| ACN | 382540 |
| Time | |
| Date | 199710 |
| Day | Mon |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : dfw |
| State Reference | TX |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : zny |
| Operator | common carrier : air carrier |
| Make Model Name | MD-80 Super 80 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | climbout : takeoff ground : preflight |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| ASRS Report | 382540 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | non adherence : published procedure non adherence : far other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
On taxi out for takeoff, all takeoff data was reviewed with multiple intersection numbers present. Both pilots discussed the fact that they must have renumbered the intxns, however, the numbers remained the same from all intxns. After departure it was discovered that all takeoff performance system data was for runway 17C. No data was on the takeoff performance system for runway 17R which was very unusual since our takeoff was after XB00. The hourly takeoff performance system summary for XA00 showed all dfw runways open and dry. I do not understand why they showed runway 17C for our primary runway and displayed no data for runway 17R. Nonetheless, we made a mistake and departed from runway 17R with the wrong data. Due to our normal light weight conditions, our takeoff performance system data appeared normal for runway 17R.
Original NASA ASRS Text
Title: AN ACR MD80 FLC TOOK OFF WITHOUT HAVING THAT RWY'S TKOF PERFORMANCE SYS DATA. THE DATA WAS COMPUTED FOR ANOTHER RWY.
Narrative: ON TAXI OUT FOR TKOF, ALL TKOF DATA WAS REVIEWED WITH MULTIPLE INTXN NUMBERS PRESENT. BOTH PLTS DISCUSSED THE FACT THAT THEY MUST HAVE RENUMBERED THE INTXNS, HOWEVER, THE NUMBERS REMAINED THE SAME FROM ALL INTXNS. AFTER DEP IT WAS DISCOVERED THAT ALL TKOF PERFORMANCE SYS DATA WAS FOR RWY 17C. NO DATA WAS ON THE TKOF PERFORMANCE SYS FOR RWY 17R WHICH WAS VERY UNUSUAL SINCE OUR TKOF WAS AFTER XB00. THE HOURLY TKOF PERFORMANCE SYS SUMMARY FOR XA00 SHOWED ALL DFW RWYS OPEN AND DRY. I DO NOT UNDERSTAND WHY THEY SHOWED RWY 17C FOR OUR PRIMARY RWY AND DISPLAYED NO DATA FOR RWY 17R. NONETHELESS, WE MADE A MISTAKE AND DEPARTED FROM RWY 17R WITH THE WRONG DATA. DUE TO OUR NORMAL LIGHT WT CONDITIONS, OUR TKOF PERFORMANCE SYS DATA APPEARED NORMAL FOR RWY 17R.
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.