While the prop is, uh, properly a wing, and technically hitting something with it would interrupt the airflow, they're quite strong and would likely just destroy the object, slightly damaging the prop. If it did damage it beyond usability, it'd been way more obvious in the video and with the prop breaking off.
If you're talking about the aircraft stalling, then it's unlikely as we don't see that significant of a movement in the brief second of video. Under g-load (an "accelerated stall") the buffer between the onset of the stall and the stall itself is decreased, and as I said elsewhere that while I have no familiarity with the handling characteristics of that aircraft, there's simply doesn't look like enough time for a stall to develop between when the aircraft supposedly hit a drone and for-sure hit the other aircraft. And from what I could see, the movement doesn't at all look like a stall, and from the moment I saw the two aircraft in the video you can see the intercept occurring - that's likely harder for the unfamiliar to see being unfamiliar with the concept of two disparate turning circles crossing at a point in the future, differing because of bank angle (one or even both "circles - i.e. vectors - could even be straight lines) and because of differing speeds.
From the limited videos I've seen, one pilot could not, or simply did not, see the other aircraft, either because of the bank angle blocking the view or not realizing the aircraft was there and being focused elsewhere (such as the aircraft in from of them) and simply ran into the other aircraft. How they got into that position is the difficult investigation, and Juan's YouTube video pointed out that the sudden airborne airboss directive was to cross flight paths, when they didn't brief such and rather unlikely had ever practiced such, and may not have even realized such.
Something that many people do not understand is that an aircraft “stall” has nothing to do with the engine or propeller except possibly as a contributing factor.
A stall in aircraft parlance refers to a change in airflow over the wings or control surfaces that causes the sudden or progressive loss of aerodynamic lift. This is an effect caused by the surface moving through the air at an excessive angle, so that the air stops flowing smoothly over the lifting surface, instead breaking down into a chaotic flow.
Stalls typically happen at low speeds, where an aircraft is pitching up excessively, but can also happen at higher speeds in steep turns or other maneuvers where the g forces on an aircraft make the wings have to support multiple times their normal load.
A midair collision with a small object is unlikely to cause a stall, unless it were to provoke a secondary reaction by the pilot or the control surfaces directly.
Either way, in this case the aircraft in question had the bomber in a blind spot and probably could not see the danger of collision, and in fact may have been frantically looking for it, even lowering the nose to get better visibility, having lost sight of it in a slightly distracted moment.
AFAIK there is no evidence of any condition here aside from inadequate planning, inadequate separation, and pilot error.
As a pilot I am only too aware of the possibility for this kind of accident to occur when operating in the vicinity of other aircraft. It’s surprisingly easy to collide with other aircraft despite the huge amount of empty space lol around you.
It usually takes a few confounding factors to line up to cause disasters to occur in aviation… it’s almost never just one or two.
If anyone reading is interested in the various types of stalls and unusual attitude recoveries, you may be able to find a flight instructor at the nearest airport willing to take a flight and show you some.
Beware that it will count as flight instruction and you may end up hooked and forking out $20k for a private pilot license.
While the prop is, uh, properly a wing, and technically hitting something with it would interrupt the airflow, they're quite strong and would likely just destroy the object, slightly damaging the prop. If it did damage it beyond usability, it'd been way more obvious in the video and with the prop breaking off.
If you're talking about the aircraft stalling, then it's unlikely as we don't see that significant of a movement in the brief second of video. Under g-load (an "accelerated stall") the buffer between the onset of the stall and the stall itself is decreased, and as I said elsewhere that while I have no familiarity with the handling characteristics of that aircraft, there's simply doesn't look like enough time for a stall to develop between when the aircraft supposedly hit a drone and for-sure hit the other aircraft. And from what I could see, the movement doesn't at all look like a stall, and from the moment I saw the two aircraft in the video you can see the intercept occurring - that's likely harder for the unfamiliar to see being unfamiliar with the concept of two disparate turning circles crossing at a point in the future, differing because of bank angle (one or even both "circles - i.e. vectors - could even be straight lines) and because of differing speeds.
From the limited videos I've seen, one pilot could not, or simply did not, see the other aircraft, either because of the bank angle blocking the view or not realizing the aircraft was there and being focused elsewhere (such as the aircraft in from of them) and simply ran into the other aircraft. How they got into that position is the difficult investigation, and Juan's YouTube video pointed out that the sudden airborne airboss directive was to cross flight paths, when they didn't brief such and rather unlikely had ever practiced such, and may not have even realized such.