Well its all speculation but thats what we're here for so..lets start with what we know:
A/C had known UAS event day before but it was controlled by crew and they landed safely.It is written up and signed
off as cleared.
A/C takes off again next day and suffers another UAS event,this time proving unrecoverable.
Conclusion: diagnosis and/or rectification work by maintenance failed to clear problem or worse still exacerbated problem.
What else do we know?
Flightradar uses ADS-B and we have the readout showing unusually high speed after takeoff well
below 10000 feet(normal altitude for speed restriction).Its GPS derived and we can trust it.
We also know(using logic) that this is not what the flightcrew saw.They saw something entirely different.
What did they see?What would cause them to overspeed,climb erratically and eventually lose control?
They must have seen the direct opposite....low airspeed,stall warning,spurious windshear warning,stuck altimeters maybe etc
Now the flightcrew are aware of the previous UAS event and they have presumably briefed each other on what to do
following UAS after takeoff.They will presumably be alert to the possibility of UAS and have reviewed the QRH and
reiterated the importance of the 80knot call and the need to cross-check all 3 airspeeds.So which scenario would let them
get airborne with no indication of a pitot static fault on the takeoff roll?
Its not pitot but static...static vent blocked.Airspeed will indicate normally on takeoff but underread in climb.Altimeters will
remain stuck after takeoff.Its a nasty little scenario and could easily lead to confusion.The subsequent loss of control could be explained by the high speeds with flaps still down(crew distraction and onset of panic).
If it happens(altimeters dont show climb after liftoff,you get windshear warning(false) and.or stick shaker(false) you have to
climb to 1500' on RADIO ALTIMETER, level off, set 60% N1,ignore the warnings and LAND immediately,either visually or on vectors.