 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An A319 flight crew experienced a flap overspeed during approach when managed speed is selected by the flying first officer. The captain takes control and disconnects autothrust allowing the approach to be continued to landing. The approach had been activated and confirmed but apparently was not accepted by the FMGC.
| Attributes | |
| ACN | 1335199 |
| Time | |
| Date | 201602 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Landing |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Commercial |
| Person 2 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Speed All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
On approach an issue arose with the aircraft accelerating possibly due to the selection of managed speed without being activated and confirmed. I saw the captain select activate; but can't confirm that the mcdu registered the confirm selection. Either way the plane accelerated once I selected managed speed. I had just used the speed brakes and misinterpreted the acceleration with the plane leveling off and the speed brakes deployed. I reached to confirm that the speed brakes were stowed. The captain correctly diagnosed the issue and assumed control of the aircraft. The captain returned the aircraft to a stabilized condition. At one point though we did dip below GS and received a low altitude alert from tower. The captain corrected and we landed without further incident.possible failure to 'confirm' once activating the approach. Distraction from the acceleration led to the unstabilized approach. Mental task saturation with approaching weather; changing alternates; receiving new data; etc. Possibly led to a lapse in confirmation of pilot monitoring (pm) duties.
Original NASA ASRS Text
Title: An A319 flight crew experienced a flap overspeed during approach when managed speed is selected by the flying First Officer. The Captain takes control and disconnects autothrust allowing the approach to be continued to landing. The approach had been activated and confirmed but apparently was not accepted by the FMGC.
Narrative: On approach an issue arose with the aircraft accelerating possibly due to the selection of managed speed without being activated and confirmed. I saw the Captain select activate; but can't confirm that the MCDU registered the confirm selection. Either way the plane accelerated once I selected managed speed. I had just used the speed brakes and misinterpreted the acceleration with the plane leveling off and the speed brakes deployed. I reached to confirm that the speed brakes were stowed. The Captain correctly diagnosed the issue and assumed control of the aircraft. The Captain returned the aircraft to a stabilized condition. At one point though we did dip below GS and received a low altitude alert from tower. The Captain corrected and we landed without further incident.Possible failure to 'confirm' once activating the approach. Distraction from the acceleration led to the unstabilized approach. Mental task saturation with approaching weather; changing alternates; receiving new data; etc. possibly led to a lapse in confirmation of Pilot Monitoring (PM) duties.
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.