 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of DC9 mistakenly taxies onto runway in midst of multiple confusions of clrncs, call signs, and clrncs at msp.
| Attributes | |
| ACN | 425010 |
| Time | |
| Date | 199901 |
| Day | Fri |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : msp |
| State Reference | MN |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Night |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Flight Phase | ground other : taxi |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 210 flight time total : 7500 flight time type : 2000 |
| ASRS Report | 425010 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial |
| Events | |
| Anomaly | incursion : runway other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | controller : issued new clearance |
| Consequence | Other |
| Supplementary | |
| Air Traffic Incident | Pilot Deviation |
Narrative:
We were #1 for takeoff at msp for runway 30L. Msp tower cleared an aircraft (XXX4) to taxi onto runway and be ready for immediate takeoff. As our call sign also had a '4' in it, that is all I heard, plus 'hurry' for immediate departure. The first officer read back the clearance for us to taxi on and hold for immediate departure. That was acknowledged by tower. On the runway we were then cleared for takeoff but we heard air carrier xyz, I think 'cleared for takeoff.' the first officer said 'negative, we are air carrier XXX.' tower replied, 'air carrier xyz.' I finally said 'are you talking to air carrier XXX?' there was no response. I said 'air carrier XXX is taxiing off runway, we are not air carrier xyz.' tower then replied 'taxi clear of runway,' which we were already doing. It turns out air carrier xyz was behind us #2 for takeoff. The tower controller's speech was rapid and hard to understand. Through all these xmissions, the real air carrier xyz behind us never said a word, though he was on frequency, because he couldn't clearly understand tower either. I assume and tower had obviously got our position and air carrier xyz reversed.
Original NASA ASRS Text
Title: FLC OF DC9 MISTAKENLY TAXIES ONTO RWY IN MIDST OF MULTIPLE CONFUSIONS OF CLRNCS, CALL SIGNS, AND CLRNCS AT MSP.
Narrative: WE WERE #1 FOR TKOF AT MSP FOR RWY 30L. MSP TWR CLRED AN ACFT (XXX4) TO TAXI ONTO RWY AND BE READY FOR IMMEDIATE TKOF. AS OUR CALL SIGN ALSO HAD A '4' IN IT, THAT IS ALL I HEARD, PLUS 'HURRY' FOR IMMEDIATE DEP. THE FO READ BACK THE CLRNC FOR US TO TAXI ON AND HOLD FOR IMMEDIATE DEP. THAT WAS ACKNOWLEDGED BY TWR. ON THE RWY WE WERE THEN CLRED FOR TKOF BUT WE HEARD ACR XYZ, I THINK 'CLRED FOR TKOF.' THE FO SAID 'NEGATIVE, WE ARE ACR XXX.' TWR REPLIED, 'ACR XYZ.' I FINALLY SAID 'ARE YOU TALKING TO ACR XXX?' THERE WAS NO RESPONSE. I SAID 'ACR XXX IS TAXIING OFF RWY, WE ARE NOT ACR XYZ.' TWR THEN REPLIED 'TAXI CLR OF RWY,' WHICH WE WERE ALREADY DOING. IT TURNS OUT ACR XYZ WAS BEHIND US #2 FOR TKOF. THE TWR CTLR'S SPEECH WAS RAPID AND HARD TO UNDERSTAND. THROUGH ALL THESE XMISSIONS, THE REAL ACR XYZ BEHIND US NEVER SAID A WORD, THOUGH HE WAS ON FREQ, BECAUSE HE COULDN'T CLRLY UNDERSTAND TWR EITHER. I ASSUME AND TWR HAD OBVIOUSLY GOT OUR POS AND ACR XYZ REVERSED.
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.