Log# 2019-0000065

This incident occurred on an unknown date in April or May 2017.


Documents