What We Know About the FlyDubai Incident | The Captain & Kennedy Airshow

Overview

The broadcast covers two major aviation-related events:

1. A FlyDubai 737 Max cockpit attack, where the co-pilot allegedly stabbed the captain, plus discussion of how passengers responded and the terminology around “kidnapping” vs “hijacking.”
2. Commentary on the U.S. NTSB preliminary report regarding a Prime Air crash in Miami.

It also includes a long interview with Dan Millikan about aviation media and safety-focused reporting.

---

1) FlyDubai 737 Max incident: cockpit attack, “kidnapping” vs “hijacking,” and passenger heroics

Flight and timeline (as described)

• FlyDubai Flight 1073 (Dubai → Tel Aviv)
• Incident occurs about two hours into a ~three-hour flight.
• The co-pilot attacked the captain, described as a stabbing; whether it involved a knife is unclear.

Terminology debate: hijacking vs “kidnapping”

The presenters argue about what terms should mean:

• Many call it hijacking/kidnapping.
• The discussion reframes “kidnapping” as a scenario where the crew’s mission/control of the aircraft is forcibly taken from the intended operation.
• Importantly, this could occur behind cockpit doors rather than by someone physically outside the cockpit.

Key events in the narrative

• Passengers drag the attacking co-pilot out of his seat and take over control actions.
• After the co-pilot is removed, the aircraft begins an extremely rapid descent, described as:
  • ~17,000 feet in ~30 seconds
• Another passenger is said to counteract the descent by pulling the control stick back, helping avert a full disaster.
• Once the crew regains cockpit access, the aircraft is described as then landing successfully, characterized as smooth (based on channel host recollection and interviewee testimony).

Damage and controllability

• The broadcast emphasizes possible aircraft damage (e.g., rudder issues).
• Despite major stress and abnormal circumstances, the plane is described as remaining controllable.

Cockpit door access and lockdown mechanisms

The hosts speculate about how cockpit security design may have affected outcomes:

• Whether the cockpit door was locked with a password or only unlockable from inside.
• They suggest rapid access likely depended on the captain being able to open the door during the brief window available.

Weapon screening concerns

• A claim is included that Saudi authorities searched the aircraft but did not find the knife.
• The discussion speculates another object (e.g., an axe allegedly present in the cockpit) could have been used.

Safety and ethics framing

• The hosts strongly condemn stabbing the pilot.
• They caution against speculation about motives.
• They argue mental illness or irrationality could be involved, while stressing authorities should investigate rather than spectators “fill in reasons.”

---

2) Passenger action and “loss of trust” in cockpit authority

A major theme is that passengers quickly appear to have taken control and monitored crew behavior, implying a loss of trust in authority and rank after 9/11-era security changes.

The broadcast claims passengers organized their response by:

• Taking control in a structured way
• Assigning watchers over crew members as the situation unfolded

The presenters describe this as a broader shift: when something catastrophic happens mid-flight, passengers no longer simply wait for experts.

---

3) Prime Air (Miami) crash: Swiss-cheese failures, ATC wind reporting, and pilot mismanagement

This segment analyzes an NTSB preliminary report about a Prime Air crash in Miami (preliminary findings released quickly), focusing on procedural and human-factor errors.

ATC / wind information issues

• The controller allegedly failed to provide required wind direction information when a tailwind situation existed.
• The hosts link this to expected controller duties and referenced guidance, including the idea that wind direction must be reported when relevant to tailwind landing considerations.

Weather timing and ATIS

• Weather updates (METAR) and ATIS updates occurred.
• The discussion suggests the pilot/controller information flow may have been mishandled or not properly verified.

Pilot-side blame emphasized

Although controller responsibility is discussed, the hosts argue the majority of fault lies with the pilots, citing:

• Repeated failures to respond to electronic warnings
• Failures to attempt landing properly
• Details from the report such as:
  • Multiple unsuccessful approach/landing opportunities
  • A landing far down the runway, with gears touching and then leaving the runway
  • Problems involving configuration/logic switching (e.g., load/air-ground logic)
  • An attempted go-around near the runway end that did not proceed correctly

Safety philosophy: layered defenses

The hosts reiterate aviation safety principles:

• Don’t rely on a single system or checklist
• Use layered defenses

What the preliminary report can/can’t conclude

• They stress that the committee reports facts, not final causal certainty.
• The final report—expected months to years later—will determine responsibility and causation more definitively.

“What-if” considerations

• They entertain counterfactuals (e.g., whether detours or different piloting choices could have prevented the outcome),
• while emphasizing the cause is not conclusively established yet.

---

4) Interview: Dan Millikan on aviation media, safety-focused research, and dealing with uncertainty

The broadcast’s final portion is an in-depth interview with Dan Millikan from the Take-Off channel.

Dan’s background and approach

• He runs a film/video production company
• He became a pilot through FAA-related steps
• He trains/flys in fixed-wing, has expanded into helicopters
• He uses aviation research and interviews to explain complex systems

Fact-based reporting and verification

• He explains why he emphasizes separating fact from opinion
• Aviation incidents often trigger “why” speculation, but investigations take time
• He claims careful verification and responsiveness to errors, including that comment sections can correct mistakes

AI usage

• AI is described as useful but not fully trusted due to hallucinations and errors
• He emphasizes double-checking AI-generated content and replacing/adjusting it when errors are found

Media ecosystem critique

• He argues YouTube can accelerate rumor-like narratives and unverified conclusions compared with more formal media checks
• To maintain trust, he focuses on accuracy and corrections

Safety mission framing

• He argues reporting on tragedies should ultimately serve:
  • Education
  • Accident prevention
• Not sensationalism

---

Presenters / contributors

• Captain Steve (host)
• Kennedy Steve (co-host / co-presenter)
• Dan Millikan (guest; Take-Off channel)

Referenced individuals and context:

• Ofer Dubrovski (passenger interviewee referenced in the FlyDubai story)
• Schmidt (identified as the captain who opened the cockpit door; mentioned as needing recovery)
• NordVPN (sponsor; not part of the aviation arguments)