37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1304121 |
Time | |
Date | 201510 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
A row/rop alert triggered in the cockpit during landing roll-out. Stable approach; stable landing configuration. First officer pilot flying; I was caught slightly off guard when touching down. While in the flare the wheels of aircraft seemed to just hover slightly above the tarmac; not making contact. Nothing seemed out of ordinary until I realized aircraft actually touched down at the end of the landing zone paint strips. At this time I began normal landing procedures...pulling thrust to reverse while applying brake pressure; it was right in this moment of thinking that was a pretty nice landing; when row/rop alert came alive. I should have cobbed throttles and [gone] around however; I believed that the thrust reversers were already being deployed therefore I jammed the brakes and continued stopping.everything about this flight was so routinely normal that nothing should have occurred. In reflection though; I find that more prudence should be placed on how we fly our differing fleets. [At my base] we tend to fly more A319's. Therefore it would be best if we focus a touch more on landing flaps full; versus config 3. In the 319; ref speeds are routinely low....low speeds; low weights etc. I believe had I not been a robot in thinking just use config 3 cause that's what we always do; focus on approach speeds/available landing distance for the A321. This flight for example had a vref of 150. Had I used full flaps I think there would have been no issue; even with the tail wind landing.
Original NASA ASRS Text
Title: A321 First Officer experienced a ROPS alert during a flaps 3 landing that floated to the end of the touchdown zone. Believing the reversers are already deployed; the landing was continued and heavy braking used to stop.
Narrative: A ROW/ROP alert triggered in the cockpit during landing roll-out. Stable approach; stable landing configuration. FO pilot flying; I was caught slightly off guard when touching down. While in the flare the wheels of aircraft seemed to just hover slightly above the tarmac; not making contact. Nothing seemed out of ordinary until I realized aircraft actually touched down at the end of the landing zone paint strips. At this time I began normal landing procedures...pulling thrust to reverse while applying brake pressure; it was right in this moment of thinking that was a pretty nice landing; when ROW/ROP alert came alive. I should have cobbed throttles and [gone] around however; I believed that the thrust reversers were already being deployed therefore I jammed the brakes and continued stopping.Everything about this flight was so routinely normal that nothing should have occurred. In reflection though; I find that more prudence should be placed on how we fly our differing fleets. [At my base] we tend to fly more A319's. Therefore it would be best if we focus a touch more on landing flaps full; versus config 3. In the 319; ref speeds are routinely low....low speeds; low weights etc. I believe had I not been a robot in thinking just use config 3 cause that's what we always do; focus on approach speeds/available landing distance for the A321. This flight for example had a Vref of 150. Had I used full flaps I think there would have been no issue; even with the tail wind landing.
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.