Air carrier First Officer reported a below glideslope alert while on final approach. The First Officer made a thrust and pitch correction and landed normally.
Synopsis
Air carrier First Officer reported a below glideslope alert while on final approach. The First Officer made a thrust and pitch correction and landed normally.
Narrative
Sorry if this is too wordy. First report submission and not necessarily a specific chain of events that led directly to the lower glideslope.I haven't flown into Austin many times and it had been awhile since my last flight there. Ultimately we received a momentary low visual glideslope indication (4 red on the PAPI) and a single glideslope auditory call out at approximately 300 ft AGL but the thrust and pitch corrections were already made (minor vertical adjustments at this distance) and the external environmental factors allowed for us to continue the approach to an uneventful landing.We received vectors from Approach Control off of the WLEEE7 approach. We were given multiple speed assignments slowing us down with the final instruction to slow to 170. We needed flaps 5 to slow to 170. We were previously configured flaps 1 with speed brakes to slow us to 190 (if I recall correctly). I put the speed brakes in and called for flaps 5 to slow to 170. Around this same time we were told we had a 40 not overtake on previous traffic. No issues with altitudes on the arrival.Once we were slowed to 170; the controller started to vector us to the visual which kept us about 4 miles behind the previous landing traffic and left us on a base vs a dogleg which drove me to use the digital display of the final course more so than the external visuals. The ATIS called for gusty winds that required a 15kt. additive for our target speed (I believe it was 220 11 gust 21). We were fully configured and on glideslope close to the FAF (ELLBJ) per the company page notes about the short final. We initiated configuration around UTEEE to ensure we were stable. I originally asked for gear down and flaps 15 about 3 miles prior to UTEEE on the base vector and the Captain recommended to delay a little longer. We discussed this on the debrief. I originally briefed UTEEE as my point to initiate configuration but I felt a little busy and fast. The Captain later stated that he thought I was configuring to slow down below the assigned 170 kts. versus just getting configured early to get ahead of the pacing and have the drag ready for our glideslope intercept and slow to target speed. At this point the Captain was pointing out the runway off his side of the aircraft so lining up visually with the runway was the priority discussion. Once I had the runway acquired the Captain stated we could configure; which was right around the point we briefed (UTEEE).The Captain called for a wind check and received a steady wind report from Tower which led us to reduce the airspeed additive to 8kts. We received a few gusts on final which required thrust addition with immediate thrust removal (maybe 5 kts below target speed quickly adjusting to 5 kts over target speed) somewhere just above the 500 ft call.The aircraft was stable and configured at all the normal gates. At the 500 ft call and I began to transition more to a visual approach. At this point I think I shifted my aim point to the front side of the touchdown markers to help ensure I didn't float the landing which may cause us to miss the Taxiway T turnoff 6269' down the runway with brakes 2 set. This resulted in 3 red on the PAPIs about 350 AGL vs 200. Shortly after this the PAPIs flashed to a 4 red status; Captain stated as much and the appropriate thrust and pitch corrections were in place. After the input; we received a glide slope aural indication at about 300ft. Due to the corrective actions already in place; the momentary nature of the visual indication from the PAPIs; the stable winds at this point; and the confirmed visual indications with the runway environment we continued the landing. The aim point corrected to the normal center of the touchdown markers and we touched down normally around 1300ft down the runway. Normal braking action resulted in an easy turnoff at Taxiway Tango.Even though this was a momentary deviation on an approach that felt like many other approaches with minor gusts; this isthe first time I received an aural glideslope indication so it seemed appropriate to submit the report.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.