B767-300 flight crew reported on arrival receiving a steep arrival from ATC resulting in an unstable approach and flight towards terrain. The flight crew was able to configure the aircraft and rejoin the glide path and landed safely.
Synopsis
B767-300 flight crew reported on arrival receiving a steep arrival from ATC resulting in an unstable approach and flight towards terrain. The flight crew was able to configure the aircraft and rejoin the glide path and landed safely.
Narrative
We were descending to 12000 direct to ZZZZZ. Went to FLCH (Flight Level Change) to hustle down as I was expecting an early turn to final. About a minute later we were told to turn direct to ZZZZZ1 and descend to 9400; cleared approach. As we approached ZZZZZ1; I set 6400 and selected VNAV and opened speed window to slow us after the slam dunk. I don't remember cross checking FMA's (Flight Mode Annunciator). As jet turned final; I selected approach tile. FO stated LOC captured; GS armed. I verified on FMA's. I selected flaps 15 then 20 and rolled speed back to vref20 for the 160 kt restriction at ZZZZZ3. Approaching ZZZZZ2 the master warning went off as the RA was at 700 then 670 with flaps 20; no gear; below 1000 RA. We were well clear of terrain and we were VMC. FO stated what mode are we in; speed tile is selected. We were flying into the sun and it was extremely hard to see any tiles selected on the MCP (Mode Control Panel). Seconds later; horn and warning stopped as we were now passed the hill and RA was 1200. GS captured just prior to ZZZZZ3 and remainder of approach and landing was uneventful. In debrief; I told FO that I believed I had selected VNAV. FO stated that he did not see FLCH selected; but saw the speed tile selected. We discussed the confusion and lack of ability to see the mode selected on the MCP due to the sun. We also discussed being around 600 feet low at ZZZZZ2; which we both realized too late. Not verifying FMA's on my part and possibly selecting the wrong mode on the MCP was also discussed as a failure on my part.Cause: Multiple revisions to paring. Latest one on drive to airport that delayed departure over 2 hours. Fatigue was a major factor. I felt good at departure; but on approach I was wiped out. Also failure to verify FMA's promptly.Suggestions: Make revisions early; not late; so crews can maximize rest. Better FMA scan.
Second reporter narrative
We were descending on the arrival proceeding direct to ZZZZZ cleared to descend to 12000 msl. Approach cleared us to a fix abeam our present position ZZZZZ1 on the approach and cleared us to descend to 9400 msl with approach clearance. We were in FLC and hurrying the descent anticipating a slam dunk to the approach. Approaching ZZZZZ1 the Captain dialed the altitude to 6400. We had already verified the altitudes on the approach. Hind sight I never verified what mode we were in at this point. Just prior to turning final I recall noticing that the approach mode was not armed yet so I just stated cleared for the approach. As we turned final the Captain selected the approach tile and I stated LOC captured and Glideslope alive. The Glideslope was just over 1 dot above us. At this point we were configuring to flaps 20 with the gear up. Seconds later the master warning went off as the RA was around 600' with flaps 20 and gear up. At this point I was trying to figure out what we missed and the RA went back up over 1200 after passing the ridge.I stated 'what mode are we in' because I thought we were Altitude protected. I looked at the FCP multiple times to ensure we were not still in FLC. All I recall is that the speed tile was illuminated and the approach tile was illuminated but the sun was directly in our face and the panel was very difficult to see. I recall seeing 6900 just prior to ZZZZZ2 which was below the 7300' Altitude restriction. We continued to configure and intercepted the Glideslope prior to ZZZZZ3. The rest of the approach continued without any issues.Cause: Getting direct to cuts on the Arrival and cleared to an Altitude below the restriction at the point we were going to. Then getting direct to the final course forcing us to expedite our descent. I missed the mode change from FLC to VNAV; which caused us to go into speed mode because we were below the path. I was also struggling to verify the Autopilot selections on the panel due to the sun directly in our face. I was looking outside more than I needed to meaning less verification and lead to a missed altitude restriction. I improperly assessed the FMAs.Suggestions: I should have verified that we were in path or some type of altitude protected mode until Glideslope capture. I assumed we were because we were on final but didn't verify the actual modes we were in.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.