Air carrier flight crew reported a CFTT event during departure from SJC airport. ATC gave the flight crew a low altitude warning which prompted the crew to initiate an immediate climb.
Synopsis
Air carrier flight crew reported a CFTT event during departure from SJC airport. ATC gave the flight crew a low altitude warning which prompted the crew to initiate an immediate climb.
Narrative
Prior to departing SJC to ZZZ1; the flight crew briefed and understood the departure procedure; and the 1.8NM DME turning point for the SJC.MOONY SID. All checklists were complete as the aircraft taxied onto 30R and was cleared for takeoff. During the initial climb; once reaching 400 feet AGL; pilot monitoring stated; '400 feet you can start that right turn' and turned the heading bug towards the right turn on the SID and armed NAV mode. Pilot flying paused for moment; then began the right turn around 650 feet. At this time PM contacted NorCal departure; 'Departure Aircraft X; 1;100 climbing 5;000 on the SJC 3 departure.' ATC replied; 'Aircraft X radar contact; and maintain 5;000.' PM; replied; 'Maintain 5;000.' Approximately 15 seconds later ATC advised the aircraft; 'Aircraft X low altitude alert; the MVA in your area is 2;000; just expedite your climb through 5;000.' At this time the aircraft was in a right turn at approximately 1;700 feet MSL. PM replied; 'We'll expedite to 5;000.' Shortly after reaching 5;000 ATC then vectored the aircraft and the flight proceeded to ZZZ1. During the climb to 7;000FT MSL PF questioned the accuracy of the departure flight path and asked ATC for their phone number. The flight continued to ZZZ1 and execute an ILS XXR approach; landing under normal conditions.Cause: Prior to this flight we had conducted 2 hand flown ILS approaches to minimums at ZZZ1 resulting in flying the published missed and holding. We also sat on the ground at SJC for over an hour. I was not quite as situationally aware as I believed I was due to the challenging conditions and cognitively demanding workload I was under for a couple hours. Despite briefing the departure procedure; I did not effectively question or verify the actions of PM in accordance with our briefed departure or the SID chart which I had displayed on my EFB during the departure.Suggestions: We could have added a reference in the automation by utilizing the FMS FIX page to display a navigational reference marker at 1.8 DME from SJC in addition to the loaded departure procedure. A technique which may have been helpful would have been to utilize NAV mode as well.
Second reporter narrative
Prior to departing SJC to ZZZ1; the flight crew briefed and understood the departure. We were then cleared for takeoff for 30R. On the initial climb we reached 400 feet AGL. Pilot monitoring said 400 feet starting the right turn. Before the turn Pilot monitoring saw that there was no traffic or terrain to the right. Pilot monitoring turned the heading bug and hit heading mode. He then hit Nav mode to the re intercept the SID. We started the right turn at 650 feet AGL. On the turn Pilot Monitoring contacted departure. We were then told to maintain 5;000. Approximately 15 seconds later we were told of a low altitude alter. We then continued to climb on the SID.Cause: Before this flight we conducted 2 missed approach procedures and a holding pattern. We diverted and then had to wait in San Jose for a good amount of time for paperwork to come through to continue from SJC to ZZZ1. Suggestions: We could have added an additional reference by adding a 1.8 DME marker on the FMS to add in situational awareness for both pilots. Also trust your Navigational guidance from FMS.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.