Narrative:

I was pilot monitoring (pm) for this leg as first officer (first officer) was flying a visual approach backed up by ILS. The first officer had the autopilot connected and was managing the approach with the thrust levers and the V/south wheel on the fcp. At 1;000 feet the first officer was approximately 1/4 dot low on the glideslope. I stated he was low and he responded with 'correcting.' he was slow to correct and the initial correction was to add thrust without decreasing V/south. He disconnected the autopilot but didn't adequately adjust his pitch. I stated glideslope as we were approaching 1 dot. About the same time the tower announced a low altitude warning using our call sign which I responded to with correcting. The first officer adjusted pitch and power and we were stabilized by 500 feet. We landed normally. First officer's fixation error while flying the approach possibly due to task saturation caused him to get low on the glide path while in visual conditions. I should have been more directive in my communication with him and checked the deviation sooner. Continue to emphasize CRM and directive clear communication between pm and pilot flying (PF). I should have been less concerned with not wanting to micro-manage a relatively experienced first officer and directed a positive correction sooner.

Related reports:

Google
 

Original NASA ASRS Text

Title: CRJ-200 Captain reported receiving a low altitude warning from the Tower during approach to ATL airport.

Narrative: I was Pilot Monitoring (PM) for this leg as First officer (FO) was flying a visual approach backed up by ILS. The FO had the autopilot connected and was managing the approach with the thrust levers and the V/S wheel on the FCP. At 1;000 feet the FO was approximately 1/4 dot low on the glideslope. I stated he was low and he responded with 'Correcting.' He was slow to correct and the initial correction was to add thrust without decreasing V/S. He disconnected the autopilot but didn't adequately adjust his pitch. I stated glideslope as we were approaching 1 dot. About the same time the Tower announced a low altitude warning using our call sign which I responded to with correcting. The FO adjusted pitch and power and we were stabilized by 500 feet. We landed normally. FO's fixation error while flying the approach possibly due to task saturation caused him to get low on the glide path while in visual conditions. I should have been more directive in my communication with him and checked the deviation sooner. Continue to emphasize CRM and directive clear communication between PM and Pilot Flying (PF). I should have been less concerned with not wanting to micro-manage a relatively experienced FO and directed a positive correction sooner.

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.