37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1761842 |
Time | |
Date | 202009 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 12 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
I was the first officer and PF ZZZ1-ZZZ. This was my first flight after not flying for over two months. The majority of the flight went fine; but as we approached ZZZ; ATC left us high (11;000 feet) very close to the airport. I was about to ask for lower when ATC gave us a descent. I thought we had just enough time to successfully descend and slow down; but when we were around 4;000 feet; ATC gave us a turn that made it clear they were directing us straight to the FAF. This was not what I was expecting; and left us high and fast and greatly increased our workload. I used the flight spoilers to slow down and then forgot to stow them after slowing enough to add flaps. Our workload was still quite high at this point; so we didn't realize the flight spoilers were still deployed until the spoiler caution message at 500 feet. At this point; the captain immediately stowed them and we continued the landing.because ATC left us high and then turned us directly to the FAF; our workload greatly increased. I deployed the spoilers in order to slow down; and then forgot to stow them because I was distracted by other things in the flight deck (arming the approach; making sure we intercepted the localizer and glideslope; making sure we were on speed and deployed our flaps and gear at the appropriate time; etc.). I was expecting something different from ATC and had a good plan in my head; but was thrown off when ATC gave us something I didn't expect. This was also my first leg after not flying for over 2 months; which I think could have contributed as well; because I was a bit rusty and a little bit slower than I normally am in the flight deck.we could have easily prevented this from happening by asking ATC for a longer downwind. I was planning a longer downwind in my head and when ATC gave us a turn directly to the FAF; we should have asked to stay on downwind instead. There wasn't anyone else out there to cause traffic issues; and it would have given us extra time to slow down and descend so that we weren't rushed. In the heat of the moment; I didn't think of this (though I used to remind my students of this option all the time when I was a flight instructor!); but I should have. When we stowed the spoilers; I decreased thrust and pitched down a little bit; which kept us on speed and caused only a slight deviation from the glideslope; which I was able to correct. Because of this; we made a completely normal landing. However; a go-around would also have been a good choice here; especially if we became unstable after retracting the spoilers.
Original NASA ASRS Text
Title: Air carrier First Officer reported an unstable approach and stated this was the first flight in 2 months.
Narrative: I was the First Officer and PF ZZZ1-ZZZ. This was my first flight after not flying for over two months. The majority of the flight went fine; but as we approached ZZZ; ATC left us high (11;000 feet) very close to the airport. I was about to ask for lower when ATC gave us a descent. I thought we had just enough time to successfully descend and slow down; but when we were around 4;000 feet; ATC gave us a turn that made it clear they were directing us straight to the FAF. This was not what I was expecting; and left us high and fast and greatly increased our workload. I used the flight spoilers to slow down and then forgot to stow them after slowing enough to add flaps. Our workload was still quite high at this point; so we didn't realize the flight spoilers were still deployed until the spoiler caution message at 500 feet. At this point; the Captain immediately stowed them and we continued the landing.Because ATC left us high and then turned us directly to the FAF; our workload greatly increased. I deployed the spoilers in order to slow down; and then forgot to stow them because I was distracted by other things in the flight deck (arming the approach; making sure we intercepted the localizer and glideslope; making sure we were on speed and deployed our flaps and gear at the appropriate time; etc.). I was expecting something different from ATC and had a good plan in my head; but was thrown off when ATC gave us something I didn't expect. This was also my first leg after not flying for over 2 months; which I think could have contributed as well; because I was a bit rusty and a little bit slower than I normally am in the flight deck.We could have easily prevented this from happening by asking ATC for a longer downwind. I was planning a longer downwind in my head and when ATC gave us a turn directly to the FAF; we should have asked to stay on downwind instead. There wasn't anyone else out there to cause traffic issues; and it would have given us extra time to slow down and descend so that we weren't rushed. In the heat of the moment; I didn't think of this (though I used to remind my students of this option all the time when I was a flight instructor!); but I should have. When we stowed the spoilers; I decreased thrust and pitched down a little bit; which kept us on speed and caused only a slight deviation from the glideslope; which I was able to correct. Because of this; we made a completely normal landing. However; a go-around would also have been a good choice here; especially if we became unstable after retracting the spoilers.
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.