- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
re: 737max crashes in Ethiopia. Killing 157
Posted on 3/13/19 at 10:17 am to GeauxxxTigers23
Posted on 3/13/19 at 10:17 am to GeauxxxTigers23
Is there any reason they can’t both get the data? At this point I’m not sure I trust either one, as there are strong political motivations on both sides.
Posted on 3/13/19 at 10:25 am to GeauxxxTigers23
Here are some excerpts from the pilot reports:
quote:
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.
quote:
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.
This post was edited on 3/13/19 at 10:29 am
Posted on 3/13/19 at 10:59 am to When in Rome
quote:
#BREAKING: Canada transport minister grounds Boeing 737 MAX
Posted on 3/13/19 at 11:12 am to When in Rome
quote:Im not familiar enough with the 73, or Boeing aircraft in general, to say one way or the other. A lot of things could happen. The runaway trim issue is a big one that I’ve actually experience in another aircraft.
Is there another system that would pitch the nose down while autopilot is engaged?
The more I read the more I think that the new 737 has a problem interpreting data it receives from instruments and relaying that to the flight control systems, whether it be the traditional autopilot or the MCAS.
This post was edited on 3/13/19 at 11:15 am
Posted on 3/13/19 at 11:27 am to When in Rome
quote:
Maintenance ACARSed us several times, requesting us to attempt to troubleshoot the failure and gather information.
Posted on 3/13/19 at 11:35 am to GeauxxxTigers23
quote:
But honestly I trust the guys at the NTSB to examine and report the factual data over Europeans.
What's the relationship between the NTSB and the FAA? does one report to the other? completely apart?
Posted on 3/13/19 at 11:36 am to HerkFlyer
quote:
frick you!
Posted on 3/13/19 at 11:37 am to LSUFanHouston
FAA is under the Dept of Transportation. NTSB is an independent agency.
Posted on 3/13/19 at 11:38 am to GeauxxxTigers23
quote:I like how polite he was.
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.
Posted on 3/13/19 at 11:46 am to When in Rome
That shite is like a twice a week occurrence at my job. A lot of times I’ll humor them if I have time. But if it’s busy and becomes a safety of flight issue I just tell them what time I’ll be back so they can meet me at the airport and then turn the radio off.
Posted on 3/13/19 at 11:57 am to GeauxxxTigers23
quote:
and then turn the radio off.
Posted on 3/13/19 at 11:59 am to When in Rome

quote:I wonder what "new data" they have. Is it new data, or is it just that they didn't want to be the last to ground the 737 MAX?
as a result of new data
Posted on 3/13/19 at 12:00 pm to LSUFanHouston
The FAA is the regulatory, certification and enforcement agency branch in the DOT. The NTSB participates in the investigation process of accidents resulting in major damage to the airframe or death. Both can work together on a case, but usually when the NTSB is involved, the FAA will let them take the lead but their resources are still available.
This post was edited on 3/13/19 at 12:18 pm
Posted on 3/13/19 at 12:01 pm to When in Rome
quote:
first officer reported that the aircraft pitched nose down after the autopilot was engaged during departure. The autopilot was then disconnected and flight continued to its destination,
So they have an unexplained and uncommanded nose down dive and they decide to continue on with the flight.
Posted on 3/13/19 at 12:10 pm to LSUFanHouston
quote:
What's the relationship between the NTSB and the FAA? does one report to the other? completely apart?
They are separate agencies with very different organizations. I believe the FAA reports to the Department of Transportation whose secretary reports to the president, who can get rid of anyone he wants to in the executive branch since he's the chief executive.
The NTSB, on the other hand, is an independent agency of the federal government in that it is not part of any executive department (though I think it might be technically placed in the executive branch, but don't quote me on that) and isn't really under Congressional oversight (outside of its budget, of course). Both the president and Congress agree on the members of the actual board, but have limited powers to remove them once seated. The idea is to separate its organization from the politics of D.C. to allow it to function as it sees fit and investigate as it sees fit without fear of political repercussions.
This post was edited on 3/13/19 at 12:18 pm
Posted on 3/13/19 at 12:27 pm to Diseasefreeforall
Good to see Mali still standing strong with Boeing.
Posted on 3/13/19 at 12:38 pm to RedRifle
Just received a company wide email that says we have suspended all company flights on the Boeing 737 Max
We are Canadian based btw.
We are Canadian based btw.
This post was edited on 3/13/19 at 12:41 pm
Posted on 3/13/19 at 1:40 pm to RedRifle
quote:
Just In: President Trump says an emergency order will be issued to ground all U.S. airline flights of the Boeing 737 Max 8 and 737 Max 9.
Any plane currently in the air will go to its destination and then will be grounded until further notice.
This post was edited on 3/13/19 at 1:44 pm
Back to top


0







