Narrative:

Due to strong gusty winds out of west; ATIS advised stadium visual approach runway 29; runway 22 for takeoff. The FMC did not contain the approach; so we built it as depicted. We put in altitudes and speeds for all fixes and threshold runway 29. The jeppfd-pro chart has nothing for slimr fix; so we put in a target so we would be stable prior and to avoid a 'slam dunk' approach. We planned on turning west and acquired the PAPI's and continuing; [but] never got to that point. On descent after gimee; ATC advised us of an altitude alert. First officer (first officer) stopped descent. As we turned west toward chumr and runway 29; got an obstacle caution/warning. We were stable at 1000' and fully configured. Executed a go around; got vectors to ILS 22L; uneventful landing. [Another air carrier] following us on the stadium visual also received an altitude alert from ATC about the time we were executing the go around. Found it odd that 2 consecutive carriers would have altitude alerts in the same area; possible altimeter issue with ATC? As a GA pilot I compared the jepp chart with the foreflight chart and found the foreflight chart had an additional target altitude 1500-2500' at slimr/lincoln park; the jeppfd-pro chart has no such target altitude. This would have been helpful; believe we would have been higher at slimr. Not sure if this was an oversight or omission by jepp or a well advised addition by nos. We are jepp certified and I only checked foreflight just out of curiosity after the flight. I was informed that [the other air carrier] also uses jeppfd-pro; so it may have been a similar issue as well.

Related reports:

Google
 

Original NASA ASRS Text

Title: B767-300 flight crew reported executing a go-around after receiving a low altitude alert from the Tower during the Stadium Visual to EWR Runway 29.

Narrative: Due to strong gusty winds out of west; ATIS advised Stadium Visual approach Runway 29; Runway 22 for takeoff. The FMC did not contain the approach; so we built it as depicted. We put in altitudes and speeds for all fixes and threshold Runway 29. The JeppFD-Pro chart has nothing for SLIMR fix; so we put in a target so we would be stable prior and to avoid a 'slam dunk' approach. We planned on turning west and acquired the PAPI's and continuing; [but] never got to that point. On descent after GIMEE; ATC advised us of an altitude alert. First Officer (FO) stopped descent. As we turned west toward CHUMR and Runway 29; got an obstacle caution/warning. We were stable at 1000' and fully configured. Executed a go around; got vectors to ILS 22L; uneventful landing. [Another air carrier] following us on the Stadium Visual also received an altitude alert from ATC about the time we were executing the go around. Found it odd that 2 consecutive carriers would have altitude alerts in the same area; possible altimeter issue with ATC? As a GA pilot I compared the Jepp chart with the Foreflight chart and found the Foreflight chart had an additional target altitude 1500-2500' at SLIMR/Lincoln Park; the JeppFD-Pro chart has no such target altitude. This would have been helpful; believe we would have been higher at SLIMR. Not sure if this was an oversight or omission by Jepp or a well advised addition by NOS. We are Jepp certified and I only checked Foreflight just out of curiosity after the flight. I was informed that [the other air carrier] also uses JeppFD-Pro; so it may have been a similar issue as well.

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.