After seeing tens of thousands of arrivals (and departures) on the arrival and departure radar and from the tower cab, it appears that the plane landed long and at rollout, there was insufficient runway left for a safe landing.
Or to attempt a go around.
That runway is equipped with ILS, at least until the aircraft mashed the antenna structure and the radio shack as it left the runway.
the Glideslope could be involved but from the news reports, it appears it was a VFR approach and not an IFR approach.
It was a VFR approach.
It appears to be pilot/s error but the NTSB will determine this.
It could be nothing else, even if there was equipment failure. The initial causing factor was bullheading to a landing despite high speed, poor configuration for landing, and landing too far down the runway either stop or get back in the air again.
The time to conduct the go around is BEFORE the wheels touch the ground.
Further, the glide slope indicator does not do anything to configure a plane properly for landing or slow the plane down to proper speed for a stable landing.
Planes using ILS go around all the time. Debris, another aircraft or animals on the runway when you break out, unstable approach speed or poor configuration for landing,
There are numerous reasons planes on an ILS approach will conduct a go around.
Indeed, on an ILS approach you should PLAN to go around, landing is only for when the shoot was good enough.
The same could be said for a visual (VFR) approach.
If you consider the go around the "normal" end of an approach, and the landing the "conditional" end, you will fly a lot safer.
In a jet aircraft it's even more important. Jet engines are at or near idle during approach. Spooling them up for the go around takes significant time. They aren't like reciprocating engines, where power is available almost immediately.
The NTSB full report will take about a year to conduct. They DID release the voice recorder and instrument recorder (which also records flight controls positions, brakes, spoiler position, reverser position, etc).
The plane was flying too fast on approach, even to the point of a sink warning being issued multiple times, followed by 'terrain' warnings. These only happen when the aircraft is NOT configured properly for landing, and/or descending too fast for a stable landing.
At the first 'sink' warning, a go around should have been initiated right then and there.
On the voice recorder, one pilot (probably the co-pilot) DID remark they were going too fast.
It is pilot error. Whether it is compounded with equipment failure (the wheel brakes were shown to be working already), it makes no difference. The pilot and only the pilot could have initiated this chain of events, and ONLY by not following correct landing procedure for that aircraft.
I hate to blame the guy, but it really couldn't have been anything else.