2023-07 · NASA ASRS report 2020758
Air carrier First Officer reported they descended 500 feet below glideslope and had a track heading deviation during approach. Reportedly; the FO did not enter the missed approach altitude at the right time and there was confusion over who had control of the aircraft during the event.
ATC instructed us to turn left heading 260 and descend down to 2;000 feet until established on the localizer for ILS XXL at ZZZ. First Officer (FO) selected 260 on the heading selector followed by NAV mode. FO then selected the altitude of 2;000 ft. followed by VS. Localizer for ILS XXL was captured. FO asked Captain (CA) if we were cleared for the approach. Captain replied yes. FO selected APP and armed the approach. FO selected the missed approach altitude of 3;000 ft. prior to capturing the glideslope as aircraft was descending towards 2;000 ft. Aircraft started to descend below 2;000 ft. and CA said we did not capture the glideslope. FO selected ALT. CA took the controls. Autopilot was overridden by Captain's input on the yolk. FO mentioned that we were off course of the approach and descending even lower. Captain asked to rearm the approach. Aircraft continued descending and was off course. Undesired aircraft state was potentially 500 ft. below flightpath at one point. Captain then said; 'my controls.' There was confusion over who had the controls when Captain took the controls prior to stating; 'my controls.' CA asked for autopilot to be reengaged again. Aircraft's flight path was eventually stabilized on the approach prior to 1;000 ft. CA asked if FO wanted the controls to land the aircraft. FO agreed and took the controls and landed the aircraft safely. Captain and First Officer debriefed at the completion of the flight and discussed what mistakes were made on both ends. FO realized selecting the missed approach altitude prior to FAF during the descent to the previously cleared altitude was incorrect. FO selected the missed approach altitude prior to FAF during the descent to the previously cleared altitude. Confusion was also created when captain took controls of the aircraft overriding the autopilot; without stating 'my controls'. Waiting to set the missed approach altitude at the correct time; after descending to at least 300 ft. below FAF altitude. FO could use CRM and delegate to CA to set missed approach altitude when needed if task saturated. Both PF/PM should delineate who has controls of the aircraft if confusion exists. A missed approach should be initiated if aircraft is not stabilized on the approach or aircraft was found in an undesired aircraft state rather than continuing with the approach
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.