37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1693104 |
Time | |
Date | 201910 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SAN.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
We were conducting the RNAV 27 approach in day VMC conditions to san with a tailwind during most of the arrival and initial approach phase. The captain was the pilot flying. When cleared for the approach he followed the typical routine of arming approach mode which quickly captured lateral and vertical guidance and began descending on the glideslope. At the time we were at flaps one with about 10-15 kts buffer under the flaps 1 redline of 235. Because of the tailwind and the somewhat steeper than normal approach angle; the aircraft started to accelerate after capturing the glideslope and quickly oversped the flaps by approximately 5-10 kts. The captain began to intervene immediately with use of the speedbrakes but the acceleration trend carried us into the red line. After removing the aircraft from approach mode and taking us off the glideslope; the aircraft slowed below the red line and we continued configuring and landed normally. We wrote up the overspeed at the gate in san.I believe that the core reason for this was a misunderstanding on the part of the PF (pilot flying) about what the aircraft would do once approach was armed. The PF said repeatedly that he thought the aircraft wouldn't overspeed with the automation set up with a selected speed and approach captured. Because of the tailwind and the aircraft's priority to follow the glideslope without regard to selected speed; an overspeed was possible. He may have been thinking of flight envelope protections in normal mode which would have protected an extreme overspeed but will allow the aircraft into the redline before they intervene.as the pm (pilot monitoring); I should have spoken up when approach mode was about to capture the glideslope to caution that an overspeed was possible. We had briefed during the approach briefing that a threat in san was the likelihood of being fast and high but I will add in the future that flap overspeeds; especially on the initial stage of the approach are possible. Additional emphasis in training about automation priorities where the aircraft will follow vertical guidance without regard to airspeeds may also be beneficial.
Original NASA ASRS Text
Title: A321 First Officer reported flap overspeed during a coupled approach with a tailwind.
Narrative: We were conducting the RNAV 27 approach in Day VMC conditions to SAN with a Tailwind during most of the Arrival and initial Approach phase. The Captain was the Pilot Flying. When Cleared for the approach he followed the typical routine of arming Approach Mode which quickly captured lateral and vertical guidance and began descending on the glideslope. At the time we were at flaps one with about 10-15 kts buffer under the Flaps 1 redline of 235. Because of the tailwind and the somewhat steeper than normal approach angle; the aircraft started to accelerate after capturing the glideslope and quickly oversped the flaps by approximately 5-10 kts. The Captain began to intervene immediately with use of the speedbrakes but the acceleration trend carried us into the red line. After removing the aircraft from approach mode and taking us off the glideslope; the aircraft slowed below the red line and we continued configuring and landed normally. We wrote up the overspeed at the Gate in SAN.I believe that the core reason for this was a misunderstanding on the part of the PF (Pilot Flying) about what the aircraft would do once approach was armed. The PF said repeatedly that he thought the aircraft wouldn't overspeed with the automation set up with a selected speed and Approach Captured. Because of the tailwind and the aircraft's priority to follow the glideslope without regard to selected speed; an overspeed was possible. He may have been thinking of flight envelope protections in normal mode which would have protected an extreme overspeed but will allow the aircraft into the redline before they intervene.As the PM (Pilot Monitoring); I should have spoken up when approach mode was about to capture the glideslope to caution that an overspeed was possible. We had briefed during the approach briefing that a threat in SAN was the likelihood of being fast and high but I will add in the future that flap overspeeds; especially on the initial stage of the approach are possible. Additional emphasis in training about automation priorities where the aircraft will follow vertical guidance without regard to airspeeds may also be beneficial.
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.