Quickly exit this site by pressing the Escape key
Leave this site
Skip to main content
Skip to main navigation
This site is a beta, which means it's a work in progress and we'll be adding more to it over the next few weeks. Your feedback helps us make things better, so please let us know what you think.
Back to Report
Back to Tell us about
Back to Apply or register
Back to Request
Back to Thanks and complaints
The forensic results have come back
Update, 8 September
Forensic examination has concluded that a skull found in a duck pond in Louth is from the Roman period.
Our officers and a team of forensics attended the pond at Pear Tree Lane in Fulstow on 16 June following a report of a skull in a duck pond.
The skull was sent off for further examination. The results have now come back.
Detective Inspector Richard Nethercott said: “The results tell us that the remains are not modern, and it is likely that this individual was alive during the Roman period, between AD 276 and 342.
“I would like to thank everyone who assisted with the investigation and thank the person who reported this to us.”
The skull will be transferred to a local archaeologist.
Update, 20 June
Our officers remain at the location, and the cordon is expected to be lifted this evening.
We believe this maybe a human skull that has been at the site for many years, but we cannot confirm this until forensic examination has taken place. This can take several weeks.
Police officers and forensics are at the duck pond in Pear Tree Lane, Fulstow, following a report of a human skull being found by a member of the public.
Our force control room was called by a member of the public who reported that the bone was in the pond at around 12.37pm on Thursday 16 June.
We believe this may be a human skull, but this will be determined by an in-depth forensic examination of the skull which can take up to several weeks to complete.
The area has been cordoned off and we expect to remain in the area carrying out a full search over the weekend and into Monday.
We will release an update when one is available.
Incident 171 of 16 June
Is there a problem with this page?