37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1535908 |
Time | |
Date | 201804 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B777 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 13264 Flight Crew Type 297 |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 120 Flight Crew Total 11546 Flight Crew Type 3889 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Speed All Types |
Narrative:
This event was due to a series of errors. On the ground; the pilot flying (PF) briefed typing in the airspeed (a/s) constraint for the SID; even though the pilot monitoring (pm); more experienced with this departure; mentioned that speed intervene usually worked well. PF also typed an alt constraint of 5000 or below in the FMC; and placed this at the [first] fix; even though [the] fix has no altitude constraint. This part was done without the pm's knowledge. After uneventful take off; PF then opened speed window instead of VNAV as briefed. Called for 220 [kts]. Told pm to ask ATC for a high speed climb. Remained at flaps 15 until ATC cleared us for high speed. PF then called for pm to set 250 [kts]. Slightly delayed reaction on pm's part; until realizing that this speed was too slow for the aircraft. Set higher speed (260 or so). At this point we are cleared to 9000 ft; initially not set in the confusion of the stick shaker; then set seconds later is set on prompt from relief pilot; and I pushed the altitude button. But PF can't get the airplane to climb. Speed rapidly erodes and an abrupt pull at the yellow band results in stick shaker. A lot of non-communicated button pushing on the part of the PF now commences at this point; none of it properly communicated; and me; trying to both make sure we [were] complying with clearance and figuring out what is going on; and [we] weren't going to get slow again--it all happened very quickly--getting slow; hitting speed intervene and then out of speed intervene. Still not climbing to 9000 ft; while I'm trying to puzzle this out; and deal with ATC. I feel very bad I didn't notice that 5000 or below was part of [the] SID; because I never knew it was put in there in the first place. So if I'd known; I'd have pushed the altitude button a second time to delete this restriction. Still not climbing. Now PF calls for max continued thrust but immediately does it himself. I notice that max cruise is annunciated; and query him. He says he had been calling for this and I didn't answer; but to my knowledge there was one call; and it came as I was answering ATC's query as to why we weren't climbing to 9000 ft. Until I told him he had set [max] cruise and not max continued thrust he didn't know he had set the wrong thrust setting; thus worsening the problem. I corrected back to max cruise; we passed [the] first fix and climbed on schedule normally. I prompted [the] PF to go back to normal climb.
Original NASA ASRS Text
Title: B777 flight crew reported activating stick shaker during departure due to crew communication breakdown.
Narrative: This event was due to a series of errors. On the ground; the Pilot Flying (PF) briefed typing in the airspeed (a/s) constraint for the SID; even though the Pilot Monitoring (PM); more experienced with this departure; mentioned that speed intervene usually worked well. PF also typed an alt constraint of 5000 or below in the FMC; and placed this at the [first] fix; even though [the] fix has no altitude constraint. This part was done without the PM's knowledge. After uneventful take off; PF then opened speed window instead of VNAV as briefed. Called for 220 [kts]. Told PM to ask ATC for a high speed climb. Remained at flaps 15 until ATC cleared us for high speed. PF then called for PM to set 250 [kts]. Slightly delayed reaction on PM's part; until realizing that this speed was too slow for the aircraft. Set higher speed (260 or so). At this point we are cleared to 9000 ft; initially not set in the confusion of the stick shaker; then set seconds later is set on prompt from relief pilot; and I pushed the ALT button. But PF can't get the airplane to climb. Speed rapidly erodes and an abrupt pull at the yellow band results in stick shaker. A lot of non-communicated button pushing on the part of the PF now commences at this point; none of it properly communicated; and me; trying to both make sure we [were] complying with clearance and figuring out what is going on; and [we] weren't going to get slow again--it all happened very quickly--getting slow; hitting speed intervene and then out of speed intervene. Still not climbing to 9000 ft; while I'm trying to puzzle this out; and deal with ATC. I feel very bad I didn't notice that 5000 or below was part of [the] SID; because I never knew it was put in there in the first place. So if I'd known; I'd have pushed the ALT button a second time to delete this restriction. Still not climbing. Now PF calls for max continued thrust but immediately does it himself. I notice that max cruise is annunciated; and query him. He says he had been calling for this and I didn't answer; but to my knowledge there was one call; and it came as I was answering ATC's query as to why we weren't climbing to 9000 ft. Until I told him he had set [max] cruise and not max continued thrust he didn't know he had set the wrong thrust setting; thus worsening the problem. I corrected back to max cruise; we passed [the] first fix and climbed on schedule normally. I prompted [the] PF to go back to normal climb.
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.