ASRS 2103659

Reporter 1

Instructed by ATC to “descend and maintain 2,400 ft. until established, cleared for RNAV 27L approach”. We complied and upon reaching 2,400 ft. ATC queried our current altitude due to a low altitude alert of 1,900 feet. The altimeter setting for SBN was 29.23 but we had 29.83 selected in the Kollsman window. The ATIS broadcast was coming in very weak and wasn’t audible until well within the descent phase of flight. Upon initial contact with approach control they informed us of the local altimeter setting and I as PM, working the radios mentally noted the large discrepancy but did not call immediate attention to it due to the high workload we were presently experiencing. By doing so I forgot to select the new local altimeter setting resulting in the crew using the wrong one. Suggestion: When an anomaly exists correct it immediately instead of delaying

Reporter 2

Cleared to descend to 2,400 ft. and cleared for the RNAV Runway 27L, we received a low altitude alert from the approach controller. He report the aircraft at 1,900 ft and gave the current altimeter setting (29.23). The altimeter set and briefed was 29.83 per the Takeoff & Landing Distance card. The root cause is an incorrectly set altimeter. There is an AWOS station that makes listening to the SBN ATIS challenging until closer to the airfield. In our case, that was approximately 16 minutes prior and well into the descent phase with other distractions and duties. As PF and Captain, in retrospect I should have used better judgement and listened, in detail, to the ATIS myself to verify and trap any discrepancies. Solution: PF, if practical, listens in to ATIS when Digital ATIS is not available.