Manually-controlled barrier with obstacle detection level crossing on the North and East route (ELR HUL1).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:37 | 🚆 2R07 | York → Hull Down (W → E) | passed |
| 09:46 | 🚆 2R04 | Hull → York Up (E → W) | approaching |
| 09:46 | 🚄 1H01 | London Kings Cross → Hull Down (W → E) | approaching |
| 10:07 | 🚃 4D88 | Milford West Sidings → Hull Biomass LP (DBS) Down (W → E) | no show |
On today’s timetable, Melton Lane crossing is predicted to be closed for about 4 h 32 min between 06:00 and 22:00, across roughly 63 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: 7.1 min (07:07–07:14, 3 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 08:51–09:51 in the morning and around 20:43–21:43 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Gibson Lane South in Melton, East Riding of Yorkshire.
Melton Lane is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Goole–Hull Dairycoates Tlcn GBRf line (North and East route · ELR HUL1). 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 1,300 trains through this crossing.
99.9% of observed passes were being warned about on this page when they passed, and 99.4% of the warnings we could verify came true.
Typical timing error was ±10s (9 in 10 within 74s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.