AN ALLEGED ALTDEV ALT OVERSHOT CREATED A POTENTIAL CONFLICT LTSS WITH OPPOSITE DIRECTION TFC.

1993-02 · NASA ASRS report 235461

Date: 1993-02 · Aircraft: Medium Transport · Phase: climb

Anomalies: atc-issue-all-types|conflict-airborne-conflict|deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance|other-unspecified

Synopsis

AN ALLEGED ALTDEV ALT OVERSHOT CREATED A POTENTIAL CONFLICT LTSS WITH OPPOSITE DIRECTION TFC.

Narrative

ORIGINAL CLRNC TO FL350 BY MDLR TWR. AFTER TKOF; HANDED OFF TO STO DGO ON 124.3. HE REFUSED THE HDOF AND TOLD US TO CONTACT LAS AMERICAS APCH; 119.3. WE DID SO. 119.3 SAID 'CONTACT 124.3.' WE DID. 124.3 AGAIN TOLD US TO 'CONTACT LAS AMERICAS APCH 119.3.' WE AGAIN CONTACTED 119.3 -- HE ONCE AGAIN TOLD US TO CONTACT 124.3. EACH TIME I CHANGED FREQS I RPTED ESTIMATED POS AND 'CLBING TO FL350.' STO DGO FINALLY ACCEPTED US AND SIMPLY SAID 'ROGER.' HAVING ESTABLISHED WHAT I THOUGHT WAS POSITIVE ACKNOWLEDGEMENT AND CTL BY STO DGO; I HANDED RADIO CTL OF 124.3 TO CO-CAPT (PF) BY SAYING 'I'M OFF THE AIR TO TALK WITH MIAMI.' HE ACKNOWLEDGED WITH 'ROGER.' AT THIS TIME; APPROX XA30 LCL; I MADE CONTACT WITH MIAMI (132.3) AND WAS RPTED RADAR CONTACT 25 MI SE OF PTA. AS IT IS NECESSARY TO MAINTAIN COORD WITH MIAMI WHEN XING THEIR FIR; WE MAINTAINED THE 'SPLIT' RADIO CONFIGN (PF WITH STO DGO; AND ME WITH MIAMI). AT THIS TIME MIAMI GAVE ME OUR OCEANIC CLRNC AND WERE ALSO ASSIGNED FL350. SHORTLY AFTER PASSING PTA; MIAMI CALLED AND ASKED IF WE WERE CALLING. I REPLIED IN THE NEGATIVE. NO FURTHER CALLS WERE MADE BY US OR MIAMI UNTIL APPROX 3 MI S OF SEKAR (FIR). AT THIS TIME MIAMI CALLED AND RPTED 'TFC 12 O'CLOCK; OPPOSITE DIRECTION; FL330.' I AM SURE HE GAVE THE RANGE; BUT I DON'T REMEMBER IT NOW. I LOOKED OUT THE WINDSHIELD AND SAW THE TFC 12 O'CLOCK AND LOW. MY ALTIMETER AT THIS TIME READ 34200 FT AND WE WERE CLBING AT 1000 FPM AND IN A L TURN. JUST SECONDS PRIOR TO MIAMI CALLING THE TFC; STO DGO HAD CALLED THE CONFLICT AND PF WAS FOLLOWING HIS RA FROM THE TCASII AS WELL AS THE TURN TO 300 DEGS GIVEN BY STO DGO. PF LATER TOLD ME HE HAD OBSERVED THE TCASII TARGET FOR ABOUT 1 MIN PRIOR TO TA BY STO DGO AND WAS READY TO TAKE EVASIVE ACTION IF NECESSARY; EVEN WITHOUT ANY COMMANDS FROM ATC. STO DGO CTL ON 124.3 IS A VERY POOR QUALITY RADIO. WE HAD COMPLAINED UPON OUR ARR IN MDLR AND ALSO HEARD OTHER ACR FLT RPT RADIO AS 3X3. RADIO QUALITY NEEDS TO IMPROVE AS WELL AS HDOFS. STO DGO SAYS THAT WE WERE ONLY CLRED TO FL310; HOWEVER; I PERSONALLY NEVER HEARD SUCH A CLRNC AND NEITHER DID PF. ALL CLRNCS WERE RECEIVED AND READ BACK AS FL350.

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.