Sorry, that doesn’t make much sense. They stalled while in the turn, somehow managed to complete the turn and fly straight on final, but stayed in the stall and did not recover for 700-800 feet down and a mile forward?
I don’t know where the idea of the base to final stall crept into the conversation (maybe based on incomplete flightaware data?), but the more complete ADS-B data doesn’t support that, nor does the NTSB saying the wreckage was located in the trees to the
left of the runway.
Here’s a pic that might help illustrate, the data pulled straight from ADS-B Exchange. Note there are
two finals. The signal is lost for both right about 100’ and the threshold (which is typical LOS blockage for the receivers that forward the data), so it doesn’t illustrate the events over or along the runway for either approach (this we can’t see the actual path of the crash). Both approaches were fairly steep, but pretty straight.
View attachment 133986
I added a blue arrow representing the general reported wind direction and an orange circle representing the trees adjacent to the left side of the runway into which the NTSB said the airplane crashed.
Note: the AWOS is located near the segmented circle on the west-southwest side of the runway, however a wind as reported from 170 true would be along the shown azimuth to the runway 21 threshold. There is a large clearing along that azimuth during short final, but the hill and the monument, then the stand of trees that begin complementary to that azimuth and the threshold could complicate an already gusty wind situation as you’re crossing the threshold.