Date: 202010
Local time of day: 1801-2400
Location: SJC.Airport, CA
Flight conditions: Marginal
Light: Night
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON NCT
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: After passing waypoint JILNA on the RNP Z RWY 30L a scratch pad message showed; check altitude constraint. Cross checking the altitude the airplane was at; it was descending through 6800-6900 MSL and the altitude restriction is at 7000. JILNA was a melded waypoint on our flight plan off of the BRIXX 2 RNAV Arrival; that had been melded once we were cleared for the approach. Breakdown in cross check during higher demand phase of flight. While also forgetting about pilot bulletin XXXXX-X. Which pertains to this situation. Section XX of the bulletin states: VNAV not complying with altitude constraint during approach. When the last waypoint of a STAR procedure is common to the first waypoint of the instrument approach procedure; the FMS may automatically meld the waypoints. The altitude constraints contained in both procedures for that particular waypoint is expected to be melded as well. In other scenarios; the last STAR waypoint contains a 'fly vectors to intercept' leg. This waypoint can also be the first one for the approach procedure and the pilot may manually delete the 'fly vectors' or copy the approach waypoint of the same waypoint on the STAR; which will also meld both waypoints.Embraer has received reports of the airplane not complying with the published altitude constraints during transition from STAR to instrument approach procedure. Investigations have revealed that an altitude violation may occur when two common waypoints are melded; either automatically by the FMS or manually by the pilot; where the last waypoint of the STAR and the first waypoint of the approach procedure has the same name; but different altitude constraints. As a consequence; the FMS constructed vertical flight path may not respect the altitude constraint; despite the altitude constraint indications of the FMS FLT PLAN page; VSD (Vertical Situation Display) and PFD (Primary Flight Display) are correctly displayed. The VNAV guidance may result in a constructed flight path above or below the published constraint. To prevent the violation of an altitude constraint; after a common waypoint is melded automatically by the FMS or manually by the pilot; perform as follows; Delete the altitude constraint at the melded waypoint; manually re-insert the altitude constraint in the FMS.




Synopsis: Air Carrier Flight Crew flying ERJ-175 aircraft report missing altitude restriction in descent.