Bum numbers are regular visitors in FOQA data centres. I'm not sure how they sneak in but their certainly do. So when exceedences are flagged they have to viewed in context. Overspeeds for example. If aircraft cannot accelerate and decelerate in fractions of a second. Unless of course there was significant windsheer. The windsheer can be detected from ADC data. Without windsheer, the airspeed exceedence can be ignited. So what I'm saying is that the value of a single parameter is not significant for a short period of time and any exceedence has to be viewed in context.
In your case, a ROD in excess of 1,500 FPM so close to the ground would be a memorable event. So if that didn't happen, the questions have to be:
1. What was the airspeed before, during and after the event?
2. What was the thrust setting before, during and after the event?
3. Where you fully configured?
4. What data was used to calculate ROD? Baro or calculated radio closure rate? The latter can be affected by too many other factors.
5. Why didn't the EGPWS chime in?
6. What sort of approach? If it was an ILS, then providing the glideslope was maintained and the airspeed remained constant then the ROD would have to have been constant.
Take a calculator, pen and paper to the repay. You may well have to do some maths.
Best of luck.