2000-10 · NASA ASRS report 488355
CL65 FLC TAXI ACROSS STL RWYS 30L&R WITH TFC ON FINAL. DISCUSSION WITH TWR DETERMINED ATC MISSED INCORRECT READBACK.
WE HAD JUST COMPLETED A REVENUE FLT AND HAD UNLOADED OUR PAX AT THE GATE. CTL INSTRUCTED US TO TAXI VIA TXWY A TO TXWY N TO HOLD SHORT OF RWY 30L. WE DID SO; AND HELD SHORT OF RWY 30L FOR APPROX 2 MINS. IT WAS OBVIOUS THE GND CTLR FORGOT ABOUT US; SO WE REMINDED HIM THAT WE WERE HOLDING SHORT. THERE WAS 1 ACFT ON A LONG FINAL TO WHAT APPEARED TO US TO BE RWY 30L. THE CTLR CAME BACK WITH SOMETHING LIKE 'CROSS RWY 30L&R TO THE RAMP.' MY FO READ BACK 'ROGER; CROSS RWY 30L&R.' WE EXPEDITED ACROSS RWY 30L&R; UTILIZING OUR STANDARD CRM PROC AS WE APCHED EACH RWY HOLD LINE OF CONFIRMING WITH EACH OTHER THAT WE WERE 'CLRED TO CROSS AND CLR L AND R' WHILE VISUALLY SCANNING THE DEP/ARR PATHS. WHEN WE WERE 1/2 WAY ACROSS RWY 30R; THE GND CTLR (WHO I BELIEVE WAS ALSO WORKING THE TWR FREQ AT THAT LATE HR) QUERIED 'ACR X; ARE YOU HOLDING SHORT RWY 30R?' THEN CAME BACK WITH 'EXPEDITE ACROSS; THERE'S TFC ON SHORT FINAL TO RWY 30R.' WHEN WE WERE SAFELY ACROSS; I STATED THAT MY FO HAD READ BACK THE CLRNC TO CROSS BOTH RWYS. WE WERE TOLD TO CALL THE TWR; WHICH WE DID AFTER SECURING THE ACFT FOR THE NIGHT. WHEN I CALLED THE TWR; THE GND CTLR APOLOGIZED AND SAID THAT HE REALIZED THAT HE HAD FAILED TO CORRECT THE READBACK AFTER HE RAN DOWN AND LISTENED TO THE TAPES OF THE RADIO XMISSIONS. HE STATED THAT HIS ORIGINAL CLRNC WAS TO CROSS RWY 30L AND HOLD SHORT OF RWY 30R; AND THAT THE FO READ BACK TO CROSS BOTH RWYS; AND THAT HE NEVER CAUGHT THE ERROR. I DON'T BELIEVE THAT THERE WAS ANY SERIOUS LOSS OF SEPARATION IN THIS INCIDENT; AS THE LNDG TFC WAS STILL SEVERAL MI OUT ON FINAL; WHICH WE CONFIRMED BY DOING A VISUAL CHK BEFORE XING. FACTORS WHICH CONTRIBUTED TO THIS BREAKDOWN IN SAFETY INCLUDED THE TWR'S ORIGINAL UNCLR XMISSION; WHICH BOTH THE FO AND MYSELF MISUNDERSTOOD; AS WELL AS THE CTLR'S FAILURE TO GET THE STANDARD HOLD SHORT READBACK REQUIRED WHEN ASKED TO HOLD SHORT OF A RWY. I BELIEVE THAT A SAFER PROC WOULD INVOLVE REQUIRING VERBAL CONFIRMATION FOR XING EVERY RWY; ALTHOUGH THIS MAY NOT BE FEASIBLE AT A BUSY ARPT LIKE STL; WHERE FREQ CONGESTION ON THE RADIO IS AN ADDED PROB. PERHAPS AN ALTERNATE IDEA TO IMPROVE SAFETY ON THE GND WOULD BE A STOP/GO LIGHT SYS FOR CLRNC TO CROSS AT EVERY TXWY/ACTIVE RWY INTXN; ALLEVIATING THE NEED FOR RADIO COMS ALTOGETHER.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.