 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reported ord tower canceled the takeoff clearance on runway 22L because of conflicting landing traffic on runway 28C.
| Attributes | |
| ACN | 1455328 |
| Time | |
| Date | 201706 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ORD.Airport |
| State Reference | IL |
| Environment | |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Widebody Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe |
Narrative:
After being cleared for takeoff on runway 22L at ord we began our takeoff roll. Between 40 and 50 knots the tower canceled our takeoff clearance and told us to hold our position. We aborted our takeoff roll using very little brakes and noticed a aircraft that was landing on runway 28C in front of us. Before we were able to stop completely; the tower directed us to turn right at taxiway Y; cross runway 28C; turn right onto november; and cleared us for takeoff again. We did not have a high speed abort; and I used very little braking to slow the aircraft; therefore; the use of the brake cooling charts were not required. We had an uneventful takeoff and continued. During climbout; when time permitted; I contacted the ord tower and spoke with a controller who said that there was no conflict with us and the aircraft because the aircraft did not fly over top of us. The tower was able to avert a potential mishap by quickly canceling our takeoff clearance. This event is highly unusual for ord and [I] felt it warranted review.the event happened because ord tower cleared me for takeoff too soon. They should have waited for the aircraft to land first.
Original NASA ASRS Text
Title: B737 flight crew reported ORD Tower canceled the takeoff clearance on Runway 22L because of conflicting landing traffic on Runway 28C.
Narrative: After being cleared for takeoff on Runway 22L at ORD we began our takeoff roll. Between 40 and 50 knots the Tower canceled our takeoff clearance and told us to hold our position. We aborted our takeoff roll using very little brakes and noticed a aircraft that was landing on Runway 28C in front of us. Before we were able to stop completely; the Tower directed us to turn right at taxiway Y; cross Runway 28C; turn right onto November; and cleared us for takeoff again. We did not have a high speed abort; and I used very little braking to slow the aircraft; therefore; the use of the brake cooling charts were not required. We had an uneventful takeoff and continued. During climbout; when time permitted; I contacted the ORD Tower and spoke with a Controller who said that there was no conflict with us and the aircraft because the aircraft did not fly over top of us. The Tower was able to avert a potential mishap by quickly canceling our takeoff clearance. This event is highly unusual for ORD and [I] felt it warranted review.The event happened because ORD Tower cleared me for takeoff too soon. They should have waited for the aircraft to land first.
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.