Before you view the video I should point out it is abundantly clear the SUV completely ignores the fact that they are driving across a runway.
The driver is not "driving across a runway". They are driving over an uncontrolled access road which is approximately 440ft from the marked (displaced) runway threshold. There were apparently warning signs, but no active control. You'd be relying on a person, who may or may not be an aviator, seeing and
possibly hearing an aircraft on final approach. In a car with a radio, aircon/fan, etc, it'd quite easily drown out the noise of a light piston on final with a low-ish power setting. On my way to and from work I drive under short final of a runway with heavy light piston use. You can't always hear them coming.
Northwest Regional Airport, Roanoke, Tx. RW "17" thresholdThe result: a poor student pilot gets caught in a bad situation.
I have a lot of sympathy for the pilot. Due to the direction the SUV was travelling, combined with a student pilot probably working quite hard an concentrating on the runway ahead, it would have been almost impossible to stop the collision as he'd have been unsighted of his 1-2 o'clock low viewpoint. But what he was doing at that height (440ft from the displaced threshold, about 40-50ft from the beginning of the runway surface)? That is another matter, and probably one that his flight school and the airport management will have to answer. Use the full length of the tarmac = close the road. Use the road = use a displaced threshold, or put traffic control lights on the road.
Easy to attempt to apportion blame, but it's not as clear cut as people think.
Looking at what has been reported, I suspect the majority of the fault will be held by the airport and school; those involved were potentially the victims of bad procedures, on the ground and in the air.