9 members · 8 posts · Boeing 737
For anyone flying, training on, or fixing the 737. NG and MAX both welcome. Type specific questions, systems talk, and honest comparisons between fleets.
No fleet wars. Keep type specific questions specific. If you are quoting a procedure, say which operator it came from, because they are not all the same.
Karen Whitfield (pinned)
Ground rule for this group. No fleet wars. NG people and MAX people both have to fly the thing. Systems questions and training resources are what we are here for.
Imani Osei
Coming back to the 737 group from the widebody side for one thing. Everything I do well on a long haul airplane, I learned on this one, in short haul, doing six legs a day in weather. Nobody gets good at flying by flying eight hours in cruise. You get good at it in the terminal area.
Emmett Boyd
Sim tech on the 737 boxes. If your visual looks slightly wrong on approach and you cannot say why, tell us rather than flying around it. Nine times in ten it is a projector alignment drifting, and it takes twenty minutes to fix. Crews assume the sim is correct and themselves wrong. Sometimes it is the sim.
Marcus Webb
Does anyone else find the MAX display layout takes a few legs to unlearn the NG scan? Third day on it and my eyes still go to the wrong spot for engine indications.
Imani Osei
Came off the 737 onto the 787 last year and the thing I miss is how honest the 737 is about what it is doing. The newer airplane protects you from more and tells you less. Both are fine. They are just different relationships.
Karen Whitfield
Sim tip for anyone heading into initial. Your callouts during the engine failure at V1 should be boring. If they sound exciting, you are already behind the airplane.
DeShawn Barr
Coming off heavy military multi and starting a type course soon. For anyone who has made this jump, how much does the course assume you already understand about the automation philosophy, as opposed to the systems?
Bruno Vargas
avionics guy lurking here. the number of these still flying with a display fault that gets deferred and rescheduled and deferred again is higher than you want to know. write it up every time even when you know it will get deferred. the paper trail is what eventually gets it fixed