PPRuNe Forums - View Single Post - Ethiopian airliner down in Africa
View Single Post
Old 13th Mar 2019, 13:52
  #1029 (permalink)  
positiverate20
 
Join Date: Jan 2019
Location: Belfast
Posts: 36
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by ManaAdaSystem

So the Americans have had 5 cases of control issues after takeoff on the MAX. At least two happened when they engaged the auto pilot.
There appears to be several issue with the MAX.
Only time before it’s grounded world wide.
Here's a couple of extracts to look at

REPORT- trim after AP is turned on: December 2018

Noted on preflight, a write up, for a cycling trim situation on the inbound leg. With no faults noted by maintenance, it was cleared. First Officer (FO) and I discussed the situation as one of the threats possible, with emphasis on being alert for the cycling trim situation to possibly repeat. Reviewed applicable procedure for a possible runaway trim scenario. Upon takeoff, Autopilot A was engaged at approximately 1,200 FT AGL. As flaps were retracted and airspeed began to increase, additional trim inputs were immediately noticed by both pilots. With flaps now up, FMC called for 250 KTS. Aircraft pitched to 260 KTS with trim inputs, then re-pitched to 240 KTS. The trim system would activate for 1-2 seconds and then immediately reverse itself, trimming in opposite direction. I directed FO to ask for intermediate stop on climb, where we then stopped at FL230. Advised ATC we were experiencing a trim system problem, but the aircraft was stable and trim stopped fluctuating once a stable and level pitch was attained. I chose not to declare an emergency at this time as we did have a stable aircraft, but contacted dispatch via radio, and informed dispatcher of the situation, that it was a reoccurring event, and that I was not comfortable taking the aircraft to ZZZ1 with a primary flight control system not operating properly. Therefore I would return to ZZZ. Dispatcher brought Maintenance Control in I believe at that point and I gave them a description of the problem. We then completed those calls, informed ATC of our desire to return to ZZZ, and no emergency being declared at this time. The trim problem immediately reappeared when given a descent to 11,000, executed via Level Change on the Mode Control Panel. I was flying and at that point disconnected the autopilot, and hand flew the remainder of the approach to the landing. No trim problems were noted with autopilot disconnected. Maintenance ACARSed us several times, requesting us to attempt to troubleshoot the failure and gather information. I elected to not do this. I knew I had a failed trim system and did not wish to engage a deeper problem if something else went wrong with the system while troubleshooting. In addition we [were] now under 15000 FT, in the terminal area, and I was hand flying the aircraft. Too many distractions, as well as a potential bigger problem if something else went wrong. We both put on the table the trim motor / elevator jackscrew failure a few years back that happened to another carrier. That situation was perhaps the final reason I did not want to troubleshoot the failure. We finally told Maintenance Control via ACARS. "We are busy ", as they were now a distraction with their requests as we were near or under 10,000 FT. Aviate, Navigate, Communicate. That is what I start every brief off with a new pilot at the beginning of a trip.
REPORT- trim after AP is turned on: November 2018

It was day three of six for me and day three with very good FO (First Officer). Well rested, great rapport and above average Crew coordination. Knew we had a MAX. It was my leg, normal Ops Brief, plus I briefed our concerns with the MAX issues, bulletin, MCAS, stab trim cutout response etc. I mentioned I would engage autopilot sooner than usual (I generally hand fly to at least above 10,000 ft.) to remove the possible MCAS threat.

Weather was about 1000 OVC drizzle, temperature dropping and an occasional snow flake. I double checked with an additional personal walkaround just prior to push; a few drops of water on the aircraft but clean aircraft, no deice required. Strong crosswind and I asked Tug Driver to push a little more tail east so as not to have slow/hung start gusts 30+.

Wind and mechanical turbulence was noted. Careful engine warm times, normal flaps 5 takeoff in strong (appeared almost direct) crosswind. Departure was normal. Takeoff and climb in light to moderate turbulence. After flaps 1 to "up" and above clean "MASI up speed" with LNAV engaged I looked at and engaged A Autopilot. As I was returning to my PFD (Primary Flight Display) PM (Pilot Monitoring) called "DESCENDING" followed by almost an immediate: "DONT SINK DONT SINK!"

I immediately disconnected AP (Autopilot) (it WAS engaged as we got full horn etc.) and resumed climb. Now, I would generally assume it was my automation error, i.e., aircraft was trying to acquire a miss-commanded speed/no autothrottles, crossing restriction etc., but frankly neither of us could find an inappropriate setup error (not to say there wasn't one).

With the concerns with the MAX 8 nose down stuff, we both thought it appropriate to bring it to your attention. We discussed issue at length over the course of the return to ZZZ. Best guess from me is airspeed fluctuation due to mechanical shear/frontal passage that overwhelmed automation temporarily or something incorrectly setup in MCP (Mode Control Panel). PM's callout on "descending" was particularly quick and welcome as I was just coming back to my display after looking away. System and procedures coupled with CRM (Resource Management) trapped and mitigated issue.

From FO perspective
Day 3 of 3 departing in a MAX 8 after a long overnight. I was well rested and had discussed the recent MAX 8 MCAS guidance with the Captain. On departure, we had strong crosswinds (gusts > 30 knots) directly off the right wing, however, no LLWS or Micro-burst activity was reported at the field. After verifying LNAV, selecting gear and flaps up, I set "UP" speed. The aircraft accelerated normally and the Captain engaged the "A" autopilot after reaching set speed. Within two to three seconds the aircraft pitched nose down bringing the VSI to approximately 1,200 to 1,500 FPM. I called "descending" just prior to the GPWS sounding "don't sink, don't sink." The Captain immediately disconnected the autopilot and pitched into a climb. The remainder of the flight was uneventful. We discussed the departure at length and I reviewed in my mind our automation setup and flight profile but can't think of any reason the aircraft would pitch nose down so aggressively.
positiverate20 is offline