[StAnDeliver]

Putting together reports from Twitter: They took off normally, tried to get into their flight path, 180 turn back to airport, oddly did not attempt direct approach from the west after the 180, but instead flew the length of the airport to do a hard figure-8 to come back at the runway from the east (wtf), and obviously ran low on speed+altitude; then on approach at a near-impossible angle, dropped across a golf course short of the runway; skid-plowed across a two-lane road (there is video of the just-after on Twitter), through the airport fence and then finally where the jet came to a stop in the middle of the airport.

Ceilings were terrible, yet feels like pilot error.

[TangoLimaSierra]

...oddly did not attempt direct approach from the west after the 180...

Must have been a stiff wind. He flew to the other end to land against the wind like you should.
Landing from the west with a hard wind would make the runway too short.
Might have been hit with a micro burst.

[Paul R.]

Wind a factor? (I’m thinking that because earlier we had a tornado warning with a t-storm line coming through, wind here I’d guess at 60+ mph, and a brief but thoroughly intense “cloudburst” of rain. Power has been out but came back on about 10 minutes ago.)

[Nifty]

Looking at the log on FlightAware, the plane was all over the place. Started losing altitude barely a minute into the flight, speed up, slowed down, alt up, down,

https://www.flightaware.com/live/flight/N257BW/history/20251218/1400Z/KSVH/KSVH/tracklog