 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Aircraft on landing rollout, tower cleared them to cross runway 9L. Flight crew thought tower wanted them to stay on runway 22R until crossing runway 9L, but a following aircraft had to go around, because reporter had not exited the highspd at taxiway C. Lack of clear communication between flight crew and tower.
| Attributes | |
| ACN | 321887 |
| Time | |
| Date | 199511 |
| Day | Wed |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : ord |
| State Reference | IL |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | DC-9 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | ground other : taxi landing other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial pilot : atp |
| Experience | flight time last 90 days : 100 flight time total : 2200 flight time type : 100 |
| ASRS Report | 321887 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | incursion : runway other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Primary Problem | Ambiguous |
| Air Traffic Incident | other |
Narrative:
Landed on runway 22R at ord. During the landing rollout tower radioed to cross runway 9L stay with him. At the time of the call the aircraft was approaching the highspd turnoff (taxiway C). When we heard the call we both felt he wanted us to continue on the active runway until crossing runway 9L. A B737 was told to go around. The tower controller asked for an explanation why the aircraft did not turn-off at taxiway C and asked for a phone call once parked. If the controller would have simply stated left at the highspd that would have been done. The tower frequency was very busy with a lot of backgnd chatter during xmissions. The lengthier clearance given during the landing roll contributed to our aircraft not exiting at taxiway C. We felt he relayed to stay on the active runway until crossing runway 9L. Tower was called and given an explanation.
Original NASA ASRS Text
Title: ACFT ON LNDG ROLLOUT, TWR CLRED THEM TO CROSS RWY 9L. FLC THOUGHT TWR WANTED THEM TO STAY ON RWY 22R UNTIL XING RWY 9L, BUT A FOLLOWING ACFT HAD TO GAR, BECAUSE RPTR HAD NOT EXITED THE HIGHSPD AT TXWY C. LACK OF CLR COM BTWN FLC AND TWR.
Narrative: LANDED ON RWY 22R AT ORD. DURING THE LNDG ROLLOUT TWR RADIOED TO CROSS RWY 9L STAY WITH HIM. AT THE TIME OF THE CALL THE ACFT WAS APCHING THE HIGHSPD TURNOFF (TXWY C). WHEN WE HEARD THE CALL WE BOTH FELT HE WANTED US TO CONTINUE ON THE ACTIVE RWY UNTIL XING RWY 9L. A B737 WAS TOLD TO GAR. THE TWR CTLR ASKED FOR AN EXPLANATION WHY THE ACFT DID NOT TURN-OFF AT TXWY C AND ASKED FOR A PHONE CALL ONCE PARKED. IF THE CTLR WOULD HAVE SIMPLY STATED L AT THE HIGHSPD THAT WOULD HAVE BEEN DONE. THE TWR FREQ WAS VERY BUSY WITH A LOT OF BACKGND CHATTER DURING XMISSIONS. THE LENGTHIER CLRNC GIVEN DURING THE LNDG ROLL CONTRIBUTED TO OUR ACFT NOT EXITING AT TXWY C. WE FELT HE RELAYED TO STAY ON THE ACTIVE RWY UNTIL XING RWY 9L. TWR WAS CALLED AND GIVEN AN EXPLANATION.
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.