37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1155004 |
Time | |
Date | 201403 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ORD.Airport |
State Reference | IL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Critical Ground Event / Encounter Other / Unknown |
Narrative:
As we had been cleared to line up and wait on runway 22L there was no delay between receiving takeoff clearance and the captain (pilot flying) beginning the takeoff roll. Shortly after brake release the tower canceled our take-off clearance and asked us to hold our position due to inadequate separation with an aircraft landing on 28C. At the point where the captain initiated the abort we were at approximately 50 knots GS. The cancel takeoff communication from tower was in a normal tone of voice; no different than any other radio communication; and (in my opinion) that resulted in a short delay between receiving the cancelation and initiating the rejected take-off. The rejected take-off was executed per SOP and the aircraft on final to runway 28C was told to execute a go-around by tower and complied with clearance. We were then told to expedite down the runway and turn-off runway on taxiway S3 (sierra-three). First-officer (pilot monitoring) repeated back instruction to expedite down runway and turn off taxiway S3. At this time I checked ord airport page and immediately noticed no 'south' designation for exits from 22L. I recall a second aircraft was also told to execute a go-around due to inadequate separation from our aircraft taxing down runway 22L. Following the go-around communication to second aircraft on final the tower again requested we expedite taxi and exit via S3. After we were we clear of the 28C final approach the captain slowed our taxi and asked the tower 'do you mean turn off on Y3; there is no S3 taxi-way?' tower acknowledged the error and corrected the clearance; stating 'turn-off at Y3; make another right turn and hold position there.'I then asked tower what caused the cancellation of our take-off clearance and he advised that shortly after giving us take-off clearance; the monitor directed a go-around of aircraft on final to 28C due to not enough separation and apologized for situation. There was no confusion; miscommunication on any taxi-clearances and instructions from that point of holding position on taxi-way Y to arriving in delay pad for runway 22L. We remained in delay pad for runway 22L for brakes to cool to temperature allowing for taxi and take-off. Following cooling of brakes; the flight was normal.
Original NASA ASRS Text
Title: When an A320 had their takeoff clearance cancelled at moderate speeds the ensuing inaccurate clearances from Tower to exit the runway resulted in delays and a go-around for an aircraft on approach.
Narrative: As we had been cleared to line up and wait on Runway 22L there was no delay between receiving takeoff clearance and the Captain (pilot flying) beginning the takeoff roll. Shortly after brake release the Tower canceled our take-off clearance and asked us to hold our position due to inadequate separation with an aircraft landing on 28C. At the point where the Captain initiated the abort we were at approximately 50 knots GS. The cancel takeoff communication from Tower was in a normal tone of voice; no different than any other radio communication; and (in my opinion) that resulted in a short delay between receiving the cancelation and initiating the rejected take-off. The rejected take-off was executed per SOP and the aircraft on final to RWY 28C was told to execute a go-around by Tower and complied with clearance. We were then told to expedite down the runway and turn-off runway on taxiway S3 (Sierra-Three). First-Officer (pilot monitoring) repeated back instruction to expedite down runway and turn off taxiway S3. At this time I checked ORD airport page and immediately noticed no 'S' designation for exits from 22L. I recall a second aircraft was also told to execute a go-around due to inadequate separation from our aircraft taxing down RWY 22L. Following the go-around communication to second aircraft on final the Tower again requested we expedite taxi and exit via S3. After we were we clear of the 28C final approach the Captain slowed our taxi and asked the tower 'do you mean turn off on Y3; there is no S3 taxi-way?' Tower acknowledged the error and corrected the clearance; stating 'turn-off at Y3; make another right turn and hold position there.'I then asked Tower what caused the cancellation of our take-off clearance and he advised that shortly after giving us take-off clearance; the monitor directed a go-around of aircraft on final to 28C due to not enough separation and apologized for situation. There was no confusion; miscommunication on any taxi-clearances and instructions from that point of holding position on taxi-way Y to arriving in delay pad for RWY 22L. We remained in delay pad for RWY 22L for brakes to cool to temperature allowing for taxi and take-off. Following cooling of brakes; the flight was normal.
Data retrieved from NASA's ASRS site 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.