B767 CREW WAS REQUIRED TO EXECUTE A GAR DUE TO BEING TOO HIGH FOR THE APCH.

2000-05 · NASA ASRS report 474282

Date: 2000-05 · Aircraft: B767-300 and 300 ER · Phase: descent

Anomalies: conflict-airborne-conflict|other-poor-atc-altitude-ctl

Synopsis

B767 CREW WAS REQUIRED TO EXECUTE A GAR DUE TO BEING TOO HIGH FOR THE APCH.

Narrative

FLT WAS BEING VECTORED BY ATL APCH CTL FOR AN APCH AND LNDG ON RWY 26R. WX WAS GOOD; BUT VERY HAZY. THE FO WAS FLYING. THE ALT DSCNTS AFTER LEAVING THE MACEY STAR WERE ALL ISSUED LATE OR DELAYED FOR UNKNOWN REASONS: TO 8000 FT; THEN 6000 FT; THEN 5000 FT; FINALLY TO 2800 FT WITH INSTRUCTIONS TO RPT THE FIELD IN SIGHT. THE CTLR DELAYS IN ISSUING DSCNT CLRNCS PUT THE ACFT HIGH AND BEHIND SCHEDULE APPROPRIATE TO AN APCH AND LNDG ON RWY 26R. AT THIS POINT; I WAS UNCLR AS TO WHAT WOULD HAPPEN NEXT. HAVING LANDED IN ATL WITHIN THE LAST 6 MONTHS WHEREBY I WAS BROUGHT IN SIMILARLY AND THEN VECTORED E WHILE DSNDING; FOLLOWED BY A R BASE; AND THEN TO INTERCEPT THE FINAL APCH COURSE FOR RWY 26R; I HAD THIS SCENARIO IN MIND. THE CTLR NEVER SAID OUR 'SEQUENCE;' NOR HER INTENTIONS; SO WHEN SHE GAVE THE FINAL VECTOR TO INTERCEPT AND RPT THE FIELD IN SIGHT; I WAS SURPRISED; PRIMARILY DUE TO THE ALT; WHICH WAS INAPPROPRIATE FOR MAKING AN APCH AND LNDG ON RWY 26R AT THAT POINT. AT THAT POINT WE APCHED 'ABEAM' THE OM; JUST LEAVING 5000 FT; WE STILL DID NOT SEE THE RWY DUE TO HAZE. THE FO WAS FLYING AND HAD THE AIRPLANE SLOWED UP APPROPRIATELY AND ANTICIPATORILY; DESPITE THE LATE DSCNTS GIVEN BY APCH CTL. THE FINAL VECTOR (240 DEGS TO INTERCEPT AS I RECALL) CAME ABOUT THE TIME THAT ALL 3 PLTS SAW OUR RELATIONSHIP TO THE RWY; WHICH WAS TOO HIGH; AND THE CTLR MUST HAVE SENSED SOMETHING WAS A BIT WRONG; TOO; AS SHE ASKED IF WE NEEDED A VECTOR TO GET DOWN. IT WAS A BUSY TIME FOR US AS WE INITIALLY TRIED TO SALVAGE THE APCH; PUT THE LNDG GEAR DOWN; INCREASED THE SPD BREAK DEPLOYMENT; ETC. I RECALL RESPONDING TO ATC 'WE'RE PRETTY HIGH;' AT WHICH POINT THE CTLR SAID TO FLY A 180 DEG HDG. THE CTLR ALSO RESPONDED WITH 'SORRY ABOUT THAT.' WE WERE PASSING THROUGH THE RWY 26R LOC BY NOW; AND THAT DID NOT SEEM LIKE A PRUDENT THING TO DO. ABOUT THIS TIME; I NOTICED OUR APCH OVERHEAD A B757 WELL BENEATH US LINED UP WITH RWY 27L. THE FO STATED THAT WE SHOULD GO AROUND. I CONCURRED; AND HE PROCEEDED WITH THE GAR PROC. AS HE APPLIED PWR; I STOWED THE SPD BRAKES. OUR FLAPS WERE 20 DEGS AT THE TIME; AND WE RAISED THE GEAR. SINCE THERE WAS QUICK DISCUSSION IN THE COCKPIT ABOUT THE HEADING WHICH WOULD PUT US INTO THE APCH PATH OF THE PARALLEL RWYS; AND WE ALSO BEGAN A TURN BACK TOWARD OUR OWN RWY. DURING THE INITIAL PHASE OF THE GAR PROC AFTER SPOTTING THE B757 BELOW US; WE HEARD A TCASII TA MOMENTARILY; THIS WAS PROBABLY DUE TO OUR SINK RATE AT THE TIME. IT WAS NOT AN RA; IT WAS A TA ONLY. BASED ON MY VISUAL ESTIMATION ONLY; I DO NOT BELIEVE WE WERE EVER CLOSER THAN 1000 FT SEPARATION. (THE TA WAS MOMENTARILY ONLY.) I IMMEDIATELY TOLD ATC THAT WE WERE GOING AROUND BECAUSE WE WERE TOO HIGH. A NEW CTLR HAD TAKEN OVER; AND ASKED ME WHAT HEADING I WAS ON; AND I RESPONDED SOMETHING LIKE 290 DEGS. HE SAID THAT WAS FINE; AND THEN TO TURN R TO 360 DEGS; CLB TO 4000 FT. WE COMPLIED; AND RE-ENTERED ANOTHER R DOWNWIND FOR RWY 26R; WHERE WE WERE FIRST IN SEQUENCE FOR THE APCH. A FEW MORE VECTORS AND A NORMAL APCH AND LNDG WERE MADE ON RWY 26R. NO FURTHER MENTION OF ANY OF THIS WAS MADE BY ANY ATC CTLR. HINDSIGHT WOULD HAVE MADE ME MORE AGGRESSIVE IN MY QUESTIONING OF THE CTLR'S INTENTIONS WITH KEEPING US HIGH AND DELAYING THE DSCNT CLRNCS; AS WELL AS OBTAINING OUR VECTORING OR APCH SEQUENCING. THE GAR AND TURN BACK TOWARD THE ORIGINAL RWY ALIGNMENT WAS A PRUDENT MANEUVER WHICH SEEMED TO MEET ATC'S SATISFACTION AS WELL. MY OTHER CREW MEMBERS PERFORMED THEIR DUTIES IN A VERY SATISFACTORY MANNER DURING THIS EVENT. I HAVE NO INTENTIONS OF PURSUING ANY OF THIS FURTHER; AND HAVE FILED THIS NASA RPT IN THE INTEREST OF SAFETY.

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.