37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 320310 |
Time | |
Date | 199511 |
Day | Sat |
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 | B737-500 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 180 flight time total : 10500 flight time type : 2800 |
ASRS Report | 320310 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | other |
Narrative:
Ord tower was departing aircraft on runway 22L and arrival aircraft on runway 27L. We were taxiing on taxiway D behind a DC10 towards runway 22L on ord tower frequency. The DC10 was not ready for takeoff and was told to pull into the run-up pad. Tower told us to continue to the runway he was going to get us right out. As we approached runway 22L, the tower controller pointed out arrival traffic 2 mi out on runway 27L. He told us to keep it rolling and cleared us for takeoff on runway 22L, reference the landing traffic 2.0 mi out for runway 27L, or if we couldn't keep it rolling to hold short of runway 22L. We accepted the takeoff clearance and kept the aircraft rolling and departed runway 22L. The sequencing appeared to work ok but on thinking about it further, later in the flight, it probably would have been more prudent to hold short and not accept the takeoff clearance. Ord does an excellent job of sequencing traffic. It was the last leg of a 3 day trip, we were thinking we were helping the controller out, he was probably thinking he was doing us a favor helping to get us out more quickly. And in hindsight I wouldn't accept that clearance again, as it was below my personal comfort factor.
Original NASA ASRS Text
Title: CAPT OF AN MLG QUESTIONS HIS JUDGEMENT IN ACCEPTING AN EXPEDITED TKOF CLRNC FROM TWR SINCE THE FLC MAY MISS SOMETHING IMPORTANT BEFORE TKOF.
Narrative: ORD TWR WAS DEPARTING ACFT ON RWY 22L AND ARR ACFT ON RWY 27L. WE WERE TAXIING ON TXWY D BEHIND A DC10 TOWARDS RWY 22L ON ORD TWR FREQ. THE DC10 WAS NOT READY FOR TKOF AND WAS TOLD TO PULL INTO THE RUN-UP PAD. TWR TOLD US TO CONTINUE TO THE RWY HE WAS GOING TO GET US RIGHT OUT. AS WE APCHED RWY 22L, THE TWR CTLR POINTED OUT ARR TFC 2 MI OUT ON RWY 27L. HE TOLD US TO KEEP IT ROLLING AND CLRED US FOR TKOF ON RWY 22L, REFERENCE THE LNDG TFC 2.0 MI OUT FOR RWY 27L, OR IF WE COULDN'T KEEP IT ROLLING TO HOLD SHORT OF RWY 22L. WE ACCEPTED THE TKOF CLRNC AND KEPT THE ACFT ROLLING AND DEPARTED RWY 22L. THE SEQUENCING APPEARED TO WORK OK BUT ON THINKING ABOUT IT FURTHER, LATER IN THE FLT, IT PROBABLY WOULD HAVE BEEN MORE PRUDENT TO HOLD SHORT AND NOT ACCEPT THE TKOF CLRNC. ORD DOES AN EXCELLENT JOB OF SEQUENCING TFC. IT WAS THE LAST LEG OF A 3 DAY TRIP, WE WERE THINKING WE WERE HELPING THE CTLR OUT, HE WAS PROBABLY THINKING HE WAS DOING US A FAVOR HELPING TO GET US OUT MORE QUICKLY. AND IN HINDSIGHT I WOULDN'T ACCEPT THAT CLRNC AGAIN, AS IT WAS BELOW MY PERSONAL COMFORT FACTOR.
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.