Johnboy

Well worth watching from what I consider a no BS source on aviation accident/incident reporting......

Not the best quality but a good synopsis of the comms during the incident.

Sorry having one of these operating in an active international airport control zone with no apparent Command and Control system is not an ACCIDENT. SA-15 TOR-M1SAM

Tweet from Tom Podolec about the fracass......scroll down for the after pictures... https://twitter.com/TomPodolec/status/1211803214401720327?s=20

Is the AC rondelle backwards on the starboard side of the tail? Asking for a friend.

Great synopsis of one of the greatest engines ever designed. Nothing like the sound of four merlin's at once. In this case Merlin 224's. Last October was fortunate enough to observe an engine runup aboard CWHM Lancaster Mk X.

For what it's worth and hoping I've have done the GMT math correctly here is a screen grab of the turnaround point and the appropriate SIG WXX chart. Certainly not the best predictor of potential CAT but it seems to be fairly benign wxx SW of HNL. Reports say the CAT was sudden and not anticipated I suppose wake turbulence from nearby aircraft will be investigated.

I know I may be contributing to the thread creep here but a couple of photos of the remains of L-188 CF-NAZ in the hanger in YSU and being loaded on to a Super Guppy for shipment to Van Nuys CA for fuselage splicing to be reborn as C-GNDZ. Photo credit unknown.

The Canadian Warplane Heritage Museum C-47 is a D-Day veteran and the museum is planning a formation flight On June 6 (12 noon) to commemorate the 75th Anniversary of D-Day, CWHM will fly three aircraft types that would have participated on D-Day – the C-47 Dakota, B-25 Mitchell and Avro Lancaster – in a formation flight over Hamilton and area. The museum C-47 FZ692 flew with 233 SQN in the late evening of 05 June 1944 and dropped paratroopers in drop zone DZ-N just NW of Toufreville France behind enemy lines. The pilot that night was W/O J.P.R. McCrae RCAF. 6 C-47 were dispatched that night from 233 SQN and 2 did not return KG556 and KG429. FZ692 was transferred to RCAF 437 SQN in September 1944 and has been restored presently to this paint scheme. She has flown 224 missions. Risky business indeed .

And it's Deja Vu all over again....again.... https://www.cbc.ca/news/business/air-canada-transat-1.5138180

It's Deja Vu all over a gain. Only thing missing is Nigel Wright....official ONEX presser.... https://ir.onex.com/static-files/92bfa37b-1bb4-4fc8-8f31-f6da878d1b05

From what I have seen on social media from Sully, Boeing will not be hiring him any time soon. The majority of the flying public probably have no idea what aircraft type they are flying in, let alone what model of the 737 their butts are in. What will be interesting to see for AC and WJ specifically is how passengers will react tactically when a/c swaps are performed on a daily/hourly basis. You board your flight, take a seat and suddenly realize you are on a MAX. Are you standing up and getting off the airplane (with or without your bag). Some properly placed PR will help but I have a feeling the $99 fare will fade peoples memories quickly.

Judging from the reactions of everyone on the ground the flight path looked erratic except for the two guys in the "pointy end".

Interesting analysis from former NTSB investigator Greg Feith from his FB page...... "The Report is published and provides a lot of detail about the flight including the fact that the crew experienced errant AOA and airspeed issues immediately after takeoff. This corroborates the scenario in my previous post, but more importantly supports the fact that the AOA fault initially experienced by the crew did not activate the MCAS because the flaps and slats were deployed. The report identifies a very good timeline of events, especially the flap retraction cycle, the operation of the stab trim and actions/inactions of the crew. In addition, the pilot engaged the autopilot which again would inhibit the MCAS. At least the story is becoming clearer and contradicts some of the “conclusions” presented in the Ethiopian report. Here are their conclusions: 2 INITIAL FINDINGS On the basis of the initial information gathered during the course of the investigation, the following facts have been determined: * The Aircraft possessed a valid certificate of airworthiness; *. The crew obtained the license and qualifications to conduct the flight; *. The takeoff roll appeared normal, including normal values of left and right angle-of-attack (AOA). *. Shortly after liftoff, the value of the left angle of attack sensor deviated from the right one and reached 74.5 degrees while the right angle of attack sensor value was 15.3 degrees; then after; the stick shaker activated and remained active until near the end of the flight. [GAF: MCAS INHIBITED] * After autopilot engagement, [GAF: MCAS INHIBITED] there were small amplitude roll oscillations accompanied by lateral acceleration, rudder oscillations and slight heading changes; these oscillations also continued after the autopilot disengaged. * After the autopilot disengaged, the DFDR recorded an automatic aircraft nose down (AND)trim command four times without pilot’s input. As a result, three motions of the stabilizer trim were recorded. The FDR data also indicated that the crew utilized the electric manual trim to counter the automatic AND input. [GAF: ELECTRIC MANUAL INPUT WOULD ONLY INTERRUPT THE MCAS TRIM COMMAND FOR 5 SECONDS] * The crew performed runaway stabilizer checklist and put the stab trim cutout switch to cutout position and confirmed that the manual trim operation was not working. [GAF: PROCEDURES DO NOT INSTRUCT REACTIVATING THE STAB TRIM] There are many questions yet to be answered but the primary question is what caused the fault with the AOA immediately after liftoff. This is key because it caused other issues during various phases of the climb including improperly activating the MCAS. Also the report does not address information about unreliable airspeed procedures which should be considered because they had erratic airspeed; and there is no information about the Autothrottle status - the FDR data appears to show the engines remained at a high power setting. More to come."

Here is a link to the preliminary report on ET302 https://www.flightradar24.com/blog/wp-content/uploads/2019/04/Preliminary-Report-ET302.pdf