37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 559176 |
Time | |
Date | 200209 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : cle.airport |
State Reference | OH |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : cle.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 : first officer |
Qualification | pilot : flight engineer pilot : cfi pilot : atp pilot : multi engine |
Experience | flight time last 90 days : 210 flight time total : 10700 flight time type : 3200 |
ASRS Report | 559176 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : clearance |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : separated traffic flight crew : executed go around |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Cle's runway layout at the approach end of runway 24L is confusing at best, and was worsened in our situation where the tower controller cleared us into position on runway 24C while another aircraft was on a 2 mi final. Aircraft awaiting takeoff on runway 24C are required to taxi on runway 28 and eventually cross runway 24L to get there. Another aircraft was holding in position on runway 24C. We were cleared to 'cross runway 24L, taxi into position and hold on runway 24C.' unfortunately, the controller cleared the aircraft holding on runway 24C for takeoff after he cleared us to taxi into position on runway 24C. We started across runway 24L and realized this wouldn't work because the previous aircraft hadn't started moving. We were forced to stop on runway 24L. The airplane on a 2 mi final was now about 1 mi and was told to go around by the controller. At no time was there any danger of a collision, but the airplane holding on runway 24C should've been cleared for takeoff first. In the future, I will hesitate to start my taxi into position until the aircraft ahead begins to move. Complicating matters was the fact that the airplane on final (a B737) was fairly close in, and we had to move quickly to make things work out. Callback conversation with reporter revealed the following information: reporter stated taxiing at cle airport is very confusing because of the construction in progress. When asked if the controller expected them to taxi around the approach end to runway 24C, the reporter said they should have referred to the airport chart before taxiing. He said he now understands why the controller issued a clearance to cross runway 24L and taxi into position and hold on runway 24C.
Original NASA ASRS Text
Title: B737-300 CREW AT CLE MAY HAVE MISUNDERSTOOD THE CTLR'S INSTRUCTIONS WHEN TOLD TO CROSS RWY 24L AND INTO POS ON RWY 24C.
Narrative: CLE'S RWY LAYOUT AT THE APCH END OF RWY 24L IS CONFUSING AT BEST, AND WAS WORSENED IN OUR SIT WHERE THE TWR CTLR CLRED US INTO POS ON RWY 24C WHILE ANOTHER ACFT WAS ON A 2 MI FINAL. ACFT AWAITING TKOF ON RWY 24C ARE REQUIRED TO TAXI ON RWY 28 AND EVENTUALLY CROSS RWY 24L TO GET THERE. ANOTHER ACFT WAS HOLDING IN POS ON RWY 24C. WE WERE CLRED TO 'CROSS RWY 24L, TAXI INTO POS AND HOLD ON RWY 24C.' UNFORTUNATELY, THE CTLR CLRED THE ACFT HOLDING ON RWY 24C FOR TKOF AFTER HE CLRED US TO TAXI INTO POS ON RWY 24C. WE STARTED ACROSS RWY 24L AND REALIZED THIS WOULDN'T WORK BECAUSE THE PREVIOUS ACFT HADN'T STARTED MOVING. WE WERE FORCED TO STOP ON RWY 24L. THE AIRPLANE ON A 2 MI FINAL WAS NOW ABOUT 1 MI AND WAS TOLD TO GO AROUND BY THE CTLR. AT NO TIME WAS THERE ANY DANGER OF A COLLISION, BUT THE AIRPLANE HOLDING ON RWY 24C SHOULD'VE BEEN CLRED FOR TKOF FIRST. IN THE FUTURE, I WILL HESITATE TO START MY TAXI INTO POS UNTIL THE ACFT AHEAD BEGINS TO MOVE. COMPLICATING MATTERS WAS THE FACT THAT THE AIRPLANE ON FINAL (A B737) WAS FAIRLY CLOSE IN, AND WE HAD TO MOVE QUICKLY TO MAKE THINGS WORK OUT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED TAXIING AT CLE ARPT IS VERY CONFUSING BECAUSE OF THE CONSTRUCTION IN PROGRESS. WHEN ASKED IF THE CTLR EXPECTED THEM TO TAXI AROUND THE APCH END TO RWY 24C, THE RPTR SAID THEY SHOULD HAVE REFERRED TO THE ARPT CHART BEFORE TAXIING. HE SAID HE NOW UNDERSTANDS WHY THE CTLR ISSUED A CLRNC TO CROSS RWY 24L AND TAXI INTO POS AND HOLD ON RWY 24C.
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.