Air Carrier pilot reported autopilot changed from VNAV to Control Wheel Pitch and increased their descent rate; descending below the published crossing altitude at CRCUS on the ANGLL4 RNAV Arrival to LAX. The reporter stated the same issue occurred with the preceding aircraft on the same STAR.

2022-06 · NASA ASRS report 1906855

Date: 2022-06 · Aircraft: Boeing Company Undifferentiated or Other Model · Phase: descent

Anomalies: aircraft-equipment-problem-less-severe|deviation-altitude-crossing-restriction-not-met|deviation-discrepancy-procedural-clearance

Synopsis

Air Carrier pilot reported autopilot changed from VNAV to Control Wheel Pitch and increased their descent rate; descending below the published crossing altitude at CRCUS on the ANGLL4 RNAV Arrival to LAX. The reporter stated the same issue occurred with the preceding aircraft on the same STAR.

Narrative

Approaching the CRCUS fix; the aircraft suddenly began a rather aggressive descent of over 4;000 fpm. Crew recognized and noted this. The aircraft was showing on path with no other anomalies noted which raised some confusion with the Crew as the aircraft was not showing off path or high. The closer we got to the fix we realized the aircraft was going to go below the 12;000 [ft.] MSL limit at CRCUS. At about the time the F/O (First Officer) began to intervene; the aircraft disconnected VNAV and went into control wheel pitch mode. VNAV Disconnect was not displayed in the scratchpad and no other indications were noted; it simply reverted modes unannounced and without warning. The F/O corrected the rate of descent smoothly; which led to a 300 [ft.] low excursion over CRCUS. The altitude was quickly corrected and the flight proceeded normally. ATC did call and ask about the deviation. We responded and explained the anomaly; no separation problems were noted and ATC did not seem to concerned. As an important note. The aircraft ahead of us was (other carrier) Aircraft Y [Same Aircraft Model]. When he heard our situation; he also communicated to ATC that the exact same thing happened to them. Their VNAV erroneously disconnected over CRCUS and they were forced to intervene with Vertical Speed mode.It appears due to two aircraft experiencing the same problem at the same time there may be a programming or database problem near CRCUS.

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.