2022-02 · NASA ASRS report 1876136
A TRACON Controller and pilot reported the aircraft's new auto pilot malfunctioned while being vectored for an approach causing the aircraft to fly below the minimum vectoring altitude.
Aircraft X was being vectored for the RNAV Y Runway XXL approach in the downwind. I descended them to 032 and told them to turn right heading 250; they descended but didn't turn; and I had to reissue the turn immediately to avoid a higher MVA. Then when being told to turn right and maintain 032 cleared for the approach; Aircraft X began a descent; and I immediately issued a low altitude alert and told them to climb back to 3200 ft. I believe they got all the way down to 2400 ft. in a 032 MVA. When asked what happened Aircraft X said they were having avionics issues; some new function on his GPS wasn't working correctly. After they climbed back to 032; I recleared them with a turn and told them again to maintain 3200 ft. which they again descended below the MVA so I issued another low altitude alert. This happened 1 or 2 more times before I decided to just climb them to 5000 ft.; and began handing off the position to a new Controller; while briefing the new controller I noticed Aircraft X climbed through 5000 ft. so I issued them 6000 ft. The pilot was issued a possible pilot deviation once safely on the ground. I can't think of any [recommendations] since it seems to have been an aircraft equipment problem.
A new advanced digital autopilot was recently installed. Test flights had been done with a safety pilot and technician aboard; and all issues resolved. After the paperwork had been signed off; I was informed that Garmin had enabled a new functionality for this aircraft. VNAV; designed to fly a vertical profile from cruise to glideslope or path intercept; including stepdowns. This function was not test flown; but I later did read the STC (Supplemental Type Certificate) and pilot's handbook descriptions of the procedures.On the day in question; the flight had gone smoothly; with the new autopilot functioning perfectly. The conditions aloft were CAVU; but with a thin stratus layer over the destination in the Willamette Valley. RNAV Y XXL was in use; with VMC below the stratus. Given the conditions; I decided to try the new VNAV functionality of the autopilot. Approach gave me vectors and stepdown altitudes; and all seemed well at first; however; the autopilot did not capture the expected altitude at the turn to base. I attempted to re-select the correct altitude; but the autopilot continued a descent. When the Approach Controller called about the altitude; I used the TOGA (takeoff/go-around) switch to command an immediate climb; but the response was rather sluggish. When the Controller then issued a low-altitude alert I disconnected the autopilot; and climbed manually. All this in VMC above the stratus layer over the airport environment; with terrain in sight around the valley perimeter at all times; and the TAWS never alerted. After asking for a delay vector; I attempted the procedure again; with the same results. I then flew the procedure manually; and landed uneventfully. Ground Control asked me to call the Supervisor; which I did; explaining the situation.In hindsight; it would have been better to first fly the new functionality in a training environment; and not at the end of a cross-country on an IFR flight plan. Also; after the autopilot unexpectedly did not capture the stepdown altitude; I should have just taken over manually and entirely immediately; instead of continuing to attempt to adjust the autopilot; which just snowballed. My rationale for persisting was that the new functionality would have to be figured out sometime; and considering the weather; this was a good time to do it (VMC until the FAF; plenty of fuel left). I would decide differently in the future.
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.