Narrative:

In anticipation of runway 27 arrival; the RNAV 27; lyndi three arrival; with tnp transition was entered into the mcdu prior to top of descent and briefed. What occurred on the arrival profile and not discovered was waypoint lucki with crossing constraint at or above 6100' was dropped out and replaced with zusub with crossing constraint at or above 5300'. All other waypoints and constraints on the lyndi three arrival remained as published. Socal approach cleared us to fly the RNAV 27 approach after lyndi. Descent was performed in managed descent mode and we crossed zusub at 5300' and lyndi at 5000' before selecting approach mode. ATC informed us at this point that we had missed the lucki crossing constraint of 6100' but this happens quiet often and was not a problem. After landing we re-entered the arrival and discovered lucki intersection had been replaced with zusub intersection with a lower altitude crossing restriction. Why was this approach constructed this way? It is a built in trap.do not fly the RNAV 27 approach! In order to comply with the lyndi three arrival you have to manually delete zusub intersection and manually insert lucki intersection with it's 6100' crossing restriction. This is contrary to how we normally load the mcdu and brief prior to top of descent in that it requires manual re-insertion of one published crossing restriction out of several on a busy arrival procedure. The san diego company page/chart should have a note of caution regarding this situation.

Google
 

Original NASA ASRS Text

Title: An A319 flight crew who had programmed the LYNDI RNAV STAR and the RNAV (GPS) Runway 27 approach to SAN were surprised when Approach Control advised they had failed to comply with STAR altitude restrictions at BARET and LUCKI waypoints and that LUCKI had; in fact; turned itself into the nearly co-located ZUSUB; a fix on the RNAV (GPS) approach. Review after landing determined that the waypoints and their restrictions on the STAR had autosequenced to 'similar' ones on the IAP but which included crossing altitudes of as much as 2;700 FT lower than their equivalent STAR crossings. Although they had not selected a 'VIA' mode; the changes were unilaterally (and repeatedly) altered by the FMGC.

Narrative: In anticipation of Runway 27 arrival; the RNAV 27; LYNDI THREE arrival; with TNP transition was entered into the MCDU prior to top of descent and briefed. What occurred on the arrival profile and not discovered was waypoint LUCKI with crossing constraint at or above 6100' was dropped out and replaced with ZUSUB with crossing constraint at or above 5300'. All other waypoints and constraints on the LYNDI THREE arrival remained as published. SOCAL Approach cleared us to fly the RNAV 27 approach after LYNDI. Descent was performed in managed descent mode and we crossed ZUSUB at 5300' and LYNDI at 5000' before selecting APPROACH mode. ATC informed us at this point that we had missed the LUCKI crossing constraint of 6100' but this happens quiet often and was not a problem. After landing we re-entered the arrival and discovered LUCKI intersection had been replaced with ZUSUB intersection with a lower altitude crossing restriction. Why was this approach constructed this way? It is a built in trap.Do not fly the RNAV 27 approach! In order to comply with the LYNDI THREE arrival you have to manually delete ZUSUB intersection and manually insert LUCKI intersection with it's 6100' crossing restriction. This is contrary to how we normally load the MCDU and brief prior to top of descent in that it requires manual re-insertion of one published crossing restriction out of several on a busy arrival procedure. The San Diego company page/chart should have a note of caution regarding this situation.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.