37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 476585 |
Time | |
Date | 200006 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : ord.airport |
State Reference | IL |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | MD-80 Super 80 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 14r |
Flight Phase | landing : roll |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : ord.tower |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : takeoff roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 476585 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : instrument pilot : commercial |
Events | |
Anomaly | conflict : ground less severe ground encounters other inflight encounter : weather inflight encounter other non adherence : published procedure non adherence : far other anomaly other |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | other |
Supplementary | |
Problem Areas | Weather ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Situations | |
ATC Facility | procedure or policy : ord.tower |
Narrative:
Possible landing and departing conflict at ord. We landed on runway 14R at ord. The ATIS had lahso operations for runway 14R and 27L, however, tower never asked us to lnd 14R and hold short of runway 27L. Because the wind conditions were strong and gusty, I would not have accepted that clearance anyway. Shortly after we landed, and still on the runway traveling over 120 KTS, the tower controller cleared another flight for takeoff on runway 27L. Although we turned off prior to the runway intersection, I thought we had permission to use the entire runway. After clearing the runway, I asked the controller about clearing a takeoff on 27L while we were still on the runway, and he said it was perfectly legal and if I had a problem, I should call the tower. Typical ord attitude. My questions is, if I have not accepted a lahso clearance on 14R, is the tower authorized to clear a runway 27L takeoff while we are still traveling at a fast speed. If that is true, could that information be made public to pilots operating into and out of ord.
Original NASA ASRS Text
Title: MD80 WAS CLRED TO LND ON RWY 14R AT ORD. WHILE STILL ROLLING OUT TWR CTLR CLRED ACFT FOR TKOF ON 27L.
Narrative: POSSIBLE LNDG AND DEPARTING CONFLICT AT ORD. WE LANDED ON RWY 14R AT ORD. THE ATIS HAD LAHSO OPS FOR RWY 14R AND 27L, HOWEVER, TWR NEVER ASKED US TO LND 14R AND HOLD SHORT OF RWY 27L. BECAUSE THE WIND CONDITIONS WERE STRONG AND GUSTY, I WOULD NOT HAVE ACCEPTED THAT CLRNC ANYWAY. SHORTLY AFTER WE LANDED, AND STILL ON THE RWY TRAVELING OVER 120 KTS, THE TWR CTLR CLEARED ANOTHER FLIGHT FOR TKOF ON RWY 27L. ALTHOUGH WE TURNED OFF PRIOR TO THE RWY INTXN, I THOUGHT WE HAD PERMISSION TO USE THE ENTIRE RWY. AFTER CLEARING THE RWY, I ASKED THE CTLR ABOUT CLEARING A TKOF ON 27L WHILE WE WERE STILL ON THE RWY, AND HE SAID IT WAS PERFECTLY LEGAL AND IF I HAD A PROB, I SHOULD CALL THE TWR. TYPICAL ORD ATTITUDE. MY QUESTIONS IS, IF I HAVE NOT ACCEPTED A LAHSO CLRNC ON 14R, IS THE TWR AUTHORIZED TO CLEAR A RWY 27L TKOF WHILE WE ARE STILL TRAVELING AT A FAST SPEED. IF THAT IS TRUE, COULD THAT INFO BE MADE PUBLIC TO PLTS OPERATING INTO AND OUT OF ORD.
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.