T75 APCH ISSUED VISUAL APCH CLRNC TO B767 CREW AT 5000 FT AND TO MAINTAIN VISUAL SEPARATION FROM COMPANY B767 LNDG ON THE PARALLEL RWY. WX AT STL ARPT AT THE TIME WAS 1300 FT OVCST; VISIBILITY 8 MI.

2002-10 · NASA ASRS report 564113

Date: 2002-10 · Aircraft: MD-80 Series (DC-9-80) Undifferentiated or Other Model

Anomalies: atc-issue-all-types|conflict-airborne-conflict|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-weather-turbulence

Synopsis

T75 APCH ISSUED VISUAL APCH CLRNC TO B767 CREW AT 5000 FT AND TO MAINTAIN VISUAL SEPARATION FROM COMPANY B767 LNDG ON THE PARALLEL RWY. WX AT STL ARPT AT THE TIME WAS 1300 FT OVCST; VISIBILITY 8 MI.

Narrative

AT 5000 FT MSL; ST LOUIS APCH ADVISED US WE WERE BEING VECTORED ACROSS THE LOC TO RWY 12R FOR TFC SEPARATION FROM A COMPANY B767. I HAD A VISUAL WITH THE B767 AND RELAYED THIS TO APCH CTL. HE GAVE US A 120 DEG HDG TO INTERCEPT THE LOC AND ASKED IF WE COULD MAINTAIN VISUAL WITH THE B767. AT OUR PRESENT POS; IT WAS EASY TO KEEP THE B767 IN SIGHT AND I ACKNOWLEDGED WE COULD. MY FO AND I WERE STILL EXPECTING TO BE CLRED FOR AN APCH BECAUSE STL WAS RPTING 1300 FT OVCST AND 8 MI VISIBILITY. UPON REACHING PAULEY INTXN; WE WERE STILL AT 5000 FT AND BEGINNING TO GO ABOVE THE GS. THE FREQ WAS CONGESTED; BUT FINALLY INQUIRED IF WE WERE CLRED FOR THE APCH. APCH RESPONDED WE WERE CLRED FOR THE VISUAL AND CONTACT TWR 118.5. BY THIS TIME WE WERE WAY ABOVE GS; 170 KTS; AND MY PRIORITY WAS TO DSND THIS AIRPLANE. EVEN WHEN APCH CLRED US FOR THE VISUAL AT 5000 FT; WE COULD SEE THE B767; BUT SOON LOST THE B767 AS HE DSNDED INTO THE OVCST. I BECAME CONCERNED THAT WE LOST VISUAL AND COULD TELL ON TCASII THAT WE WERE OVERTAKING THE B767. I TRIED TO CONTACT APCH; BUT THE FREQ WAS AGAIN CONGESTED. BY THIS TIME WE HAD DSNDED INTO THE OVCST AND WERE APCHING OBLILO; THE OM. I THEN CONTACTED TWR AND AFTER A SHORT DELAY; TWR INSTRUCTED US TO GO AROUND DUE TO INADEQUATE SEPARATION FROM THE B767. AT APPROX 1500 FT AGL; WE INITIATED THE GAR AND WERE GIVEN VECTORS BACK TO LAND UNEVENTFULLY ON RWY 12R. TWR SEEMED CONCERNED THAT WE DID NOT HAVE SEPARATION WITH THE B767 AND MY CONCERN IS THAT; UPON BEING VECTORED BACK TO STL; THE APCH CTLR REMARKED THAT TWR WAS UNAWARE THAT WE WERE ON A VISUAL APCH. I DID NOT DISCUSS WITH THE CTLR THE FACT WE WERE UNABLE TO CONTACT HIM TO ADVISE HIM WE HAD LOST VISUAL WITH THE B767. AFTER LNDG AND COMMUTING HOME; I REPLAYED THIS SCENARIO IN MY MIND AND REALIZED WHAT MAY HAVE CAUSED THIS SIT. WE WERE INBOUND ON THE TRAKE 8 ARR WITH A 50 KT OR MORE TAILWIND. ZKC GAVE US A CLRNC TO CROSS THE KAYLA ARC AT 11000 FT AND 250 KTS. WE WERE ON THE SGF TRANSITION AND I REQUESTED DIRECT FST. CTR CLRED US DIRECT; BUT I SOON REALIZED MY FO WAS NOT DSNDING AS RAPIDLY AS I HAD EXPECTED. I ADVISED ZKC WE WERE PROBABLY GOING TO MAKE KAYLA AT 11000 FT; BUT MAY NOT MAKE THE SPD. HE ADVISED ME TO DO THE BEST WE COULD AND SWITCHED US TO APCH CTL. I THINK APCH WAS THEN TRYING TO HANDLE THE DECREASED SEPARATION BY ISSUING US A VISUAL APCH. THIS IS WHERE THE BREAKDOWN IN COM HAPPENED. I DID HAVE THE B767 IN SIGHT; BUT NEVER CALLED STL IN SIGHT. WHEN I REALIZED APCH HAD CLRED ME FOR A VISUAL; MY WORKLOAD INCREASED BECAUSE WE WERE HIGH ON GS AND LOST CONTACT WITH THE B767. I FEEL APCH ISSUED A VISUAL TO KEEP THE FLOW OF TFC GOING; BUT WAS SURPRISED HE WOULD ISSUE A VISUAL WITH THE WX CONDITIONS GIVEN. SUPPLEMENTAL INFO FROM ACN 564680: THE CLOUD DECK CAUSED US TO LOSE THE B767 WHICH WE COULD NOT HAVE POSSIBLE VISUAL TO FOLLOW THROUGH THE CLOUDS. WE EVENTUALLY WENT AROUND. IT WAS WRONG FOR THE CTLR TO USE THIS CLRNC AND WRONG FOR US TO ACCEPT IT.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.