Potential conflict when air carrier X stays on runway too long when PIC has a problem with the clearance interpretation expected. Landing traffic behind, air carrier Y, performs a go around.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	358830
Time
Date	199701
Day	Sun
Local Time Of Day	1201 To 1800
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	MD-80 Super 80
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	ground other : taxi landing other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	descent : approach landing : go around
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	358830
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	conflict : ground less severe non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera other other : unspecified
Resolutory Action	controller : issued new clearance other other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other

Narrative:

ATC facility: ord tower. Location: runway 14L at ord. We landed on runway 14L. During rollout, tower instructed us to join taxiway P, cross runway 9L, and head for the bravo bridge. I missed the join taxiway P part of the instruction. We rolled long, across runway 9L, and turned off at taxiway B, headed toward the bridge. The aircraft behind us had to go around. I see 2 problems: 1) tower frequency was very busy, with no chance for a readback, and 2) we have, in the past, received such a taxi route by the tower. In the future, we will always clear the runway, stop, and then ask for clarification of taxi instructions.

Original NASA ASRS Text

Title: POTENTIAL CONFLICT WHEN ACR X STAYS ON RWY TOO LONG WHEN PIC HAS A PROB WITH THE CLRNC INTERP EXPECTED. LNDG TFC BEHIND, ACR Y, PERFORMS A GAR.

Narrative: ATC FACILITY: ORD TWR. LOCATION: RWY 14L AT ORD. WE LANDED ON RWY 14L. DURING ROLLOUT, TWR INSTRUCTED US TO JOIN TXWY P, CROSS RWY 9L, AND HEAD FOR THE BRAVO BRIDGE. I MISSED THE JOIN TXWY P PART OF THE INSTRUCTION. WE ROLLED LONG, ACROSS RWY 9L, AND TURNED OFF AT TXWY B, HEADED TOWARD THE BRIDGE. THE ACFT BEHIND US HAD TO GAR. I SEE 2 PROBS: 1) TWR FREQ WAS VERY BUSY, WITH NO CHANCE FOR A READBACK, AND 2) WE HAVE, IN THE PAST, RECEIVED SUCH A TAXI RTE BY THE TWR. IN THE FUTURE, WE WILL ALWAYS CLR THE RWY, STOP, AND THEN ASK FOR CLARIFICATION OF TAXI INSTRUCTIONS.

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.