The Flydubai Dive: Why the Numbers DON’T Add Up

The Flydubai flight data reported a climb of roughly 23,000 feet per minute, followed seconds later by a descent exceeding 24,000 feet per minute. Taken literally, those rapid changes imply extraordinary forces. Yet the aircraft landed. Do the strange numbers support a “false flag” theory—or reveal the limits of flight-tracking data? In this video, I examine the conflicting altitude and vertical-speed reports, explain how static-pressure disturbances and message timing could affect ADS-B readings, and assess the widely reported 3.08 G recovery estimate. We also look at the reporting surrounding two other Flydubai pilots and what it actually establishes about their involvement. We’ll cover: • Why reported altitude and vertical speed can contradict each other • How rudder inputs and yaw can affect air-data indications • Why a steep descent doesn’t necessarily mean extreme G forces • What the reported data gaps leave unanswered • The distinction between questioning, detention, and evidence of complicity The numbers can be wrong without the attack being fake. This analysis distinguishes reported information, estimates, and my own hypotheses. Public flight-tracking records are not a substitute for flight-recorder data or the findings of an official investigation. Reporting discussed is current through October 17, 2026. #Flydubai #Aviation #Boeing737MAX