ERJ175 Captain reports missing an assigned crossing restriction of 12;000 FT on the CLIPR 1 RNAV to DCA after the FMS has been programmed to comply with clearance. The flight is then cleared direct to BAL and programmed by the Captain. A few moments later the aircraft is found to be proceeding direct to EYESS and the crew is again questioned by ATC.

2011-06 · NASA ASRS report 952659

Date: 2011-06 · Aircraft: EMB ERJ 170/175 ER/LR · Phase: descent

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

Synopsis

ERJ175 Captain reports missing an assigned crossing restriction of 12;000 FT on the CLIPR 1 RNAV to DCA after the FMS has been programmed to comply with clearance. The flight is then cleared direct to BAL and programmed by the Captain. A few moments later the aircraft is found to be proceeding direct to EYESS and the crew is again questioned by ATC.

Narrative

Flight at FL220 ATC assigned us to cross CLIPR at FL120. MCDU was programmed by non flying pilot and verified by pilot flying. It was also observed to be correct by the non flying pilot on the vertical profile. Aircraft was stable on VNAV descent; when we were questioned by ATC about our crossing restriction issued. When we both looked at our flight status; we were over CLIPR at FL132. Approximately 1;200 FT MSL off altitude. We were issued a heading for vectors to continue to FL100 due to this deviation. After the heading we were re-cleared direct to BAL. The pilot flying set the MCDU and the non flying pilot confirmed. The aircraft was put into LNAV mode and began heading in the proper direction. A few moments later we noticed we were off course again. The MCDU had dropped out BAL and replaced it with direct EYESS. ATC then questioned our navigation once again. We notified them we were having some navigational issues and corrected course again. The aircraft was placed in LNAV mode to re-intercept the course from PPOS [present position]. After the FMA indicated capture of LNAV; the aircraft was still under command of the heading bug for a few moments. After this; navigation was normal again and the flight was completed with no further issues or incidents.

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.