 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 captain starts taxiing across runway after hearing what he believed he was told to do by tower controller causing another B737 to go around.
| Attributes | |
| ACN | 558779 |
| Time | |
| Date | 200209 |
| Day | Mon |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : cle.airport |
| State Reference | OH |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| 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 | Regional Jet CL65, Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : position and hold |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 240 flight time total : 20000 |
| ASRS Report | 558779 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | conflict : ground less severe ground encounters other incursion : runway non adherence : clearance |
| Independent Detector | other controllera |
| Resolutory Action | controller : separated traffic flight crew : executed go around |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Airport ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Flight had been holding on runway 28, short of runway 24L (cle). Tower cleared flight to expedite across runway 24L for takeoff on runway 24C. However, an rj was still holding in position on runway 24C at position #1 on end of runway 24C. Rj had not moved, nor had been cleared for takeoff. B737 was on approach to runway 24L. We stopped at the intersection of runway 28 and runway 24L. We thought rj would be rolling on runway 24C. He still had not. We were not in a position to turn right on runway 24L to position #2 on taxi chart. Cle tower told B737 to go around. I (captain) thought I heard tower to initially say expedite across runway 24L for runway 24R which would be the new or closed runway, which caused me to be at the intersection of runway 28/runway 24L. I believe the controller could have erroneously called for runway 24C, runway 24R.
Original NASA ASRS Text
Title: B737 CAPT STARTS TAXIING ACROSS RWY AFTER HEARING WHAT HE BELIEVED HE WAS TOLD TO DO BY TWR CTLR CAUSING ANOTHER B737 TO GO AROUND.
Narrative: FLT HAD BEEN HOLDING ON RWY 28, SHORT OF RWY 24L (CLE). TWR CLRED FLT TO EXPEDITE ACROSS RWY 24L FOR TKOF ON RWY 24C. HOWEVER, AN RJ WAS STILL HOLDING IN POS ON RWY 24C AT POS #1 ON END OF RWY 24C. RJ HAD NOT MOVED, NOR HAD BEEN CLRED FOR TKOF. B737 WAS ON APCH TO RWY 24L. WE STOPPED AT THE INTXN OF RWY 28 AND RWY 24L. WE THOUGHT RJ WOULD BE ROLLING ON RWY 24C. HE STILL HAD NOT. WE WERE NOT IN A POS TO TURN R ON RWY 24L TO POS #2 ON TAXI CHART. CLE TWR TOLD B737 TO GO AROUND. I (CAPT) THOUGHT I HEARD TWR TO INITIALLY SAY EXPEDITE ACROSS RWY 24L FOR RWY 24R WHICH WOULD BE THE NEW OR CLOSED RWY, WHICH CAUSED ME TO BE AT THE INTXN OF RWY 28/RWY 24L. I BELIEVE THE CTLR COULD HAVE ERRONEOUSLY CALLED FOR RWY 24C, RWY 24R.
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.