Manually-controlled barrier with obstacle detection level crossing on the East Midlands route (ELR SPD1).
| 01:15 | 4L20 | 🚛 | DONCIGB → FLXSSGB | → from Sleaford | -12 min |
| 01:18 | 6V85 | 🚛 | TINSLYY → ACTONTC | → from Sleaford | no show |
| 01:37 | 4E52 | 🚛 | WLSDEUT → HRTLPDF | ← from Peterborough North Yd GBRf | +4 min |
| 01:37 | 4E19 | 🚛 | THMSLGB → DONCIGB | ← from Peterborough North Yd GBRf | +15 min |
| 01:45 | 4L88 | 🚛 | LEEDFLT → THMSFLI | → from Sleaford | -8 min |
On today’s timetable, Church Lane crossing is predicted to be closed for about 2 h 9 min between 06:00 and 22:00, across roughly 31 closures. The longest single predicted closure is 7 minutes. Freight paths scheduled “as required” — most don’t run on any given day — aren’t counted here; when one does run, the live timeline above shows it.
Longest closure so far today: 3.9 min (00:19–00:23, 2 trains), timed from trains actually seen on the signalling wire — the window edges use the same per-type margins as the forecast, since barrier positions aren't in any feed we can read.
Closures cluster around 06:52–07:52 in the morning and around 16:59–17:59 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Church Lane is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Peterborough North Yd GBRf–Sleaford line (East Midlands route · ELR SPD1). An obstacle-detection system scans the crossing and confirms it is clear before the barriers lower automatically. Forecasts here combine the working timetable with live train-movement data (and live signalling where the crossing has it), so they reflect actual running including delays and freight — though they can still be wrong when the network is disrupted.
We score this page against what actually happened on the railway — over the last 7 days that covered 5 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 100.0% of the warnings we could verify came true.
Typical timing error was ±174s (9 in 10 within 687s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.